Re: [FFmpeg-trac] #9814(undetermined:closed): time_scale / num_units_in_tick is not infinite precision

[FFmpeg]

#9814: time_scale / num_units_in_tick is not infinite precision
-+-
 Reporter:  Balling  |Owner:  (none)
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:
 |  undetermined
  Version:  git-master   |   Resolution:  invalid
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+-
Changes (by Elon Musk):

 * status:  open => closed
 * resolution:   => invalid

Comment:

 Issue is that your timebase is generic one that can not reproduce your fps
 perfectly, and .h264 does not store pts or timebase at all.

 ffmpeg -i example.h264 -vf settb=1001/3,vfrdet -f null -

 This shows that file is "CFR", but that is meaningless as format never
 store timestamps or timebase, its just put by ffmpeg code so it can
 process it somehow.
-- 
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] #7395(avformat:open): DASH demuxing error "unterminated entity reference" due to ampersand in URL

[FFmpeg]

#7395: DASH demuxing error "unterminated entity reference" due to ampersand in 
URL
-+-
 Reporter:  Starchild|Owner:  (none)
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  dash |   Blocked By:
  regression |
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by gorilla.maguila):

 * Attachment "dash.mpd" added.

 MPD file with & in BaseURL
-- 
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] #7395(avformat:open): DASH demuxing error "unterminated entity reference" due to ampersand in URL

[FFmpeg]

