Re: [FFmpeg-trac] #10594(ffmpeg:new): AMD VAAPI Driver does not support some wanted Ubuntu 22.04 LTS

[FFmpeg]

#10594: AMD VAAPI Driver does not support some wanted Ubuntu 22.04 LTS
-+-
 Reporter:  Mateo|Owner:  (none)
  Bohoquez   |
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  ffmpeg
  Version:  git-master   |   Resolution:
 Keywords:  VAAPI, No|   Blocked By:
  global header, packed sequence |
  headers|
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by Mateo Bohoquez):

 * version:  5.1.3 => git-master
 * component:  undetermined => ffmpeg

-- 
Ticket URL: 
FFmpeg 
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".

[FFmpeg-trac] #10594(undetermined:new): AMD VAAPI Driver does not support some wanted Ubuntu 22.04 LTS

[FFmpeg]

#10594: AMD VAAPI Driver does not support some wanted Ubuntu 22.04 LTS
-+-
 Reporter:  Mateo| Type:  defect
  Bohoquez   |
   Status:  new  | Priority:  normal
Component:   |  Version:  5.1.3
  undetermined   |
 Keywords:  VAAPI, No|   Blocked By:
  global header, packed sequence |
  headers|
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 **Summary of the bug:**

 I get this **warn/error** but i can encode my video, however in hevc_vaapi
 i get visual gliches while play the video, and some smartphones cant
 reproduce the video.
 {{{
 [h264_vaapi @ 0x56248c107500] Driver does not support some wanted packed
 headers (wanted 0xd, found 0).
 [h264_vaapi @ 0x56248c107500] Driver does not support packed sequence
 headers, but a global header is requested.
 [h264_vaapi @ 0x56248c107500] No global header will be written: this may
 result in a stream which is not usable for some purposes (e.g. not muxable
 to some containers).
 }}}


 How to reproduce (with my GPU AMD RX6750 XT):

 {{{
 LIBVA_DRIVER_NAME=radeonsi # for AMD
 allow_rgb10_configs=false # Video decoding corruption or distortion with
 AMDGPU driver
 ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD129 -i
 "/media/noe/WinterOS:
 Rev09/Users/NoeXVanitasXJunk/LinuxCaches/Davinci/Renders/14.mov" -vf
 'format=nv12,hwupload'  -c:v h264_vaapi -b:v 2.7M "/media/noe/WinterOS:
 Rev09/Users/NoeXVanitasXJunk/LinuxCaches/Davinci/Renders/14_h264Otri.mp4"
 -y
 }}}



 Complete output
 {{{
 ffmpeg version N-112184-g8fa83ad70f Copyright (c) 2000-2023 the FFmpeg
 developers
   built with gcc 11 (Ubuntu 11.4.0-1ubuntu1~22.04)
   configuration: --prefix=/home/noe/ffmpeg_build --pkg-config-
 flags=--static --extra-cflags=-I/home/noe/ffmpeg_build/include --extra-
 ldflags=-L/home/noe/ffmpeg_build/lib --extra-libs='-lpthread -lm' --ld=g++
 --bindir=/home/noe/bin --enable-gpl --enable-gnutls --enable-libaom
 --enable-libass --enable-libfreetype --enable-libmp3lame --enable-libopus
 --enable-libdav1d --enable-libvorbis --enable-libvpx --enable-libx264
 --enable-libx265 --enable-vaapi --enable-amf --target-os=linux --enable-
 opengl --enable-opencl --enable-nonfree --enable-libwebp --enable-
 libopenjpeg --enable-libpulse --enable-frei0r --enable-libbs2b --enable-
 libcdio --enable-librubberband --enable-libspeex --enable-libtheora
 --enable-libfontconfig --enable-libfribidi --enable-libxml2 --enable-
 libxvid --enable-libsmbclient --enable-version3 --enable-libv4l2 --enable-
 libvidstab --enable-libcaca --enable-libopenmpt --enable-libmodplug
 --enable-libgme --enable-libopencore-amrwb --enable-libsnappy --enable-
 libmysofa --enable-libshine --enable-libopencore-amrnb --enable-libtwolame
 --enable-libvo-amrwbenc --enable-libflite --enable-libsoxr --enable-ladspa
   libavutil  58. 25.100 / 58. 25.100
   libavcodec 60. 27.100 / 60. 27.100
   libavformat60. 13.100 / 60. 13.100
   libavdevice60.  2.101 / 60.  2.101
   libavfilter 9. 11.100 /  9. 11.100
   libswscale  7.  3.100 /  7.  3.100
   libswresample   4. 11.100 /  4. 11.100
   libpostproc57.  2.100 / 57.  2.100
 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/media/noe/WinterOS:
 Rev09/Users/NoeXVanitasXJunk/LinuxCaches/Davinci/Renders/14.mov':
   Metadata:
 major_brand : qt
 minor_version   : 512
 compatible_brands: qt
 creation_time   : 2023-09-26T17:35:40.00Z
 encoder : Blackmagic Design DaVinci Resolve Studio
   Duration: 00:45:34.63, start: 0.00, bitrate: 21029 kb/s
   Stream #0:0[0x1]: Video: dnxhd (DNXHR LB) (AVdh / 0x68645641),
 yuv422p(tv, bt709), 720x1280, 19604 kb/s, SAR 1:1 DAR 9:16, 30 fps, 30
 tbr, 15360 tbn (default)
 Metadata:
   creation_time   : 2023-09-26T17:35:40.00Z
   handler_name: VideoHandler
   vendor_id   :
   encoder : DNxHR LB
   timecode: 01:00:00:00
   Stream #0:1[0x2]: Audio: pcm_s16le (lpcm / 0x6D63706C), 44100 Hz,
 stereo, s16, 1411 kb/s (default)
 Metadata:
   creation_time   : 2023-09-26T17:35:40.00Z
   handler_name: SoundHandler
   vendor_id   : [0][0][0][0]
   Stream #0:2[0x3](eng): Data: none (tmcd / 0x64636D74) (default)
 Metadata:
   creation_time   : 2023-09-26T17:35:40.00Z
   handler_name: TimeCodeHandler
   timecode: 01:00:00:00
 Stream mapping:
   Stream #0:0 -> #0:0 (dnxhd (native) -> h264 (h264_vaapi))
   Stream #0:1 -> #0:1 (pcm_s16le (native) -> aac (native))
 Press [q] to stop, [?] for help
 [h264_vaapi @ 0x56248c107500] Driver does not support some wanted packed
 headers 

Re: [FFmpeg-trac] #9673(undetermined:closed): ffmpeg not reading color information from JPEG ICC profile

[FFmpeg]

#9673: ffmpeg not reading color information from JPEG ICC profile
-+-
 Reporter:  Cosmin   |Owner:  haasn
  Stejerean  |
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
 |  undetermined
  Version:  unspecified  |   Resolution:  fixed
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by haasn):

 > The ICC profile reading/writing is already behind a flag so I think it's
 low risk to update this to be more compatible with things that we are
 likely to find in the wild (and this Apple P3 profile seems quite common).
 It sounds like ICCv4 not using D50 is a bug, and it seems like it could be
 a safe fallback to assume D50 when reading ICCv4 (ignore the whitepoint if
 it's not D50 in v4 as not being spec compliant).

 Yes, that's actually a good idea. I'll try and implement this tomorrow.
-- 
Ticket URL: 
FFmpeg 
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] #10593(undetermined:new): magicyuv: support 14-bit rgb(a)

[FFmpeg]

#10593: magicyuv: support 14-bit rgb(a)
-+-
 Reporter:  ami_stuff|Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  undetermined
  Version:  unspecified  |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by ami_stuff):

 * Attachment "magicyuv_14bit_rgba.avi" added.

-- 
Ticket URL: 
FFmpeg 
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] #10593(undetermined:new): magicyuv: support 14-bit rgb(a)

