Streamlined Neat Video Workflow with Vegasaur

MartinE wrote on 2/2/2017, 5:09 AM

Hi to all you editors.
First a big thanks to many of the pros here from whom I have learned so much over the last couple of years. Nick Hope, you’re top of my list, many thanks especially for the FAQ posts, a great help

I shoot with a Canon XF100 which is well known to be noisy in low light. The Neat Video plug-in does a great job of cleaning up the grainy footage, in a word it transforms it!. The down side is that it cripples your rendering speed 2fps max on my slow system. I frequently end up making small changes even after my “final” render (when is it ever final?) and every time I have to wait hours/days (weddings) for VP to crunch through the NV filtering. So I’ve been trying to come up with a better workflow and here it is. It makes extensive use of the Vegasaur extension (worth every penny in my opinion). It basically creates digital intermediates for the noisy clips. No doubt some of you pros have been doing this sort of thing for years but it’s new for me and I’m just sharing it here in case others are in the same boat and looking for a solution. Here’s my new workflow.

Load the original clips in VP (for me that’s MXF/MPEG2/422/50MB/s) and edit as normal.

When the timeline is nearing the picture lock stage ie you know which clips you are going to be using and they’re all on the t/l, open another instance of VP and paste your video tracks into the new project and call it **** De-Noise.veg or whatever.

Get all of the clips that you want to de-noise on one track (doesn’t matter about the order) and apply the NV filter as an event Fx.

Using Vegasaur timeline tools, add regions to each event and name them with “the active take name”.

Using the Vegasaur render tools, batch transcode each region to a digital intermediate file (DI) using the codec of your choice (I’m using the free Magic YUV *.avi codec) and naming them by the region name (there is a macro drop down for this) and output them to a separate folder on your project drive (make sure you have the space, files are big approx. 1GB/min). This is the time consuming bit, but the beauty of it is that you can just leave to run in the background and carry on editing in the main project. You will end up with a folder with clean clips with the same name as the original clips but with an *.avi (likely) extension.

When batch rendering is finished (overnight or maybe a couple days if your clips are long), open the main project and use the Vegasaur batch media replace tool to replace your noisy original clips with the cleaned up DI files, takes a few secs and you carry on  editing with the new files. For me I now have on the t/l a mix of original cam files (MXF) and DIs (avi).

The beauty of this is that you only have to render the NV Fx once and you can do the batch transcode at any time in the edit and in the background to suit your convenience. My project renders will now take a more reasonable time.

I guess it’s a bit like a proxy workflow but you can do it at a late stage in editing if you wish and its virtually all automated.

Hope this may be of help to other NV users particularly those who have low spec hardware.

 

Comments

NickHope wrote on 2/2/2017, 6:59 AM

Thanks for posting the useful workflow (and for the kind words 😊).

OldSmoke wrote on 2/2/2017, 7:25 AM

I apply NV once I am done with all the editing. I render an intermediate XAVC-I file, check if that is ok and only apply once NV to the whole final file. This way, you don't have to render sections of a clip that you are not using therefore further reducing the render time for NV. Especially for multicam editing your workflow increases the render time.

Last changed by OldSmoke on 2/2/2017, 7:26 AM, changed a total of 1 times.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

MartinE wrote on 2/2/2017, 7:48 AM

Nick, thanks for the response.

Old Smoke, I get what you are saying but I’m not sure your workflow would work for me (if I understand you correctly). Firstly I only want to add the NV Fx to selected clips, not the whole piece and secondly I keep my options open to go back at any stage and change the edit (cuts, sound etc etc) and re-render fast without having to wait for Vegas to process the NV Fx every time I render. I understand your workflow for a once through system
(ie don’t render till all editing is absolutely finished) but the reality is that when I watch my renders I inevitably keep seeing things that I could improve or glitches I hadn’t spotted before. Bye the way this particular project is a multi
cam edit and true I end up with DIs for lots of footage that I’m not using but disc space is cheap and time is in short supply.

Thanks for the input. Much appreciated.


 

OldSmoke wrote on 2/2/2017, 8:44 AM

I mostly work with live events, 3 to 4 cam edits. If I would apply NV to all the footage first and than edit, the total render time would be much longer because I would have rendered each camera to it's full length. If I have corrections, I just overlay the sections I need redone in a master project on top of the master file and apply NV only to the overlayed portion; I have done that on several occasions. But if your workflow works for you, stick with it.

Last changed by OldSmoke on 2/2/2017, 3:36 PM, changed a total of 2 times.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

MartinE wrote on 2/2/2017, 9:33 AM

OldSmoke, OK I think I get what you're doing now and it looks interesting. I never thought of creating a master project with a master file (DI) of the whole piece and just overlaying corrected sections. So when you render the master project presumably again to XAVC I does VP smart render till it gets to the corrected bits? That sounds fast. This could be very useful for me. I'm sort of new to using lossless DIs but I'm beginning to see all sorts of possibilities to speed up changes.

Many thanks. So much experience on here, don't know what I'd do without it!

set wrote on 2/2/2017, 1:11 PM

Added this to my Other sources tutorial list: https://www.vegascreativesoftware.info/us/forum/vegas-pro-tutorials--103245/

OldSmoke wrote on 2/2/2017, 1:52 PM

Yes, XAVC-I does smart render in Vegas.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

OldSmoke wrote on 2/2/2017, 3:39 PM

By the way. Vegasaur can apply FX to a clip, project section or anything that it can render in the transcoder without having to put it on a timeline first; it is an extremely versatile tool.

Last changed by OldSmoke on 2/2/2017, 3:39 PM, changed a total of 1 times.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)