#7395: DASH demuxing error "unterminated entity reference" due to ampersand in 
URL
-+-
 Reporter:  Starchild|Owner:  (none)
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  dash |   Blocked By:
  regression |
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by gorilla.maguila):

 The bug is still present in latest git:


 {{{
 $ ffplay -allowed_extensions ALL -loglevel debug dash.mpd
 ffplay version N-109662-g2c3107c3e9 Copyright (c) 2003-2023 the FFmpeg
 developers
   built with gcc 12.2.1 (GCC) 20230111
   configuration: --prefix=/usr --disable-debug --disable-static --disable-
 stripping --enable-amf --enable-avisynth --enable-cuda-llvm --enable-lto
 --enable-fontconfig --enable-gmp --enable-gnutls --enable-gpl --enable-
 ladspa --enable-libaom --enable-libass --enable-libbluray --enable-
 libdav1d --enable-libdrm --enable-libfreetype --enable-libfribidi
 --enable-libgsm --enable-libiec61883 --enable-libjack --enable-libmfx
 --enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb
 --enable-libopencore_amrwb --enable-libopenjpeg --enable-libopus --enable-
 libpulse --enable-librav1e --enable-librsvg --enable-libsoxr --enable-
 libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-
 libtheora --enable-libv4l2 --enable-libvidstab --enable-libvmaf --enable-
 libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-
 libx265 --enable-libxcb --enable-libxml2 --enable-libxvid --enable-libzimg
 --enable-nvdec --enable-nvenc --enable-shared --enable-version3
   libavutil  57. 44.100 / 57. 44.100
   libavcodec 59. 57.100 / 59. 57.100
   libavformat59. 36.100 / 59. 36.100
   libavdevice59.  8.101 / 59.  8.101
   libavfilter 8. 54.100 /  8. 54.100
   libswscale  6.  8.112 /  6.  8.112
   libswresample   4.  9.100 /  4.  9.100
   libpostproc56.  7.100 / 56.  7.100
 Initialized opengl renderer.
 [NULL @ 0x7fa2b8000c80] Opening 'dash.mpd' for reading
 [file @ 0x7fa2b8001580] Setting default whitelist 'file,crypto,data'
 [dash @ 0x7fa2b8000c80] Format dash probed with size=2048 and score=100
 dash.mpd:-1: error : unterminated entity reference
 
ccb=1-7&_nc_sid=5aebc0&efg=eyJ2ZW5jb2RlX3RhZyI6ImRhc2hfcjJfYXZjX2dlbjFhdmNfbGNfcTQwX2ZyYWdfMl92aWRlbyJ9&_nc_ohc=gXFNqgRhAcwAX8Yb-D0&_nc_ht=video.fleu1-1.fna&edm
 =AGo2L-
 IE&oh=00_AfDMoCt5QVQN33LvqnQlS71aelYjHdt_PPdK5BziM80XIw&oe=63D6955E
 error : unterminated entity reference
 
ccb=1-7&_nc_sid=5aebc0&efg=eyJ2ZW5jb2RlX3RhZyI6ImRhc2hfcjJfYXZjX2dlbjFhdmNfbGNfcTQwX2ZyYWdfMl92aWRlbyJ9&_nc_ohc=gXFNqgRhAcwAX8Yb-D0&_nc_ht=video.fleu1-1.fna&edm
 =AGo2L-
 IE&oh=00_AfDMoCt5QVQN33LvqnQlS71aelYjHdt_PPdK5BziM80XIw&oe=63D6955E/
 dash.mpd:-1: error : unterminated entity reference
 
ccb=1-7&_nc_sid=5aebc0&efg=eyJ2ZW5jb2RlX3RhZyI6ImRhc2hfcjJfYXZjX2dlbjFhdmNfbGNfcTUwX2ZyYWdfMl92aWRlbyJ9&_nc_ohc=6f9UIoVRzpMAX9M_6S_&_nc_ht=video.fleu1-2.fna&edm
 =AGo2L-
 IE&oh=00_AfAVIx_3CNuMDq0Q6O_jQ1gU7rZGD1qjkS9Sn4f3I6ekNg&oe=63D6DE1E
 error : unterminated entity reference
 
ccb=1-7&_nc_sid=5aebc0&efg=eyJ2ZW5jb2RlX3RhZyI6ImRhc2hfcjJfYXZjX2dlbjFhdmNfbGNfcTUwX2ZyYWdfMl92aWRlbyJ9&_nc_ohc=6f9UIoVRzpMAX9M_6S_&_nc_ht=video.fleu1-2.fna&edm
 =AGo2L-
 IE&oh=00_AfAVIx_3CNuMDq0Q6O_jQ1gU7rZGD1qjkS9Sn4f3I6ekNg&oe=63D6DE1E/
 dash.mpd:-1: error : unterminated entity reference
 
ccb=1-7&_nc_sid=5aebc0&efg=eyJ2ZW5jb2RlX3RhZyI6ImRhc2hfcjJfYXZjX2dlbjFhdmNfbGNfcTYwX2ZyYWdfMl92aWRlbyJ9&_nc_ohc
 =SOsmeiEVSywAX-p9YlN&_nc_ht=video.fleu1-1.fna&edm=AGo2L-
 IE&oh=00_AfANHbgTW4WLZubbDDBk5afYfMjNLWu9jSpsSRjzKv6iVQ&oe=63D59A7E
 error : unterminated entity reference
 
ccb=1-7&_nc_sid=5aebc0&efg=eyJ2ZW5jb2RlX3RhZyI6ImRhc2hfcjJfYXZjX2dlbjFhdmNfbGNfcTYwX2ZyYWdfMl92aWRlbyJ9&_nc_ohc
 =SOsmeiEVSywAX-p9YlN&_nc_ht=video.fleu1-1.fna&edm=AGo2L-
 IE&oh=00_AfANHbgTW4WLZubbDDBk5afYfMjNLWu9jSpsSRjzKv6iVQ&oe=63D59A7E/
 dash.mpd:-1: error : unterminated entity reference
 
ccb=1-7&_nc_sid=5aebc0&efg=eyJ2ZW5jb2RlX3RhZyI6ImRhc2hfcjJfYXZjX2dlbjFhdmNfbGNfcTcwX2ZyYWdfMl92aWRlbyJ9&_nc_ohc
 =32rdvxB-5cUAX8YK0s3&_nc_ht=video.fleu1-1.fna&edm=AGo2L-
 IE&oh=00_AfDthNfPzYihPAVrPXm9Xy_hds7G82_bB8g8bVS2cFAoZg&oe=63D72EFC
 error : unterminated entity reference
 
ccb=1-7&_nc_sid=5aebc0&efg=eyJ2ZW5jb2RlX3RhZyI6ImRhc2hfcjJfYXZjX2dlbjFhdmNfbGNfcTcwX2ZyYWdfMl92aWRlbyJ9&_nc_ohc
 =32rdvxB-5cUAX8YK0s3&_nc_ht=video.fleu1-1.fna&edm=AGo2L-
 IE&oh=00_AfDthNfPzYihPAVrPXm9Xy_hds7G82_bB8g8bVS2cFAoZg&oe=63D72EFC/
 dash.mpd:-1: error : unterminated entity reference
 
ccb=1-7&_nc_sid=5aebc0&efg=eyJ2ZW5jb2RlX3RhZyI6ImRhc2hf

Re: [FFmpeg-trac] #9814(undetermined:reopened): time_scale / num_units_in_tick is not infinite precision

[FFmpeg]

#9814: time_scale / num_units_in_tick is not infinite precision
-+-
 Reporter:  Balling  |Owner:  (none)
 Type:  enhancement  |   Status:  reopened
 Priority:  wish |Component:
 |  undetermined
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+-
Changes (by Balling):

 * priority:  normal => wish
 * status:  closed => reopened
 * resolution:  invalid =>
 * type:  defect => enhancement

Comment:

 >Issue is that your timebase is generic one that can not reproduce your
 fps perfectly

 I need 30k tbn, '''not 1200k''' tbn BY DEFAULT. Nice that you understand.
 Changing to feature request.


 Why does it report


 {{{
 [mp4 @ 022d9775a040] Timestamps are unset in a packet for stream 0.
 This is deprecated and will stop working in the future. Fix your code to
 set the timestamps properly

 }}}

 That is just strange.


 >and .h264 does not store pts or timebase at all.

 It does have timing SEI, but not in my sample. Anyway, it sets
 fixed_frame_rate_flag, yet after this genius remux it has CFR with a
 different frame rate. Like how strange is that.
-- 
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|
-+-
Changes (by Balling):

 * status:  new => open

Comment:

 I propose to introduce -allowrvfr to bypass



 {{{
 av_log(NULL, AV_LOG_FATAL, "One of -r/-fpsmax was specified "
"together a non-CFR -vsync/-fps_mode. This is
 contradictory.\n");
 }}}
-- 
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] #9814(undetermined:reopened): time_scale / num_units_in_tick is not infinite precision

[FFmpeg]

#9814: time_scale / num_units_in_tick is not infinite precision
-+-
 Reporter:  Balling  |Owner:  (none)
 Type:  enhancement  |   Status:  reopened
 Priority:  wish |Component:
 |  undetermined
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+-
Comment (by Balling):

 >Issue is that your timebase is generic one

 But we have fixed_frame_rate_flag set. So in reality we can assume it is
 CFR and THAT IS WHAT mov/mp4 muxer does. It sets '''Frame rate mode:
 Constant'''. Okay? Yet, because of bad code somewhere, it does paste 29.97
 instead of 29.97002997. Okay?? This is what was happening when drop-frame
 timecode!

 That is why I said

 >For that you need to increase 3/1001 precision.
-- 
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] #7395(avformat:open): DASH demuxing error "unterminated entity reference" due to ampersand in URL

[FFmpeg]

#7395: DASH demuxing error "unterminated entity reference" due to ampersand in 
URL
-+-
 Reporter:  Starchild|Owner:  (none)
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  dash |   Blocked By:
  regression |
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by gorilla.maguila):

 Probably xmlEncodeEntitiesReentrant() or xmlEncodeSpecialChars() must be
 used before xmlNodeSetContent()

 [https://cpp.hotexamples.com/examples/-/-/xmlEncodeSpecialChars/cpp-
 xmlencodespecialchars-function-examples.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] #1851(swscale:reopened): libswscale does incorrect range conversion for RGB->YUV and RGB->RGB

[FFmpeg]

#1851: libswscale does incorrect range conversion for RGB->YUV and RGB->RGB
+
 Reporter:  gjdfgh  |Owner:  (none)
 Type:  defect  |   Status:  reopened
 Priority:  normal  |Component:  swscale
  Version:  git-master  |   Resolution:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+
Changes (by Balling):

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

Comment:

 >Please do not reopen ancient tickets.

 https://w3c.github.io/PNG-spec/#cICP-chunk

 PNG cICP now requires limited range RGB. HAHAHA, wasted.
-- 
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] #10000(undetermined:reopened): PNG produced from BT.709 video should be tagged as gAMA 2.4

