On Fri, Apr 03, 2015 at 12:55:15PM +0200, Steve Dierker wrote:
> Hello,
>
> >
> > +{ {
> > 0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x02,0x0d,0x01,0x03,0x01,0x02,0x04,0x
> > 60,0x02
> > }, 14, AV_CODEC_ID_MPEG2VIDEO }, /* Ikegami */
> >
> > Errm where did this coming from, its unrelated (and wrong
Hello,
>
> +{ {
> 0x06,0x0E,0x2B,0x34,0x04,0x01,0x01,0x02,0x0d,0x01,0x03,0x01,0x02,0x04,0x
> 60,0x02
> }, 14, AV_CODEC_ID_MPEG2VIDEO }, /* Ikegami */
>
> Errm where did this coming from, its unrelated (and wrong afaik as
> its a container UL).
>
Oh, sorry this is unrelated, I'm current
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/04/15 10:57, Steve Dierker wrote:
> Hello,
>
>>
>> I am currently looking at the whole range of UL's to see if they can
>> be tidied up, but that will also take some time, so perhaps in the
>> interests of progress use your suggestion for now *b
Hello,
>
> I am currently looking at the whole range of UL's to see if they can
> be tidied up, but that will also take some time, so perhaps in the
> interests of progress use your suggestion for now *but* change the
> inline comment to something like:-
>
> /* Avid MC7 Prores */
>
> That will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/04/15 16:32, Steve Dierker wrote:
> Hello,
>
>> I support this patch if you didn't make the
>> file yourself.
>> I only had one sample.
>
> This sample is from the same customer as the other ProRes in MXF sampl
e
> I uploaded for the bug. (Don
Hello,
> I support this patch if you didn't make the
> file yourself.
> I only had one sample.
This sample is from the same customer as the other ProRes in MXF sample
I uploaded for the bug. (Doner Advertisment)
I found it while searching for the reason why FFmpeg refused to encode
some files af
On Tue, Mar 31, 2015 at 04:06:18PM +0100, tim nicholson wrote:
> On 31/03/15 13:41, Steve Dierker wrote:
> > Hello List,
> >
> > I found another MXF File containing ProRes with the following
> > codec_uls: 060E2B34040101010E04020102110500
> > Therefor I relaxed the pattern.
> >
>
> Are the Prore
Steve Dierker flavoursys.com> writes:
> I found another MXF File containing ProRes with the following
> codec_uls: 060E2B34040101010E04020102110500
> Therefor I relaxed the pattern.
I support this patch if you didn't make the
file yourself.
I only had one sample.
Thank you, Carl Eugen
___
On 31/03/15 13:41, Steve Dierker wrote:
> Hello List,
>
> I found another MXF File containing ProRes with the following
> codec_uls: 060E2B34040101010E04020102110500
> Therefor I relaxed the pattern.
>
Are the Prores variants likely to be that big?
Difficult I know for private UL's
I wonder if
Hello List,
I found another MXF File containing ProRes with the following
codec_uls: 060E2B34040101010E04020102110500
Therefor I relaxed the pattern.
Related to issue #4349
---
libavformat/mxf.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/mxf.c b/libavforma
10 matches
Mail list logo
