Skip to content

Conversation

@ylatuya
Copy link
Contributor

@ylatuya ylatuya commented Dec 10, 2025

Add a new GStreamer runner to launch pipelines that gives use more control in errors and allow us to differentiate for example between a pipelines miss-configuration or a format that's not supported.

This a first iteration in order to support #319

Add a new GStreamer runner to launch pipelines that gives use more
control in errors and allow us to differentiate for example between a
pipelines miss-configuration or a format that's not supported.
@dabrain34
Copy link
Contributor

dabrain34 commented Dec 10, 2025

I would put the gstreamer cffi in decoders as it should be not located in fluster base. IMHO fluster is GStreamer agnostic.

@ylatuya
Copy link
Contributor Author

ylatuya commented Dec 10, 2025

I would put the gstreamer cffi in decoders as it should not be located in the fluster base. IMHO, fluster is GStreamer agnostic.

The fluster.gstreamer namespace contains generic helpers around GStreamer that are not specific to decoders, that's why I decided to leave them under fluster.gstreamer instead of fluster.decoders.gstreamer. They can be used by a GStreamer decoder or a future GStreamer encoder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants