Re: [FFmpeg-trac] #4437(avdevice:open): AVFoundation recording has consistent intermittent frame drops
#4437: AVFoundation recording has consistent intermittent frame drops -+- Reporter: LordHDL |Owner: mateo Type: defect | Status: open Priority: normal |Component: avdevice Version: git-master | Resolution: Keywords: | Blocked By: avfoundation bounty| Reproduced by developer: 0 Blocking: | Analyzed by developer: 0| -+- Comment (by thilo.borgmann): Unfortunately I will be offline for the whole weekend so maybe mateo can comment on how the patch work for him. If it just fixes an audio issue (got a ticket for that?), then it might help with that but does not fix this issue. Still I wonder if the FFmpeg side causes the frame drops or if we never come to see these frames and Apple drops them. I will also need some more time to review the patch on the ml. -- Ticket URL: https://trac.ffmpeg.org/ticket/4437#comment:24 FFmpeg https://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #3900(avformat:closed): ff_check_h264_startcode does not support 3-byte startcodes
#3900: ff_check_h264_startcode does not support 3-byte startcodes + Reporter: Lastique|Owner: Type: defect | Status: closed Priority: normal |Component: avformat Version: git-master | Resolution: fixed Keywords: h264 avi| Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | + Comment (by Lastique): Thanks. Did you not fix the similar problem for HEVC in check_hevc_startcode? -- Ticket URL: https://trac.ffmpeg.org/ticket/3900#comment:19 FFmpeg https://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #3900(avformat:closed): ff_check_h264_startcode does not support 3-byte startcodes
#3900: ff_check_h264_startcode does not support 3-byte startcodes + Reporter: Lastique|Owner: Type: defect | Status: closed Priority: normal |Component: avformat Version: git-master | Resolution: fixed Keywords: h264 avi| Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | + Changes (by cehoyos): * status: new = closed * resolution: = fixed Comment: It appears that I fixed this issue in 56ffde3f619076650bdc6003cc683cf2f563463f -- Ticket URL: https://trac.ffmpeg.org/ticket/3900#comment:18 FFmpeg https://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
[FFmpeg-trac] #4811(swscale:new): float pixel format support in libswscale
#4811: float pixel format support in libswscale ---+- Reporter: richardpl| Owner: Type: enhancement | Status: new Priority: normal | Component: swscale Version: git-master | Keywords: Blocked By: | Blocking: Reproduced by developer: 0| Analyzed by developer: 0 ---+- Summary of the bug: Float pixel format support in libswscale. -- Ticket URL: https://trac.ffmpeg.org/ticket/4811 FFmpeg https://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
[FFmpeg-trac] #4812(undetermined:new): scale filter does not apply pure range change
#4812: scale filter does not apply pure range change
-+-
Reporter: rmk | Type: defect
Status: new | Priority: normal
Component: | Version:
undetermined | unspecified
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0|
-+-
It appears the scale filter (or libswscale underneath) does not scale the
input if only the range (tv vs. pc) has to be changed.
Steps to reproduce:
1) Produce a file that contains tv range (16-235) luma values
{{{
ffmpeg -i ~/tmp/colortest/gradient-broadcast-range.mov -vf
scale=in_range=tv:out_range=pc -c:v ffv1 ~/tmp/colortest/tv-to-full.mov
ffmpeg version N-74650-ga16251a Copyright (c) 2000-2015 the FFmpeg
developers
built with Apple LLVM version 6.1.0 (clang-602.0.49) (based on LLVM
3.6.0svn)
configuration: --enable-gpl
libavutil 54. 31.100 / 54. 31.100
libavcodec 56. 58.100 / 56. 58.100
libavformat56. 40.101 / 56. 40.101
libavdevice56. 4.100 / 56. 4.100
libavfilter 5. 37.100 / 5. 37.100
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 2.101 / 1. 2.101
libpostproc53. 3.100 / 53. 3.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/Users/krueger/tmp/colortest
/gradient-broadcast-range.mov':
Metadata:
major_brand : qt
minor_version : 512
compatible_brands: qt
encoder : Lavf56.40.101
Duration: 00:00:00.04, start: 0.00, bitrate: 2628 kb/s
Stream #0:0(eng): Video: ffv1 (FFV1 / 0x31564646), yuv420p, 256x256,
2483 kb/s, 25 fps, 25 tbr, 12800 tbn, 12800 tbc (default)
Metadata:
handler_name: DataHandler
encoder : Lavc56.58.100 ffv1
[mov @ 0x7fea32013200] Using MS style video codec tag, the file may be
unplayable!
Output #0, mov, to '/Users/krueger/tmp/colortest/tv-to-full.mov':
Metadata:
major_brand : qt
minor_version : 512
compatible_brands: qt
encoder : Lavf56.40.101
Stream #0:0(eng): Video: ffv1, yuv420p, 256x256, q=2-31, 200 kb/s, 25
fps, 12800 tbn, 25 tbc (default)
Metadata:
handler_name: DataHandler
encoder : Lavc56.58.100 ffv1
Stream mapping:
Stream #0:0 - #0:0 (ffv1 (native) - ffv1 (native))
Press [q] to stop, [?] for help
frame=1 fps=0.0 q=-0.0 Lsize= 13kB time=00:00:00.04
bitrate=2628.6kbits/s
video:12kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB
muxing overhead: 5.846823%
}}}
2) Verify the range is correct
{{{
ffprobe -f lavfi movie=/Users/krueger/tmp/colortest/gradient-broadcast-
range.mov,signalstats -show_entries
frame_tags=lavfi.signalstats.YMAX,lavfi.signalstats.YMIN
ffprobe version N-74650-ga16251a Copyright (c) 2007-2015 the FFmpeg
developers
built with Apple LLVM version 6.1.0 (clang-602.0.49) (based on LLVM
3.6.0svn)
configuration: --enable-gpl
libavutil 54. 31.100 / 54. 31.100
libavcodec 56. 58.100 / 56. 58.100
libavformat56. 40.101 / 56. 40.101
libavdevice56. 4.100 / 56. 4.100
libavfilter 5. 37.100 / 5. 37.100
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 2.101 / 1. 2.101
libpostproc53. 3.100 / 53. 3.100
Input #0, lavfi, from 'movie=/Users/krueger/tmp/colortest/gradient-
broadcast-range.mov,signalstats':
Duration: N/A, start: 0.00, bitrate: N/A
Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 256x256
[SAR 1:1 DAR 1:1], 12800 tbr, 12800 tbn, 12800 tbc
[FRAME]
TAG:lavfi.signalstats.YMIN=16
TAG:lavfi.signalstats.YMAX=235
[/FRAME]
}}}
3) Attempt to scale this to full range
{{{
ffmpeg -i ~/tmp/colortest/gradient-broadcast-range.mov -vf
scale=in_range=tv:out_range=pc -c:v ffv1 -y ~/tmp/colortest/tv-to-full.mov
ffmpeg version N-74650-ga16251a Copyright (c) 2000-2015 the FFmpeg
developers
built with Apple LLVM version 6.1.0 (clang-602.0.49) (based on LLVM
3.6.0svn)
configuration: --enable-gpl
libavutil 54. 31.100 / 54. 31.100
libavcodec 56. 58.100 / 56. 58.100
libavformat56. 40.101 / 56. 40.101
libavdevice56. 4.100 / 56. 4.100
libavfilter 5. 37.100 / 5. 37.100
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 2.101 / 1. 2.101
libpostproc53. 3.100 / 53. 3.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/Users/krueger/tmp/colortest
/gradient-broadcast-range.mov':
Metadata:
major_brand : qt
minor_version : 512
compatible_brands: qt
encoder : Lavf56.40.101
Duration: 00:00:00.04, start: 0.00, bitrate: 190 kb/s
Stream #0:0(eng): Video: ffv1 (FFV1 / 0x31564646),
Re: [FFmpeg-trac] #4812(undetermined:new): scale filter does not apply pure range change
#4812: scale filter does not apply pure range change -+- Reporter: rmk |Owner: Type: defect | Status: new Priority: normal |Component: Version: unspecified | undetermined Keywords: | Resolution: Blocking: | Blocked By: Analyzed by developer: 0| Reproduced by developer: 0 -+- Comment (by cehoyos): Is there really a difference to ticket #4805? (Can one ticket be fixed without the other?) -- Ticket URL: https://trac.ffmpeg.org/ticket/4812#comment:1 FFmpeg https://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #4805(swscale:open): swscale does not process pixels when only color-matrix differs between input and output
#4805: swscale does not process pixels when only color-matrix differs between input and output +--- Reporter: rmk |Owner: Type: defect | Status: open Priority: normal |Component: swscale Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 0 | +--- Comment (by rmk): Created ticket 4812 for it. -- Ticket URL: https://trac.ffmpeg.org/ticket/4805#comment:7 FFmpeg https://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #4437(avdevice:open): AVFoundation recording has consistent intermittent frame drops
#4437: AVFoundation recording has consistent intermittent frame drops -+- Reporter: LordHDL |Owner: mateo Type: defect | Status: open Priority: normal |Component: avdevice Version: git-master | Resolution: Keywords: | Blocked By: avfoundation bounty| Reproduced by developer: 0 Blocking: | Analyzed by developer: 0| -+- Comment (by LordHDL): I'm hoping it's not a rooted issue in AV Foundation itself. As I said before, recordings in Windows do not exhibit the drops (on the same hardware). I know OS X is capable of perfectly smooth capture, as evidenced by the recording app ScreenFlow, so it's not a limitation of the OS so much as something janky in the software somewhere. The audio bug ticket is #4463. -- Ticket URL: https://trac.ffmpeg.org/ticket/4437#comment:25 FFmpeg https://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
Re: [FFmpeg-trac] #2891(undetermined:closed): 2013-Autumn'llogampng (was: 2013 Autumn Website Art Contest)
#2891: 2013-Autumn'llogampng -+- Reporter: beastd |Owner: Type: art | Status: closed Priority: minor|Component: Version: unspecified | undetermined Keywords: | Resolution: completed Blocking: | (art) Analyzed by developer: 1| Blocked By: | Reproduced by developer: 1 -+- Changes (by oily): * analyzed: 0 = 1 * cc: oily.myfanta@… (added) * reproduced: 0 = 1 -- Ticket URL: https://trac.ffmpeg.org/ticket/2891#comment:4 FFmpeg https://ffmpeg.org FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://ffmpeg.org/mailman/listinfo/ffmpeg-trac
