Re: [FFmpeg-trac] #11115(avutil:new): 7.0: FTBFS on 32 bit architectures with GCC 14

g.org/ticket/5#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 above, or email ffmpeg-trac-requ...@ff

Re: [FFmpeg-trac] #11115(avutil:new): 7.0: FTBFS on 32 bit architectures with GCC 14

by developer: 0| -+- Changes (by Sebastian Ramacher): * component: avcodec => avutil -- Ticket URL: <https://trac.ffmpeg.org/ticket/5#comment:1> FFmpeg <https://ffmpeg.org&g

[FFmpeg-trac] #11115(avcodec:new): 7.0: FTBFS on 32 bit architectures with GCC 14

| -+- Since Debian switched to GCC 14, ffmpeg 7.0.1 no longer builds on 32 bit architectures: {{{ gcc -I. -Isrc/ -Wdate-time -D_FORTIFY_SOURCE=2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -D_ISOC11_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE

Re: [FFmpeg-trac] #9898(undetermined:closed): Different result using FFmpeg 5.1 and 5.0.1 with -color_trc log / log_sqrt

#9898: Different result using FFmpeg 5.1 and 5.0.1 with -color_trc log / log_sqrt -+- Reporter: gabriele_ls |Owner: (none) Type: defect | Status

Re: [FFmpeg-trac] #9898(undetermined:closed): Different result using FFmpeg 5.1 and 5.0.1 with -color_trc log / log_sqrt

#9898: Different result using FFmpeg 5.1 and 5.0.1 with -color_trc log / log_sqrt -+- Reporter: gabriele_ls |Owner: (none) Type: defect | Status

Re: [FFmpeg-trac] #11110(avcodec:closed): Corrupted output on h264 veryslow preset with common hardware decoders

| +--- Comment (by MasterQuestionable): ͏    Well, enough evidence then. ͏    No need to further bother. Thanks. -- Ticket URL: <https://trac.ffmpeg.org/ticket/0#comment:11> FFmpeg <https://ffmpeg.or

Re: [FFmpeg-trac] #11110(avcodec:closed): Corrupted output on h264 veryslow preset with common hardware decoders

htp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=60 rc=crf mbtree=1 crf=25.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00' (666 bytes) -- Ticket URL: <https://trac.ffmpeg.org/ticket/0#comment:10> FFmpeg <https:/

Re: [FFmpeg-trac] #11110(avcodec:closed): Corrupted output on h264 veryslow preset with common hardware decoders

to ensure the encoding procedure actually changed. -- Ticket URL: <https://trac.ffmpeg.org/ticket/0#comment:9> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mail

Re: [FFmpeg-trac] #11078(avcodec:new): Speex decoding speed regression? (was: ffplay plays .spx very slowly)

ing speed regression? Comment: ͏    Speex appears to be a much defunct codec. ("obsoleted by Opus") ͏    Please help ascertain the exact regression window, if you deem it important. ͏    (simple revert may be applicable..?) -- Ticket URL: <https://trac.ffmpeg.org/ticket/1

Re: [FFmpeg-trac] #11078(ffplay:new): ffplay plays .spx very slowly

| ---+-- Changes (by Ronald): * priority: critical => important -- Ticket URL: <https://trac.ffmpeg.org/ticket/11078#comment:5> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker___ FFmpeg-trac mailing list FFmpeg-trac@av

Re: [FFmpeg-trac] #11078(ffplay:new): ffplay plays .spx very slowly

| --+-- Changes (by Ronald): * cc: Ronald (added) -- Ticket URL: <https://trac.ffmpeg.org/ticket/11078#comment:4> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg

Re: [FFmpeg-trac] #11078(ffplay:new): ffplay plays .spx very slowly

| --+-- Changes (by Ronald): * priority: normal => critical -- Ticket URL: <https://trac.ffmpeg.org/ticket/11078#comment:3> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org htt

Re: [FFmpeg-trac] #11110(avcodec:closed): Corrupted output on h264 veryslow preset with common hardware decoders

ver of unsupported profiles of AVC. FFMPEG ALWAYS ALLOWS DECODING. Also remember that my bug about slices is still open -- Ticket URL: <https://trac.ffmpeg.org/ticket/0#comment:8> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker___ FFmpeg-trac mail

Re: [FFmpeg-trac] #11110(avcodec:closed): Corrupted output on h264 veryslow preset with common hardware decoders

adata? It does change the encoding, reducing the level from 6 to 5.1 slightly increases the file size of the output and removes all of the artifacts -- Ticket URL: <https://trac.ffmpeg.org/ticket/0#comment:7> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker__

Re: [FFmpeg-trac] #11110(avcodec:closed): Corrupted output on h264 veryslow preset with common hardware decoders

gy various aspects... ͏    And much unfixable, for "hardware". -- Ticket URL: <https://trac.ffmpeg.org/ticket/0#comment:6> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker_______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org htt

Re: [FFmpeg-trac] #11110(avcodec:closed): Corrupted output on h264 veryslow preset with common hardware decoders

| +--- Comment (by Zeblote): Perhaps ffmpeg should change the default level to 5.1 if that's the limit of common decoders? While not directly the fault of the library (the hardware decoder should just refuse to play

Re: [FFmpeg-trac] #11109(avformat:closed): Matroska output format missing supported video codec tags (additional_video_tags)

ame name) and probably it should be unique? -- Ticket URL: <https://trac.ffmpeg.org/ticket/11109#comment:3> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listi

Re: [FFmpeg-trac] #11110(avcodec:closed): Corrupted output on h264 veryslow preset with common hardware decoders

log above, it is trying to use: > [libx264 @ 0224a6ee6bc0] profile High, level 6.0, 4:2:0, 8-bit So the underlying issue is that ffmpeg defaults to using a feature level that the hardware decoder can't support. Adding {{{ -level 5.1 }}} to the command line fixes the problem.

Re: [FFmpeg-trac] #7158(avformat:new): Attempt HTTP compression (was: Send "Accept-Encoding: gzip" on .m3u8 HTTP requests)

    Disregard, it needs the decompressor support. -- Ticket URL: <https://trac.ffmpeg.org/ticket/7158#comment:4> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker_______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mai

Re: [FFmpeg-trac] #11110(avcodec:closed): Corrupted output on h264 veryslow preset with common hardware decoders

| +--- Changes (by MasterQuestionable): * cc: MasterQuestionable (added) * keywords: => h264 * status: new => closed * component: ffmpeg => avcodec * resolution: => invalid Comment: ͏    Hardw

Re: [FFmpeg-trac] #11107(avfilter:new): Enhancement Request: Improve VAAPI Color Type Detection for HDR Content

a single definition) ͏    As workaround, try various colorspace conversions in: ͏    https://trac.ffmpeg.org/wiki/colorspace -- Ticket URL: <https://trac.ffmpeg.org/ticket/11107#comment:3> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker___

Re: [FFmpeg-trac] #11096(undetermined:new): Chaotic escaping rules

work". ͏    As in URI, !RegEx, ... ͏    Straight answer: ͏    Whatever works doesn't need to be escaped... ͏    Though several relevant implementations have to be considered considering the interoperability. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11096#comment:8> FFmpeg <https:/

Re: [FFmpeg-trac] #11109(avformat:closed): Matroska output format missing supported video codec tags (additional_video_tags)

e comment in matroska.c has not been changed; it now means that an additional_video_tags would have to be readded in the future if needed by a new video codec in ff_mkv_codec_tags. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11109#comment:2> FFmpeg <https://ffmpeg

Re: [FFmpeg-trac] #11114(avcodec:new): fate-avid-meridian fails on ppc64{, el}

ffmpeg.org/ticket/4#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 above, or email ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #11114(avcodec:new): fate-avid-meridian fails on ppc64{, el}

| ---+--- Comment (by Sean McGovern): If I disable the all of the DSP code in `libavcodec/ppc/idctdsp.c`, the test succeeds. -- Ticket URL: <https://trac.ffmpeg.org/ticket/4#comment:1> FFmpeg <https://ffmpeg.org>

[FFmpeg-trac] #11114(avcodec:new): fate-avid-meridian fails on ppc64{, el}

tps://trac.ffmpeg.org/ticket/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..

Re: [FFmpeg-trac] #9604(undetermined:new): 5.0 regression: test failure on ppc64el: checkas-sw_scale and filter-scale2ref_keep_aspect

ket/9604#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 above, or email ffmpeg-trac-requ...@ffmpeg.org

Re: [FFmpeg-trac] #10955(undetermined:new): 7.0: checkasm failures on ppc64el

by developer: 0 Analyzed by developer: 0| -+- Changes (by Sean McGovern): * cc: Sean McGovern (added) -- Ticket URL: <https://trac.ffmpeg.org/ticket/10955#comment:1> FFmpeg <https://ffmpeg.org>

Re: [FFmpeg-trac] #9604(undetermined:new): 5.0 regression: test failure on ppc64el: checkas-sw_scale and filter-scale2ref_keep_aspect

. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9604#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, or

Re: [FFmpeg-trac] #11111(avcodec:new): When decoding a multilayer DWAA compressed .exr, I get error decode_block()

URL: <https://trac.ffmpeg.org/ticket/1#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 abov

Re: [FFmpeg-trac] #10725(avcodec:new): mediacodecdec tunneled playback support

URL: <https://trac.ffmpeg.org/ticket/10725#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 above, or

Re: [FFmpeg-trac] #11111(avcodec:new): When decoding a multilayer DWAA compressed .exr, I get error decode_block()

BTW, -- Ticket URL: <https://trac.ffmpeg.org/ticket/1#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, visi

Re: [FFmpeg-trac] #11054(undetermined:new): distortion on speex playback

| -+- Comment (by shenlebantongying): Can confirm this is happening with FFmpeg 7.0.1 found in a related project https://github.com/xiaoyifang/goldendict- ng/issues/1707#issuecomment-2251999373 Sample speex

Re: [FFmpeg-trac] #4907(avcodec:open): Support decoding animated WebP images

| --+--- Comment (by se7enxf): Is anyone still working on this? -- Ticket URL: <https://trac.ffmpeg.org/ticket/4907#comment:30> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker___ FFmpeg-trac

Re: [FFmpeg-trac] #11096(undetermined:new): Chaotic escaping rules

by developer: 0 Analyzed by developer: 0| -+- Comment (by superbonaci): Question: which characters need to be escaped in `;FFMETADATA1` files? According to this https://ffmpeg.org/ffmpeg-utils.html#Quoting-and- escaping

Re: [FFmpeg-trac] #11111(avcodec:new): When decoding a multilayer DWAA compressed .exr, I get error decode_block()

by developer: 0 Analyzed by developer: 1| -+- Comment (by Sean Devonport): Yes, DaVinci does seem to be able to decode and I can select the various layers. Any ideas of how to get it to work for ffmpeg would

Re: [FFmpeg-trac] #11111(avcodec:new): When decoding a multilayer DWAA compressed .exr, I get error decode_block()

tps://trac.ffmpeg.org/ticket/1#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 email ffmpeg-trac-requ..

Re: [FFmpeg-trac] #7158(avformat:new): Send "Accept-Encoding: gzip" on .m3u8 HTTP requests

eloper: 0| -+ Comment (by Balling): What about brotli, btw...  -- Ticket URL: <https://trac.ffmpeg.org/ticket/7158#comment:3> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker_____

Re: [FFmpeg-trac] #11093(ffmpeg:new): ffmpeg and libopusoverwrting channel layout, resluting in no sound in vlc (was: ffmpeg overwrting channel layout, resluting in no sound in vlc)

#11093: ffmpeg and libopusoverwrting channel layout, resluting in no sound in vlc -+- Reporter: solomoncyj |Owner: (none) Type: defect | Status

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

after building version 7. > Prior to that, however, I don't think I ever had a filtergraph that > included upsampling and multiple input and/or output pads, so I am not > claiming the error was recently introduced. > > If I recall correctly, originally, FFmpeg would crash, thro

Re: [FFmpeg-trac] #11113(undetermined:new): output option `-f ffmetadata` may stop the filter chain application

Ticket URL: <https://trac.ffmpeg.org/ticket/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

[FFmpeg-trac] #11113(undetermined:new): output option `-f ffmetadata` may stop the filter chain application

by developer: 0| -+- Summary of the bug: In some configurations, `-f ffmetadata` as an output option will prevent the filter chain from being applied. How to reproduce: {{{ % ffmpeg -hide_banner -i

[FFmpeg-trac] #11112(avcodec:new): Compile error

les.h" | ^~~ compilation terminated. make: *** [/home/macchinista/Sources/ffmpeg/ffbuild/common.mak:81: libavcodec/aac/aacdec_fixed.o] Error 1 I configured sources with flag "--enable-hardcoded-tables" and checking libavcodec/sinewin_fixed_tabl

Re: [FFmpeg-trac] #10018(undetermined:new): Duration estimation regression for h264 in mov

/7828#comment:8 Patch is here to use stts atom. https://patchwork.ffmpeg.org/project/ffmpeg/patch/20190429225027.81295-1-fumoboy...@me.com/ -- Ticket URL: <https://trac.ffmpeg.org/ticket/10018#comment:8> FFmpeg <https://ffmpeg.org>

Re: [FFmpeg-trac] #11111(avcodec:new): When decoding a multilayer DWAA compressed .exr, I get error decode_block()

by developer: 0 Analyzed by developer: 1| -+- Changes (by Sean Devonport): * Attachment "ffmpeg-20240723-115204.log" added. ffmpeg log that results in decode_block() failed -- Ticket U

Re: [FFmpeg-trac] #4976(avcodec:open): BK2 format support

| -+--- Comment (by intermediary): Is https://patchwork.ffmpeg.org/project/ffmpeg/patch/20220524133650.18299-1-one...@gmail.com/#72100 incomplete or why hasn'T it been merged yet? -- Ticket URL: <https://trac.ffmpeg.org/ticket/4976#comment:21> FFmpeg <https://f

Re: [FFmpeg-trac] #5777(avfilter:open): No support for coloured emoji with drawtext filter

the `FT_LOAD_COLOR` flag] to drawtext's `ft_load_flags` param? -- Ticket URL: <https://trac.ffmpeg.org/ticket/5777#comment:11> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mail

Re: [FFmpeg-trac] #11111(avcodec:new): When decoding a multilayer DWAA compressed .exr, I get error decode_block()

by developer: 0 Analyzed by developer: 1| -+- Changes (by Sean Devonport): * component: ffmpeg => avcodec -- Ticket URL: <https://trac.ffmpeg.org/ticket/1#comment:2> FFmpeg <https://ffmpeg

Re: [FFmpeg-trac] #11111(ffmpeg:new): When decoding a multilayer DWAA compressed .exr, I get error decode_block()

| Status: new Priority: important |Component: ffmpeg Version: git-master | Resolution: Keywords: exr | Blocked By: Blocking: | Reproduced by developer: 0

[FFmpeg-trac] #11111(ffmpeg:new): When decoding a multilayer DWAA compressed .exr, I get error decode_block()

: new | Priority: important Component: ffmpeg | Version: git- | master Keywords: exr | Blocked By: Blocking: | Reproduced by developer

Re: [FFmpeg-trac] #11107(avfilter:new): Enhancement Request: Improve VAAPI Color Type Detection for HDR Content

  . > ͏    So I much wonder what HDR does really? -- Ticket URL: <https://trac.ffmpeg.org/ticket/11107#comment:2> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker_______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/

Re: [FFmpeg-trac] #11110(ffmpeg:new): Corrupted output on h264 veryslow preset with common hardware decoders

Priority: normal |Component: ffmpeg Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0

Re: [FFmpeg-trac] #11110(ffmpeg:new): Corrupted output on h264 veryslow preset with common hardware decoders

Priority: normal |Component: ffmpeg Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0

Re: [FFmpeg-trac] #11110(ffmpeg:new): Corrupted output on h264 veryslow preset with common hardware decoders

Priority: normal |Component: ffmpeg Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0

Re: [FFmpeg-trac] #11110(ffmpeg:new): Corrupted output on h264 veryslow preset with common hardware decoders

Priority: normal |Component: ffmpeg Version: git-master | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0

Re: [FFmpeg-trac] #4954(avformat:open): joint stereo indicator missing from mp3 headers

vel. -- Ticket URL: <https://trac.ffmpeg.org/ticket/4954#comment:14> 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

Re: [FFmpeg-trac] #4954(avformat:open): joint stereo indicator missing from mp3 headers

| + Comment (by GraniteStateColin): Confirmed that the bug still exists in version 7.0.1 of ffmpeg. Given the age of the bug, I am concerned that because this is not a problem for some important users, this bug is just being dismissed or ignored

Re: [FFmpeg-trac] #11010(avcodec:closed): Android MediaCodec: encoding videos with resolution not divisible by 16 to codec other than H.264 and H.265

411b98 and 7d46ab9e1206b09ebe1a94ecac49cc99d9b3522e -- Ticket URL: <https://trac.ffmpeg.org/ticket/11010#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

Re: [FFmpeg-trac] #11010(avcodec:new): Android MediaCodec: encoding videos with resolution not divisible by 16 to codec other than H.264 and H.265

URL: <https://trac.ffmpeg.org/ticket/11010#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 above, or email f

Re: [FFmpeg-trac] #7045(avformat:reopened): Should retain pixel density metadata from HiDPI/Retina screen recordings

: 0| -+ Changes (by broly): * status: closed => reopened * resolution: invalid => -- Ticket URL: <https://trac.ffmpeg.org/ticket/7045#comment:12> FFmpeg <https://ffmpeg.or

Re: [FFmpeg-trac] #7045(avformat:closed): Should retain pixel density metadata from HiDPI/Retina screen recordings

by developer: 0| -+ Changes (by broly): * status: new => closed * resolution: => invalid -- Ticket URL: <https://trac.ffmpeg.org/ticket/7045#comment:11> FFmpeg <https://ffmpeg.or

Re: [FFmpeg-trac] #7045(avformat:new): Should retain pixel density metadata from HiDPI/Retina screen recordings

. anyways can someone fix it or put this in mainline? it's something i'd appreciate even though mac ARM users are losers. -- Ticket URL: <https://trac.ffmpeg.org/ticket/7045#comment:10> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker___ FFmpeg-

Re: [FFmpeg-trac] #7045(avformat:new): Should retain pixel density metadata from HiDPI/Retina screen recordings

| -+ Changes (by broly): * Attachment "new_mov_pixeldensity.patch" added. updated patch -- Ticket URL: <https://trac.ffmpeg.org/ticket/7045> FFmpeg <https://ffmpe

Re: [FFmpeg-trac] #11095(avutil:open): Can't compile FFmpeg on Mac from latest Git version

#11095: Can't compile FFmpeg on Mac from latest Git version ---+-- Reporter: Paul Pacifico |Owner: ePirat Type: defect | Status: open

Re: [FFmpeg-trac] #11105(undetermined:new): webvtt not seeking properly (was: webvtt codec not seeking properly with output seeking)

00:02.680 --> 00:00:13.760 12, one, 00:00:13.760 --> 00:00:24.040 two, three, 00:00:24.040 --> 00:00:29.920 four, five. 00:00:33.200 --> 00:00:33.720 Six. }}} ]] -- Ticket URL: <https://trac.ffmpeg.org/ticket/11105#comment:5> FFmpeg <https://ffmpeg.org> FFmpeg

