Most efficient way to work with HDV

Cliff Etzel wrote on 10/23/2007, 5:12 PM
I'm doing my homework for my transition to HDV.

What is the most efficient way of working with HDV files in Vegas Pro?

Is Cineform the way to go or is the native files format directly in Vegas the way to go? Which is the least resource intensive to work with? Are intermediate files still appropriate now with VP8?

Cliff Etzel
bluprojekt

Comments

jrazz wrote on 10/23/2007, 5:30 PM
It depends on what you are doing. Are you doing cuts and fades and no CC? Or are you doing a lot of CC and FX?

If the former then working with M2T files will be great as long as your system can keep up. If the latter, then Cineform would be in order as you will suffer less degredation. Also, you might want to read up on some of the irregularities with using 32 bit if you plan on using it as Cineform is/was affected.

j razz
blink3times wrote on 10/23/2007, 5:32 PM
Prior to Vegas's smart render (no recompress) I believe cineform was probably the best way to go.... but NOW... it's a different ballgame!

Using smart render as much as you can is most definitely the best route to go. No recompress means no loss so the more you can fit it into your schedule, the more original quality will be retained.
Cliff Etzel wrote on 10/23/2007, 10:09 PM
jrazz - The majority of work I do requires some amount of CC - especially when shooting underwater, but I edit straight cuts and some dissolves. FX aren't my usual thing. I'm striving for the style of shooting similar to Discovery, Travel Channel, etc.

What issues are there with 32bit processing and using CC, FX, etc?

B3T - I have smart rendering on currently when I edit my DV footaage in 32bit mode - Are you saying then that this new feature in VP8 removes the need for Cineform when working with HDV? For laptop editing, does Cineform provide something that native editing in Vegas doesn't provide?

Thanks! :-)

Cliff Etzel
bluprojekt
Serena wrote on 10/23/2007, 10:52 PM
Probably the best answers can be found at http://www.cineform.com/technology/default.htmCineform technology[/link] where you can see the benefits of the digital intermediate (such as working in 4:2:2 rather than 4:2:0). If you have to produce results quickly (e.g. produce a cut of the afternoon wedding to show at the evening reception) then cutting m2t is the only way to go and will be fine because even with effects (levels/CC/etc) you've only got one or two extra generations. But if time isn't so pressing, the digital intermediate offers advantages.
Cliff Etzel wrote on 10/24/2007, 5:32 AM
Serena - Thanks for your input - I'm working primarily in deadline mode, but have been asked to work on a pilot series for broadcast overseas where quality will preside over speed (although Vegas does bring both to the table) - sounds as though Cineform will have to be a part of my work flow.

Cliff Etzel
bluprojekt
Jeff9329 wrote on 10/24/2007, 7:03 AM
Since you are doing commercial work, I assume you are using the latest workstation with a Quad processor and a fast drive system (RAID), right?

If so, you should have no problems with HDV using any method.

Cliff Etzel wrote on 10/24/2007, 7:13 AM
Jeff - I'm holding out to see what AMD brings to the table for their Quad Core offerings coming soon since I built my workstation around the AM2 socket specifically for this last year.

Cliff Etzel
bluprojekt
Jeff9329 wrote on 10/24/2007, 7:30 AM
My system is an Intel using a Q6600 processor.

IMO, the quad processors have essentially completely tamed the HDV editing, where it is real time...ish, depending upon effects. And almost no long waits or freezes wondering what is happening. Also, in some cases, your video card processor will also come into play.

If your camera work is tuned by camera presets to what you are looking for; ie: bleach bypass, vivid RGB, etc., you should be able to smart render and reduce/eliminate all the additional introduced HDV artifacts from a render.

For me, using camera presets to get what I am looking for (instead of accurate color reproduction), makes the whole production process much easier.

Cliff Etzel wrote on 10/24/2007, 7:33 AM
Thanks for your experiences Jeff - I'm making a list of hits and tricks.. ;-)

Cliff Etzel
bluprojekt
CClub wrote on 10/25/2007, 11:24 AM
Jeff,
I was thinking of changing over to a quad core from a dual core, but I seem to recall a posting here where people weren't incredibly impressed with the difference between the dual vs. the quad. Any input on this?
rs170a wrote on 10/25/2007, 12:07 PM
Check out the results in the NEW Rendertest-HDV.veg thread.
Most of us quad core users are very happy with the speed :-)

Mike
Cliff Etzel wrote on 10/25/2007, 12:14 PM
I'm as curious myself CClub

Cliff Etzel
bluprojekt
Jeff9329 wrote on 10/25/2007, 3:02 PM
CClub:

I moved from a P4 3.4E OCd to the Q6600 system. There is no comparing the P4 to the Q6600, it is so much faster. I never had current dual core system for a comparison.

The other thread link above is fairly accurate. It seems that for that render test, a quad core is very roughly twice as fast as a dual core.
CClub wrote on 10/25/2007, 4:11 PM
It seems pretty clear from all of the info on the link that it is roughly twice the speed of my dual core. When I purchased the dual core, I picked up the same motherboard and RAM that John Cline had stated is in his system (which can handle the quad core). If I replaced the dual core with the quad core, would I have to change anything else? I have 3 fans in the tower but nothing like water cooled or anything.

Does the quad core help with preview also or just render speed?
Jeff9329 wrote on 10/26/2007, 7:40 AM
If you have a P35 based motherboard, you are ready for the quad processor. The latest variation of the Q6600 has the GO stepping which allows it to run cooler that the earlier Q6600s with the B3 stepping. So no, you don't need any special cooling. I used the fan supplied in the retail box and it runs very cool.

Im not sure about helping on preview, that seems to be mostly RAM based, but someone else probably knows for sure. You could do a preview and look at processor usage. If it uses the CPU, it's going to be a lot faster.