January 2015 - FFmpeg-trac - lists.ffmpeg.org

Re: [FFmpeg-trac] #1333(avformat:closed): Seeking in voc
by FFmpeg 10 Jan '15

10 Jan '15

#1333: Seeking in voc -------------------------------------+------------------------------------ Reporter: cehoyos | Owner: Type: enhancement | Status: closed Priority: wish | Component: avformat Version: git-master | Resolution: fixed Keywords: voc roundup | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+------------------------------------ Changes (by michael): * status: new => closed * resolution: => fixed Comment: Fixed in c8f83a4c78e429ebd6184e5cd663fdf65c48b9cc -- Ticket URL: <https://trac.ffmpeg.org/ticket/1333#comment:3> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

Re: [FFmpeg-trac] #1092(avcodec:closed): amv: gray bar at the bottom
by FFmpeg 10 Jan '15

10 Jan '15

#1092: amv: gray bar at the bottom -------------------------------------+----------------------------------- Reporter: ami_stuff | Owner: Type: enhancement | Status: closed Priority: wish | Component: avcodec Version: git-master | Resolution: fixed Keywords: amv mjpeg | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Changes (by michael): * status: open => closed * resolution: => fixed Comment: I dont see an issue remaining (-strict -1 is needed to encode non mod 16), decode works with a warning but no gray bar and no crashes so iam closing this as fixed, if its not fixed please reopen -- Ticket URL: <https://trac.ffmpeg.org/ticket/1092#comment:7> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

#4240(ffmpeg:new): Add iPad Air 2 10bit
by FFmpeg 10 Jan '15

10 Jan '15

#4240: Add iPad Air 2 10bit -------------------------------------+------------------------------------- Reporter: Muscleping | Type: Status: new | enhancement Component: ffmpeg | Priority: normal Keywords: | Version: Blocking: | unspecified Analyzed by developer: 0 | Blocked By: | Reproduced by developer: 0 -------------------------------------+------------------------------------- Summary of the bug: How to reproduce: {{{ % ffmpeg -i input ... output ffmpeg version built on ... }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. Optimized 10bit playback 1080p iPad Air 2 new GPU!!! -- Ticket URL: <https://trac.ffmpeg.org/ticket/4240> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#4247(undetermined:new): AAC bitstream not in ADTS format and extradata missing [mpegts]
by FFmpeg 10 Jan '15

10 Jan '15

#4247: AAC bitstream not in ADTS format and extradata missing [mpegts] -------------------------------------+------------------------------------- Reporter: BlackDream | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- {{{ ffmpeg -re -y -i "STREAM_URL" -c copy -f mpegts /tmp/test.ts ffmpeg version 2.5.3 Copyright (c) 2000-2015 the FFmpeg developers built on Jan 10 2015 08:04:28 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1) configuration: --prefix=/root/ffmpeg/target --extra- cflags='-I/root/ffmpeg/target/include -static' --extra- ldflags='-L/root/ffmpeg/target/lib -lm -static' --disable-debug --disable- shared --enable-static --extra-cflags=--static --disable-ffplay --disable- ffserver --disable-doc --enable-openssl --enable-gpl --enable-pthreads --enable-postproc --enable-libass --enable-gray --enable-runtime-cpudetect --enable-libfaac --enable-gnutls --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-bzlib --enable-zlib --enable-nonfree --enable-version3 --enable- libvpx --enable-libxavs --disable-devices --enable-librtmp --extra- libs='-lrtmp -lnettle -lhogweed -lgmp -lssl -lcrypto -lz -lc -ldl' libavutil 54. 15.100 / 54. 15.100 libavcodec 56. 13.100 / 56. 13.100 libavformat 56. 15.102 / 56. 15.102 libavdevice 56. 3.100 / 56. 3.100 libavfilter 5. 2.103 / 5. 2.103 libswscale 3. 1.101 / 3. 1.101 libswresample 1. 1.100 / 1. 1.100 libpostproc 53. 3.100 / 53. 3.100 Input #0, mpegts, from '{STREAM_URL}': Duration: N/A, start: 9619.031478, bitrate: 89 kb/s Program 1 Metadata: service_name : rik2 service_provider: IPTV Stream #0:0[0x100]: Video: h264 (Main) ([27][0][0][0] / 0x001B), yuv420p, 720x576 [SAR 64:45 DAR 16:9], 50 fps, 25 tbr, 90k tbn, 100 tbc Stream #0:1[0x101]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 48000 Hz, stereo, fltp, 89 kb/s Output #0, mpegts, to '/tmp/test.ts': Metadata: encoder : Lavf56.15.102 Stream #0:0: Video: h264 ([27][0][0][0] / 0x001B), yuv420p, 720x576 [SAR 64:45 DAR 16:9], q=2-31, 50 fps, 90k tbn, 50 tbc Stream #0:1: Audio: aac ([15][0][0][0] / 0x000F), 48000 Hz, stereo, 89 kb/s Stream mapping: Stream #0:0 -> #0:0 (copy) Stream #0:1 -> #0:1 (copy) Press [q] to stop, [?] for help [mpegts @ 0x37aade0] PES packet size mismatchme=00:00:49.89 bitrate= 634.9kbits/s [mpegts @ 0x37d0c20] AAC bitstream not in ADTS format and extradata missing av_interleaved_write_frame(): Invalid data found when processing input frame= 1101 fps= 22 q=-1.0 Lsize= 3915kB time=00:00:50.09 bitrate= 640.3kbits/s video:2934kB audio:557kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 12.153324% Conversion failed! }}} '''It must be mention that exactly the same stream in FFmpeg 2.4.x branch works PERFECTLY''' so it must be a bug. I think it has to do something with this ticket i created as well ( https://trac.ffmpeg.org/ticket/4243 ) When i get that error PES Packet size mismatch always a problem appears whereas in FFmpeg 2.4.x there wasn't any problem with this nor with the stream i'm testing as well. '''IMPORTANT NOTE 1''' It appears that '''''WITHOUT -re argument i don't get this error'''''. -- Ticket URL: <https://trac.ffmpeg.org/ticket/4247> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

#4245(undetermined:new): Lida Daidaihua Products Cleanse EFX
by FFmpeg 10 Jan '15

10 Jan '15

#4245: Lida Daidaihua Products Cleanse EFX -------------------------------------+------------------------------------- Reporter: LieseAudel | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- There are several individuals that mortal actually used the wraps and obtained instant results [http://www.healthcaresup.com/cleanse-efx/ Cleanse EFX]you too can buy pleasance in the benefits though you must eff that this method present not get rid of sufficiency fats to represent you retrograde a few pounds, it is just good in eliminating a two of inches of fat from a confident portion of the body, not for head embody metric eduction.You can do gone along with all these, and change a smoother, finer and healthier tegument within a mates of life making use of embody wraps. In this post, I bonk investigated and instrument prophesy you on the pros of body wraps. Embody wraps mortal actually changed over the life. Originally, they were made use of as a fast way to temporarily. http://www.healthcaresup.com/cleanse-efx/ -- Ticket URL: <https://trac.ffmpeg.org/ticket/4245> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#4241(undetermined:new): Tenorshare violates the license
by FFmpeg 09 Jan '15

09 Jan '15

#4241: Tenorshare violates the license -------------------------------------+------------------------------------- Reporter: llogan | Owner: Type: license | Status: new violation | Component: Priority: normal | undetermined Version: | Keywords: unspecified | Blocking: Blocked By: | Analyzed by developer: 0 Reproduced by developer: 0 | -------------------------------------+------------------------------------- Distributes the libraries compiled with `--enable-gpl --enable-nonfree`. {{{ $ md5sum tenorshare-video-converter-for-mac-trial.dmg 93d4c8125850b9ac30406c9b764c27e4 tenorshare-video-converter-for-mac- trial.dmg }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/4241> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

Re: [FFmpeg-trac] #3085(avcodec:open): Audio in broken transport stream can be decoded with other software
by FFmpeg 09 Jan '15

09 Jan '15