Re: [FFmpeg-trac] #11108(avformat:closed): youtube googlevideo 403 forbidden (was: youtube googlevideo 403 forbidden googlevideo)

| -+- Changes (by MasterQuestionable): * status: new => closed * cc: MasterQuestionable (added) * type: defect => enhancement * component: ffmpeg => avformat * summary: youtube googlevideo 403 forbidden googlevideo =

Re: [FFmpeg-trac] #11095(avutil:open): Can't compile FFmpeg on Mac from latest Git version

#11095: Can't compile FFmpeg on Mac from latest Git version ---+-- Reporter: Paul Pacifico |Owner: ePirat Type: defect | Status: open

Re: [FFmpeg-trac] #11095(avutil:new): Can't compile FFmpeg on Mac from latest Git version

#11095: Can't compile FFmpeg on Mac from latest Git version ---+-- Reporter: Paul Pacifico |Owner: (none) Type: defect | Status: new

Re: [FFmpeg-trac] #11109(avformat:new): Matroska output format missing supported video codec tags (additional_video_tags)

c_tags for output formats to check whether is supported or not by the specified format. -- -- Ticket URL: <https://trac.ffmpeg.org/ticket/11109#comment:1> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org ht

[FFmpeg-trac] #11109(avformat:new): Matroska output format missing supported video codec tags (additional_video_tags)

