multi-camera editing best practices - losing event FX - Prodad

lilpengy wrote on 7/23/2017, 2:18 PM

Ok, so I've done lots of editing over the years but never multi-camera.

I have Vegas Pro 14 and I'm having trouble figuring out my best practices

Typically I'd take a one camera video add levels fx, maybe color correction etc and now Mercalli stabilization. Then I'd edit

I find that I lose all fx when I go to multi-camera editing. So I looked around and it says that I should apply the fx at the MEDIA level not the event level. Unfortunately, when I try to use prodad cmos and Mercalli v4 at the media level it won't run the sensor estimate for Cmos and won't analyze for mercalli. Which is very confusing because with the vegas stabilize plugins you HAVE to run at media level.

So, could someone give me their best practices workflow for editing multi-camera and how/where they are applying image stabilization?

thanks

 

 

Comments

Ralf wrote on 7/23/2017, 3:23 PM

I've found it best just to treat the different angles as I wish and render them out as precursor files. Then import the fx'd rendered files for multicamera editing. I look at it this way: Multicamera editing is very resource intensive so if I pre-render the individual angles with whatever I want to do to them first it saves (well, it saves nothing because it's an extra step) resources --- when I multicamera edit that's ALL I want to do outside of initial trimming and aligning.

redpaw wrote on 7/24/2017, 3:18 AM

Unfortunately, when I try to use prodad cmos and Mercalli v4 at the media level it won't run the sensor estimate for Cmos and won't analyze for mercalli. Which is very confusing because with the vegas stabilize plugins you HAVE to run at media level.

Make sure you put the video on the timeline (select the right track and have the video fx's on in the preview screen) before running the mercalli analyze. Might be working for cmos as well, but i'm not sure. it's definitely working for mercalli v4 cause that's what i usually do.

NigelO wrote on 7/24/2017, 6:24 AM

Ok, so I've done lots of editing over the years but never multi-camera.

I have Vegas Pro 14 and I'm having trouble figuring out my best practices

Typically I'd take a one camera video add levels fx, maybe color correction etc and now Mercalli stabilization. Then I'd edit

I find that I lose all fx when I go to multi-camera editing. So I looked around and it says that I should apply the fx at the MEDIA level not the event level. Unfortunately, when I try to use prodad cmos and Mercalli v4 at the media level it won't run the sensor estimate for Cmos and won't analyze for mercalli. Which is very confusing because with the vegas stabilize plugins you HAVE to run at media level.

So, could someone give me their best practices workflow for editing multi-camera and how/where they are applying image stabilization?

thanks

 

 

I do almost multicam work exclusively and use Vasst Ultimate S Pro 4.20 with the Quadcam tool. You can apply FX at event, media and track level. The Ultimate S Pro package comes with a heap of other useful and indispensable tools.

 

My workflow is trim then align/sync, enable multicam, colour correct and match, do the cuts, generate the output, playback and fine tune the cuts, edit the audio (volume, ducking) and finally, render out.

 

I don't use image stabilization because I find it introduces unwanted artefacts. I make sure I stabilise at the point of capture e.g. use a tripod or monopod. I do have cameras with balanced optical stabilisation and have done an ice skating shoot hand held with a monopod and no one could tell!

lilpengy wrote on 7/24/2017, 11:53 AM

I've found it best just to treat the different angles as I wish and render them out as precursor files. Then import the fx'd rendered files for multicamera editing. I look at it this way: Multicamera editing is very resource intensive so if I pre-render the individual angles with whatever I want to do to them first it saves (well, it saves nothing because it's an extra step) resources --- when I multicamera edit that's ALL I want to do outside of initial trimming and aligning.

That sounds like a good way to go, thanks!

NigelO wrote on 7/24/2017, 4:44 PM

That workflow works too, but you are restricted to how dynamically you can make changes, and it adds time. With respect to being resource intensive, I use a 6th generation i7 Intel processor with 16 GB and I don't really notice too much of a performance lag. Video editing requires the fastest processor possible. Hopefully, Magix will get CUDA working stably in Vegas 15 :-)