From: Yalda <marth64@proxyid.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Marvin Scholz <epirat07@gmail.com>, Lynne <dev@lynne.ee>, Andreas Rheinhardt <andreas.rheinhardt@outlook.com> Subject: Re: [FFmpeg-devel] [PATCH v2] ogg/vorbis: implement header packet skip in chained ogg bitstreams. Date: Tue, 12 Aug 2025 11:33:11 -0500 Message-ID: <CAAhd_PWwFeffV9AshO5uZRqenvmQdqj3mvW_-mbNnBNdHY+geA@mail.gmail.com> (raw) In-Reply-To: <CABWZ6OQu7-Zq49Ad61BKjhekKfWGM=1p6NHLjod+943gysq7Gw@mail.gmail.com> Romain Beauxis: Thank you, Romain, for the clarity. I have some follow up questions just to solidify my understanding. I think this is a good match since this sounds like a segment joining problem which is ironically what I have been doing in principle with my other contributions. 1) Can core stream parameters (channels, sample rate) change mid-flight? 2) Why are the header packets emitted to begin with? Are they necessary for the audible bitstream or preamble metadata? Alternatively, a link to external reading is fine by me! 3) Is it possible that doing the stream copy is a front-line goal in actuality? In other words, by solving 1/2/3, we are actually wanting to solve 4? (If this thought makes sense) 4) Is there a sample command to spawn such a source stream, or is setting up Icecast with defaults enough and play segments to simulate the conditions? _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-08-12 16:34 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-04 16:58 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 [this message] 2025-08-12 16:38 ` Yalda 2025-08-12 19:49 ` Romain Beauxis
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_PWwFeffV9AshO5uZRqenvmQdqj3mvW_-mbNnBNdHY+geA@mail.gmail.com \ --to=marth64@proxyid.net \ --cc=andreas.rheinhardt@outlook.com \ --cc=dev@lynne.ee \ --cc=epirat07@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /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 https://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/ https://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