enc.c" but additional_video_tags are not specified. Wondering if generally we could trust codec_tags for output formats to check whether is supported or not by the specified format. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11109> FFmpeg <https://ffmpe

Re: [FFmpeg-trac] #11108(ffmpeg:new): youtube googlevideo 403 forbidden googlevideo

: normal |Component: ffmpeg Version: unspecified| Resolution: Keywords: forbidden 403 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0

Re: [FFmpeg-trac] #11108(ffmpeg:new): youtube googlevideo 403 forbidden googlevideo

: normal |Component: ffmpeg Version: unspecified| Resolution: Keywords: forbidden 403 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0

Re: [FFmpeg-trac] #11108(ffmpeg:new): youtube googlevideo 403 forbidden googlevideo

: normal |Component: ffmpeg Version: unspecified| Resolution: Keywords: forbidden 403 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0

Re: [FFmpeg-trac] #11108(ffmpeg:new): youtube googlevideo 403 forbidden googlevideo

: normal |Component: ffmpeg Version: unspecified| Resolution: Keywords: forbidden 403 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0

[FFmpeg-trac] #11108(ffmpeg:new): youtube googlevideo 403 forbidden googlevideo

: ffmpeg | Version: Keywords: forbidden| unspecified 403| Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0

Re: [FFmpeg-trac] #11105(undetermined:new): webvtt codec not seeking properly with output seeking

