DV Info Net

DV Info Net (https://www.dvinfo.net/forum/)
-   What Happens in Vegas... (https://www.dvinfo.net/forum/what-happens-vegas/)
-   -   16 hours to render 30 minute film (Vegas 12). (https://www.dvinfo.net/forum/what-happens-vegas/524729-16-hours-render-30-minute-film-vegas-12-a.html)

Jordan Brindle August 31st, 2014 02:59 AM

16 hours to render 30 minute film (Vegas 12).
 
Vegas 12 Pro. Rendering 30-40 min MP4 films With GPU accel turned off, this is what im facing. Ridiculous. How do they always manage to go backwards with Vegas? It crashes with GPU on and sucks with it off.

Anyone manage to get round this? Have been Googling for hours to no avail. I can't get round having GPU off, which improves speed by a huge margin. It's only usable for editing in low-preview mode right now.

Win 7 64bit
ATi Radeon HD 6950 (latest drivers).
i7 @ 3.07GHz.
6GB Ram

Dave Baker August 31st, 2014 04:15 AM

Re: 16 hours to render 30 minute film (Vegas 12).
 
I never got beyond Vegas Pro 10, I haven't used it in a long while and I no longer have it installed anywhere, so these odd things I found out are from memory. I had both 32 and 64-bit Vegas installed.

32-bit Vegas takes around 3 times as long to render the same event as 64-bit. Make sure to be using 64-bit.
Sony AVC is faster than Main Concept.
Need to make sure all processing threads are activated.
Need to make sure Windows is seeing and able to use all the RAM.
Make sure to only render to as high a bit rate as necessary.
Using too many effects slows rendering, especially sharpening.
Use the system monitor to find out where the bottleneck(s) is/are.
Use the desktop CPU widget to keep an eye on things when not using the system monitor.
Always render from one physical drive to another, not partition to partition.
Do not render to or from a USB external drive. (this may be out of date for USB 3.0 drives).
Only render 2-pass when necessary, it doubles the render time.

No doubt I have forgotten a few things.

Dave

Gerald Webb August 31st, 2014 04:16 AM

Re: 16 hours to render 30 minute film (Vegas 12).
 
Hi Jordan,
Just render out to DnxHD then use Handbrake to render your Mp4 from that. (think Handbrake also accepts xavc if that works better for you).

Leslie Wand August 31st, 2014 08:02 AM

Re: 16 hours to render 30 minute film (Vegas 12).
 
you don't actually write what it is you're rendering?

fx, opacity, heavy duty compositing, whatever?

James Manford August 31st, 2014 08:29 AM

Re: 16 hours to render 30 minute film (Vegas 12).
 
Tell us EVERYTHING.

I had this issue with Vegas 12 but got my problems diagnosed on this forum. I absolutely love the NLE with all my heart. I am scared to upgrade to Vegas 13 incase I encounter other problems so i'm staying firm with Vegas 12 as it does everything I need it to do plus more.

You need to tell us if you are using any SONY plugins, or Third Party ones, if the track/video clips opacity levels are not at 100% etc. All of these things effects the render time.

For example, if I add a third party plugin like Twixtor PRO to two or three 10 second clips in my timeline it can take a render of a 5min highlight video that would normally take 12mins to render in 1080p all the way to 35-40mins to render.

Jordan Brindle August 31st, 2014 03:27 PM

Re: 16 hours to render 30 minute film (Vegas 12).
 
1 Attachment(s)
Quote:

Originally Posted by Dave Baker (Post 1859681)
I never got beyond Vegas Pro 10, I haven't used it in a long while and I no longer have it installed anywhere, so these odd things I found out are from memory. I had both 32 and 64-bit Vegas installed.

32-bit Vegas takes around 3 times as long to render the same event as 64-bit. Make sure to be using 64-bit.
Sony AVC is faster than Main Concept.
Need to make sure all processing threads are activated.
Need to make sure Windows is seeing and able to use all the RAM.
Make sure to only render to as high a bit rate as necessary.
Using too many effects slows rendering, especially sharpening.
Use the system monitor to find out where the bottleneck(s) is/are.
Use the desktop CPU widget to keep an eye on things when not using the system monitor.
Always render from one physical drive to another, not partition to partition.
Do not render to or from a USB external drive. (this may be out of date for USB 3.0 drives).
Only render 2-pass when necessary, it doubles the render time.

No doubt I have forgotten a few things.

Dave

Thank you Dave this looks very useful, will go over all these things.

Quote:

Originally Posted by Gerald Webb (Post 1859683)
Hi Jordan,
Just render out to DnxHD then use Handbrake to render your Mp4 from that. (think Handbrake also accepts xavc if that works better for you).

Could be a solution thank you.

Quote:

Originally Posted by Leslie Wand (Post 1859700)
you don't actually write what it is you're rendering?

fx, opacity, heavy duty compositing, whatever?

30 minute 1920x1080 25p MP4 film with basic colour correction and soundtrack. Single track. A few basic fades. Nothing different to what i have rendered in the past with Vegas 10 which would only take 1.5/2x the length of the video to render.

Quote:

Originally Posted by James Manford (Post 1859704)
Tell us EVERYTHING.

I had this issue with Vegas 12 but got my problems diagnosed on this forum. I absolutely love the NLE with all my heart. I am scared to upgrade to Vegas 13 incase I encounter other problems so i'm staying firm with Vegas 12 as it does everything I need it to do plus more.

You need to tell us if you are using any SONY plugins, or Third Party ones, if the track/video clips opacity levels are not at 100% etc. All of these things effects the render time.

For example, if I add a third party plugin like Twixtor PRO to two or three 10 second clips in my timeline it can take a render of a 5min highlight video that would normally take 12mins to render in 1080p all the way to 35-40mins to render.

No third party plugins active. As described above, basic color correction, grading, fades - a few Sony Stabalizers. No sharpening. I've never had to optimize my Sony Vegas ever before and have been using it since VP9. It always just works. I do want to use VP12 as it appears to be a bit more stable than 10, its just the rendering is painful without GPU support.

As seen in the attachment, computer becomes completely unusable whilst rendering a 5 minute video. CPU Usage @ 100%. Something must be set wrong somewhere?

Juris Lielpeteris August 31st, 2014 10:36 PM

Re: 16 hours to render 30 minute film (Vegas 12).
 
Quote:

Originally Posted by Jordan Brindle (Post 1859736)
30 minute 1920x1080 25p MP4 film with basic colour correction and soundtrack. Single track. A few basic fades.

Quote:

basic color correction, grading, fades - a few Sony Stabalizers
i3@1.8 GHz with Intel HD 4000 video in my laptop just works more faster... Time of render of similar 30 min project but 50p AVCHD with 5.1 soundtrack with GPU accel turned off takes about 3 hours
There's something you're not told or your pc is wrong.

Leslie Wand September 1st, 2014 12:22 AM

Re: 16 hours to render 30 minute film (Vegas 12).
 
if you open new project and just load a few clean clips without any fx, etc., how does it render?

looks like there's either an fx, track opacity perhaps, or even bad media.

how's the pc doing otherwise?

scanned with malwarebytes?

Jordan Brindle September 1st, 2014 04:35 PM

Re: 16 hours to render 30 minute film (Vegas 12).
 
Quote:

Originally Posted by Leslie Wand (Post 1859758)
if you open new project and just load a few clean clips without any fx, etc., how does it render?

looks like there's either an fx, track opacity perhaps, or even bad media.

how's the pc doing otherwise?

scanned with malwarebytes?

Just threw 40 mins of footage onto a raw timeline. 2 hours 45 mins to render. This is what i have come to expect of finalized films with FX/correction etc with VP10! Perhaps there is an issue with some FX and VP12 as you have said... But what? The same footage, edited, is estimating 8 hours 6 minutes to render.

Here are the FX active at track level (2x Video Tracks):
Video:
Brightness Contrast.
Color Corrector.
Color Curves.
Sony Stabilization (handful of clips).

Audio:
Noise Gate.
EQ.
Compressor.

Video Source:
1080p DSLR .MOV files @ 25p.

Project Properties:
1920x1080p
Progressive
32 Bit Full Range
1.0 Aspect Ratio

Render:
45 Mins Length
MainConcept MP4
10,000 Bitrate
25p

Encode: CPU Only.
GPU Acceleration: Off
CPU Threads: 4

:(

Leslie Wand September 1st, 2014 05:09 PM

Re: 16 hours to render 30 minute film (Vegas 12).
 
and what happens if you just do a straight render of that footage, ie, no fx, stabilisation, etc.,?

this is just to double check that it's not a wayward / corrupt fx or something....

AH, as someone later wrote - 32bit? why?

Jordan Brindle September 2nd, 2014 03:36 AM

Re: 16 hours to render 30 minute film (Vegas 12).
 
Quote:

Originally Posted by Jordan Brindle (Post 1859842)
Just threw 40 mins of footage onto a raw timeline. 2 hours 45 mins to render. .

As stated above. It renders in good enough time.

Juris Lielpeteris September 2nd, 2014 05:42 AM

Re: 16 hours to render 30 minute film (Vegas 12).
 
Quote:

Originally Posted by Jordan Brindle (Post 1859842)
32 Bit Full Range

Why?
It may be the real cause of too slow render.

Jordan Brindle September 2nd, 2014 01:21 PM

Re: 16 hours to render 30 minute film (Vegas 12).
 
Quote:

Originally Posted by Juris Lielpeteris (Post 1859890)
Why?
It may be the real cause of too slow render.

If im not mistake it produces a better looking video / precision for color correction / grading? It's what i always set in VP10 with no issues?

Juris Lielpeteris September 2nd, 2014 11:04 PM

Re: 16 hours to render 30 minute film (Vegas 12).
 
Significant improvement of quality can be only in some cases, but significantly increase the time of render take place always. This means that 32 bit processing is appropriate to use only in short nested projects.

Jordan Brindle September 3rd, 2014 06:42 AM

Re: 16 hours to render 30 minute film (Vegas 12).
 
Quote:

Originally Posted by Juris Lielpeteris (Post 1859974)
Significant improvement of quality can be only in some cases, but significantly increase the time of render take place always. This means that 32 bit processing is appropriate to use only in short nested projects.

I see. So what would you class as a short nested project? And in what cases would 32 bit make the difference?

I'm 100% certain this is how i have always rendered in VP10. But upon switching between 8 bit and 32bit i don't see a big difference in my preview window.

I am confused right now.


All times are GMT -6. The time now is 02:50 AM.

DV Info Net -- Real Names, Real People, Real Info!
1998-2024 The Digital Video Information Network