Skip to content

RasPiOS “Bullseye” support via cvlc#135

Draft
PaintYourDragon wants to merge 25 commits intomasterfrom
pb-bullseye
Draft

RasPiOS “Bullseye” support via cvlc#135
PaintYourDragon wants to merge 25 commits intomasterfrom
pb-bullseye

Conversation

@PaintYourDragon
Copy link

Installer now detects the OS version and takes a different path if Bullseye or later. omxplayer and hello_video are no longer supported in the new OS, so cvlc is used there instead, along with some required device tree overlay shenanigans. The older lightweight players can still be used by installing on an earlier OS, if hardware supports it.

@PaintYourDragon PaintYourDragon marked this pull request as draft December 29, 2021 01:15
@PaintYourDragon
Copy link
Author

Huh, I’d been distracted and didn’t notice the release of the “Legacy” Raspberry Pi OS among canonical downloads, which includes omxplayer and allows hello_video to build and run, even on Pi 4.

Reading their blog post about this…at some point, Legacy will eventually go Bullseye-based…so it’s probably wise to continue with vlc as the more future-proof option, keeping it in the installer and so forth.

But the good news is, even without merging the PR with the new stuff, I can go ahead and update the guide and just tell them to install the Legacy option. When vlc feels robust enough and this gets merged, I can update with the Legacy vs non-Legacy differences.

@tofuSCHNITZEL
Copy link
Collaborator

no worries - I think using/including a player that is in active dev and support is generally a good idea ;) even if it can't loop as seamless as omx. but people that need this specific requirement will always be able to download an old image that supports omx. so I would vote for keeping it included in the videolooper code as long as possible.

I will go ahead and try to port as many settings as possible from omx to vlc.

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