[FFmpeg]

#10593: magicyuv: support 14-bit rgb(a)
-+-
 Reporter:  ami_stuff|Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  undetermined
  Version:  unspecified  |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by ami_stuff):

 * Attachment "magicyuv_14bit_rgb.avi" added.

-- 
Ticket URL: 
FFmpeg 
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".

[FFmpeg-trac] #10593(undetermined:new): magicyuv: support 14-bit rgb(a)

[FFmpeg]

#10593: magicyuv: support 14-bit rgb(a)
-+-
 Reporter:  ami_stuff| Type:  defect
   Status:  new  | Priority:  normal
Component:   |  Version:
  undetermined   |  unspecified
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 {{{
 ./ffmpeg -i magicyuv_14bit_rgb.avi
 ffmpeg version N-112164-gcb26b85953 Copyright (c) 2000-2023 the FFmpeg
 developers
   built with gcc 11 (Ubuntu 11.4.0-1ubuntu1~22.04)
   configuration:
   libavutil  58. 25.100 / 58. 25.100
   libavcodec 60. 27.100 / 60. 27.100
   libavformat60. 13.100 / 60. 13.100
   libavdevice60.  2.101 / 60.  2.101
   libavfilter 9. 11.100 /  9. 11.100
   libswscale  7.  3.100 /  7.  3.100
   libswresample   4. 11.100 /  4. 11.100
 [avi @ 0x5643c30ca580] Could not find codec parameters for stream 0
 (Video: none (M4RG / 0x4752344D), none, 640x480): unknown codec
 Consider increasing the value for the 'analyzeduration' (0) and
 'probesize' (500) options
 Input #0, avi, from 'magicyuv_14bit_rgb.avi':
   Metadata:
 title   : Planet Earth II S01E01 4K
 software: Lavf60.13.100
   Duration: 00:00:00.13, start: 0.00, bitrate: 124727 kb/s
   Stream #0:0: Video: none (M4RG / 0x4752344D), none, 640x480, 23.98 fps,
 23.98 tbr, 23.98 tbn
 At least one output file must be specified
 }}}


 {{{
 ./ffmpeg -i magicyuv_14bit_rgba.avi
 ffmpeg version N-112164-gcb26b85953 Copyright (c) 2000-2023 the FFmpeg
 developers
   built with gcc 11 (Ubuntu 11.4.0-1ubuntu1~22.04)
   configuration:
   libavutil  58. 25.100 / 58. 25.100
   libavcodec 60. 27.100 / 60. 27.100
   libavformat60. 13.100 / 60. 13.100
   libavdevice60.  2.101 / 60.  2.101
   libavfilter 9. 11.100 /  9. 11.100
   libswscale  7.  3.100 /  7.  3.100
   libswresample   4. 11.100 /  4. 11.100
 [avi @ 0x55c79c67c580] Could not find codec parameters for stream 0
 (Video: none (M4RA / 0x4152344D), none, 640x480): unknown codec
 Consider increasing the value for the 'analyzeduration' (0) and
 'probesize' (500) options
 Input #0, avi, from 'magicyuv_14bit_rgba.avi':
   Metadata:
 title   : Planet Earth II S01E01 4K
 software: Lavf60.13.100
   Duration: 00:00:00.13, start: 0.00, bitrate: 132147 kb/s
   Stream #0:0: Video: none (M4RA / 0x4152344D), none, 640x480, 23.98 fps,
 23.98 tbr, 23.98 tbn
 At least one output file must be specified
 }}}
