Site icon EfmSoft

What does HRESULT 0xC00D1B60 (NS_E_CANNOT_DELETE_ACTIVE_SOURCEGROUP) mean?

 
Previous Next
NS_E_MISMATCHED_MEDIACONTENT NS_E_AUDIODEVICE_BUSY

NS_E_CANNOT_DELETE_ACTIVE_SOURCEGROUP

Diagnostic meaning beyond the standard text

For NS_E_CANNOT_DELETE_ACTIVE_SOURCEGROUP (0xC00D1B60), the actionable event is removal of the source group currently active in the running encoder graph.

Why the session can reach this point

WMEncoder exposes configuration, preparation, running, paused, stopped and archival states. Properties that alter graph topology are normally set before Start, while statistics and some control operations are meaningful only after a session reaches the matching state.

The same method can be valid in one encoder state and rejected in another without any file, codec or network defect. One concrete way to reach the condition is that cleanup code removes all source groups while one is still supplying a broadcast.

Decision path

  1. Record 0xC00D1B60, the Encoder version and the exact API call or property access that returned it.
  2. Export the current .wme or .prx configuration, then capture active source-group identity, RunState and the caller that attempted collection removal.
  3. Verify the encoder state-machine sequencing precondition without changing the source, profile and output sink at the same time.
  4. Run one controlled comparison that changes only the identified precondition: activate another prepared group or stop the encoder before removing the active group.

Codes with similar symptoms but different owners

ResultWhy it differs
NS_E_INVALIDCALL_WHILE_ENCODER_RUNNINGattempt to change a topology-affecting property after WMEncoder.Start
NS_E_NO_ACTIVE_SOURCEGROUPan operation that requires SourceGroupCollection.Active when no group is selected
NS_E_INVALIDCALL_WHILE_ARCHIVAL_RUNNINGattempt to alter archive configuration while the archive sink is active

Safe recovery

Activate another prepared group or stop the encoder before removing the active group.

Do not hide the ordering problem behind unconditional retries; log the transition sequence and make the operation occur at the documented lifecycle point.

Source material


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

Exit mobile version