/ticket/11105#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...@f

Re: [FFmpeg-trac] #11105(undetermined:new): webvtt codec not seeking properly with output seeking

suppose the output subtitle is empty. (during of 0?) ͏    Is it relevant with "-shortest"? -- Ticket URL: <https://trac.ffmpeg.org/ticket/11105#comment:3> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker_______ FFmpeg-trac ma

Re: [FFmpeg-trac] #10972(avcodec:new): An FFmpeg decoding error caused by --constrained-intra in x265

#10972: An FFmpeg decoding error caused by --constrained-intra in x265 -+- Reporter: ronifue |Owner: (none) Type: defect | Status: new

Re: [FFmpeg-trac] #11105(undetermined:new): webvtt codec not seeking properly with output seeking

nullify the subtitles in this instance. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11105#comment:2> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo

Re: [FFmpeg-trac] #10930(avcodec:new): reencoding to x264 introduces playback stutter in Chrome

was poorly produced. (therefore potentially broken) ͏    If such is the case, caution that FFmpeg currently may not handle non-perfectly-valid files in the most sensible way. ͏    E.g. https://trac.ffmpeg.org/ticket/11055 -- Ticket URL: <https://trac.ffmpeg.org/ticket/10930#comment:5> FFmpeg

Re: [FFmpeg-trac] #11107(avfilter:new): Enhancement Request: Improve VAAPI Color Type Detection for HDR Content

