gt; > > Hi!
> > >
> > > Le mar. 12 août 2025 à 11:33, Yalda a écrit :
> > > >
> > > > Romain Beauxis:
> > > >
> > > > Thank you, Romain, for the clarity.
> > > >
> > > > I have some follow up questions
Nicolas George:
> Now that I have access to your mail address too, it seems to evoke
> somebody who contributed usefully to the project in the recent years.
For clarity, I announced my handle change in an email titled "Handle change"
on July 13th.
Your categorization is noted. It does not change
Re: Yalda (myself)
> 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!
My apologies, you already linked the Xiph doc.
I can read that on my own.
Inferring
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 st
Nicolas George:
> Approval full stop is []. The only approval worth something comes
> from somebody who knows the code.
>
> How do you know that approval was worth anything?
>
> So as a default, they are maintained by whoever maintains libavfilter
I was the one who approved this PR.
Hi Romain,
I can try to help out here.
I am not familiar with the OGG spec but I can at least help with
reviews/facilitate to a degree, and it's free so I can read if needed.
It seems you are trying to fix issues in and improve OGG support.
Can you give me a brief summary of your goals?
(i.e. wha
PR #20116 opened by Yalda
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20116
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20116.patch
At last, the BDMV demuxer.
The goal is to replace the limited bluray protocol handler that exists today.
Seeking is still experimental (can be
PR #20107 opened by Yalda
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20107
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20107.patch
This is based on the previously used, simple TRAC form
with new description language.
We can iterate on it to improve as needed.
Note I put this in
I'm not seeing a code change, just indenting the same line. Mistake?
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with su
F, due to it feeling faster and more responsive while navigating.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subje
All,
I will be slowly transitioning to using my name. Nice to meet you again.
Yalda
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ
11 matches
Mail list logo
