Re: [FFmpeg-trac] #9846(avcodec:open): DNxHR doesn't work with LB in Shutter Encoder

2025-09-11 Thread FFmpeg
ed by developer: 0| -+- Comment (by slenk): I just experienced the same error with some of my own footage: {{{ ↳ ffprobe ../1_RAWS/2025-07-25\ 20-03-49.mkv ffprobe version 8.0 Copyright (c) 2007-2025 the F

Re: [FFmpeg-trac] #11651(ffprobe:open): NULL Pointer Dereference in FFmpeg ffprobe

2025-09-11 Thread FFmpeg
#11651: NULL Pointer Dereference in FFmpeg ffprobe -+- Reporter: momo-trip|Owner: (none) Type: defect | Status: open Priority

Re: [FFmpeg-trac] #9861(undetermined:closed): Cannot open hevc mp4 file that was saved by ffmpeg itself

2025-09-11 Thread FFmpeg
#9861: Cannot open hevc mp4 file that was saved by ffmpeg itself -+- Reporter: chao |Owner: (none) Type: defect | Status: closed

Re: [FFmpeg-trac] #8515(avcodec:closed): vc1_parser erroneously flagged every packet as keyframe

2025-09-10 Thread FFmpeg
fixed: fbbb2996d573844a2f4c901b704d8361a384766b -- Ticket URL: <https://trac.ffmpeg.org/ticket/8515#comment:8> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmpeg-trac To

Re: [FFmpeg-trac] #11240(tools:closed): [Windows] Non-ASCII characters in "FFREPORT" may produce garbled filename or fail

2025-09-10 Thread FFmpeg
* status: open => closed Comment: In [changeset:"2a1d5dd720fcaecd9272b5dafdf40a301868f85d/ffmpeg" 2a1d5dd7/ffmpeg]: {{{#!CommitTicketReference repository="ffmpeg" revision="2a1d5dd720fcaecd9272b5dafdf40a301868f85d" fftools: use fopen_utf8 to open FFREPOR

Re: [FFmpeg-trac] #9357(avformat:new): HLS live seek support

2025-09-10 Thread FFmpeg
. Check this for example https://ertflix.akamaized.net/ertlive/ert1/clrdef24723b/index.m3u8 which has about 4 hours segments that you could seek. Can't see this with mpv. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9357#comment:2> FFmpeg <https://ffmpeg.org> FFm

Re: [FFmpeg-trac] #8054(avcodec:open): prores_ks codec does not allow 12bit pix_fmt

2025-09-09 Thread FFmpeg
| --+--- Comment (by rgr): As far as I'm concerned, prores_ks generates _only_ 12-bit video ( and xq), even if ffmpeg claims to generate yuv444p10. https://code.ffmpeg.org/FFmpeg/FFmpeg/issues/20468 -- Ticket URL: &

Re: [FFmpeg-trac] #11215(avcodec:open): AAC USAC Mps212 support

2025-09-08 Thread FFmpeg
| -+- Comment (by alexanderino): Replying to [comment:10 Artem S. Tashkinov]: > Patches or funding :-) ''*cries*'' -- Ticket URL: <https://trac.ffmpeg.org/ticket/11215#comment:11> FFmpeg <

Re: [FFmpeg-trac] #10608(avcodec:new): AV1 decoder gets "Static surface pool size exceeded" issue with "-hwaccel d3d11va"

2025-09-08 Thread FFmpeg
6DZHjCZHXS3ePZryKQbq/view?usp=sharing -- Ticket URL: <https://trac.ffmpeg.org/ticket/10608#comment:2> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ff

Re: [FFmpeg-trac] #11215(avcodec:open): AAC USAC Mps212 support

2025-09-08 Thread FFmpeg
| -+- Comment (by Artem S. Tashkinov): Replying to [comment:9 alexanderino]: > Please let me know if anything is required. Patches or funding :-) -- Ticket URL: <https://trac.ffmpeg.org/ticket/11215#comment:10&g

Re: [FFmpeg-trac] #11215(avcodec:open): AAC USAC Mps212 support

2025-09-08 Thread FFmpeg
| -+- Changes (by alexanderino): * cc: alexanderino (added) Comment: Hi all, the latest ffmpeg master [2025-09-07] fails spectacularly when attempting to decode a USAC + SBR + PS file. Please check this pastebin log

Re: [FFmpeg-trac] #10608(avcodec:new): AV1 decoder gets "Static surface pool size exceeded" issue with "-hwaccel d3d11va"

2025-09-07 Thread FFmpeg
Blocking: | Reproduced by developer: 0 Analyzed by developer: 0| -+- Comment (by SuRGeoNix): It seems that the initial_pool_size of the hardware frames must be + 1 (or even more? in my case -nvidia ffmpeg

Re: [FFmpeg-trac] #11240(tools:open): [Windows] Non-ASCII characters in "FFREPORT" may produce garbled filename or fail

2025-09-07 Thread FFmpeg
Blocking: | Reproduced by developer: 0 Analyzed by developer: 0| -+- Comment (by MasterQuestionable): ͏    Didn't notice any apparent patch..? ͏    Try submit a clear one? ͏    https://code.ffmpeg.org/FFmp

Re: [FFmpeg-trac] #6023(avcodec:open): support Transfer characteristic in DPX encoder

2025-09-07 Thread FFmpeg
| -+- Comment (by Balling): Mostly fixed in 16d32a1c1d040d1b444ec476901d7458e1620301, except for printing density -- Ticket URL: <https://trac.ffmpeg.org/ticket/6023#comment:5> FFmpeg <https://ffmpeg.org> FFmpeg i

Re: [FFmpeg-trac] #9201(undetermined:reopened): -c:v mpeg2video ignoring -qmin+qmax

2025-09-06 Thread FFmpeg
d the film: {{{ffmpeg -i "Alice_in_Wonderland_(1903).ogv" -c:v mpeg2video -b:v 1024k -maxrate:v 1575k -bufsize:v 921.6k -qmin:v 4 -qmax:v 20 -an alice.mkv}}} The resulting output will show the non-working qmin/qmax problem: {{{ Stream #0:0: Video: mpeg2video (Main) (mpg2 / 0x3267

Re: [FFmpeg-trac] #8738(avfilter:open): subtitle filter can't render indic languages

2025-09-06 Thread FFmpeg
ed by developer: 0| -+- Comment (by Balling): https://github.com/harfbuzz/harfbuzz/issues/3487 is now fixed btw -- Ticket URL: <https://trac.ffmpeg.org/ticket/8738#comment:13> FFmpeg <https://ffmpeg.org

Re: [FFmpeg-trac] #11497(avfilter:new): channelsplit regression: no longer supports custom channel_layouts ("Query format failed for 'Parsed_channelsplit_0': Invalid argument")

2025-09-06 Thread FFmpeg
ll facing this issue. Can anyone acknowledge if this is a bug or whether I'm using it wrong? -- Ticket URL: <https://trac.ffmpeg.org/ticket/11497#comment:2> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker ___________ FFmpeg-trac mailing list FFmpeg-t

Re: [FFmpeg-trac] #9201(undetermined:reopened): -c:v mpeg2video ignoring -qmin+qmax

2025-09-04 Thread FFmpeg
: | Reproduced by developer: 0 Analyzed by developer: 0| -+- Comment (by IvanDSM): I'm having this issue with both FFmpeg 7.1.1-5 and the latest BtbN auto build as of writing (2025-09-04 14:22, ffmpeg-N-1

Re: [FFmpeg-trac] #10722(avcodec:new): Build failure with librsvg older than 2.52

2025-09-04 Thread FFmpeg
| -+--- Comment (by Leo Izen): Fixed by 9ee7796c540ce9cec3fdff0dd246de842228707b -- Ticket URL: <https://trac.ffmpeg.org/ticket/10722#comment:1> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker __

Re: [FFmpeg-trac] #10722(avcodec:closed): Build failure with librsvg older than 2.52

2025-09-04 Thread FFmpeg
Analyzed by developer: 0| -+- Changes (by Leo Izen ): * owner: (none) => Leo Izen Comment: In [changeset:"9ee7796c540ce9cec3fdff0dd246de842228707b/ffmpeg" 9ee7796c/ffmpeg]: {{{#!CommitTi

Re: [FFmpeg-trac] #10722(avcodec:closed): Build failure with librsvg older than 2.52

2025-09-04 Thread FFmpeg
| -+--- Changes (by Leo Izen): * resolution: => fixed * status: new => closed -- Ticket URL: <https://trac.ffmpeg.org/ticket/10722#comment:2> FFmpeg <https://ffmpeg.org> FF

Re: [FFmpeg-trac] #10834(undetermined:closed): ffmpeg does not gracefully stops when receiving SIGTERM

2025-09-02 Thread FFmpeg
#10834: ffmpeg does not gracefully stops when receiving SIGTERM -+- Reporter: razvan |Owner: Michael | Niedermayer Type: defect

Re: [FFmpeg-trac] #11600(undetermined:closed): Ffprobe/Ffmpeg with libfdk-aac doesn't recognize AAC-HE(v2) livestreams

2025-09-02 Thread FFmpeg
#11600: Ffprobe/Ffmpeg with libfdk-aac doesn't recognize AAC-HE(v2) livestreams -+- Reporter: Radu |Owner: Michael Motrescu | Nieder

Re: [FFmpeg-trac] #11240(tools:open): [Windows] Non-ASCII characters in "FFREPORT" may produce garbled filename or fail

2025-08-31 Thread FFmpeg
Blocking: | Reproduced by developer: 0 Analyzed by developer: 0| -+- Comment (by m.feriati): hello, any updates to share ? -- Ticket URL: <https://trac.ffmpeg.org/ticket/11240#comment:14> FFmpeg <https://ffmpe

Re: [FFmpeg-trac] #11649(ffmpeg:closed): -noautorotate -display_rotation 0 passes through rotation metadata with JPEG inputs

2025-08-26 Thread FFmpeg
: closed Priority: important |Component: ffmpeg Version: git-master | Resolution: fixed Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by

Re: [FFmpeg-trac] #10834(undetermined:new): ffmpeg does not gracefully stops when receiving SIGTERM

2025-08-25 Thread FFmpeg
#10834: ffmpeg does not gracefully stops when receiving SIGTERM -+- Reporter: razvan |Owner: (none) Type: defect | Status: new

Re: [FFmpeg-trac] #11604(ffmpeg:new): Infinite loop filter does not shutdown gracefully on SIGTERM

2025-08-25 Thread FFmpeg
: normal |Component: ffmpeg Version: 7.1 | Resolution: Keywords: loop| Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0

Re: [FFmpeg-trac] #11479(avcodec:new): Segfault with LTO - MacOS M4

2025-08-24 Thread FFmpeg
probe" Current executable set to '/Volumes/External/ffmpeg- builder/gitignore/darwin_sysroot/bin/ffprobe' (arm64). (lldb) settings set -- target.run-args "test.mkv" (lldb) r Process 88020 launched: '/Volumes/External/ffmpeg- builder/gitignore/darwin_sysroot/bi

Re: [FFmpeg-trac] #7965(avcodec:closed): Support for HEVC with Alpha

2025-08-23 Thread FFmpeg
| -+--- Changes (by quinkblack): * resolution: => fixed * status: open => closed Comment: Both decoding and encoding are supported now by FFmpeg 8.0 -- Ticket URL: <https://trac.ffmpeg.org/ticket/7965#comment:21> FFmpeg <https://ffm

Re: [FFmpeg-trac] #7756(avcodec:new): add mastering display color volume and content light level information to hevc_metadata bitstream filter

2025-08-22 Thread FFmpeg
docs.io/en/master/cli.html#cmdoption-master- display|documentation]] {{{ ffmpeg -i input.hevc -c copy -bsf:v "hevc_metadata=max_cll='1000,400':master_display='G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(1000,1)’" output.hevc }}} According to

Re: [FFmpeg-trac] #5406(undetermined:closed): adpcm_vima: problem with stereo files

2025-08-20 Thread FFmpeg
6#comment:8> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmpeg-trac To unsubscribe, visit link above, or email ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #11447(ffmpeg:closed): ffpreset functionality does not work as advertised

2025-08-18 Thread FFmpeg
: normal |Component: ffmpeg Version: git-master | Resolution: fixed Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0

Re: [FFmpeg-trac] #1530(ffmpeg:closed): Feature Request :: Allow more options in .ffpreset files

2025-08-18 Thread FFmpeg
| Status: closed Priority: wish |Component: ffmpeg Version: git-master | Resolution: fixed Keywords: ffpreset | Blocked By: Blocking: | Reproduced by

Re: [FFmpeg-trac] #11665(undetermined:new): Input pattern recognition broken when using avif format

2025-08-17 Thread FFmpeg
t:1> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmpeg-trac To unsubscribe, visit link above, or email ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10909(undetermined:new): Output of av1_nvenc cannot be processed by nvdec

2025-08-15 Thread FFmpeg
909#comment:4> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmpeg-trac To unsubscribe, visit link above, or email ffmpeg-trac-requ...@ffmpeg.org

Re: [FFmpeg-trac] #11390(ffmpeg:reopened): av1_nvenc output frames sometimes cannot be decoded

2025-08-15 Thread FFmpeg
Priority: normal |Component: ffmpeg Version: git-master | Resolution: Keywords: av1_nvenc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0

Re: [FFmpeg-trac] #11390(ffmpeg:closed): av1_nvenc output frames sometimes cannot be decoded

2025-08-15 Thread FFmpeg
: normal |Component: ffmpeg Version: git-master | Resolution: invalid Keywords: av1_nvenc | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0

Re: [FFmpeg-trac] #11696(avformat:new): WAV ≥ 4 GiB abnormal decoding due to length field overflow

2025-08-14 Thread FFmpeg
RL: <https://trac.ffmpeg.org/ticket/11696#comment:7> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmpeg-trac To unsubscribe, visit link above, or email ffmpeg-t

Re: [FFmpeg-trac] #11683(avformat:closed): "libx265" generated videos abnormal frames parsing?

2025-08-14 Thread FFmpeg
icable. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11683#comment:10> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker ___________ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmpeg-trac To unsubscribe, v

Re: [FFmpeg-trac] #11012(avformat:closed): APNG decoder incorrectly assumes fcTL chunk must be immediately followed by fdAT or IDAT

2025-08-14 Thread FFmpeg
: | Reproduced by developer: 1 Analyzed by developer: 1| -+- Changes (by devjeonghwan): * resolution: => fixed * status: open => closed Comment: Fixed [https://code.ffmpeg.org/FFmpeg/

Re: [FFmpeg-trac] #11012(avformat:open): APNG decoder incorrectly assumes fcTL chunk must be immediately followed by fdAT or IDAT

2025-08-14 Thread FFmpeg
Ticket URL: <https://trac.ffmpeg.org/ticket/11012#comment:2> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmpeg-trac To unsubscribe, visit link abo

Re: [FFmpeg-trac] #11696(avformat:new): WAV ≥ 4 GiB abnormal decoding due to length field overflow

2025-08-13 Thread FFmpeg
| --+ Comment (by Marton Balint): Replying to [comment:4 MasterQuestionable]: > ͏    Would it be sensible to automatically apply "-ignore_length": > ͏    https://ffmpeg.org/ffmpeg-formats.html#wav (documentation yet incomplete) > ͏

Re: [FFmpeg-trac] #9523(avcodec:open): segment_times splits at I-frames that are not keyframes

2025-08-12 Thread FFmpeg
| +--- Comment (by Balling): I created this https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20091 but we need a sample. From here or arteficially created: https://video.stackexchange.com/questions/28358/ffmpeg-identify-non-idr- frame-i-frame-as

Re: [FFmpeg-trac] #11526(avformat:closed): cmfv and cmfa not in hls allowed_extensions

2025-08-10 Thread FFmpeg
| + Changes (by Michael Niedermayer): * resolution: => fixed * status: reopened => closed Comment: Fixed in f3c3a6ecfb230c56a8ff9d219d79d5981b2aa4f3 -- Ticket URL: <https://trac.ffmpeg.org/ticket/11526#comment:5> F

Re: [FFmpeg-trac] #11640(avfilter:closed): Specific combination of timeclamp, fps, and count on showcqt causing crash

2025-08-09 Thread FFmpeg
fmpeg.org/ticket/11640#comment:6> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmpeg-trac To unsubscribe, visit link above, or email ffmpeg-trac-requ...@ffmpe

Re: [FFmpeg-trac] #9693(avcodec:open): change of matrix cannot happen on full range

2025-08-08 Thread FFmpeg
| + Comment (by Balling): The chroma sample location should be fixed with this patch when it will get eventually applied. https://patchwork.ffmpeg.org/project/ffmpeg/patch/20250723135626.1390296-12-ffm...@haasn.xyz/ -- Ticket URL: <ht

Re: [FFmpeg-trac] #11677(avformat:closed): ffplay does not properly sync LRC subtitles with 3-digit milliseconds

2025-08-06 Thread FFmpeg
ngeset:"bc3cc0a6af44adc63caf4e5097fcfebd7a7475b4/ffmpeg" bc3cc0a6/ffmpeg]: {{{#!CommitTicketReference repository="ffmpeg" revision="bc3cc0a6af44adc63caf4e5097fcfebd7a7475b4" avformat/lrcdec: support arbitrary precision timestamp Apparently files with milliseconds exist in the wild. A

Re: [FFmpeg-trac] #11683(avformat:closed): "libx265" generated videos abnormal frames parsing?

2025-08-06 Thread FFmpeg
Ticket URL: <https://trac.ffmpeg.org/ticket/11683#comment:9> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmpeg-trac To unsubscribe, visit link above

Re: [FFmpeg-trac] #11683(avformat:closed): "libx265" generated videos abnormal frames parsing?

2025-08-05 Thread FFmpeg
at about using both? ͏    `-x265-params "open-gop=0" -use_editlist 0` ͏    This is fundamentally core definition issues of MP4 and H.265. ͏    Beyond what FFmpeg could fix. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11683#comment:8> FFmpeg <ht

Re: [FFmpeg-trac] #5419(avformat:open): HLS EXT-X-DISCONTINUITY tag is not supported

2025-08-05 Thread FFmpeg
| + Comment (by Aleš Hrubý): Adding robust support for EXT-X-DISCONTINUITY would greatly improve FFmpeg’s usability for live and segmented streaming workflows. -- Ticket URL: <https://trac.ffmpeg.org/ticket/5419#comment:35> FFmpeg

Re: [FFmpeg-trac] #11659(avutil:closed): Regression: cannot use frames with alpha channel on vulkan

2025-08-05 Thread FFmpeg
| --+-- Changes (by bermond): * resolution: => fixed * status: new => closed -- Ticket URL: <https://trac.ffmpeg.org/ticket/11659#comment:2> FFmpeg <https://ffmpeg.org> FF

Re: [FFmpeg-trac] #11659(avutil:new): Regression: cannot use frames with alpha channel on vulkan

2025-08-05 Thread FFmpeg
| --+-- Comment (by bermond): This was fixed by commit 53826f1815240c8ecddba408ed517f4f242ace80. Thank you for fixing it. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11659#comment:1> FFmpeg <https://ffmpeg.org>

Re: [FFmpeg-trac] #11683(avformat:new): "libx265" generated videos abnormal frames parsing?

2025-08-05 Thread FFmpeg
's strange, because VirtualDub uses the ffmpeg libraries. I've reported the problem. Thanks for the reply, everything seems to be fine. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11683#comment:7> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _______

Re: [FFmpeg-trac] #11570(avdevice:closed): v4l2 1.30 breaks build of 7.1.1

2025-08-05 Thread FFmpeg
| + Changes (by bbhtt): * resolution: => fixed * status: new => closed -- Ticket URL: <https://trac.ffmpeg.org/ticket/11570#comment:5> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _____

Re: [FFmpeg-trac] #11570(avdevice:new): v4l2 1.30 breaks build of 7.1.1

2025-08-05 Thread FFmpeg
| + Comment (by bbhtt): This was fixed via https://github.com/FFmpeg/FFmpeg/commit/5fea5e3e11d6ff425db48f44489916399822aece would've been nice to mention or close this bug, anyways... -- Ticket URL: <https://trac.ffmpeg.org/ticket/11570#comment:4

Re: [FFmpeg-trac] #11677(avformat:closed): ffplay does not properly sync LRC subtitles with 3-digit milliseconds

2025-08-04 Thread FFmpeg
| -+ Changes (by kasper93): * component: undetermined => avformat * status: new => closed -- Ticket URL: <https://trac.ffmpeg.org/ticket/11677#comment:10> FFmpeg <https://ffmpeg.org> FF

Re: [FFmpeg-trac] #11677(undetermined:new): ffplay does not properly sync LRC subtitles with 3-digit milliseconds

2025-08-04 Thread FFmpeg
developer: 0 Analyzed by developer: 0| -+- Comment (by kasper93): Fixed by: bc3cc0a6af44adc63caf4e5097fcfebd7a7475b4 (https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20025) -- Ticket URL: <https://trac.ffmpeg.

Re: [FFmpeg-trac] #11696(avformat:new): WAV ≥ 4 GiB abnormal decoding due to length field overflow

2025-08-04 Thread FFmpeg
1` resolves the issue: {{{ $ ffmpeg -ignore_length 1 -i "2025-07-22 21.39.41.wav" 2025-07-22_21.39.41.flac ffmpeg version n7.1.1 Copyright (c) 2000-2025 the FFmpeg developers built with gcc 15.1.1 (GCC) 20250425 configuration: --prefix=/usr --disable-debug --disable-static

Re: [FFmpeg-trac] #11403(avdevice:new): [Regression] Abnormal "kmsgrab" exit handling of FF7 threading change

2025-08-04 Thread FFmpeg
Ticket URL: <https://trac.ffmpeg.org/ticket/11403#comment:3> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmpeg-trac To unsubscribe, visit link above, or

Re: [FFmpeg-trac] #11683(avformat:new): "libx265" generated videos abnormal frames parsing?

2025-08-03 Thread FFmpeg
eloper: 0 Analyzed by developer: 1| -+- Changes (by MasterQuestionable): * component: avcodec => avformat * keywords: libx265 OGOP => libx265 OGOP mp4 Comment: ͏    Would below reproduce? ͏    `ff

Re: [FFmpeg-trac] #11696(avformat:new): WAV ≥ 4 GiB abnormal decoding due to length field overflow (was: Long PCM WAV incomplete decoding?)

2025-08-03 Thread FFmpeg
uld it be sensible to automatically apply "-ignore_length": ͏    https://ffmpeg.org/ffmpeg-formats.html#wav (documentation yet incomplete) ͏ https://github.com/FFmpeg/FFmpeg/blob/ce01c7fb58597f525e130f47a13ff77f1db62bf4/libavformat/wavdec.c#L76 ͏    ; for all WAV ≥ 4 GiB? --

Re: [FFmpeg-trac] #11653(avformat:new): -c copy does not copy track names

2025-08-03 Thread FFmpeg
tps://trac.ffmpeg.org/ticket/11653#comment:13> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmpeg-trac To unsubscribe, visit link above, or email ffmp

Re: [FFmpeg-trac] #11606(avcodec:closed): avcodec/dvbsubenc: Broken dvb_encode_rle8

2025-08-03 Thread FFmpeg
| -+--- Changes (by Marton Balint): * resolution: => fixed * status: new => closed Comment: Fixed in 74f470c05c3ea76091b6d85d8fbf54ea3db1805b. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11606#comment:4> FFmpeg <htt

Re: [FFmpeg-trac] #11606(avcodec:new): avcodec/dvbsubenc: Broken dvb_encode_rle8

2025-08-03 Thread FFmpeg
| -+--- Comment (by Balling): Fix upcoming. https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20090/ -- Ticket URL: <https://trac.ffmpeg.org/ticket/11606#comment:3> FFmpeg <https://ffmpeg.org> FFmpeg i

Re: [FFmpeg-trac] #11606(avcodec:new): avcodec/dvbsubenc: Broken dvb_encode_rle8

2025-08-03 Thread FFmpeg
| -+--- Comment (by pbk): Hi, I think you are missing following line in the Table 26: 8-bits per pixel code string: 8-bit_zero 8 bslbf So, the total zero bits are 16 (8 + 1 + 7). When I was developing my own ffmpeg TS muxer with ability to

Re: [FFmpeg-trac] #2909(avcodec:new): Make dvbsubs more compliant among stb's

2025-08-03 Thread FFmpeg
ng in the spec for something else.) -- Ticket URL: <https://trac.ffmpeg.org/ticket/2909#comment:9> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmp

Re: [FFmpeg-trac] #11606(avcodec:new): avcodec/dvbsubenc: Broken dvb_encode_rle8

2025-08-03 Thread FFmpeg
ext ("The end of 8-bit/pixel_code_string shall be 2 zeroes") as I can't find it or anything quite like it in the above spec. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11606#comment:1> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _____

Re: [FFmpeg-trac] #11683(avcodec:new): "libx265" generated videos abnormal frames parsing?

2025-08-03 Thread FFmpeg
eloper: 1 | --+--- Comment (by rgr): If I save to "out.mkv," there's no problem. If I save to "out.mp4," the problem persists. Logs: https://files.fm/u/5n9f59syke -- Ticket URL: <https://trac.ffmpeg.org

Re: [FFmpeg-trac] #11683(avcodec:new): "libx265" generated videos abnormal frames parsing?

2025-08-03 Thread FFmpeg
RL: <https://trac.ffmpeg.org/ticket/11683#comment:4> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmpeg-trac To unsubscribe, visit link above, or email ffmpeg-t

Re: [FFmpeg-trac] #11653(avformat:new): -c copy does not copy track names

2025-08-03 Thread FFmpeg
d the audio/video/subtitle track names but only the languages, right? -- Ticket URL: <https://trac.ffmpeg.org/ticket/11653#comment:12> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://f

Re: [FFmpeg-trac] #11696(avcodec:new): Long PCM WAV incomplete decoding?

2025-08-02 Thread FFmpeg
MAX, then that can limit the read audio. Based on the numbers above I would guess it has overflown value. 131 min / 5.62 GB * (5.62 - 4) = 37.7 min -- Ticket URL: <https://trac.ffmpeg.org/ticket/11696#comment:3> FFmpeg <https://ffmpeg.org> FFmpe

Re: [FFmpeg-trac] #10966(undetermined:open): Regression - Memory leak when muxing raw h264 streams

2025-08-02 Thread FFmpeg
ket URL: <https://trac.ffmpeg.org/ticket/10966#comment:1> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmpeg-trac To unsubscribe, visit link above,

Re: [FFmpeg-trac] #5413(avformat:closed): Image size, pixel format cannot be detected ( 0x0, -1 ) for short h264 video

2025-08-02 Thread FFmpeg
:3 DAR 16:9], 29.97 fps, 59.94 tbr, 90k tbn, Start 1.100100 }}} is no printed instead of ffmpeg from 2020 {{{ Stream #0:0[0x1011]: Video: h264 (HDMV / 0x564D4448), none, 29.97 fps, 29.97 tbr, 90k tbn, 180k tbc }}} Fixed in some commit, not gonna bisect which one -- Ticket URL:

Re: [FFmpeg-trac] #11295(avcodec:open): Decoding p1_03.j2k returns a warning

2025-08-02 Thread FFmpeg
pass 18 of 22 6.90 M-V: 0.000 fd= 0 aq=0KB vq=0KB sq=0B }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/11295#comment:1> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _______ FFmpeg-trac mailing list FFmpeg-trac@avcod

Re: [FFmpeg-trac] #11696(avcodec:new): Long PCM WAV incomplete decoding?

2025-08-02 Thread FFmpeg
audio. Alternatively you might want to upload here the first 64kb of some of your samples which are > 4GiB so we can check if there is a pattern which can be used to autodetect this... -- Ticket URL: <https://trac.ffmpeg.org/ticket/11696#comment:2> FFmpeg <https://ffmpeg.org> FFmpe

Re: [FFmpeg-trac] #11624(undetermined:closed): Using audio filters throws Assertion best_input >= 0 failed

2025-08-02 Thread FFmpeg
Fixed in 44546751db824002f07cc0b8b2fc62587a5a34b5. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11624#comment:1> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmpeg-trac To un

Re: [FFmpeg-trac] #10990(undetermined:closed): "Assertion best_input >= 0 failed" IFF upsampling AND complex filtergraph

2025-08-02 Thread FFmpeg
Comment: Fixed in 44546751db824002f07cc0b8b2fc62587a5a34b5. -- Ticket URL: <https://trac.ffmpeg.org/ticket/10990#comment:3> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/m

Re: [FFmpeg-trac] #10988(undetermined:closed): Acrossover crash

2025-08-02 Thread FFmpeg
rg/ticket/10988#comment:5> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmpeg-trac To unsubscribe, visit link above, or email ffmpeg-trac-requ...@ffmpe

Re: [FFmpeg-trac] #11683(avcodec:new): "libx265" generated videos abnormal frames parsing? (was: Error encoding to H265 (H264 is ok))

2025-08-02 Thread FFmpeg
enerated videos abnormal frames parsing? Comment: ͏    I guess the cause might be OGOP (Open GOP). ͏    What are the interpreted encoding configs (returned by "libx265")? ͏    (or "Encoding settings" of MediaInfo) ͏    Should: ͏    `ffmpeg -y -v debug -hide_banner -nos

Re: [FFmpeg-trac] #11696(avcodec:new): Long PCM WAV incomplete decoding?

2025-08-02 Thread FFmpeg
| ---+--- Changes (by MasterQuestionable): * Attachment "long-wav.log" added. ͏    Filtered from "ffmpeg-20250730-211000.log".\\ ͏    Cue: https://trac.ffmpeg.org/attachment/ticket/11696/long- wav.log#L132 -- Ticket URL: <https://trac.ffmpeg.org/tick

Re: [FFmpeg-trac] #11696(avcodec:new): Long PCM WAV incomplete decoding? (was: ffmpeg unable to parse full runtime of wav file)

2025-08-02 Thread FFmpeg
| ---+--- Changes (by MasterQuestionable): * analyzed: 0 => 1 * cc: MasterQuestionable (added) * component: undetermined => avcodec * keywords: wav => pcm_f32le * summary: ffmpeg unable to parse full runtime of wav file => Long PCM WAV incomplete decodi

Re: [FFmpeg-trac] #11653(avformat:new): -c copy does not copy track names

2025-08-02 Thread FFmpeg
653#comment:11> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmpeg-trac To unsubscribe, visit link above, or email ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #11047(avformat:closed): Bad output with "libx264" "yuv422p10le" in MOV

2025-08-01 Thread FFmpeg
Blocking: | Reproduced by developer: 0 Analyzed by developer: 0| -+- Changes (by Mads Johansen): * resolution: => fixed * status: new => closed Comment: Fixed in https://githu

Re: [FFmpeg-trac] #11691(swscale:new): [Security] heap-buffer-overflow on yuv2rgb.c:558

2025-07-31 Thread FFmpeg
| +--- Changes (by Michael Niedermayer): * cc: Michael Niedermayer, Niklas Haas (added) -- Ticket URL: <https://trac.ffmpeg.org/ticket/11691#comment:1> FFmpeg <https://ffmpeg.org> FFmpeg i

Re: [FFmpeg-trac] #11690(swscale:new): [Security] Null pointer dereference on libswscale/swscale.c:1125

2025-07-31 Thread FFmpeg
| +--- Changes (by Michael Niedermayer): * cc: Niklas Haas, Michael Niedermayer (added) -- Ticket URL: <https://trac.ffmpeg.org/ticket/11690#comment:2> FFmpeg <https://ffmpeg.org> FFmpeg i

Re: [FFmpeg-trac] #11689(swscale:new): [Security] Division by zero on libswscale/utils.c:1408:60

2025-07-31 Thread FFmpeg
| +--- Changes (by Michael Niedermayer): * cc: Michael Niedermayer, Niklas Haas (added) -- Ticket URL: <https://trac.ffmpeg.org/ticket/11689#comment:1> FFmpeg <https://ffmpeg.org> FFmpeg i

Re: [FFmpeg-trac] #11688(swscale:new): [Assertion Failed] libswscale/x86/swscale.c:573

2025-07-31 Thread FFmpeg
| +--- Changes (by Michael Niedermayer): * cc: Niklas Haas, Michael Niedermayer (added) -- Ticket URL: <https://trac.ffmpeg.org/ticket/11688#comment:1> FFmpeg <https://ffmpeg.org> FFmpeg i

Re: [FFmpeg-trac] #11687(swscale:new): [Security] Null pointer dereference on libswscale/slice.c

2025-07-31 Thread FFmpeg
| +--- Changes (by Michael Niedermayer): * cc: Niklas Haas (added) -- Ticket URL: <https://trac.ffmpeg.org/ticket/11687#comment:4> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker ___

Re: [FFmpeg-trac] #11683(avcodec:new): Error encoding to H265 (H264 is ok)

2025-07-31 Thread FFmpeg
| ---+--- Comment (by rgr): You don't even need to download my files, just any ffmpeg/libx265 encoded one is enough. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11683#comment:2> FFmpeg <https://ffmpeg.org> FFm

Re: [FFmpeg-trac] #9195(avfilter:closed): vibrance (video filter) incorrect defaults for luma

2025-07-31 Thread FFmpeg
developer: 0 Analyzed by developer: 0| -+- Changes (by Zhao Zhili ): * owner: (none) => Zhao Zhili * resolution: wontfix => fixed Comment: In [changeset:"2a49d05d1a92cd6454b4e6fc026a66b697c7

Re: [FFmpeg-trac] #11696(undetermined:new): ffmpeg unable to parse full runtime of wav file

2025-07-30 Thread FFmpeg
#11696: ffmpeg unable to parse full runtime of wav file --+ Reporter: wavybaby |Owner: (none) Type: defect| Status: new Priority: minor

[FFmpeg-trac] #11696(undetermined:new): ffmpeg unable to parse full runtime of wav file

2025-07-30 Thread FFmpeg
#11696: ffmpeg unable to parse full runtime of wav file --+-- Reporter: wavybaby | Type: defect Status: new | Priority: minor Component

[FFmpeg-trac] #11695(build system:new): Configure for armv6 doesn't disable neon and armv6t2.

2025-07-30 Thread FFmpeg
r: 0| -+- I'm trying to configure ffmpeg for rpi1 (armv6). First, I have modified this line: https://github.com/FFmpeg/FFmpeg/blob/master/configure#L8021 From `echo "ARCH $arch ($cpu)"` To `echo "ARCH

Re: [FFmpeg-trac] #11692(swscale:open): [Security] heap-buffer-overflow on alphablend.c:77

2025-07-30 Thread FFmpeg
Analyzed by developer: 0| -+- Changes (by Niklas Haas): * owner: (none) => Niklas Haas * status: new => open Comment: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20063 -- Ticket URL: <https://trac.f

Re: [FFmpeg-trac] #11694(undetermined:new): Multi-GPU: NVDec cant find CUDA device when used inside a docker container and targeting specific GPU ID

2025-07-29 Thread FFmpeg
etDecoderCaps(&caps) failed > -> CUDA_ERROR_NO_DEVICE: no CUDA-capable device is detected > }}} > > The issue here is that from what I can tell, only ffmpeg has this issue. > Other libs/apps in the container that target a specific GPU work: loading > ONNX models into the GPU works when targeting a s

Re: [FFmpeg-trac] #11694(undetermined:new): Multi-GPU: NVDec cant find CUDA device when used inside a docker container and targeting specific GPU ID

2025-07-29 Thread FFmpeg
-container-toolkit| Blocking: | Reproduced by developer: 0 Analyzed by developer: 0| -+- Changes (by baudneo): * Attachment "ffmpeg-error.log" added. FFREPORT log file

[FFmpeg-trac] #11694(undetermined:new): Multi-GPU: NVDec cant find CUDA device when used inside a docker container and targeting specific GPU ID

2025-07-29 Thread FFmpeg
default index: 0) using one of several methods results in an error: {{{ [h264 @ 0x557b6d7f3900] decoder->cvdl->cuvidGetDecoderCaps(&caps) failed -> CUDA_ERROR_NO_DEVICE: no CUDA-capable device is detected }}} The issue here is that from what I can tell, only ffmpeg has this issue

Re: [FFmpeg-trac] #11692(swscale:new): [Security] heap-buffer-overflow on alphablend.c:77

2025-07-29 Thread FFmpeg
ore more code paths. If you're interested, we could explore deeper research and collaboration. By the way, please check these bugs :) -- Ticket URL: <https://trac.ffmpeg.org/ticket/11692#comment:4> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker ____

Re: [FFmpeg-trac] #11686(swscale:closed): [Security] signed integer overflow on libswscale/output.c

2025-07-29 Thread FFmpeg
developer: 0 Analyzed by developer: 0| -+- Comment (by Michael Niedermayer): https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20060 -- Ticket URL: <https://trac.ffmpeg.org/ticket/11686#comment:4> FFmpeg

Re: [FFmpeg-trac] #11692(swscale:new): [Security] heap-buffer-overflow on alphablend.c:77

2025-07-29 Thread FFmpeg
modified. Is this report AI generated ? -- Ticket URL: <https://trac.ffmpeg.org/ticket/11692#comment:3> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker ___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo

  1   2   3   4   5   6   7   8   9   10   >