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

Remove OMX and MMAL from ARM builds #77

Merged
merged 4 commits into from
Dec 31, 2021
Merged

Remove OMX and MMAL from ARM builds #77

merged 4 commits into from
Dec 31, 2021

Conversation

ferferga
Copy link
Member

@ferferga ferferga commented Nov 16, 2021

For 10.8, I think we should remove all of the Pi-specific hardware acceleration stuff: it never worked properly (besides a very specific configuration set) and it's better to integrate something that truly works fine instead of the patchwork that current MMAL and OMX is.

Raspberry Pi development is transitioning towards V4L2 for hardware decoding/encoding and MMAL/OMX are in a deprecation path. They also only worked properly in Raspbian Stretch and Pi3 devices, other configurations produced mixed results. Right now, in Bullseye, ffmpeg and ffprobe doesn't start at all.

With this patch, Pis will do software encoding/decoding (which is what most people ended using up anyway) until there's a better hardware acceleration path in the future.

Fixes jellyfin/jellyfin#32 jellyfin/jellyfin#75

@ferferga ferferga added the bug Something isn't working label Nov 16, 2021
@nyanmisaka
Copy link
Member

+1 for this. Link to the issue #310

@ferferga
Copy link
Member Author

jellyfin/jellyfin#29 has useful resources as well

Copy link
Member

@nyanmisaka nyanmisaka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LTGM

error: RPC failed; curl 56 GnuTLS recv error (-54): Error in the pull function.
fatal: the remote end hung up unexpectedly
fatal: early EOF

Copy link
Member

@joshuaboniface joshuaboniface left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM aside from the mentioned comment.

debian/changelog Show resolved Hide resolved
@nyanmisaka
Copy link
Member

The github server seems to be unstable these days.
Is there a better way to make git retry after losing the connection?

@ferferga
Copy link
Member Author

ferferga commented Dec 27, 2021

@nyanmisaka Thats what I'm trying to fix with the latest commits, but I think it's a bug in the git installed, not 100% related to GitHub (which also plays a role as some of these repos clone rather slow).

@ferferga
Copy link
Member Author

@nyanmisaka Checks are passing now, stretch is failing for a completely different reason. Probably jellyfin/jellyfin#65 ? First checks with fails in that strecth suite comes from that merge

@nyanmisaka
Copy link
Member

LTO is not supported in old GCC. We should retire stretch.

@Shadowghost
Copy link
Contributor

I'm all in for deprecating Debian stretch. We should only support Debian stable and oldstable imo (same for the other packages).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants