Tuesday, May 10, 2016

Re: [Avid-L2] Nightmare Time Code coincidence point on network delivery?

 



On Tuesday, May 10, 2016 9:13 PM, "John Moore bigfish@pacbell.net [Avid-L2]" <Avid-L2@yahoogroups.com> wrote:


 
At my main gig we have adopted the 23.976 workflow for all our series after all the complaints of random cadence when we work in 59.94i with our 23.976 material.  For most of our work we are able to deliver a 23.976 file.  Now a new series on a different network is requiring XDCam50 422 .mov with 16 channels of audio.  Their specs request the file to start at 58;30;00 and have a minute of bars.  This creates a problem of the program start at 1:00:00:00 no coinciding with the Avid 29.97DF TC display.  Traditionally I start my sequences at 59:00:00 24F TC to avoid this issue but the wienies at this network are insisting on a minute of bars.  Now if I was setting up a Quad or 1 inch machine a minute of bars is good to have but on a file that's just BS in my book.

We were thinking of just making a 23.976 file and sending it to our Dub house who can convert to 59.94i but then there is the potential of the 2 frame offset because the file starts at 58:30:00.  We've been working successfully with 59:00:00 sequence starts for so long I just don't understand this networks insistence on a minute of bars which makes it virtually impossible to easily zero out act times.  What are others doing in these situations.  This is such a ridiculous time suck to deliver to people who clearly don't get what happens in a 23.976 project.  I can't imagine any network ingest system profile for files that would absolutely require a start time of 58;30;00.  Can someone enlighten me on why this would be so necessary.
 
John Moore Barking Trout Productions Studio City, CA bigfish@pacbell.net


__._,_.___

Posted by: <ramsey.gael@yahoo.com>
Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (3)
this is the Avid-L2

.

__,_._,___

No comments:

Post a Comment