#3085: Audio in broken transport stream can be decoded with other software -------------------------------------+----------------------------------- Reporter: ramitbhalla | Owner: Type: enhancement | Status: open Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: mpegts aac | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+----------------------------------- Comment (by jave): Hi I have probably similar problem with Lumia 635 video ffmpeg -v ffmpeg version 1.2.6 Copyright (c) 2000-2014 the FFmpeg developers built on Jan 8 2015 21:15:44 with gcc 4.7.3 (Gentoo 4.7.3-r1 p1.4, pie-0.5.5) configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --mandir=/usr/share/man --enable-shared --cc=x86_64-pc-linux-gnu-gcc --cxx=x86_64-pc-linux-gnu-g++ --ar=x86_64-pc-linux-gnu-ar --optflags='-march=core2 -O2 -pipe -fomit-frame-pointer' --extra- cflags='-march=core2 -O2 -pipe -fomit-frame-pointer' --extra- cxxflags='-march=core2 -O2 -pipe -fomit-frame-pointer' --disable-static --enable-gpl --enable-postproc --enable-avfilter --enable-avresample --disable-stripping --enable-version3 --enable-nonfree --disable-indev=oss --disable-indev=jack --disable-outdev=oss --enable-version3 --enable-bzlib --disable-runtime-cpudetect --disable-debug --disable-doc --disable-gnutls --enable-hardcoded-tables --enable-iconv --enable-network --disable- openssl --enable-ffplay --disable-vaapi --enable-vdpau --enable-zlib --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libmp3lame --disable-libfdk-aac --disable-libaacplus --enable-libfaac --disable- libtheora --enable-libtwolame --enable-libx264 --enable-lib libavutil 52. 18.100 / 52. 18.100 libavcodec 54. 92.100 / 54. 92.100 libavformat 54. 63.104 / 54. 63.104 libavdevice 54. 3.103 / 54. 3.103 libavfilter 3. 42.103 / 3. 42.103 libswscale 2. 2.100 / 2. 2.100 libswresample 0. 17.102 / 0. 17.102 libpostproc 52. 2.100 / 52. 2.100 Video file snippet stored: http://uloz.to/xSv8YVbB/eepou7uofeng4xei-mp4 (for english switch web interface to ENG by UK flag in right top corner) -- Ticket URL: <https://trac.ffmpeg.org/ticket/3085#comment:29> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

#3405(undetermined:new): Bizare behaviour with RTP mpegts sources,
by FFmpeg 09 Jan '15

09 Jan '15

#3405: Bizare behaviour with RTP mpegts sources, -------------------------------------+------------------------------------- Reporter: sharbatgula | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: RTP, | Blocked By: mpegts, source mix-up | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: Hi, I'm transcoding a bunch of SD sources from SPTS mpegts transported on different multicast addresses with RTP on port 5530. (VBR h264 video, mp2 audio) When I transcode the first source from mcast IP1:5530 the output is sort of OK (occasional green patches and false reporting of unsupported source features) Once I run a second ffmpeg instance to transcode source IP2:5530 the second instance is not ingesting IP2 content but IP1 and both instances start to interfere and they don't even come to a state to start transcoding. It's bizare that even two ffplay instances tuned to different sources play back the same content! I tried playing back with vlc and there is no such problem. {{{ % ffmpeg -y -f mpegts -i rtp://@239.2.2.22:5530 -threads 0 -acodec libfdk_aac -ab 64k -ar 44100 -vcodec libx264 -vprofile baseline -vlevel 1.3 -x264opts fps=25:keyint=100:bitrate=200 -s 320x240 -f mpegts udp://224.10.2.3:5004?pkt_size=1316 I uploaded a sample of my mpegts on: ftp://upload.ffmpeg.org/MPlayer/incoming/ts__sample.ts ffmpeg version 2.1.git built on Jan 30 2014 12:22:30 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5) }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/3405> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 9

#4199(build system:new): When omitting '--shlibdir=' for configure, SHLIBDIR expands to $DESTDIR$DESTDIR...
by FFmpeg 09 Jan '15

09 Jan '15

#4199: When omitting '--shlibdir=' for configure, SHLIBDIR expands to $DESTDIR$DESTDIR... -------------------------------------+------------------------------------- Reporter: | Type: defect friedinsugar | Priority: important Status: new | Version: git- Component: build | master system | Blocked By: Keywords: | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: In the generated config.mak, SHLIBDIR expands to $(DESTDIR)$(DESTDIR)... How to reproduce: Run configure without '--shlibdir=' Possible cause of bug: the following line in the 'configure' file: shlibdir_default='${LIBDIR}' should be instead shlibdir_default='${libdir_default}' but I need a second opinion. -- Ticket URL: <https://trac.ffmpeg.org/ticket/4199> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 8

Re: [FFmpeg-trac] #964(avformat:closed): No h263 Mode B support?
by FFmpeg 07 Jan '15

07 Jan '15

#964: No h263 Mode B support? ------------------------------------+------------------------------------ Reporter: walker | Owner: Type: defect | Status: closed Priority: normal | Component: avformat Version: git-master | Resolution: fixed Keywords: h263 | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | ------------------------------------+------------------------------------ Changes (by thovo): * status: open => closed * resolution: => fixed Comment: The cmd line "ffmpeg -i demo.h263 demo.mp4" instructs ffmpeg to assume plain H.263 as input format (not H.263+RTP). Hence, the output of this conversion will always look corrupted. The current RTP packetizer for H.263 also supports the desired additional modes. So, the ticket can be closed as "fixed". -- Ticket URL: <https://trac.ffmpeg.org/ticket/964#comment:6> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0