Monday, December 7, 2015

Re: [Avid-L2] Okay so I did and Fing Avid Mixdown now I get the double video mixdown whammy?

 

John,

Here is my advice, which is different from Bogdan's, for specific reasons you will see.

In the 23.976p project, when ready to output, first DUPLICATE your sequence. Then in the duplicate sequence, do a VIDEO MIXDOWN.
Open a 59.94i project, and open the bin where your mixdown sequence is located. Do a VIDEO MIXDOWN. Then, export same-as-source.

The first mixdown is so that all of the random clips (and matte keys if any) are combined into a single piece of video. When you open this in the 59.94i project and do a mixdown, it bakes in the pulldown in a constant cadence, to the resolution you desire.

If you do not do the first mixdown, you will have motion adapters on all of your clips, creating broken pulldown cadence. Sometimes this can be a problem for QC to pass. Also, if you had any matte keys in your 23.976p sequence and did not mixdown there, you simply won't be able to open the sequence in the 59.94i project. MC will tell you that it's not possible.

Mixdown once in 23.976, then mixdown again in 59.94i. And doing these mixdowns and outputting SAS is many times faster than the tape workflow you're dreaming about.



On Sat, Dec 5, 2015 at 11:50 PM, bigfish@pacbell.net [Avid-L2] <Avid-L2@yahoogroups.com> wrote:
 

I'm on OS 10.8.5 Ver. 6.5.4.7 so maybe there is a difference there.  My steps are as follows:

Online in 1080 23.976P project with DNX 175X material and all renders forced to DNX 175X.  10 tracks from a ProTools aaf.  The aaf is a solid track on each channel no edits from tone to region silence at the end pad.

While in 23.976 project mixdown video to ProResHQ.  Make a sequence with just the mixdown on V8 and no other video and the 10 tracks of pro tools stems. 

Create a 59.94 project and open the sequence bin from the other project.  Open my mixdown sequence which gets modified in the process to 29.97I.  Do you think opening the bin from the other 23.976 project could effect anything as opposed to creating a new bin in the 59.94 project and copying the sequence into there before opening it to modify it to 29.97I?

Now export same as source and I get a prompt that there is no native to the project video so Avid is going to export to DNX 220X instead of same as source.  It then makes a DNX .mov if I say continue.  I haven't tried to do a custom export setting it up to prores there.  My mixdown from the 23.976 is definitely ProRes.

Am I missing a step here?



---In avid-l2@yahoogroups.com, <bogdan_grigorescu@...> wrote :

we're on MC8.3.0/OSX10.9.5 - sources are 23.98 DNxHD and delivery is 1080i/59.94 ProResHQ

BG
 
 
image
 
 
 
 
 
FINALÉ - Redefining Post
Our creative vision and independent spirit has helped revolutionize post production workflows for film, television, and commercial media content for more than 25 ye...
Preview by Yahoo
 



From: "bigfish@... [Avid-L2]" <Avid-L2@yahoogroups.com>

To: Avid-L2@yahoogroups.com
Sent: Saturday, December 5, 2015 4:30 PM
Subject: Re: [Avid-L2] Okay so I did and Fing Avid Mixdown now I get the double video mixdown whammy?

 
Well if there is no second mixdown required why is Avid telling me there is stuff not native to the project frame rate, or some such prompt, and telling me it will make a DNX 220X file when I want a ProRes.  Is the problem that I'm telling it same as source and not making a custom ProRes format output.  I'm on 6.5.4.7 if that factors into the equation.  I agree on the audio mixdown when I'm saving with direct audio option as long as interleaved audio is okay.  I have read on the L2 that later versions of 8 don't interleave the audio on export so there is a solution for that if I jump to V. 8.  The speed is nice for the mixdowns and  the export but the ProRes seems to be causing problems for some reason.

I don't know what I can be missing on steps.  What version are you running this workflow and are you going to ProRes from DNX material.  In the past the DNX outputs were the delivery spec and this is my first ProRes deliverable where I'm using Avid to do the frame rate convert.


---In avid-l2@yahoogroups.com, <bogdan_grigorescu@...> wrote :

-no second video mixdown required
-no audio mixdown needed

whole process is slightly faster than RT and reliable. We're doing this everyday on various shows with zero problems.

cheers,
BG
 
 
image
 
 
 
 
 
FINALÉ - Redefining Post
Our creative vision and independent spirit has helped revolutionize post production workflows for film, television, and commercial media content for more than 25 ye...
Preview by Yahoo
 



From: "John Moore bigfish@... [Avid-L2]" <Avid-L2@yahoogroups.com>
To: yahoogroups <avid-l2@yahoogroups.com>
Sent: Saturday, December 5, 2015 2:05 PM
Subject: [Avid-L2] Okay so I did and Fing Avid Mixdown now I get the double video mixdown whammy?

 
So on a tight turn around show I committed to the Avid mixdown workflow for frame rate conversion and I ended up getting burned by my own mistake.  I mixed down the 23.976 to ProRes, the delivery format, and then opened a mixdown only sequence in a 59.94 1080I project.   Pulldown was perfect etc....  From there I went to save as and in my haste okay'd through the part where it tells me the sequence is a non native format and it will make an Avid DNX220X instead of a ProRes.  I'm assuming and about to correct this by making a second mixdown to ProRes while in the 59,94 project and using that to save a same as source.  I'm pretty sure that will work but I've always glossed over the part in people's work flows where they mention a second mixdown.

In the past I've done this but the deliverables were to be Avid DNX anyways so I didn't flag the gotcha until now.  I know this is the best way to assure a solid file but what a double pain in the arse.  The other issue is because the audio stems are 23.976 I have to do audio mixdowns of each track while in the 59.94 project or I get the prompt I must select audio mixdowns in the export settings.  Is there a way to avoid that prompt in an elegant manner.  I could try reimporting the aaf into the 59.94 project but it's a 23.976 ProTools AAF so I doubt that would work.
 
John Moore Barking Trout Productions Studio City, CA bigfish@...





__._,_.___

Posted by: Mark Spano <cutandcover@gmail.com>
Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (7)
this is the Avid-L2

.

__,_._,___

No comments:

Post a Comment