[issue2583] Unable to play some relative applehttp streams from NRJ France
Martin Storsjö mar...@martin.st added the comment: Quite close, but not exactly. The code tried to open /apple/nrj/nrjlive-1/nrjurbanhi/Seg_012111_024157_518/nrjurbanhi_012111_024157_103658.ts as a local file name instead of keeping the server name but stripping the rest of the URL. The attached patch should solve the issue. FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2583 0001-applehttp-Handle-absolute-paths-relative-to-the-curr.patch Description: Binary data
[issue2585] Error when execute ffmpeg
New submission from comicway c...@labomatik.com: After compile FFMEG on ARM NAS, i've got an error on ffmpeg execution: ./ffmpeg: /usr/lib/libavdevice.so.52: no version information available (required by ./ffmpeg) ./ffmpeg: /usr/lib/libavcodec.so.52: no version information available (required by ./ffmpeg) ./ffmpeg: /usr/lib/libavformat.so.52: no version information available (required by ./ffmpeg) FFmpeg version git-a9d921c, Copyright (c) 2000-2011 the FFmpeg developers built on Feb 3 2011 21:07:57 with gcc 4.2.3 configuration: --enable-libtheora --enable-libvorbis --disable-static --enable-shared ./ffmpeg: relocation error: ./ffmpeg: symbol avcodec_configuration, version LIBAVCODEC_52 not defined in file libavcodec.so.52 with link time reference -- messages: 13606 priority: normal status: new substatus: new title: Error when execute ffmpeg type: bug FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2585
[issue2359] -aspect 16:9 flag and -vf aspect=16:9 don't work
scheutzo mike.scheut...@alcatel-lucent.com added the comment: Attach my patch to fix this bug. It appears the git repo is going to solve this with a different approach. FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2359 0001-Fix-issue2359-ffmpeg-aspect-16-9-doesn-t-work.patch Description: Binary data
[issue2556] Can't detect AC3 stream properly in WTV
Justin Ruggles justin.rugg...@gmail.com added the comment: Our wtv demuxer isn't handling something correctly. There seem to be 2 streams with the same stream id of 267. The first is AC-3, and it uses a stream2 GUID. The second is MP2, and it uses a stream GUID. The 2nd seems to be overriding the first, which then is possibly filtering out the data based on the index of the MP2 stream? or maybe there is a data2 chuck type we're not detecting? I don't know... but there is definitely AC-3 in the file. -- status: new - open substatus: new - reproduced topic: +avformat FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2556
[issue2556] Can't detect AC3 stream properly in WTV
Justin Ruggles justin.rugg...@gmail.com added the comment: It seems that the mp2 and ac3 are interleaved in the same stream, with each packet having an mp2 frame concatenated with an ac3 frame. Our demuxer skips the ac3 frames. The data for ac3 is using stream id 266, but that is not detected in the stream setup. Both are detected as 267 for some reason... -- substatus: reproduced - analyzed FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2556
[issue2556] Can't detect AC3 stream properly in WTV
Justin Ruggles justin.rugg...@gmail.com added the comment: I mean... they're not interleaved in the same stream. they have 2 separate stream id's (266 267) but the setup is not detecting the AC3 as a separate stream id. they're both detected as 267 and the mp2 info overrides the ac3 info. the ac3 data is skipped due to the data stream id (266) not matching anything from the stream setup. Hope that explains it... now to find the fix... FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2556
[issue2556] Can't detect AC3 stream properly in WTV
Justin Ruggles justin.rugg...@gmail.com added the comment: I have a fix. I'll send it to ffmpeg-devel after a bit more testing. Basically, stream2_guid chunks can initialize new streams as well. Existing demuxer only parses stream2_guid info if the stream already exists but no data has been read for it. FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2556
[issue2583] Unable to play some relative applehttp streams from NRJ France
Martin Storsjö mar...@martin.st added the comment: Applied in git://git.ffmpeg.org/ffmpeg.git now. FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2583
[issue2583] Unable to play some relative applehttp streams from NRJ France
Ronald S. Bultje rsbul...@gmail.com added the comment: Closing... -- status: new - closed substatus: new - fixed FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2583
[issue2583] Unable to play some relative applehttp streams from NRJ France
Kyle kyl...@aol.com added the comment: It's now working with similar relative streams too, thanks for the quick fix. FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2583
[issue2556] Can't detect AC3 stream properly in WTV
Justin Ruggles justin.rugg...@gmail.com added the comment: Out of the 3 samples streams (this one + 2 in mphq samples), all of them have extra streams using other stream ids that are skipped because they're initialized with stream2_guid, not stream_guid. But this is the only sample of the 3 that actually sends data chunks for one of the other sid's. It seems pointless to initialize the others and never have them used, especially since they may come before the primary stream(s). Maybe there is a flag somewhere that says whether there will be data sent for this stream? Or maybe it's just setting up multiple TV channels then switching between them by sending data chunks with those sids? I can't think of a good solution. Sometimes there are even data chunks sent with silence. For example, the Law+and+Order-+SVU_Five_2008_08_12_23_36_55.wtv sample has many sid's but data is only sent for 4: subtitle, stereo audio, video, and mono audio. The mono audio is valid mp2, but it's just silence... The silent one is initialized with stream2_guid. But in the case of this AC3 sample, it is also initialized with stream2_guid, data chunks are sent for it, and it doesn't contain silence, but rather a 5.1 version of the primary stereo mp2 audio stream. FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2556
[issue2586] Unable to play applehttp streams that have EXT-X-KEY
New submission from Kyle kyl...@aol.com: ffmpeg is unable to handle applehttp streams that use EXT-X-KEY with the following line in the .m3u8 file: #EXT-X-KEY:METHOD=AES-128,URI=http://servername/keys/station/.key; Unfortunately since the stream belongs to a paid app I cannot provide the real url in the open, but I can confirm that the urls work when entered directly on the browser of my iPod Touch 2G and upon request I can provide a clone sample of the .ts, .key and .m3u8 files on another server or send you a zipped clone that you can use for testing. ffmpeg output with debug level logging: ffmpeg -i http://servername/station/***.m3u8 -loglevel=verbose FFmpeg version git-185a155, Copyright (c) 2000-2011 the FFmpeg developers built on Feb 4 2011 12:33:47 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 libavutil50. 37. 0 / 50. 37. 0 libavcore 0. 16. 1 / 0. 16. 1 libavcodec 52.109. 0 / 52.109. 0 libavformat 52. 96. 0 / 52. 96. 0 libavdevice 52. 2. 3 / 52. 2. 3 libavfilter 1. 74. 0 / 1. 74. 0 libswscale0. 12. 0 / 0. 12. 0 libpostproc 51. 2. 0 / 51. 2. 0 http://servername/station/***.m3u8: Invalid data found when processing input -- messages: 13616 priority: normal status: new substatus: new title: Unable to play applehttp streams that have EXT-X-KEY type: bug FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2586
[issue2556] Can't detect AC3 stream properly in WTV
Justin Ruggles justin.rugg...@gmail.com added the comment: Actually the stereo mp2 stream seems to be descriptive audio for the visually impaired, while the ac3 stream is the main program. FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/issue2556