[FFmpeg]

#1: PNG produced from BT.709 video should be tagged as gAMA 2.4
-+-
 Reporter:  Balling  |Owner:  (none)
 Type:  defect   |   Status:  reopened
 Priority:  normal   |Component:
 |  undetermined
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by Balling):

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

Comment:

 Even after f7bab37c8e66f3c77a5fbb5b5b72c10b0fb4ca5a it still writes Gamma
 1.961, that is incorrect. It must be 2.4 gamma. At least it writes PNG
 cICP now, so mpv should work correctly now, YES!! But AFAIK, fallback for
 BT.709 must be 2.4 gamma, but I cannot see that in the spec here
 https://w3c.github.io/PNG-spec/#example-4

 Command line

 ffmpeg -i C:\Users\ZAQU\Downloads\example.h264 -v:frames 1 mcasa.png

 ffmpeg.exe -v verbose -i C:\Users\ZAQU\Downloads\example.h264 -v:frames 1
 mcasa.png
 ffmpeg version N-109662-g2c3107c3e9-20230125 Copyright (c) 2000-2023 the
 FFmpeg developers
   built with gcc 12.2.0 (crosstool-NG 1.25.0.90_cf9beb1)
   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 --disable-libmfx --enable-libvpl --enable-
 openal --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-
 libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable-librav1e
 --enable-librubberband --enable-schannel --enable-sdl2 --enable-libsoxr
 --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d
 --disable-libdrm --disable-vaapi --enable-libvidstab --enable-vulkan
 --enable-libshaderc --enable-libplacebo --enable-libx264 --enable-libx265
 --enable-libxavs2 --enable-libxvid --enable-libzimg --enable-libzvbi
 --extra-cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra-
 ldflags=-pthread --extra-ldexeflags= --extra-libs=-lgomp --extra-
 version=20230125
   libavutil  57. 44.100 / 57. 44.100
   libavcodec 59. 57.100 / 59. 57.100
   libavformat59. 36.100 / 59. 36.100
   libavdevice59.  8.101 / 59.  8.101
   libavfilter 8. 54.100 /  8. 54.100
   libswscale  6.  8.112 /  6.  8.112
   libswresample   4.  9.100 /  4.  9.100
   libpostproc56.  7.100 / 56.  7.100


 PS C:\Users\> exiftool.exe  mcasa.png
 ExifTool Version Number : 12.44
 File Name   : mcasa.png
 Directory   : C:/Users/
 File Size   : 87 kB
 File Modification Date/Time : 2023:01:26 12:59:24+03:00
 File Access Date/Time   : 2023:01:26 12:59:42+03:00
 File Creation Date/Time : 2023:01:26 12:59:24+03:00
 File Permissions: -rw-rw-rw-
 File Type   : PNG
 File Type Extension : png
 MIME Type   : image/png
 Image Width : 1280
 Image Height: 720
 Bit Depth   : 8
 Color Type  : RGB
 Compression : Deflate/Inflate
 Filter  : Adaptive
 Interlace   : Noninterlaced
 Pixels Per Unit X   : 1
 Pixels Per Unit Y   : 1
 Pixel Units : Unknown
 White Point X   : 0.3127
 White Point Y   : 0.329
 Red X   : 0.64
 Red Y   : 0.33
 Green X : 0.3
 Green Y : 0.6
 Blue X  : 0.15
 Blue Y  : 0.06
 Gamma   : '''1.961'''
 Image Size  : 1280x720
 Megapixels  : 0.922


 Sample is here: https://github.com/wang-bin/QtAV/files/1132086/example.zip
