[FFmpeg-user] Problem with decoding an MP3 stream introduced after April 6th

dvlpr volodomanov at gmail.com
Fri Apr 19 09:53:29 CEST 2013

Carl Eugen Hoyos wrote
> In the past, ffmpeg used a ffmpeg-specific user agent 
> when opening http streams, it now uses a common string 
> to allow access to http servers that expect a "normal" 
> browser.
> Workaround is to use:
> $ ffmpeg -user-agent something_random -i http://radio.retro-retro.ru
> See ticket #2265 for a similar (Google-) page that 
> also behaves strangely, unfortunately in the 
> opposite way.

Thank you - that works. I saw that change, but would've never guessed that
the server would fail to reply without a user-agent.


View this message in context: http://ffmpeg-users.933282.n4.nabble.com/Problem-with-decoding-an-MP3-stream-introduced-after-April-6th-tp4658580p4658588.html
Sent from the FFmpeg-users mailing list archive at Nabble.com.

More information about the ffmpeg-user mailing list