-- 
Ticket URL: 
FFmpeg 
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] #10440(undetermined:new): Segmentation fault (core dumped) when trying to generate hls output from .mp4 file

[FFmpeg]

#10440: Segmentation fault (core dumped) when trying to generate hls output from
.mp4 file
-+-
 Reporter:   |Owner:  (none)
  ffmpeg.golden  |
 Type:  defect   |   Status:  new
 Priority:  important|Component:
 |  undetermined
  Version:  6.0  |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by piusbnsl):

 I am getting the same error. Following is the command I used -

 {{{
 ffmpeg \
 -report \
 -i fireship-rust.mp4 \
 -i fireship-rust.vtt \
 -filter_complex
 
"[0:v]scale=1280:720[vyuv];[vyuv]split=2[v0][vtemp1];[vtemp1]scale=w=960:h=540[v1];"
 \
 -map "[v0]" -map "[v1]" -map 0:a -map 0:a -map 1:s -map 1:s \
 -b:v:0 3500k -maxrate:v:0 3500k -bufsize:v:0 3500k \
 -b:v:1 1690k -maxrate:v:1 1690k -bufsize:v:1 1690k \
 -b:a 128k \
 -c:s webvtt \
 -c:v libx264 \
 -c:a aac \
 -f hls \
 -var_stream_map "v:0,a:0,s:0,sgroup:subtitle v:1,a:1,s:1,sgroup:subtitle"
 \
 -master_pl_name master.m3u8 \
 stream_%v/stream.m3u8
 }}}

 I am getting similar logs as above. I have pasted the whole report here -
 https://pastebin.com/mfqL24EZ

 I have tried multiple variations of the above command and am not able to
 get the subtitles working with multiple streams. It works fine for single
 stream -

 {{{
 ffmpeg \
 -i fireship-rust.mp4 \
 -i fireship-rust.vtt \
 -filter_complex "[0:v]scale=1280:720[v0];" \
 -map "[v0]" -map 0:a -map 1:s \
 -b:v:0 3500k -maxrate:v:0 3500k -bufsize:v:0 3500k \
 -b:a 128k \
 -c:s webvtt \
 -c:v libx264 \
 -c:a aac \
 -f hls \
 -var_stream_map "v:0,a:0,s:0,sgroup:subtitle" \
 -master_pl_name master.m3u8 \
 stream_%v/stream.m3u8
 }}}

 or

 {{{
 ffmpeg \
 -i fireship-rust.mp4 \
 -i fireship-rust.vtt \
 -filter_complex
 
"[0:v]scale=1280:720[vyuv];[vyuv]split=2[v0][vtemp1];[vtemp1]scale=w=960:h=540[v1];"
 \
 -map "[v0]" -map 0:a -map 1:s \
 -b:a 128k \
 -c:s webvtt \
 -c:v libx264 \
 -c:a aac \
 -f hls \
 -var_stream_map "v:0,a:0,s:0,sgroup:subtitle" \
 -master_pl_name master.m3u8 \
 -hls_time 2 \
 -hls_segment_filename stream_%v/data%03d.ts \
 stream_%v/stream.m3u8 \
 -map "[v1]" -map 0:a \
 output.mkv
 }}}


 Let me know if you need my help anyhow debugging this.
-- 
Ticket URL: 
FFmpeg 
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] #10150(undetermined:open): Variable framerate with a maximum value

[FFmpeg]

#10150: Variable framerate with a maximum value
-+-
 Reporter:  Zoont|Owner:  (none)
 Type:  defect   |   Status:  open
 Priority:  important|Component:
 |  undetermined
  Version:  git-master   |   Resolution:
 Keywords:  fps  |   Blocked By:
  framerate vfr cfr vsync|
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by Tynach):

 Replying to [comment:2 elenril]:
 > Are you entirely sure this worked as you wanted? I see no indication
 that -fpsmax was ever intended to work with VFR. As per the manpage:
 >  -fpsmax[:stream_specifier] fps (output,per-stream)
 >Set maximum frame rate (Hz value, fraction or abbreviation).
 >
 >Clamps output frame rate when output framerate is auto-set and is
 higher than this value. Useful in batch processing or when input framerate
 is wrongly detected as very high.  It cannot be set together with "-r". It
 is ignored during streamcopy.
 >
 > In other words, it affects the way the output framerate is selected, but
 there still is a fixed output framerate.

 I used to do the same thing, using `-r` and `-vsync vfr` together. I
 thought it was a nifty undocumented feature. Also, elenril, while I'm not
 the same person as the one who opened this bug, I ''have'' extensively
 tested it, and it ''did'' used to do what is described (allow a variable
 framerate with a maximum output framerate).

 Personally, I think that commit should be completely reverted, and instead
 the documentation changed to reflect the actual behavior. The commit in
 question only provides one reason for their change, and that is that the
 behavior didn't match the documentation.. But this is **clearly** a
 regression in functionality.

 Either revert the commit and make a different commit that updates the
 documentation, or add another flag that provides the old behavior. Seeing
 as `-fpsmax` already exists and sounds like it ought to do what used to be
 possible, and according to Zoont used to also provide this desired
 behavior, then if it's decided ''not'' to fully revert the offending
 commit then I propose that `-fpsmax` is modified to allow the previous
 behavior.

 Also, for what it's worth, I documented this working back in 2016 by
 writing [https://superuser.com/a/1073260/184072 this Super User answer].
 Given it has 35 upvotes, it's almost certain that there are other people
 who depend on this functionality, or at least have used it at some point
 in the past.

 In regards to the original reason why the change was made.. There are
 PLENTY of undocumented behaviors in FFmpeg, including undocumented command
 line parameters. Looking at the commit in question, it seems like the
 tests had to be changed in order to pass.. That should have been a red
 flag that the changes shouldn't have been made to begin with. if tests
 didn't need to be changed for this commit to pass them, then the test
 changes should have been a separate commit.
-- 
Ticket URL: 
FFmpeg 
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] #10581(undetermined:new): notchlc: wrong colors with avi's variant of codec

[FFmpeg]

#10581: notchlc: wrong colors with avi's variant of codec
-+-
 Reporter:  ami_stuff|Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  undetermined
  Version:  unspecified  |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by Elon Musk):

 as expected, this should not be the case here. Thus i consider notchlc
 encoding in avi broken from reference implementation, (to get better
 colors use -vf swapuv), because codec bitstream should be same in every
 container.
-- 
Ticket URL: 
FFmpeg 
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] #9673(undetermined:closed): ffmpeg not reading color information from JPEG ICC profile

[FFmpeg]

#9673: ffmpeg not reading color information from JPEG ICC profile
-+-
 Reporter:  Cosmin   |Owner:  haasn
  Stejerean  |
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
 |  undetermined
  Version:  unspecified  |   Resolution:  fixed
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by Balling):

 >ignore the whitepoint if it's not D50 in v4 as not being spec compliant

 Yep, indeed any white point chromatically adapted to D50 is just D50. At
 least if we are talking Plancian locus. But is that the case with DCI
 white point, that is slightly remobed from Plancian locus?
-- 
Ticket URL: 
FFmpeg 
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] #10590(undetermined:closed): magicyuv: invalid reads with valid 12-bit RGBA file

[FFmpeg]

#10590: magicyuv: invalid reads with valid 12-bit RGBA file
-+-
 Reporter:  ami_stuff|Owner:  (none)
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
 |  undetermined
  Version:  unspecified  |   Resolution:  fixed
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by Elon Musk):

 * status:  new => closed
 * resolution:   => fixed

-- 
Ticket URL: 
FFmpeg 
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] #10592(undetermined:new): piped input partial file error

[FFmpeg]

#10592: piped input partial file error
+
 Reporter:  Mark|Owner:  (none)
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  undetermined
  Version:  6.0 |   Resolution:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+
Comment (by Elon Musk):

 for mp4 one usually needs to seek to end and than to beginning and that
 can not work via pipe.
 Not really ffmpeg fault but of mp4 file.
-- 
Ticket URL: 
FFmpeg 
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] #10592(undetermined:new): piped input partial file error

[FFmpeg]

#10592: piped input partial file error
+
 Reporter:  Mark|Owner:  (none)
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  undetermined
  Version:  6.0 |   Resolution:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+
Changes (by Mark):

 * Attachment "piped_input_fail.mp4" added.

-- 
Ticket URL: 
FFmpeg 
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".

[FFmpeg-trac] #10592(undetermined:new): piped input partial file error

[FFmpeg]

#10592: piped input partial file error
--+--
 Reporter:  Mark  | Type:  defect
   Status:  new   | Priority:  normal
Component:  undetermined  |  Version:  6.0
 Keywords:|   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+--
 Summary of the bug:

 ffmpeg failes to read file from the piped input

 ffmpeg -i - out.mp3 < in.mp4 # it works perfectly

 cat in.mp4 | ffmpeg -i - out.mp3 # fails with the error below.

 Why do I need it:
 I'm trying to convert to pcm_s16le file while downloading it from the
 internet. And this is the simplest example to reproduce the issue. cat is
 the replacement of wget/curl.

 How to reproduce:
 {{{
 % cat in.mp4 | ffmpeg -i - out.mp3
 ffmpeg version 6.0 Copyright (c) 2000-2023 the FFmpeg developers
   built with Apple clang version 14.0.3 (clang-1403.0.22.14.1)
   configuration: --prefix=/usr/local/Cellar/ffmpeg/6.0_1 --enable-shared
 --enable-pthreads --enable-version3 --cc=clang --host-cflags= --host-
 ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom
 --enable-libaribb24 --enable-libbluray --enable-libdav1d --enable-
 libmp3lame --enable-libopus --enable-librav1e --enable-librist --enable-
 librubberband --enable-libsnappy --enable-libsrt --enable-libsvtav1
 --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-
 libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-
 libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-lzma
 --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-
 libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-
 libopenjpeg --enable-libspeex --enable-libsoxr --enable-libzmq --enable-
 libzimg --disable-libjack --disable-indev=jack --enable-videotoolbox
 --enable-audiotoolbox
   libavutil  58.  2.100 / 58.  2.100
   libavcodec 60.  3.100 / 60.  3.100
   libavformat60.  3.100 / 60.  3.100
   libavdevice60.  1.100 / 60.  1.100
   libavfilter 9.  3.100 /  9.  3.100
   libswscale  7.  1.100 /  7.  1.100
   libswresample   4. 10.100 /  4. 10.100
   libpostproc57.  1.100 / 57.  1.100
 [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7fe6f5704b80] stream 0, offset 0x2c: partial
 file
 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'fd:':
   Metadata:
 major_brand : isom
 minor_version   : 512
 compatible_brands: isomiso2mp41
 encoder : Lavf60.3.100
   Duration: 00:00:08.00, start: 0.00, bitrate: N/A
   Stream #0:0[0x1](eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, mono,
 fltp, 69 kb/s (default)
 Metadata:
   handler_name: SoundHandle
   vendor_id   : [0][0][0][0]
 Stream mapping:
   Stream #0:0 -> #0:0 (aac (native) -> mp3 (libmp3lame))
 [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7fe6f5704b80] stream 0, offset 0x2c: partial
 file
 Error demuxing input file 0: Invalid data found when processing input
 fd:: Invalid data found when processing input
 Output #0, mp3, to 'out.mp3':
   Metadata:
 major_brand : isom
 minor_version   : 512
 compatible_brands: isomiso2mp41
 TSSE: Lavf60.3.100
   Stream #0:0(eng): Audio: mp3, 48000 Hz, mono, fltp (default)
 Metadata:
   handler_name: SoundHandle
   vendor_id   : [0][0][0][0]
   encoder : Lavc60.3.100 libmp3lame
 size=   0kB time=-577014:32:22.77 bitrate=N/A speed=N/Aed=N/A
 video:0kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB
 muxing overhead: unknown
 Output file is empty, nothing was encoded (check -ss / -t / -frames
 parameters if used)
 }}}
-- 
Ticket URL: 
FFmpeg 
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] #7621(avformat:open): Add .avif support (AV1 Image File Format

[FFmpeg]

#7621: Add .avif support (AV1 Image File Format
-+-
 Reporter:  Ewout|Owner:  Vignesh
 |  Venkatasubramanian
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  mov  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by Vignesh Venkatasubramanian):

 Replying to [comment:30 hydra]:
 > Just a thought ...
 > https://trac.ffmpeg.org/ticket/6521#comment:21
 >
 > which asks about any possibility of ffmpeg supporting libheif
 > ​https://github.com/strukturag/libheif

 The ffmpeg MOV parser (and the muxer) has the capability to handle HEIF
 with minimal changes. I have a patch locally for parsing HEIF. i will try
 to clean it up and upload it.

 I don't think we need to add a seperate dependency for something that
 ffmpeg almost already natively supports. :)
-- 
Ticket URL: 
FFmpeg 
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] #9673(undetermined:closed): ffmpeg not reading color information from JPEG ICC profile

[FFmpeg]

#9673: ffmpeg not reading color information from JPEG ICC profile
-+-
 Reporter:  Cosmin   |Owner:  haasn
  Stejerean  |
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
 |  undetermined
  Version:  unspecified  |   Resolution:  fixed
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by Cosmin Stejerean):

 The ICC profile reading/writing is already behind a flag so I think it's
 low risk to update this to be more compatible with things that we are
 likely to find in the wild (and this Apple P3 profile seems quite common).
 It sounds like ICCv4 not using D50 is a bug, and it seems like it could be
 a safe fallback to assume D50 when reading ICCv4 (ignore the whitepoint if
 it's not D50 in v4 as not being spec compliant).
-- 
Ticket URL: 
FFmpeg 
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] #10591(avcodec:closed): -err_detect crccheck and explode+crccheck are broken for flac files

[FFmpeg]

#10591: -err_detect crccheck and explode+crccheck are broken for flac files
-+-
 Reporter:  Balling  |Owner:  (none)
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:  wontfix
 Keywords:  flac crc |   Blocked By:
  regression |
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by Balling):

 Why? Chrome uses explode, this means bad flac files will pass through. I
 did not notice that other issue, but that is worse.

 Of course it is more or less cosmetic, but still. Do you like dead log
 code?
-- 
Ticket URL: 
FFmpeg 
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] #10591(avcodec:closed): -err_detect crccheck and explode+crccheck are broken for flac files

[FFmpeg]

#10591: -err_detect crccheck and explode+crccheck are broken for flac files
-+-
 Reporter:  Balling  |Owner:  (none)
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:  wontfix
 Keywords:  flac crc |   Blocked By:
  regression |
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by Elon Musk):

 * status:  reopened => closed
 * resolution:   => wontfix

-- 
Ticket URL: 
FFmpeg 
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] #9673(undetermined:closed): ffmpeg not reading color information from JPEG ICC profile

[FFmpeg]

#9673: ffmpeg not reading color information from JPEG ICC profile
-+-
 Reporter:  Cosmin   |Owner:  haasn
  Stejerean  |
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
 |  undetermined
  Version:  unspecified  |   Resolution:  fixed
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by Balling):

 DCI-P3-D65 from https://www.color.org/chardata/rgb/DCIP3.xalter is 2.6
 gamma. Did you even look into rTRC of it? It is not really relevant, is
 it... Its Red Z is -0.00081, so negative, so noncompliant. **Why would you
 think ICC pages will have no bugs? LOL.
 **
 >Except that the media white point in the ICC profile is correct (D50),
 whereas the one in the Apple profile is incorrect (D65).

 So? I told you that. Who cares. It is not used for color managment. ICCV4
 is always USING D50.

 >instead of the (correct) "Inverse(chromaticAdaptationTag) *
 mediaWhitePointTag

 No. ICCV4 is always USING D50. WHAT?? You do not need this and even chad
 is not used really, except to make negative Z of R positive.
-- 
Ticket URL: 
FFmpeg 
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] #10566(undetermined:closed): AV1 decoding with -hwaccel d3d11va performance issue

[FFmpeg]

#10566: AV1 decoding with -hwaccel d3d11va performance issue
-+-
 Reporter:  Evgeny   |Owner:  (none)
 Type:  enhancement  |   Status:  closed
 Priority:  normal   |Component:
 |  undetermined
  Version:  git-master   |   Resolution:  invalid
 Keywords:  av1  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by Evgeny):

 @arm64-v9a Thanks a lot for your answer. I just wondering why ffmpeg has
 different behavior for av1 and h264 decoder? I just found that AV1 decoder
 doesn't declare AV_CODEC_CAP_FRAME_THREADS in ff_av1_decoder, does it mean
 that av1 decoder doesn't support frame-level multithreading?
-- 
Ticket URL: 
FFmpeg 
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] #10591(avcodec:reopened): -err_detect crccheck and explode+crccheck are broken for flac files (was: -err_detect crccheck is again broken for flac files)

[FFmpeg]

#10591: -err_detect crccheck and explode+crccheck are broken for flac files
-+-
 Reporter:  Balling  |Owner:  (none)
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  flac crc |   Blocked By:
  regression |
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by Balling):

 * keywords:   => flac crc regression
 * summary:  -err_detect crccheck is again broken for flac files =>
 -err_detect crccheck and explode+crccheck are broken for flac files

-- 
Ticket URL: 
FFmpeg 
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] #9673(undetermined:closed): ffmpeg not reading color information from JPEG ICC profile

[FFmpeg]

#9673: ffmpeg not reading color information from JPEG ICC profile
-+-
 Reporter:  Cosmin   |Owner:  haasn
  Stejerean  |
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
 |  undetermined
  Version:  unspecified  |   Resolution:  fixed
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by haasn):

 So, I did some extensive reverse engineering of the Apple DCI-P3 profile
 and came to the following conclusions:

 1. They (accidentally?) used the D65 Chromatic Adaptation matrix for this
 profile (as would be correct for Display-P3)
 2. They then used this Chromatic Adaptation matrix on the (correct) DCI-P3
 primaries, resulting in the "correct" R/G/B Matrix columns. But, for some
 reason, Little-CMS does not correctly read these back out, probably
 because of the white point issue.
 3. They then encoded the *unadapted* white point (D65) into the media
 white point tag, which violates spec as you're supposed to encode the
 *adapted* white point (D50) instead. (See sections 6.2.3 and 6.3.2)

 So, the tl;dr here is that Apple made a mistake when creating this
 profile, and I can prove it. (It violates ICCv4 spec)

 For further information/cross verification, notice that the Apple DCI-P3
 profile almost matches the "DCI-P3-D65.icc" profile from ICC/color.org:

 Connection Space Illuminant : 0.9642 1 0.82491
 Chromatic Adaptation: 1.04791 0.02293 -0.0502 0.0296 0.99046
 -0.01707 -0.00925 0.01506 0.75179
 Red Matrix Column   : 0.51512 0.2412 -0.00105
 Green Matrix Column : 0.29198 0.69225 0.04189
 Blue Matrix Column  : 0.1571 0.06657 0.78407
 Media White Point   : 0.96419 1 0.82491

 Except that the media white point in the ICC profile is correct (D50),
 whereas the one in the Apple profile is incorrect (D65).

 This does, mean, however, that we could apply a simple work-around in
 principle: If the profile fails decoding, we can try a second time using
 the (incorrect) "mediaWhitePointTag" as the white point instead of the
 (correct) "chromaticAdaptationTag^-1 * mediaWhitePointTag". If that
 produces an exact match, return it.

 However, since this is a hack and a work-around for a broken profile, I'd
 rather hide it behind some sort of extra option or debug flag. I'll have
 to think about whether this is a preferred solution or not.

 Maybe you can work around it on your side instead, by detecting the
 profile e.g. by its "Profile Description" tag? What do you think?