-- 
Ticket 

[FFmpeg-trac] #10151(avfilter:new): vidstab error - build Btbn

[FFmpeg]

#10151: vidstab error - build Btbn
-+-
 Reporter:  Michael  | Type:  defect
  Møller |
   Status:  new  | Priority:  normal
Component:  avfilter |  Version:
 |  unspecified
 Keywords:  libvidstab   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 Summary of the bug:
 How to reproduce:
 I have used both gyan.dev download of ffmpeg.exe and btbn download.
 btbn gives an error/warning "not enough transformations found" in the
 vidstabtransform step and produce an output file without stabilization.
 The exact same command works in the gyan.dev build with an stabilized
 output file.
 Names of downloads:
 btbn: ffmpeg-master-latest-win64-gpl.zip(2023-01-26)
 gyan.dev: ffmpeg-git-full.7z (2023-01-18)

 I believe it is file independ, input is from a GoPro 9.

 Commands:
 1) ffmpeg -i joined2.mp4 -vf
 
vidstabdetect=shakiness=10:accuracy=15:mincontrast=0.200:stepsize=6:show=0:result=data.trf:tripod=0:result=data.trf
 -f null -
 2) ffmpeg -i joined2.mp4 -vf
 
vidstabtransform=smoothing=25:crop=black:zoom=0:optzoom=0:interpol='bicubic':input=data.trf:tripod=0
 -c:v libx264 -crf 26 -r 25 -preset fast -pix_fmt yuv420p -y "deshaked.mp4"

 Error: vidstab

 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] #1851(swscale:closed): libswscale does incorrect range conversion for RGB->YUV and RGB->RGB

[FFmpeg]

#1851: libswscale does incorrect range conversion for RGB->YUV and RGB->RGB
+---
 Reporter:  gjdfgh  |Owner:  (none)
 Type:  defect  |   Status:  closed
 Priority:  normal  |Component:  swscale
  Version:  git-master  |   Resolution:  invalid
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+---
Changes (by Elon Musk):

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

Comment:

 It supports both, 0 is limited, 1 is full.
-- 
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] #9814(avformat:reopened): time_scale / num_units_in_tick is not infinite precision

[FFmpeg]

#9814: time_scale / num_units_in_tick is not infinite precision
-+
 Reporter:  Balling  |Owner:  (none)
 Type:  enhancement  |   Status:  reopened
 Priority:  wish |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+
Changes (by Elon Musk):

 * component:  undetermined => avformat

