Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Yalda via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: Romain Beauxis <romain.beauxis@gmail.com>
Cc: FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>, Marvin Scholz <epirat07@gmail.com>,
	Lynne <dev@lynne.ee>,
	Andreas Rheinhardt <andreas.rheinhardt@outlook.com>,
	Yalda <marth64@proxyid.net>
Subject: [FFmpeg-devel] Re: [PATCH v2] ogg/vorbis: implement header packet skip in chained ogg bitstreams.
Date: Sat, 27 Sep 2025 15:39:18 -0500
Message-ID: <CAAhd_PW=MxU-LQKitvyjZoPr2jD-Ne1Wb2cwVFiwc4P_SvOuvw@mail.gmail.com> (raw)
In-Reply-To: <CABWZ6OTFsaCCkK8JaGWmyhxi0m5c9rLhJjqBE0Vq7BmcS=A2bQ@mail.gmail.com>

Hello,

Apologies for the delay.
I have been testing #20327 today with various samples (local, online)
and the api-dump-stream-meta-test tool to observe metadata changes
while listening.

Code looks good, and to me it seems Romain addressed concerns.
I think it makes sense to drop the header packets from output on
segment change and store them as extradata.

I do believe there might be a leak in the api-dump-stream-meta-test
tool (but not in the demuxer change, which is this patch).

Compare (valgrind reports errors):
```
valgrind --leak-check=full ./api-dump-stream-meta-test
http://play.global.audio/city.ogg
```
vs. ffmpeg itself (clean)
```
valgrind --leak-check=full ./ffmpeg -i
http://play.global.audio/city.ogg -c copy -f null -
```

I left a question in the PR, but no other concerns.
Note I had found the above input stream from https://dir.xiph.org/codecs/Vorbis

Thank you!
Yalda
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  reply	other threads:[~2025-09-27 20:40 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-04 16:58 [FFmpeg-devel] " Romain Beauxis
2025-06-10 18:04 ` Romain Beauxis
2025-06-12 11:35   ` Michael Niedermayer
2025-06-14 10:39     ` Romain Beauxis
2025-06-14 22:57 ` Michael Niedermayer
2025-06-21  8:45   ` Romain Beauxis
2025-06-21 21:59     ` Michael Niedermayer
2025-07-23 19:06       ` Romain Beauxis
2025-07-28  0:22         ` Michael Niedermayer
2025-07-28 21:12           ` Romain Beauxis
2025-08-03 21:36             ` Michael Niedermayer
2025-08-03 22:50               ` Romain Beauxis
2025-08-04  0:11                 ` Michael Niedermayer
2025-08-04  0:19                   ` Kieran Kunhya via ffmpeg-devel
2025-08-04 10:53                     ` Nicolas George
2025-08-04  8:21                   ` Michael Niedermayer
2025-08-04 15:59                     ` Romain Beauxis
2025-08-11 22:31                       ` Yalda
2025-08-12  0:21                         ` Romain Beauxis
2025-08-12  0:23                           ` Romain Beauxis
2025-08-12 16:33                             ` Yalda
2025-08-12 16:38                               ` Yalda
2025-08-12 19:49                               ` Romain Beauxis
2025-08-13 13:44                                 ` Romain Beauxis
2025-08-13 13:46                                   ` Romain Beauxis
2025-08-20 20:24                                     ` Yalda via ffmpeg-devel
2025-08-24 15:28                                       ` Romain Beauxis via ffmpeg-devel
2025-09-27 20:39                                         ` Yalda via ffmpeg-devel [this message]
2025-09-29 15:24                                           ` [FFmpeg-devel] " Romain Beauxis via ffmpeg-devel
2025-09-29 16:46                                             ` Yalda via ffmpeg-devel
2025-09-29 17:51                                               ` Romain Beauxis via ffmpeg-devel
2025-09-29 18:24                                                 ` Yalda via ffmpeg-devel
2025-10-01 14:21                                                   ` Yalda via ffmpeg-devel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAAhd_PW=MxU-LQKitvyjZoPr2jD-Ne1Wb2cwVFiwc4P_SvOuvw@mail.gmail.com' \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=andreas.rheinhardt@outlook.com \
    --cc=dev@lynne.ee \
    --cc=epirat07@gmail.com \
    --cc=marth64@proxyid.net \
    --cc=romain.beauxis@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ http://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git