-- 
Ticket URL: 
FFmpeg 
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] #10591(avcodec:reopened): -err_detect crccheck is again broken for flac files

[FFmpeg]

#10591: -err_detect crccheck is again broken for flac files
+
 Reporter:  Balling |Owner:  (none)
 Type:  defect  |   Status:  reopened
 Priority:  normal  |Component:  avcodec
  Version:  git-master  |   Resolution:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+
Changes (by Balling):

 * status:  closed => reopened
 * resolution:  invalid =>
 * version:  unspecified => git-master
 * component:  undetermined => avcodec

Comment:

 Before:

 {{{
 ffmpeg version git-2020-08-31-4a11a6f Copyright (c) 2000-2020 the FFmpeg
 developers
   built with gcc 10.2.1 (GCC) 20200805
   configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-
 fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-
 libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame
 --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg
 --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr
 --enable-libsrt --enable-libtheora --enable-libtwolame --enable-libvpx
 --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265
 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp
 --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvo-
 amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-
 libaom --enable-libgsm --enable-librav1e --enable-libsvtav1 --disable-
 w32threads --enable-libmfx --enable-ffnvcodec --enable-cuda-llvm --enable-
 cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2
 --enable-avisynth --enable-libopenmpt --enable-amf
   libavutil  56. 58.100 / 56. 58.100
   libavcodec 58.101.101 / 58.101.101
   libavformat58. 51.101 / 58. 51.101
   libavdevice58. 11.101 / 58. 11.101
   libavfilter 7. 87.100 /  7. 87.100
   libswscale  5.  8.100 /  5.  8.100
   libswresample   3.  8.100 /  3.  8.100
   libpostproc55.  8.100 / 55.  8.100
 Input #0, flac, from 'kvvrac.flac':
   Metadata:
 ARTIST  : Van Morrison
 Title   : See Me Through > Soldier Of Fortune > Thank You
 Falletin Me Be Mice Elf Agin > Burning Ground
 ALBUM   : Playhouse Theatre, Edinburgh, Scotland (1999-04-02)
 Date: 1999-04-02
 track   : 07
 comment : Encoded by FLAC v1.1.2a with FLAC Frontend v1.7.1;
 CD 2
   Duration: 00:17:55.21, start: 0.00, bitrate: 589 kb/s
 Stream #0:0: Audio: flac, 44100 Hz, stereo, s16
 Stream mapping:
   Stream #0:0 -> #0:0 (flac (native) -> pcm_s16le (native))
 Press [q] to stop, [?] for help
 Output #0, null, to 'pipe:':
   Metadata:
 ARTIST  : Van Morrison
 Title   : See Me Through > Soldier Of Fortune > Thank You
 Falletin Me Be Mice Elf Agin > Burning Ground
 ALBUM   : Playhouse Theatre, Edinburgh, Scotland (1999-04-02)
 Date: 1999-04-02
 track   : 07
 comment : Encoded by FLAC v1.1.2a with FLAC Frontend v1.7.1;
 CD 2
 encoder : Lavf58.51.101
 Stream #0:0: Audio: pcm_s16le, 44100 Hz, stereo, s16, 1411 kb/s
 Metadata:
   encoder : Lavc58.101.101 pcm_s16le
 [flac @ 01de24b1a380] CRC error at PTS 29583360
 size=N/A time=00:17:55.21 bitrate=N/A speed=2.17e+03x
 video:0kB audio:185222kB subtitle:0kB other streams:0kB global headers:0kB
 muxing overhead: unknown

 }}}

 After:


 {{{
 ffmpeg version N-111995-g5f8c113b75-20230909 Copyright (c) 2000-2023 the
 FFmpeg developers
   built with gcc 13.1.0 (crosstool-NG 1.25.0.196_227d99d)
   configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static
 --pkg-config=pkg-config --cross-prefix=x86_64-w64-mingw32- --arch=x86_64
 --target-os=mingw32 --enable-gpl --enable-version3 --disable-debug
 --enable-shared --disable-static --disable-w32threads --enable-pthreads
 --enable-iconv --enable-libxml2 --enable-zlib --enable-libfreetype
 --enable-libfribidi --enable-gmp --enable-lzma --enable-fontconfig
 --enable-libvorbis --enable-opencl --disable-libpulse --enable-libvmaf
 --disable-libxcb --disable-xlib --enable-amf --enable-libaom --enable-
 libaribb24 --enable-avisynth --enable-chromaprint --enable-libdav1d
 --enable-libdavs2 --disable-libfdk-aac --enable-ffnvcodec --enable-cuda-
 llvm --enable-frei0r --enable-libgme --enable-libkvazaar --enable-libass
 --enable-libbluray --enable-libjxl --enable-libmp3lame --enable-libopus
 --enable-librist --enable-libssh --enable-libtheora --enable-libvpx
 --enable-libwebp --enable-lv2 --enable-libvpl --enable-openal --enable-
 libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264
 

Re: [FFmpeg-trac] #10591(undetermined:closed): -err_detect crccheck is again broken for flac files

[FFmpeg]

#10591: -err_detect crccheck is again broken for flac files
-+-
 Reporter:  Balling  |Owner:  (none)
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
 |  undetermined
  Version:  unspecified  |   Resolution:  invalid
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by Elon Musk):

 * keywords:  flac crc regression =>
 * resolution:   => invalid
 * status:  new => closed
 * component:  avcodec => undetermined
 * version:  git-master => unspecified

Comment:

 Not proof of anything. Just some statements that have no hard evidence.
 If you knew how to check you would know that code at line 772 is still
 always executed.
-- 
Ticket URL: 
FFmpeg 
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".

[FFmpeg-trac] #10591(avcodec:new): -err_detect crccheck is again broken for flac files

[FFmpeg]

#10591: -err_detect crccheck is again broken for flac files
-+-
 Reporter:  Balling  | Type:  defect
   Status:  new  | Priority:  normal
Component:  avcodec  |  Version:  git-
 Keywords:  flac crc |  master
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 Summary of the bug: use https://files.catbox.moe/kvvrac.flac it was
 printing "CRC error at PTS 29583360" but it no longer warns about it.
 Regression of #2266 probably because of #9621. It is problematic that line
 
https://github.com/FFmpeg/FFmpeg/blob/56085e057ff2d2da180a5d56bdd1efd70d53e662/libavcodec/flacdec.c#L772
 is dead code now.
 How to reproduce:
 {{{
 % ffmpeg -err_detect crccheck -i https://files.catbox.moe/kvvrac.flac -f
 null -

 }}}
 Patches should be submitted to the ffmpeg-devel mailing list and not this
 bug tracker.
-- 
Ticket URL: 
FFmpeg 
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] #2266(avcodec:closed): support flac crcchecks

[FFmpeg]

#2266: support flac crcchecks
-+---
 Reporter:  dave rice|Owner:  (none)
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:  fixed
 Keywords:  flac crc |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---
Comment (by Balling):

 >#9621 sample flac file decode same MD5 hash as reference flac decoder.

 As I said.
-- 
Ticket URL: 
FFmpeg 
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] #2266(avcodec:closed): support flac crcchecks