Comment:

 bc 1.07.1
 Copyright 1991-1994, 1997, 1998, 2000, 2004, 2006, 2008, 2012-2017 Free
 Software Foundation, Inc.
 This is free software with ABSOLUTELY NO WARRANTY.
 For details type `warranty'.
 scale=1000
 3/1001
 29.97002997002997002997002997002997002997002997002997002997002997002\
 99700299700299700299700299700299700299700299700299700299700299700299\
 70029970029970029970029970029970029970029970029970029970029970029970\
 02997002997002997002997002997002997002997002997002997002997002997002\
 99700299700299700299700299700299700299700299700299700299700299700299\
 70029970029970029970029970029970029970029970029970029970029970029970\
 02997002997002997002997002997002997002997002997002997002997002997002\
 99700299700299700299700299700299700299700299700299700299700299700299\
 70029970029970029970029970029970029970029970029970029970029970029970\
 02997002997002997002997002997002997002997002997002997002997002997002\
 99700299700299700299700299700299700299700299700299700299700299700299\
 70029970029970029970029970029970029970029970029970029970029970029970\
 02997002997002997002997002997002997002997002997002997002997002997002\
 99700299700299700299700299700299700299700299700299700299700299700299\
 700299700299700299700299700299700299700299700299700

 So timebase could be set to reverse of detected framerate. Need to inspect
 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] #9814(avformat:reopened): time_scale / num_units_in_tick is not infinite precision

[FFmpeg]

#9814: time_scale / num_units_in_tick is not infinite precision
-+
 Reporter:  Balling  |Owner:  (none)
 Type:  enhancement  |   Status:  reopened
 Priority:  wish |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+
Comment (by Balling):

 That is just 29.(970029), periodic... The point is at some moment this
 becomes 29.97 which is wrong, and it is very simple to isolate as opposed
 to the whole mp4 to mp4 demux.
-- 
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] #10148(undetermined:new): TS encoding of H.264 omits the SPS and PPS medata (was: M2TS encoding of H.264 omits the SPS and PPS medata)

[FFmpeg]

#10148: TS encoding of H.264 omits the SPS and PPS medata
-+-
 Reporter:  John Coiner  |Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  undetermined
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by John Coiner):

 * summary:  M2TS encoding of H.264 omits the SPS and PPS medata => TS
 encoding of H.264 omits the SPS and PPS medata


Old description:

> == Summary of the bug
>
> Users of OBS who stream with HLS are transmitting non-compliant HLS
> streams, and the root cause is in FFmpeg's '''mpegtsenc.c'''.
>
> == Background
>
> === HLS
>
> Each chunk of an HLS stream should be independently-decodable -- it
> should begin with a key frame and include any metadata (eg. SPS, PPS)
> needed to initialize the decoders. Section 3 of the HLS RFC requires
> this: "Any Media Segment that contains video SHOULD include enough
> information to initialize a video decoder and decode a continuous set of
> frames ..."
>
> === YouTube
>
> I work at YouTube Live, where these non-compliant HLS streams cause
> certain headaches. Today YouTube is able to support them, with the caveat
> that noncompliant HLS uploads reduce the reliability of the resulting
> livestream broadcasts. In the future, it would be nice if OBS would
> produce compliant streams and YouTube could eventually reject
> noncompliant HLS.
>
> === The Bug
>
> The OBS HLS implementation uses the muxer in '''mpegtsenc.c''' to format
> media into M2TS segments.
>

> For H.264, this file has logic that intends to take the "extradata"
> (which includes the SPS and PPS) from the codec parser and re-emit it at
> the beginning of key-frame segments. This is the logic:
>
> {{{
> if (st->codecpar->codec_id == AV_CODEC_ID_H264) {
> const uint8_t *p = buf, *buf_end = p + size;
> uint32_t state = -1;
> int extradd = (pkt->flags & AV_PKT_FLAG_KEY) ?
> st->codecpar->extradata_size : 0;
> int ret = ff_check_h264_startcode(s, st, pkt);
> if (ret < 0)
> return ret;
>
> if (extradd && AV_RB24(st->codecpar->extradata) > 1)
> extradd = 0;
>
> do {
> p = avpriv_find_start_code(p, buf_end, &state);
> av_log(s, AV_LOG_TRACE, "nal %"PRId32"\n", state & 0x1f);
> if ((state & 0x1f) == 7)
> extradd = 0;
> } while (p < buf_end && (state & 0x1f) != 9 &&
>  (state & 0x1f) != 5 && (state & 0x1f) != 1);
>
> if ((state & 0x1f) != 5)
> extradd = 0;
> if ((state & 0x1f) != 9) { // AUD NAL
> data = av_malloc(pkt->size + 6 + extradd);
> if (!data)
> return AVERROR(ENOMEM);
> memcpy(data + 6, st->codecpar->extradata, extradd);
> memcpy(data + 6 + extradd, pkt->data, pkt->size);
> AV_WB32(data, 0x0001);
> data[4] = 0x09;
> data[5] = 0xf0; // any slice type (0xe) + rbsp stop one bit
> buf = data;
> size= pkt->size + 6 + extradd;
> }
> } else ...
> }}}
>
> This code scans the segment for NALs until it finds either an Access Unit
> Delimiter (9), an IDR picture (5), another SPS (7), or a non-IDR picture
> (1). If the first one found is an IDR picture (a key frame) it re-emits
> the "extradata" into its output buffer ahead of the key frame.
>
> The problem is that encoders sometimes preface the key frame with another
> Access Unit Delimiter. In that case this code does not repeat the
> "extradata" and the resulting HLS stream may be noncompliant and
> unjoinable.
>
> == Proposed Fix?
>
> Could this be more robustly written as:
>
> {{{
> if (st->codecpar->codec_id == AV_CODEC_ID_H264) {
> const uint8_t *p = buf, *buf_end = p + size;
> uint32_t state = -1;
> int extradd = (pkt->flags & AV_PKT_FLAG_KEY) ?
> st->codecpar->extradata_size : 0;
> int ret = ff_check_h264_startcode(s, st, pkt);
> if (ret < 0)
> return ret;
>
> if (extradd && AV_RB24(st->codecpar->extradata) > 1)
> extradd = 0;
>
> while (p < buf_end
>&& extradd > 0
>&& (state & 0x1f) != 5  // IDR picture
>&& (state & 0x1f) != 1  // non-IDR picture
>) {
> p = avpriv_find_start_code(p, buf_end, &state);
> av_log(s, AV_LOG_TRACE, "nal %"PRId32"\n", state & 0x1f);
> if ((state & 0x1f) == 7)  // SPS NAL
> extra

Re: [FFmpeg-trac] #10148(undetermined:new): TS encoding of H.264 omits the SPS and PPS medata

[FFmpeg]

#10148: TS encoding of H.264 omits the SPS and PPS medata
-+-
 Reporter:  John Coiner  |Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  undetermined
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by John Coiner):

 Thanks Balling. I've substituted M2TS with TS in the description.

 To be clear, the problem concerns "ingestions" -- Live uploads to YouTube.
 For these, YouTube doesn't decide when the resolution changes -- the
 content creator does. I suspect YouTube supports resolution changes in the
 middle of an HLS ingestion and even in the middle of an HLS chunk, but
 haven't tested this. Certainly, we should not do anything that would
 preclude this.

 I'm not sure how the posted patch would preclude a change of resolution;
 could you elaborate on the sequence you're concerned about? 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".

Re: [FFmpeg-trac] #10148(undetermined:new): TS encoding of H.264 omits the SPS and PPS medata

[FFmpeg]

#10148: TS encoding of H.264 omits the SPS and PPS medata
-+-
 Reporter:  John Coiner  |Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  undetermined
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by John Coiner):

 * Attachment "sample_input_ffmpeg_bug_10148.ts" 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] #10148(undetermined:new): TS encoding of H.264 omits the SPS and PPS medata

[FFmpeg]

#10148: TS encoding of H.264 omits the SPS and PPS medata
-+-
 Reporter:  John Coiner  |Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  undetermined
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by John Coiner):

 To reproduce, use the attached file and run:

 {{{
  $ ffmpeg -re -i sample_input_ffmpeg_bug_10148.ts -codec copy -f hls
 -method PUT
 
'https://upload.youtube.com/http_upload_hls?cid=<>©=0&file=out.m3u8'
 }}}

 (Is there an option to capture HLS output to local files? That'd work too;
 certainly uploading to YouTube should not really be necessary to check
 this. Just upload to any webserver that accepts PUT/POST.)

 This upload a few HLS chunks. Only the first chunk is independently-
 decodable, all others are missing their SPS/PPS due to the bug. With the
 suggested fix, all chunks include SPS/PPS.
-- 
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] #10148(undetermined:new): TS encoding of H.264 omits the SPS and PPS medata

[FFmpeg]

#10148: TS encoding of H.264 omits the SPS and PPS medata
-+-
 Reporter:  John Coiner  |Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  undetermined
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Description changed by John Coiner:

Old description:

> == Summary of the bug
>
> Users of OBS who stream with HLS are transmitting non-compliant HLS
> streams, and the root cause is in FFmpeg's '''mpegtsenc.c'''.
>
> == Background
>
> === HLS
>
> Each chunk of an HLS stream should be independently-decodable -- it
> should begin with a key frame and include any metadata (eg. SPS, PPS)
> needed to initialize the decoders. Section 3 of the HLS RFC requires
> this: "Any Media Segment that contains video SHOULD include enough
> information to initialize a video decoder and decode a continuous set of
> frames ..."
>
> === YouTube
>
> I work at YouTube Live, where these non-compliant HLS streams cause
> certain headaches. Today YouTube is able to support them, with the caveat
> that noncompliant HLS uploads reduce the reliability of the resulting
> livestream broadcasts. In the future, it would be nice if OBS would
> produce compliant streams and YouTube could eventually reject
> noncompliant HLS.
>
> === The Bug
>
> The OBS HLS implementation uses the muxer in '''mpegtsenc.c''' to format
> media into TS segments.
>

> For H.264, this file has logic that intends to take the "extradata"
> (which includes the SPS and PPS) from the codec parser and re-emit it at
> the beginning of key-frame segments. This is the logic:
>
> {{{
> if (st->codecpar->codec_id == AV_CODEC_ID_H264) {
> const uint8_t *p = buf, *buf_end = p + size;
> uint32_t state = -1;
> int extradd = (pkt->flags & AV_PKT_FLAG_KEY) ?
> st->codecpar->extradata_size : 0;
> int ret = ff_check_h264_startcode(s, st, pkt);
> if (ret < 0)
> return ret;
>
> if (extradd && AV_RB24(st->codecpar->extradata) > 1)
> extradd = 0;
>
> do {
> p = avpriv_find_start_code(p, buf_end, &state);
> av_log(s, AV_LOG_TRACE, "nal %"PRId32"\n", state & 0x1f);
> if ((state & 0x1f) == 7)
> extradd = 0;
> } while (p < buf_end && (state & 0x1f) != 9 &&
>  (state & 0x1f) != 5 && (state & 0x1f) != 1);
>
> if ((state & 0x1f) != 5)
> extradd = 0;
> if ((state & 0x1f) != 9) { // AUD NAL
> data = av_malloc(pkt->size + 6 + extradd);
> if (!data)
> return AVERROR(ENOMEM);
> memcpy(data + 6, st->codecpar->extradata, extradd);
> memcpy(data + 6 + extradd, pkt->data, pkt->size);
> AV_WB32(data, 0x0001);
> data[4] = 0x09;
> data[5] = 0xf0; // any slice type (0xe) + rbsp stop one bit
> buf = data;
> size= pkt->size + 6 + extradd;
> }
> } else ...
> }}}
>
> This code scans the segment for NALs until it finds either an Access Unit
> Delimiter (9), an IDR picture (5), another SPS (7), or a non-IDR picture
> (1). If the first one found is an IDR picture (a key frame) it re-emits
> the "extradata" into its output buffer ahead of the key frame.
>
> The problem is that encoders sometimes preface the key frame with another
> Access Unit Delimiter. In that case this code does not repeat the
> "extradata" and the resulting HLS stream may be noncompliant and
> unjoinable.
>
> == Proposed Fix?
>
> Could this be more robustly written as:
>
> {{{
> if (st->codecpar->codec_id == AV_CODEC_ID_H264) {
> const uint8_t *p = buf, *buf_end = p + size;
> uint32_t state = -1;
> int extradd = (pkt->flags & AV_PKT_FLAG_KEY) ?
> st->codecpar->extradata_size : 0;
> int ret = ff_check_h264_startcode(s, st, pkt);
> if (ret < 0)
> return ret;
>
> if (extradd && AV_RB24(st->codecpar->extradata) > 1)
> extradd = 0;
>
> while (p < buf_end
>&& extradd > 0
>&& (state & 0x1f) != 5  // IDR picture
>&& (state & 0x1f) != 1  // non-IDR picture
>) {
> p = avpriv_find_start_code(p, buf_end, &state);
> av_log(s, AV_LOG_TRACE, "nal %"PRId32"\n", state & 0x1f);
> if ((state & 0x1f) == 7)  // SPS NAL
> extradd = 0;
> }
>
> if ((state & 0x1f) != 5) {
> // Not an IDR picture
> extradd 

Re: [FFmpeg-trac] #10148(undetermined:new): TS encoding of H.264 omits the SPS and PPS medata

[FFmpeg]

#10148: TS encoding of H.264 omits the SPS and PPS medata
-+-
 Reporter:  John Coiner  |Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  undetermined
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by John Coiner):

 * Attachment "0001-Proposed-fix-for-https-trac.ffmpeg.org-
 ticket-10148.patch" added.

 Proposed patch
-- 
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] #10148(undetermined:new): TS encoding of H.264 omits the SPS and PPS medata

[FFmpeg]

#10148: TS encoding of H.264 omits the SPS and PPS medata
-+-
 Reporter:  John Coiner  |Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  undetermined
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by John Coiner):

 * Attachment "0001-Proposed-fix-for-https-trac.ffmpeg.org-
 ticket-10148.patch.txt" added.

 Proposed patch, as plain text
-- 
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] #10152(undetermined:new): hwupload from cuda to vulkan doesn't work on Linux

[FFmpeg]

#10152: hwupload from cuda to vulkan doesn't work on Linux
-+-
 Reporter:  serql| Type:  defect
   Status:  new  | Priority:  normal
Component:   |  Version:  git-
  undetermined   |  master
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 Summary of the bug:
 How to reproduce:
 {{{
 % ffmpeg -hwaccel nvdec -hwaccel_output_format cuda -i 1.ts
 -init_hw_device cuda=cuda:0 -filter_hw_device cuda -vf
 hwupload=derive_device=vulkan,scale_vulkan=w=1920:h=1440 -f null -
 ffmpeg version N-109662-g2c3107c3e9 Copyright (c) 2000-2023 the FFmpeg
 developers
   built with gcc 11 (GCC)
   configuration: --enable-nonfree --enable-cuda-nvcc --enable-libnpp
 --prefix=/root/ffmpeg_build --pkg-config-flags=--static --extra-
 cflags='-I/root/ffmpeg_build/include -I/usr/local/cuda/include' --extra-
 ldflags='-L/root/ffmpeg_build/lib -L/usr/local/cuda/lib64
 -L/root/ffmpeg_sources/1.3.236.0/x86_64/lib' --extra-libs=-lpthread
 --extra-libs=-lm --bindir=/root/bin --enable-gpl --enable-libfdk_aac
 --enable-libfreetype --enable-libx264 --enable-libx265 --enable-cuvid
 --enable-hwaccel=hevc_nvdec --enable-hwaccel=h264_nvdec --enable-opencl
 --enable-libzimg --enable-vulkan --enable-libshaderc --enable-libplacebo
   libavutil  57. 44.100 / 57. 44.100
   libavcodec 59. 57.100 / 59. 57.100
   libavformat59. 36.100 / 59. 36.100
   libavdevice59.  8.101 / 59.  8.101
   libavfilter 8. 54.100 /  8. 54.100
   libswscale  6.  8.112 /  6.  8.112
   libswresample   4.  9.100 /  4.  9.100
   libpostproc56.  7.100 / 56.  7.100
 Input #0, mpegts, from '1.ts':
   Duration: 00:01:00.06, start: 27664.427600, bitrate: 3665 kb/s
   Program 3
   Stream #0:0[0x31]: Video: hevc (Main 10) ([36][0][0][0] / 0x0024),
 yuv420p10le(tv, bt2020nc/bt2020/smpte2084), 1920x1080 [SAR 1:1 DAR 16:9],
 Closed Captions, 59.94 fps, 59.94 tbr, 90k tbn
 Stream mapping:
   Stream #0:0 -> #0:0 (hevc (native) -> wrapped_avframe (native))
 Press [q] to stop, [?] for help
 [AVHWFramesContext @ 0x9cd0ac0] There are no supported modifiers for the
 given sw_format
 [Parsed_hwupload_0 @ 0xd038a80] Failed to configure output pad on
 Parsed_hwupload_0
 Error reinitializing filters!
 Failed to inject frame into filter network: Invalid argument
 Error while processing the decoded data for stream #0:0
 Conversion failed!

 ffmpeg version N-109662-g2c3107c3e9
 built on Linux (Centos 7)
 }}}

 Ref: https://trac.ffmpeg.org/ticket/8512

 What I'm trying to do: I want to decode hevc using nvidia gpu, then upload
 it to vulkan, then use libplacebo to convert HDR to SDR, then return it
 back to cpu mem. First step always fail (hwupload to vulkan). nvdec and
 nvenc works fine if I don't try to use vulkan filter

 {{{
 # nvidia-smi
 Thu Jan 26 16:13:33 2023
 +-+
 | NVIDIA-SMI 525.85.05Driver Version: 525.85.05CUDA Version: 12.0
 |
 |---+--+--+
 | GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr.
 ECC |
 | Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute
 M. |
 |   |  |   MIG
 M. |
 |===+==+==|
 |   0  NVIDIA T1000 8GBOff  | :17:00.0 Off |
 N/A |
 ...

 Vulkan info:
 Device Properties and Extensions:
 =
 GPU0:
 VkPhysicalDeviceProperties:
 ---
 apiVersion= 1.3.224 (4206816)
 driverVersion = 525.85.5.320 (2203402560)
 vendorID  = 0x10de
 deviceID  = 0x1ff0
 deviceType= PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
 deviceName= NVIDIA T1000 8GB
 pipelineCacheUUID = 5e84b6ed-4e70-35e3-ab42-c0b2fad24793
 }}}

 Messages from trace level:
 {{{
 Parsed_hwupload_0 @ 0x64a1b40] Setting 'derive_device' to value 'vulkan'
 [Parsed_scale_vulkan_1 @ 0x64a1c40] Setting 'w' to value '1920'
 [Parsed_scale_vulkan_1 @ 0x64a1c40] Setting 'h' to value '1440'
 [graph 0 input from stream 0:0 @ 0x9f51c00] Setting 'video_size' to value
 '1920x1080'
 [graph 0 input from stream 0:0 @ 0x9f51c00] Setting 'pix_fmt' to value
 '117'
 [graph 0 input from stream 0:0 @ 0x9f51c00] Setting 'time_base' to value
 '1/9'
 [graph 0 input from stream 0:0 @ 0x9f51c00] Setting 'pixel_aspect' to
 value '1/1'
 [graph 0 input from stream 0:0 @ 0x9f51c00] Setting 'frame_rate' to value
 '6/1001'
 [graph 0 input from stream 0:0 @ 0x9f51c

Re: [FFmpeg-trac] #1851(swscale:closed): libswscale does incorrect range conversion for RGB->YUV and RGB->RGB

[FFmpeg]

#1851: libswscale does incorrect range conversion for RGB->YUV and RGB->RGB
+---
 Reporter:  gjdfgh  |Owner:  (none)
 Type:  defect  |   Status:  closed
 Priority:  normal  |Component:  swscale
  Version:  git-master  |   Resolution:  invalid
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+---
Comment (by Balling):

 >It supports both, 0 is limited, 1 is full.

 Indeed. And we do not.
-- 
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] #10148(undetermined:open): TS encoding of H.264 omits the SPS and PPS medata

[FFmpeg]

#10148: TS encoding of H.264 omits the SPS and PPS medata
-+-
 Reporter:  John Coiner  |Owner:  (none)
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:
 |  undetermined
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by Balling):

 * status:  new => open

Comment:

 You need to use git send-email. You cannot use anything else because of
 broken google email protocol.
-- 
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] #10151(avfilter:open): vidstab error - build Btbn

[FFmpeg]

#10151: vidstab error - build Btbn
-+-
 Reporter:  Michael  |Owner:  Timo R.
  Møller |
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:  avfilter
  Version:  unspecified  |   Resolution:
 Keywords:  libvidstab   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by Balling):

 * owner:  (none) => Timo R.
 * status:  new => open

Comment:

 You really should report it here: https://github.com/BtbN/FFmpeg-Builds

 But I will assign...
-- 
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] #10151(avfilter:open): vidstab error - build Btbn

[FFmpeg]

#10151: vidstab error - build Btbn
-+-
 Reporter:  Michael  |Owner:  Timo R.
  Møller |
 Type:  defect   |   Status:  open
 Priority:  normal   |Component:  avfilter
  Version:  unspecified  |   Resolution:
 Keywords:  libvidstab   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by Balling):

 * owner:  Timo R. => Timo R.

Comment:

 Maybe 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] #8174(avcodec:open): CUVID decoder doesn't perform a capability check on chroma subsampling

[FFmpeg]

#8174: CUVID decoder doesn't perform a capability check on chroma subsampling
+---
 Reporter:  HolyWu  |Owner:  Timo R.
 Type:  defect  |   Status:  open
 Priority:  normal  |Component:  avcodec
  Version:  git-master  |   Resolution:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+---
Comment (by Balling):

 So again, this does not affect 2080 Ti. But older that do not support 444
 in HEVC. Please apply.
-- 
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] #8948(undetermined:open): NVDEC fails on file: requires (29 + threads) surfaces; thus fails on >3 threads

[FFmpeg]

#8948: NVDEC fails on file: requires (29 + threads) surfaces; thus fails on >3
threads
-+-
 Reporter:  ericbg   |Owner:  Timo R.
 Type:  defect   |   Status:  open
 Priority:  important|Component:
 |  undetermined
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by Balling):

 * priority:  normal => important

Comment:

 it says now to lower threads but it still fails. It does not try to lower
 the ammount of threads.
  Why cannot that be automcatic???


 {{{
 [h264 @ 02ab2312dcc0] Try lowering the amount of threads. Using 4
 right now.

 }}}

 So now:


 {{{
 [h264 @ 0244c19223c0]
 decoder->cvdl->cuvidCreateDecoder(&decoder->decoder, params) failed ->
 CUDA_ERROR_INVALID_VALUE: invalid argument
 [h264 @ 0244c19223c0] Using more than 32 (34) decode surfaces might
 cause nvdec to fail.
 [h264 @ 0244c19223c0] Try lowering the amount of threads. Using 5
 right now.
 [h264 @ 0244c19223c0] Failed setup for format cuda: hwaccel
 initialisation returned error.
 }}}
-- 
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] #10126(avcodec:open): TrueHD decoding regression

[FFmpeg]

#10126: TrueHD decoding regression
-+-
 Reporter:  cgbug|Owner:  Elon Musk
 Type:  defect   |   Status:  open
 Priority:  important|Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  thd  |   Blocked By:
  regression |
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by Balling):

 * owner:  (none) => Elon Musk

-- 
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".