Re: [FFmpeg-trac] #10314(ffmpeg:new): FFmpeg concat introduces gaps, even encoding to wav; does not occur with mpg123.

[FFmpeg]

#10314: FFmpeg concat introduces gaps, even encoding to wav; does not occur with
mpg123.
-+-
 Reporter:  Karen|Owner:  (none)
  Róbertsdóttir  |
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  ffmpeg
  Version:  5.0.2|   Resolution:
 Keywords:  gaps, mp3,   |   Blocked By:
  wav, mpg123|
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by Gyan):

 The primary consumers of bug reports are the project developers. All these
 metadata fields are meant to be in relation to the FFmpeg project, not the
 bug reporter.
-- 
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] #10867(avfilter:new): Video convolution filter ignores some values

[FFmpeg]

#10867: Video convolution filter ignores some values
-+-
 Reporter:  Ing. | Type:  defect
  Radovan Konečný|
   Status:  new  | Priority:  normal
Component:  avfilter |  Version:
 Keywords:  convolution  |  unspecified
  0rdiv 1rdiv 2rdiv 3rdiv|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 Summary of the bug: Video convolution filter ignores the specified values
 0rdiv, 1rdiv, 2rdiv and 3rdiv. Always uses sum of all matrix elements.
 How to reproduce:
 {{{
 % ffmpeg -i input -vf convolution="1 1 1 1 1 1 1 1 1:1 1 1 1 1 1 1 1 1:1 1
 1 1 1 1 1 1 1:1 1 1 1 1 1 1 1 1:100:100:100:100" output
 ffmpeg version N-113649-ga2cfd6062c-20240215
 built with gcc 13.2.0 (crosstool-NG 1.25.0.232_c175b21)
 }}}