[FFmpeg]

#2266: support flac crcchecks
-+---
 Reporter:  dave rice|Owner:  (none)
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:  fixed
 Keywords:  flac crc |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---
Comment (by Elon Musk):

 #9621 sample flac file decode same MD5 hash as reference flac decoder.

 If you have extraordinary proof for extraordinary claim than by all means
 open new ticket.

 If you want consulting help, visit http://ffmpeg.org/consulting.html
-- 
Ticket URL: 
FFmpeg 
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] #2266(avcodec:closed): support flac crcchecks

[FFmpeg]

#2266: support flac crcchecks
-+---
 Reporter:  dave rice|Owner:  (none)
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:  fixed
 Keywords:  flac crc |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---
Comment (by Balling):

 >Before you would get sometimes invalid data from fully valid .flac files.

 #9621 was valid file that flac.exe accepts no problem, but you broke this
 issue, I even mentioned


 >I think we are not going to validate crc16 by default

 So not by default we still will. Just like this "verified with the
 AV_EF_CRCCHECK flag":
 
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20230809174657.76-1-tcchlis...@gmail.com/


 By the way, I have a question. ​https://files.catbox.moe/kvvrac.flac is a
 file from torrents (you can find it with Btdigg). Can you tell me why is
 it corrupted? Is it possible to bruteforce and restore it?


 Also, I do not get it why cannot I reopen old issues. It is common to do
 that when issue regresses in other projects.
-- 
Ticket URL: 
FFmpeg 
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] #10492(undetermined:open): scale_vt does not seems to work correctly

[FFmpeg]

#10492: scale_vt does not seems to work correctly
-+-
 Reporter:  Paul |Owner:
  Pacifico   |  quinkblack
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:
 |  undetermined
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by Paul Pacifico):

 It works great now, thanks!
-- 
Ticket URL: 
FFmpeg 
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".