RTP streaming @25 fps failing - how do I get better trace?
Posted: 21 Aug 2013 22:38
I'm creating streams using a few different input sources and streaming with RTP. I get great results with my 29.97 fps content. When I try to play PAL content at 25 fps, I get the popup saying "VLC does not support the audio or video format "h264"".
Looking at the message log ends up with this message:
avcodec error: cannot open codec (H264 - MPEG-4 AVC (part 10))
The first 30 lines of the message log are identical for my successful (29.97 fps) and fail (25fps) attempts, with the first difference of note being the line shown above.
I see the same results whether I am unicasting RTP directly to my Windows player or am reflecting it from the RTSP server (Darwin 5.5.5).
These same streams bundled up in an MPEG-TS stream play just fine - and the SPS and PPS values in the MPEG-TS stream are identical to those in the SDP file for the RTP streams.
The 25 fps streams play in QT player, but they seem to have some issues there as well.
What this all leads up is this: I'd like to get trace from ffmpeg telling me why it can't start - or perhaps it is live555 that is having the trouble. How can I capture some additional debug output from ffmpeg, libavcodec, and others? I see a clue for ffmpeg in that I can set a debug mask, but I have not seen that actually do anything.
- Mark
Looking at the message log ends up with this message:
avcodec error: cannot open codec (H264 - MPEG-4 AVC (part 10))
The first 30 lines of the message log are identical for my successful (29.97 fps) and fail (25fps) attempts, with the first difference of note being the line shown above.
I see the same results whether I am unicasting RTP directly to my Windows player or am reflecting it from the RTSP server (Darwin 5.5.5).
These same streams bundled up in an MPEG-TS stream play just fine - and the SPS and PPS values in the MPEG-TS stream are identical to those in the SDP file for the RTP streams.
The 25 fps streams play in QT player, but they seem to have some issues there as well.
What this all leads up is this: I'd like to get trace from ffmpeg telling me why it can't start - or perhaps it is live555 that is having the trouble. How can I capture some additional debug output from ffmpeg, libavcodec, and others? I see a clue for ffmpeg in that I can set a debug mask, but I have not seen that actually do anything.
- Mark