NS_E_CANNOT_GENERATE_BROADCAST_INFO_FOR

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

It is not possible to generate the stream format file if you are using quality-based VBR encoding for the audio or video stream. Instead use the Windows Media file generated after encoding to create the announcement file.%0

Previous	Next
NS_E_INVALID_SOURCE_WITH_DEVICE_CONTROL	NS_E_EXCEED_MAX_DRM_PROFILE_LIMIT

NS_E_CANNOT_GENERATE_BROADCAST_INFO_FOR_QUALITYVBR

Where the Encoder produces this result

0xC00D1BDF (NS_E_CANNOT_GENERATE_BROADCAST_INFO_FOR_QUALITYVBR) identifies announcement or stream-format generation cannot represent quality-based VBR output before encoding. This is an Encoder validation error; a later “cannot start encoding” dialog can hide the original HRESULT.

The Encoder can expose an HTTP broadcast and can push to Windows Media Services. Packet sizing, publishing-point data and announcement generation are output-distribution concerns, separate from source capture and codec selection.

What has already succeeded

A stream can encode correctly to a file yet fail distribution because the broadcast sink or announcement metadata cannot represent the selected profile. For example, automation requests broadcast metadata from a quality-VBR profile with no fixed stream rate. Reproduce the condition at the Encoder object that returned the HRESULT rather than treating it as a general codec or operating-system failure.

A controlled diagnostic sequence

Record 0xC00D1BDF, the Encoder version and the exact API call or property access that returned it.
Export the current .wme or .prx configuration, then capture VBR mode, profile streams and requested.nsc/.asx operation.
Verify the broadcast and packet-output setup precondition without changing the source, profile and output sink at the same time.
Run one controlled comparison that changes only the identified precondition: encode the file first and derive announcement information from the completed output, or use a compatible rate mode.

Nearby HRESULTs that mean something else

Result	Why it differs
`NS_E_INVALIDPACKETSIZE`	validation of the configured maximum packet size for encoded output

Corrective action at the right layer

Do not change the source and codec while testing a distribution-only failure; first prove that the same profile writes a local file and preserve the output configuration.

Technical references

Looking for a different code? Search another status or error code.