On 06/01/15 19:01, Mark Reid wrote:
> On Tue, Jan 6, 2015 at 12:03 AM, tim nicholson <
> nichot20-at-yahoo@ffmpeg.org> wrote:
>
>> On 05/01/15 20:41, Mark Reid wrote:
>>> Hi,
>>> This patch exports the full umid of packages as metadata. ffmpeg
>> currently
>>> only exports the material number
On Tue, Jan 6, 2015 at 12:03 AM, tim nicholson <
nichot20-at-yahoo@ffmpeg.org> wrote:
> On 05/01/15 20:41, Mark Reid wrote:
> > Hi,
> > This patch exports the full umid of packages as metadata. ffmpeg
> currently
> > only exports the material number portion of the umid.
> >
> > The new format
On 05/01/15 20:41, Mark Reid wrote:
> Hi,
> This patch exports the full umid of packages as metadata. ffmpeg currently
> only exports the material number portion of the umid.
>
> The new format is
>---
> example:
>060a2b340101010101010f00-13-00-53dc416b9a770251060e2b347f7f2a80
>
I th
---
libavformat/mxfdec.c | 39 ---
1 file changed, 32 insertions(+), 7 deletions(-)
diff --git a/libavformat/mxfdec.c b/libavformat/mxfdec.c
index 4715169..5ade23a 100644
--- a/libavformat/mxfdec.c
+++ b/libavformat/mxfdec.c
@@ -200,6 +200,7 @@ typedef struct {
Hi,
This patch exports the full umid of packages as metadata. ffmpeg currently
only exports the material number portion of the umid.
The new format is
---
example:
060a2b340101010101010f00-13-00-53dc416b9a770251060e2b347f7f2a80
Some applications use the umids to link to mxf media instea
