Rendering from Vegas 13 for FCP7

BullMooseFilms wrote on 1/5/2017, 10:32 AM

Hey everyone.

I'm delivering a feature film that I've edited in Vegas 13 up to their in house team, who work on FCP7.

They had requested ProRes 4:2:2 (HQ) for delivery but of course you can't do that without a Mac. Alternately they requested this:

If you DO NOT output with Apple ProRes 422 (HQ), then I need:
One feature file HQ Quicktime H.264 with soundtrack
One feature file HQ HDV1080i with soundtrack
One feature file HQ HDV1080i with NO soundtrack

So my understanding is, I could actually give them a DNxHD render in an .mov wrapper, though it isn't H.264 - but FCP7 should be able to read it with the codec installed - or at the very least they should be able to run it through compressor on their system to turn it losslessly into the ProRes file they want.

Film is 1080p as well so I'm hesitant to actually encode an HDV1080i and introduce all those artifacts.

Anyway I'm rendering all morning and if anyone sees this in time to help or offer thoughts, thanks in advance!

Comments

Former user wrote on 1/5/2017, 10:48 AM

Why aren't you going to deliver what they requested? Not everybody on a Mac uses DNxHD, so I would clear that first. Have you asked them why they want an interlaced video?

BullMooseFilms wrote on 1/5/2017, 10:54 AM

No I don't think they're in the office yet to ask.

It's easy enough to download the codec though on their end - the issue is that a lot of render cases seem to cause gamma issues when going to FCP and DNxHD is one that avoids that problem.

I was going to have the DNxHD in addition to what they talked about because I just feel like it's going to be a problem, but I thought I'd see if anyone else had similar experience and any ideas or stories to relate.

NickHope wrote on 1/5/2017, 8:13 PM

They had requested ProRes 4:2:2 (HQ) for delivery but of course you can't do that without a Mac.

Actually, since VP14 build 201, you can:

The codec might still have some kinks, but I'm not sure if that's with encoding or decoding. I'm planning to test that today.

BullMooseFilms wrote on 1/5/2017, 8:30 PM

Ok from what I had seen it could read ProRes but not encode it...

NickHope wrote on 1/5/2017, 8:35 PM

Ok from what I had seen it could read ProRes but not encode it...

Builds 161-189 yes, but encoding was introduced too in 201.