ble. ͏    . ͏    So I much wonder what HDR does really? -- Ticket URL: <https://trac.ffmpeg.org/ticket/11107#comment:1> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/

Re: [FFmpeg-trac] #10930(avcodec:new): reencoding to x264 introduces playback stutter in Chrome

| +--- Comment (by diviaki): Might relate that in the original, 30 minutes long video the sound slowly gets out of sync finishing about 3 seconds earlier when video ends. -- Ticket URL: <https://trac.ffmpeg.org/ticket/10930#comment:4>

Re: [FFmpeg-trac] #10930(avcodec:new): reencoding to x264 introduces playback stutter in Chrome

RL: <https://trac.ffmpeg.org/ticket/10930> 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

[FFmpeg-trac] #11107(avfilter:new): Enhancement Request: Improve VAAPI Color Type Detection for HDR Content

detection for VAAPI needs to be enhanced to properly handle HDR content. **Description:** While trying to play an HDR video using FFmpeg with VAAPI, the color type is mistakenly identified as BT.709 instead of the correct HDR color type (e.g., BT.2020). Specifically, in my test video

Re: [FFmpeg-trac] #11105(undetermined:new): webvtt codec not seeking properly with output seeking

ffmpeg.org/ticket/11105#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, or email ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #11105(undetermined:new): webvtt codec not seeking properly with output seeking

