[FFmpeg-user] importing rtp packet stream and decoding
daveh at beachdognet.com
Fri Sep 22 22:41:50 EEST 2017
>> Sorry, my bad — I was able to fix that error — which was a simple typo in my command that led to a blank output url.
>> With that fixed, I get further:
Now I have figured out why the audio sounded like crap. The problem was that ffmpeg was treating the input stream as pcma, when it in fact was pcmu.
The issue is that the SDP indicated that the audio endpoint was able to receive _either_ pcmu or pcma — both were in the SDP, as follows:
o=root 2116403914 2116403914 IN IP4 126.96.36.199
c=IN IP4 127.0.0.1
m=audio 40558 RTP/AVP 0 8 101
a=silenceSupp:off - - - -
However, the rtp stream contained only PCMU audio. The payload type of 0 in the RTP header should have clued ffmpeg in that this was PCMU, as per the SDP. Yet ffmpeg logged out that it was PCMA and transcoded it as such, incorrectly.
This seems like a bug to me, should I recreate on HEAD and open a ticket somewhere?
I’m still wondering about to sync my sending side with ffmpeg being ready to receive, and also if lengthier decodes are expected when using rtp vs file
More information about the ffmpeg-user