-
Notifications
You must be signed in to change notification settings - Fork 136
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
[BUG] CDG files fail to play to completion in latest bookworm pi release #323
Comments
I seem to have better luck with the non rp3 version of 5.1.4: Edit: song seems to get further but still terminates after 2m (the rpt3 version terminates at 40s). When hosting on the pi and running splash screen on another machine, the song completes. |
This also fails on RPi 5 with bookworm, with both rpt3 and deb12u1 versions of ffmpeg 5.1.4. When running with "./pikaraoke -l 0" for debug-output I got the following output:
Where the following lines seems to be the suspect:
Found the following after some searching: https://forums.raspberrypi.com/viewtopic.php?t=364180 Line 382 in 0741c2c
To read:
And that worked :) |
I've been trying to play with your software inside a docker container I made. I can't get anything to play (CDG or Youtube) through any browser. It displays the up next notification but no audio plays. The only error it seems to throw is that it's just killing the ffmpeg process. The same happens for YT videos, they download but don't play. I also tried modifying that default_vcodec line in the post above mine but that didn't work either.
|
This doesn't sound related to the issue as described in this ticket. You may want to see this ticket on docker. There is some stuff that needs to happen to enable the multiple ports on which pikaraoke operates |
I'm running bullseye, with a fresh install, and I get the same problem on RP3. What do I need to do to get things working on RP3/Bullseye? Previously this setup was working, but something must have changed. |
I have a branch with extra logging, seeing some h264_v4l2m2m errors every time the file terminates early, which are:
|
This appears to be some regressions to h264_v4l2m2m encoding, but only for cdg files. It appears as though these conversions are exhausting the GPU memory. However, non-CDG transcoding is ok. Luckily, it seems like falling back to non-hardware accelerated h264 encoding is fine for CDG, it's not very demanding on the CPU. I will do some testing on pi3 add this fix if it can keep up. |
Fixed in #351 |
Describe the bug
In the latest bookworm release, cdg files will play for a couple of seconds, then terminate early. This is NOT reproducible on bullseye. I imagine that other transcoded files such as avi, mpeg, mkv will experience the same.
For now please use Bullseye
To Reproduce
Install a fresh bookworm image, install pikaraoke. Add CDG files and try to play them.
Platform (please complete the following information):
Additional context
Looks like bookworm installs
ffmpeg version 5.1.4-0+rpt3+deb12u1
while bullseye installsffmpeg version 4.3.6-0+deb11u1+rpt5
so that might be the major difference.Discovered in #317
Seeing this in the ffmpeg log when this issue occurs. I believe the GPU is running out of memory while converting CDG:
The text was updated successfully, but these errors were encountered: