0

Concerning Gstream state changes, we should send a event when the pipeline is working correctly (Stream OK) and when there is an error we should send another event (Stream Error).

Catching errors over the message callback works, but we don't know which state indicate that the full pipeline is working correctly (from src to sync).

dandan78
  • 13,328
  • 13
  • 64
  • 78
Christoph Acs
  • 68
  • 1
  • 10
  • I'don't know the complete answer but this may give a starting point. Whenever I have a problem with the pipeline I receive error indicating it is having problems setting state to `PAUSED`. – Alper Kucukkomurler May 09 '17 at 09:12

1 Answers1

1

There is no specific error state in GStreamer (GStreamer states are: NULL, READY, PAUSED, PLAYING (*)). Thus, you need to watch and check if any error occurs. You should check, at least:

  • the return value of the function for changing the state (gst_element_set_state)
  • if any error message is sent to the bus:

    Errors can be received by listening to the GstBus of the element/pipeline for GstMessage objects with the type GST_MESSAGE_ERROR or GST_MESSAGE_WARNING. The thrown errors should be inspected, and filtered if appropriate.

(*) Note: actually, the complete list of states in the API includes also a pending state that may be relevant in some cases (see e.g. How to resume playing after paused using gstreamer?)

Community
  • 1
  • 1
airos
  • 742
  • 5
  • 14