-
Nearly an hour to render each minute of footage?!
Posted by Andrew O’leary on May 6, 2011 at 7:10 amI have HDV footage minimally edited down to a 90 minute production. It uses a couple of video tracks and about 4 audio tracks. Most tracks have a couple of filters.
Now I’m rendering the footage to the widescreen DV preset in Vegas Pro 8 and it’s taking nearly an hour to render every minute of footage! To be exact it’s rendered about 35 minutes of footage and it’s been going for 26 hours. This is on a quad core 3.6ghz machine with 6 gig of ram (although only 3.5 shows because its win xp 32 bit). Processor usage sits at about 65%-70% the whole time.
Virus scanning is paused and the computer isn’t being used for anything else.
The filters are mainly brightness / contrast and neat video denoiser on the video and sony eq / volume gain on audio.
Why on earth could it be taking so long?!
Dave Haynie replied 15 years ago 7 Members · 7 Replies -
7 Replies
-
Scott Francis
May 6, 2011 at 12:17 pmYES!!! Neatvideo takes a ton of time to process, I use to have about the same system as you and there were a few 36hr renders when I used those types of effects especially Neatvideo….
Scott Francis
Mind’s Eye Audio/Video Productions -
Jeff Schroeder
May 6, 2011 at 1:58 pmTry reducing the Dynamic RAM Preview max (MB): to 0 just before rendering. I find that when rendering mpeg DV and I have a large amount of RAM allocated it starts out fast then quickly fades to a snails pace. Maybe the render engine is 32 bit and has problems when the Dynamic RAM is taking up it’s preferred space.
If this works, please let me know.
Jeff
http://www.narrowroadmedia.com
-
Stephen Mann
May 6, 2011 at 2:03 pmThe denoiser has to examine every pixel on every frame then then the frame has to be rendered. Your long time rendering/encoding does not surprise me. Don’t apply the FX to the whole project if you don’t need to. The event opacity also sometimes trips people up if they accidentally drop the opacity to 99% with an errant mouse movement. You won’t see it but a few minutes of video will take hours to render.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
John Rofrano
May 6, 2011 at 2:06 pmYea, I agree with Scott. Neatvideo takes forever to render. I use it very sparingly. In fact, I preprocess my videos if I’m using noise reduction. That is… I process each clip that requires noise reduction separately, then I use the processed clips in my project. More than likely, I will render the project multiple times to make changes so there is no reason to wait for noise reduction to run each time. I just run it once at the start.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Dave Haynie
May 6, 2011 at 3:23 pmI agree with John… even on my six core AMD, NeatVideo takes a really long time. If I need it, I render to an intermediate format (Cineform, back when that worked with Vegas, now probably MXF/MPEG-2), then move on from there. It’s not the kind of thing you’d like to have to do twice in a project.
-Dave
-
Nigel O’neill
May 6, 2011 at 11:29 pmI agree with all that is said about Neat Video being the culprit, but is Neat Video really necessary? I shot a wedding reception at night recently and was advised by the client that they did not want any bright on camera lighting, so I had to dim down my LEDs. The resulting footage was grainy due to excessive camera gain which was visible on the timeline.
I do notice that when HDV is crunched down to DVD, a lot of the noise ‘disappears’. When I showed that to the client, they did not mind. I also showed them what I had done with Neat Video and they did not like the softening of the image at all. It made the 5 o’clock shadow of the groomsmen look a bit cartoonish like fred flintstone (the older generation on the forum will know what I mean). What I am trying to say is ask the client.
Another suggestion from an Edius editor I know is that he applies a pure black background (i.e. a black background text media event), above the noisy video track and reduces opacity of that event by 60-70% which supposedly minimises the speckling effect of camera noise. It is worth a try in lieu of Neat Video.
Intel i7 920, 12GB RAM, ASUS P6T, Vegas Pro 10 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
Dave Haynie
May 7, 2011 at 4:57 am[Nigel O'Neill] “I agree with all that is said about Neat Video being the culprit, but is Neat Video really necessary? I shot a wedding reception at night recently and was advised by the client that they did not want any bright on camera lighting, so I had to dim down my LEDs. The resulting footage was grainy due to excessive camera gain which was visible on the timeline. “
I shot a wedding a year ago, in a dark night club. They did not want much in the way of on-camera lighting either, so yeah, I had some pretty serious “grain” noise. You can overcorrect with Neat Video, but its like any other tool.
I’ve been working with LPs this week… digitizing a bunch of my Mom’s old 78s and 33s, custom cut discs from the 40’s and 50’s. Very noisy, not in terribly good shape, etc. It’s possibly to apply so much noise reduction on the recording that there’s no sign it came from an LP… but you destroy the music in the process. With a light touch, the result is a day vs. night improvement. Same with video noise reduction.
Going from HD to SD does something of the same thing as Neat… you’re averaging adjacent pixels, so higher frequency noise is gone. A blur on the background will do some of the same things. The Neat filter just does it more intelligently. My final product looks a bit fuzzy for HD on the Blu-ray print, pretty normal on the DVD print, but in both cases a big improvement over the raw video.
Next time… HDSLR!
-Dave
Reply to this Discussion! Login or Sign Up