Closed hmelder closed 3 months ago
This is hopefully better when using a Magewell capture card.
This occurs when the input at the camlink changes. Instead of retrieving the new metadata and sending a RECONFIGURE event down the pipeline, an error is produced which in the end results in an eos.
I need to investigate this further.
This is now supported via automatic pipeline restarts. The restart is scheduled on the runloop after receiving an EOS from the affected pipeline.
If the restart was not successful (-[VMPPipelineManager start] returning NO), a new attempt is rescheduled with an increasing delay (up to 30s max).
The camlink capture card is a bit flaky when it comes to online resolution changes. I experience EOS events when tapping into the card with the v4l2src element which uses the v4l2 subsystem.