Sorry about that. I just attached the patch directly. Please let me know if
this still doesn't work.
On Mon, 30 Jun 2025 at 12:41, Michael Niedermayer
wrote:
> On Sun, Jun 29, 2025 at 09:42:27AM +1200, Ken McGaugh wrote:
> > On Sun, 29 Jun 2025 at 08:33, Ken McGaugh wrote:
> &
On Sun, 29 Jun 2025 at 08:33, Ken McGaugh wrote:
> On Sun, 29 Jun 2025 at 7:44 AM, Baptiste Coudurier <
> baptiste.coudurier-at-gmail@ffmpeg.org> wrote:
>
>> Hey Ken
>>
>> > On Jun 28, 2025, at 1:04 AM, Ken McGaugh wrote:
>> >
>>
On Sun, 29 Jun 2025 at 7:44 AM, Baptiste Coudurier <
baptiste.coudurier-at-gmail@ffmpeg.org> wrote:
> Hey Ken
>
> > On Jun 28, 2025, at 1:04 AM, Ken McGaugh wrote:
> >
> > On Sat, 28 Jun 2025 at 13:52, Baptiste Coudurier <
> > baptiste.coudurier-at-gmai
On Sat, 28 Jun 2025 at 13:52, Baptiste Coudurier <
baptiste.coudurier-at-gmail@ffmpeg.org> wrote:
> Hi
>
> > On Jun 27, 2025, at 5:46 PM, Ken McGaugh wrote:
> >
> > Hi, first time contributing to ffmpeg so I hope I got this right. We use
> > custom udta ta
Hi, first time contributing to ffmpeg so I hope I got this right. We use
custom udta tags in our pipeline but they were not coming through
correctly. Looks like they were incorrectly being routed through the code
path for "raw" data.
---
libavformat/mov.c | 2 +-
1 file changed, 1 insertion(+), 1