om running the "-c:s webvtt" encoding -- Ticket URL: <https://trac.ffmpeg.org/ticket/11105> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker_______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

[FFmpeg-trac] #11106(undetermined:new): Add decoding support for MPEG-H audio

can be mapped to those in {{{libavutil/channel_layout.h}}} 100%. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11106> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker___ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mail

[FFmpeg-trac] #11105(undetermined:new): webvtt codec not seeking properly with output seeking

/samples/counting.vtt and trim and mux them with: {{{ % ffmpeg -i counting.mp4 -i counting.vtt -shortest -c:v copy -c:s webvtt -ss 20s trimmed.mkv }}} To see the working/expected version, do: {{{ % ffmpeg -i counting.mp4 -i counting.vtt -shortest -c:v copy -c:s copy -ss 20s trimmed.mkv

Re: [FFmpeg-trac] #11077(ffplay:closed): ffplay uses the -ac option to play pcm and reports an error 'ac': Option not found

ayout" feels verbose, much unjustifiably. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11077#comment:3> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker_______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.org/mailma

Re: [FFmpeg-trac] #11077(ffplay:closed): ffplay uses the -ac option to play pcm and reports an error 'ac': Option not found

: | Reproduced by developer: 0 Analyzed by developer: 0| -+- Changes (by Marton Balint): * status: new => closed * resolution: => invalid Comment: ffplay no longer supports the -ac option. ffmpeg h

Re: [FFmpeg-trac] #11080(documentation:new): FFmpeg timestamps do not consistently agree with packet timestamps

#11080: FFmpeg timestamps do not consistently agree with packet timestamps -+- Reporter: markfilipak |Owner: (none) Type: task | Status: new

Re: [FFmpeg-trac] #11080(documentation:new): FFmpeg timestamps do not consistently agree with packet timestamps

#11080: FFmpeg timestamps do not consistently agree with packet timestamps -+- Reporter: markfilipak |Owner: (none) Type: task | Status: new

Re: [FFmpeg-trac] #11080(documentation:new): FFmpeg timestamps do not consistently agree with packet timestamps

#11080: FFmpeg timestamps do not consistently agree with packet timestamps -+- Reporter: markfilipak |Owner: (none) Type: task | Status: new

Re: [FFmpeg-trac] #11080(documentation:new): FFmpeg timestamps do not consistently agree with packet timestamps

#11080: FFmpeg timestamps do not consistently agree with packet timestamps -+- Reporter: markfilipak |Owner: (none) Type: task | Status: new

Re: [FFmpeg-trac] #11080(documentation:new): FFmpeg timestamps do not consistently agree with packet timestamps

#11080: FFmpeg timestamps do not consistently agree with packet timestamps -+- Reporter: markfilipak |Owner: (none) Type: task | Status: new

Re: [FFmpeg-trac] #11080(documentation:new): FFmpeg timestamps do not consistently agree with packet timestamps

#11080: FFmpeg timestamps do not consistently agree with packet timestamps -+- Reporter: markfilipak |Owner: (none) Type: task | Status: new

Re: [FFmpeg-trac] #11080(documentation:new): FFmpeg timestamps do not consistently agree with packet timestamps

#11080: FFmpeg timestamps do not consistently agree with packet timestamps -+- Reporter: markfilipak |Owner: (none) Type: task | Status: new

Re: [FFmpeg-trac] #11080(documentation:new): FFmpeg timestamps do not consistently agree with packet timestamps

#11080: FFmpeg timestamps do not consistently agree with packet timestamps -+- Reporter: markfilipak |Owner: (none) Type: task | Status: new

Re: [FFmpeg-trac] #11080(documentation:new): FFmpeg timestamps do not consistently agree with packet timestamps

#11080: FFmpeg timestamps do not consistently agree with packet timestamps -+- Reporter: markfilipak |Owner: (none) Type: task | Status: new

Re: [FFmpeg-trac] #11099(documentation:reopened): "streamselect" filter, "map" parsing

he feedback may help analyzing the relevant filters' design. -- Ticket URL: <https://trac.ffmpeg.org/ticket/11099#comment:6> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker_______ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org https://ffmpeg.

  1   2   3   4   5   6   7   8   9   10   >