Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

encoder: output: Fix bug where network output was not routed through … #636

Merged
merged 1 commit into from
Jan 30, 2024

Conversation

naushir
Copy link
Collaborator

@naushir naushir commented Jan 30, 2024

…libav on Pi 5

If the --codec libav option is not set, and a network stream output is specified, the NetOutput class will be initialised together with libav and fail to work on a Pi 5.

Fix this by ensuring if we are going to use libav, do not initialise the NetOutput class, and allow libav to handle the network output.

@naushir naushir requested a review from davidplowman January 30, 2024 09:27
@davidplowman
Copy link
Collaborator

LGTM (assuming we don't care about the test failure)!

I suppose the more fundamental issue is that we used to use the "codec" to tell if we were using libav or not, but now that's no longer the case. Now we're using "is the h/w codec available", though I wonder slightly whether we'd do better to have an explicit and distinct "I'm using libav" flag somewhere. But that's only me thinking out loud for the slightly longer term, I'm happy to merge!

…libav on Pi 5

If the --codec libav option is not set, and a network stream output is
specified, the NetOutput class will be initialised together with libav
and fail to work on a Pi 5.

Fix this by ensuring if we are going to use libav, do not initialise the
NetOutput class, and allow libav to handle the network output.

Signed-off-by: Naushir Patuck <[email protected]>
@naushir naushir merged commit 9ae39f8 into main Jan 30, 2024
10 checks passed
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.

2 participants