Do you think if it will be possible to add an option for the audio decoder to process the data in certain order? Or even add a filter thru the command line? I wonder why -af format=s16le doesnt work for me..<br><br>Ratin<br>
<br><div class="gmail_quote">On Thu, Mar 20, 2008 at 11:40 PM, Ratin <<a href="mailto:ratin3@gmail.com" target="_blank">ratin3@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><p>From: Ross Finlayson <<a href="mailto:finlayson@live555.com" target="_blank">finlayson@live555.com</a>><br>
To: LIVE555 Streaming Media - development & use <<a href="mailto:live-devel@ns.live555.com" target="_blank">live-devel@ns.live555.com</a>><br>
Date: Wed, 19 Mar 2008 23:18:49 -0700<br>Subject: Re: [Live-devel] live 555 rtsp library for mplayer<br>>>When you stream audio over live-555's RTSP plugin on mplayer, what<br>>>decides the<br>>>audio data to be big endian vs little endian?</p>
<p>>16-bit PCM audio data - when streamed using RTP using an<br>>IETF-standard RTP payload format - is *always* in Big Endian order<br>>(called "Network Byte Order" in the RFCs). That's the standard[*].</p>
Do you think if it will be possible to add an option for the audio
decoder to process the data in certain order? Or even add a filter thru
the command line? I wonder why -af format=s16le doesnt work for me..</blockquote><div><br>Thanks, <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
Ratin<br><br></blockquote></div><br>