This IS the Avid L2: [Avid-L2] Re: EDL Manager Wonky So what else is new?

Monday, February 4, 2013

[Avid-L2] Re: EDL Manager Wonky So what else is new?

Worth a look. I thought the CMX 3600 format opened up some of the restrictions with the number of characters for a Reel Number but I don't know about the events max number. I know GVG openened up the total number of lines in an edl to accomodate all the extra hidden lines that were taken up with the PEGS commands.

--- In Avid-L2@yahoogroups.com, Mark Spano wrote:
>
> Check that you have less than 999 events. That's the most common issue with
> creating long EDLs - CMX EDL can't have more than 999 events. More than
> that, you need to break the sequence up into multiple parts to get full EDL.
>
>
> On Mon, Feb 4, 2013 at 4:25 PM, John Moore wrote:
>
> > **
> >
> >
> > On a mac SNDX 6.0.3.2 EDL Manager V. 28.0.3.2 trying to export V1 A1thru 4
> > EDL of a 48 minute show. If I choose CMX 340 or 3600 I get the usual
> > errors message about events being changed but more annoying is the edl only
> > goes to the 1;27;00;00 minute mark approx. If I choose GVG 7.0 I get the
> > whole list with a lot less errors. I know various versions of EDL manager
> > have had their share of bugs etc..... I even tried EDL manager 28.5 on my
> > laptop that was bundled with SN 6.5.0 and it doesn't even see the bin as a
> > valid file WTF. I ultimately went GVG 7.0 and just had to locate a couple
> > of corrupt audio clips that were crashing EDL Manager V 28.0.3.2. Why
> > would the newer 28.5 EDL not even recognize the bin as a valid file?
> > Traditionally EDL manager has always been plagued with issues and it
> > appears that the tradition is being upheld in the latest versions. Oh well
> > I don't even know why the network wants this as a deliverable other than
> > clinging to legacy delivery requirements. Any tips on what's going on
> > would be appreciated.
> >
> > John Moore
> >
> > Barking Trout Productions
> >
> > Studio City, CA
> >
> > bigfish@...
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>