New submission from Kyle <[email protected]>: I think liquidcompass made some changes to their servers because many of their windows media streams are now unplayable with ffplay while mplayer, who I believe uses libmms, can handle them.
url: mmsh://wmc1.den.liquidcompass.net/KTXXFM output: ffprobe mmsh://wmc1.den.liquidcompass.net/KTXXFM -loglevel 99 FFprobe version git-8032d1d, Copyright (c) 2007-2011 the FFmpeg developers built on Jan 16 2011 13:46:12 with gcc 4.4.5 configuration: --prefix=/usr --enable-gpl --enable-version3 --enable-nonfree --enable-shared --enable-postproc --enable-libx264 --enable-frei0r --enable-librtmp --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libdc1394 --enable-libmp3lame --enable-libtheora --enable-libopenjpeg --enable-libdirac --enable-libvpx --enable-libgsm --enable-libschroedinger --enable-libspeex --enable-libvorbis --enable-libxvid --enable-libfaac --cpu=amdfam10 --arch=x86_64 --enable-x11grab --enable-libxavs --enable-libnut libavutil 50.36. 0 / 50.36. 0 libavcore 0.16. 1 / 0.16. 1 libavcodec 52.108. 0 / 52.108. 0 libavformat 52.93. 0 / 52.93. 0 libavdevice 52. 2. 3 / 52. 2. 3 libavfilter 1.74. 0 / 1.74. 0 libswscale 0.12. 0 / 0.12. 0 libpostproc 51. 2. 0 / 51. 2. 0 Recv asf header data len -104 != expected len 2595 Get http header data failed! mmsh://wmc1.den.liquidcompass.net/KTXXFM: Input/output error ---------- messages: 13479 priority: normal status: new substatus: open title: ffplay unable to handle liquidcompass mmsh type: bug ________________________________________________ FFmpeg issue tracker <[email protected]> <https://roundup.ffmpeg.org/issue2557> ________________________________________________