-- 
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 paul31415):

 For anyone interested, this fixes the issue:

 diff --git a/libavformat/dashdec.c b/libavformat/dashdec.c
 index 9ae28491e1ecd..41311d6e8f931 100644
 --- a/libavformat/dashdec.c
 +++ b/libavformat/dashdec.c
 @@ -805,8 +805,10 @@ static int resolve_content_path(AVFormatContext *s,
 const char *url, int *max_ur
  memset(p + 1, 0, strlen(p));
  }
  av_strlcat(tmp_str, text + start, tmp_max_url_size);
 -xmlNodeSetContent(baseurl_nodes[i], tmp_str);
 +xmlChar *escaped = xmlEncodeSpecialChars(NULL, escaped);
 +xmlNodeSetContent(baseurl_nodes[i], escaped);
  updated = 1;
 +xmlFree(escaped);
  xmlFree(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".

Re: [FFmpeg-trac] #10865(undetermined:new): xdcam mxf tracks are not identified

[FFmpeg]

#10865: xdcam mxf tracks are not identified
-+-
 Reporter:  dave rice|Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  undetermined
  Version:  6.1  |   Resolution:
 Keywords:  mxf  |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by dave rice):

 I've found that this is a regression.

 In ffmpeg 4.4.4, the streams are identified:
 ```
 % /opt/homebrew/opt/ffmpeg@4/bin/ffmpeg -i
 
/Volumes/LTO9-85/LTO5-TAPES/B00024/SWB00092/data/object/XDCAM8004602012511C8/Clip/C0001.MXF
 ffmpeg version 4.4.4 Copyright (c) 2000-2023 the FFmpeg developers
   built with Apple clang version 14.0.0 (clang-1400.0.29.202)
   configuration: --prefix='/opt/homebrew/Cellar/ffmpeg@4/4.4.4_4'
 --enable-shared --enable-pthreads --enable-version3 --cc=clang --host-
 cflags= --host-ldflags= --enable-avresample --enable-ffplay --enable-
 gnutls --enable-gpl --enable-libaom --enable-libbluray --enable-libdav1d
 --enable-libmp3lame --enable-libopus --enable-librav1e --enable-librist
 --enable-librubberband --enable-libsnappy --enable-libsrt --enable-
 libtesseract --enable-libtheora --enable-libvidstab --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
   libavutil  56. 70.100 / 56. 70.100
   libavcodec 58.134.100 / 58.134.100
   libavformat58. 76.100 / 58. 76.100
   libavdevice58. 13.100 / 58. 13.100
   libavfilter 7.110.100 /  7.110.100
   libavresample   4.  0.  0 /  4.  0.  0
   libswscale  5.  9.100 /  5.  9.100
   libswresample   3.  9.100 /  3.  9.100
   libpostproc55.  9.100 / 55.  9.100
 Guessed Channel Layout for Input Stream #0.1 : mono
 Guessed Channel Layout for Input Stream #0.2 : mono
 Guessed Channel Layout for Input Stream #0.3 : mono
 Guessed Channel Layout for Input Stream #0.4 : mono
 Guessed Channel Layout for Input Stream #0.5 : mono
 Guessed Channel Layout for Input Stream #0.6 : mono
 Guessed Channel Layout for Input Stream #0.7 : mono
 Guessed Channel Layout for Input Stream #0.8 : mono
 Input #0, mxf, from
 
'/Volumes/LTO9-85/LTO5-TAPES/B00024/SWB00092/data/object/XDCAM8004602012511C8/Clip/C0001.MXF':
   Metadata:
 operational_pattern_ul: 060e2b34.04010101.0d010201.01010900
 uid : e7bf1600-7960-05c1-07ef-080046020130
 generation_uid  : e7bf1600-7960-05c2-07ef-080046020130
 company_name: SONY
 product_name: Opt
 product_version : 1.22
 product_uid : 060e2b34-0401-0103-0e06-012002030300
 modification_date: 2012-06-01T13:47:57.00Z
 material_package_umid:
 0x060A2B340101010501010D431300BA7E17007960058008004602013007EF
 timecode: 00:58:05;02
   Duration: 00:26:48.04, start: 0.00, bitrate: 60192 kb/s
   Stream #0:0: Video: mpeg2video (4:2:2), yuv422p(tv, bt709, top first),
 1920x1080 [SAR 1:1 DAR 16:9], 5 kb/s, 29.97 fps, 29.97 tbr, 29.97 tbn,
 59.94 tbc
 Metadata:
   file_package_umid:
 0x060A2B340101010501010D43130098B716007960058008004602013007EF
 Side data:
   cpb: bitrate max/min/avg: 5000/0/0 buffer size: 17825792
 vbv_delay: N/A
   Stream #0:1: Audio: pcm_s24le, 48000 Hz, mono, s32 (24 bit), 1152 kb/s
 Metadata:
   file_package_umid:
 0x060A2B340101010501010D43130098B716007960058008004602013007EF
   Stream #0:2: Audio: pcm_s24le, 48000 Hz, mono, s32 (24 bit), 1152 kb/s
 Metadata:
   file_package_umid:
 0x060A2B340101010501010D43130098B716007960058008004602013007EF
   Stream #0:3: Audio: pcm_s24le, 48000 Hz, mono, s32 (24 bit), 1152 kb/s
 Metadata:
   file_package_umid:
 0x060A2B340101010501010D43130098B716007960058008004602013007EF
   Stream #0:4: Audio: pcm_s24le, 48000 Hz, mono, s32 (24 bit), 1152 kb/s
 Metadata:
   file_package_umid:
 0x060A2B340101010501010D43130098B716007960058008004602013007EF
   Stream #0:5: Audio: pcm_s24le, 48000 Hz, mono, s32 (24 bit), 1152 kb/s
 Metadata:
   file_package_umid:
 0x060A2B340101010501010D43130098B716007960058008004602013007EF
   Stream #0:6: Audio: pcm_s24le, 48000 Hz, mono, s32 (24 bit), 1152 kb/s
 Metadata:
   file_package_umid:
 0x060A2B340101010501010D43130098B716007960058008004602013007EF
   Stream #0:7: Audio: pcm_s24le, 48000 Hz, m

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 paul31415):

 * tmp_str, not escaped
-- 
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] #9142(avformat:new): LIBSRT uses wrong write-readiness epoll on a listener socket

[FFmpeg]

#9142: LIBSRT uses wrong write-readiness epoll on a listener socket
-+-
 Reporter:  Mikołaj  |Owner:  (none)
  Małecki|
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  libsrt   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by Mikołaj Małecki):

 Just a reminder. We would like to fix this bug in SRT, and after we do it
 the listener mode for SRT in ffmpeg will no longer work.

 Let me clarify: the SRT documentation stated it clearly that the epoll
 flag in the listener socket that triggers the accept-readiness is
 SRT_EPOLL_IN. If this was done differently, it wasn't done according to
 the API documentation and it only works thanks to a bug that will soon be
 fixed.

 To test this above fix, simply run ffmpeg with reading or sending a stream
 in listener mode. To make a transmission over SRT (even within the
 internal network of one machine) from a media file using `ffmpeg -re` for
 sending and the other command for sending it to a file (or simply receive
 it via ffplay).
-- 
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] #10866(avcodec:closed): speexdec regression

[FFmpeg]

#10866: speexdec regression
-+-
 Reporter:  Michael  |Owner:  (none)
  Niedermayer|
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:  fixed
 Keywords:   |   Blocked By:
 Blocking:  7.0  |  Reproduced by developer:  1
Analyzed by developer:  0|
-+-
Changes (by Michael Niedermayer):

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

Comment:

 Fixed by james in 66b50445cb36cf6adb49c2397362509aedb42c71
-- 
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] #10865(avformat:open): xdcam mxf tracks are not identified

[FFmpeg]

#10865: xdcam mxf tracks are not identified
-+-
 Reporter:  dave rice|Owner:  Marton
 |  Balint
 Type:  defect   |   Status:  open
 Priority:  important|Component:  avformat
  Version:  6.1  |   Resolution:
 Keywords:  mxf  |   Blocked By:
  regression |
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by Marton Balint):

 * status:  new => open
 * cc: Marton Balint (added)
 * component:  undetermined => avformat
 * priority:  normal => important
 * owner:  (none) => Marton Balint
 * keywords:  mxf => mxf regression

Comment:

 A regression since 7b4bdcd68e1e0abfab21a8be81789531d649c1ff.

 Nevetheless, the file is likely broken (has non-unique metadata set UIDs),
 and it only worked previously because the commit changed the order of
 finding a metadata set based on an instance UID.

 Still, regressions are bad, so I sent a patch series which should fix
 this:
 https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=10800

 Can you please test? I am not sure if I managed to download the file
 without corruption, because the archive.org source is quite slow here...
-- 
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] #10855(undetermined:new): Huge RTSP latency achieved over long time of streaming from specific IP camera

[FFmpeg]

#10855: Huge RTSP latency achieved over long time of streaming from specific IP
camera
-+-
 Reporter:  VincasD  |Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  undetermined
  Version:  6.1  |   Resolution:
 Keywords:  RTSP H264|   Blocked By:
  latency|
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by Marton Balint):

 FFplay is not really developed to maintain a fixed latency for live
 sources, or to regenerate the clock of the input.

 Typically the clock source for playback is the playback audio clock, which
 just depends on the internal clock of your sound card. This is likely
 slighly different from the local clock of your camera, so in time the
 latency will change.

 You might try using the -sync ext mode, which does some playback clock
 adjustments to keep the buffered data (and therefore latency) constant,
 but it might cause some sudden audio pitch changes.
-- 
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".