-
Notifications
You must be signed in to change notification settings - Fork 1.7k
h264 video file crash video playback capabilities until next reboot. #549
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
Comments
Admittedly I'm running a debug firmware build, but it's not crashing my build. There are a few asserts firing though, and the output isn't useful (mainly green). Looking at the file, avprobe describes it as: |
The codec only supports 4:2:0 video (or monochrome); theoretically we could support (and may or may not have written the code for -- I forget) 4:4:4 with separate planes, but I don't think the rest of the system would understand it... This is a hardware limitation. Having said this, the codec certainly shouldn't crash if presented with this; it just won't produce any output. |
Thank for all the info. |
As deborah-c has confirmed, the hardware does not support High 4:2:2 Profile. I can take a look as to why it crashes, but you will never be able to play that file on a Pi. @deborah-c Where would that profile be signaled? Just from header bytes with profile_idc==122 by the looks of it. dec_requirements the right place to throw the error? |
Jun 10 2015 20:42:58 |
That image is 9 months out of date, so things may well have been improved to not crash, even if we don't just throw the clip out as unsupported. |
… a size error firmware: image_fx: Avoid setting the vpitch for YUVUV buffers firmware: image_fx: Add YUVUV as supported type firmware: image_fx: relax check on inout/output formats to support standalone deinterlace firmware: h264_parse: Silently discard macroblocks with unsupported profile See: #549 userland: MMAL_VC_SHM: Explicitly lock buffer when requested See: raspberrypi/userland@dd9636d userland: khronos: Use vchiq_get_client_id to determine global PID See: raspberrypi/userland#315 userland: various warning fixes
… a size error firmware: image_fx: Avoid setting the vpitch for YUVUV buffers firmware: image_fx: Add YUVUV as supported type firmware: image_fx: relax check on inout/output formats to support standalone deinterlace firmware: h264_parse: Silently discard macroblocks with unsupported profile See: raspberrypi/firmware#549 userland: MMAL_VC_SHM: Explicitly lock buffer when requested See: raspberrypi/userland@dd9636d userland: khronos: Use vchiq_get_client_id to determine global PID See: raspberrypi/userland#315 userland: various warning fixes
@fredericofs latest rpi-update firmware will now avoid decoding formats it knows aren't supported. |
… a size error firmware: image_fx: Avoid setting the vpitch for YUVUV buffers firmware: image_fx: Add YUVUV as supported type firmware: image_fx: relax check on inout/output formats to support standalone deinterlace firmware: h264_parse: Silently discard macroblocks with unsupported profile See: raspberrypi#549 userland: MMAL_VC_SHM: Explicitly lock buffer when requested See: raspberrypi/userland@dd9636d userland: khronos: Use vchiq_get_client_id to determine global PID See: raspberrypi/userland#315 userland: various warning fixes
Hello, this raw h264 video file makes hello_video.bin crash.
https://www.dropbox.com/s/uwiml8iddp625a2/crashvideo.h264?dl=0
After any attempt to play this video, no other video can be played. Including any good .mp4 video with omxplayer, or good raw .h264 with hello_video.bin
The system is not crashed after the attempt.. The command prompt is working and other process can be started including the loading of images with FBI. But video playback capabilities are gone, system wide, until the next reboot.
The video plays fine in on desktop computer with MPV player.
What could it be?
The text was updated successfully, but these errors were encountered: