Live UDP streams crash due to ffmpeg av_read_frame() returning -5 (i/o error) about omxplayer HOT 6 CLOSED

I see this as well on 7-8 Mb h.264 streams - after about 5-8 seconds. If you use the 'overrun_nonfatal=1' parameter omxplayer will show significant artifacting from the overrun but not exit; it will continue and stabilize so the stream plays clean after that initial corruption.
Also make sure you have the right balance of GPU/CPU memory allocation. I run 128MB for the GPU and it handles an ~8Mbit h.264 stream at 1080i just fine. Lower GPU memory it will choke.

from omxplayer.

Thanks!
Where are you putting that parameter?

from omxplayer.

It's an ffmpeg parameter, you add it on to the UDP URL like this:
omxplayer 'udp://@239.10.1.1:1234?overrun_nonfatal=1'

from omxplayer.

Thanks again, it works :)

How high of a bit rate seems to work for you?

from omxplayer.

I've done h.264 1080i up to 12 Mbit and h.264 24p up to about 15Mbit, mpeg2 up to 17Mbit, haven't ever tried to find the limit - I've been focused on ironing out other problems.

from omxplayer.

For me I can get 18Mbps 1080p30 mostly stable, but 20Mbps isn't. Seems like ARM is the limiting factor though, so probably could be pushed higher. Not sure why it is busy anyway, gpu should be doing all the work.

from omxplayer.