Help! Reea-ally Slooo-ow Render

Soniclight wrote on 7/6/2012, 2:52 AM

VP10e 64-bit
Project Rez: 1920x960 1:0 Pix ratio Progressive
Total Video Length: 6:05 min.
Project Tracks (all events are the same length):
1. 1 Event =1920x960 Uncompressed AVI intermediate - no audio**
2. 1 Event = Music .WAV
3. 1 Event = Background Sound Effects WAV

**

Render is for a test at half rez (960x480) to then Handbrake for a 720x386 MP4. Vegas render started 3 hours ago, still only at 62%. Usually Vegas uses all of my cores almost at full tilt. The original render for that no-audio uncompressed AVI on track #1 above that had to slog through an ungodly amount of tracks and effects pushed my CPU as expected and rendered in reasonable time.

But as you can see in this image of my CoreTemp widget, with this simple 3-event render it's barely using any of them:

What am I not getting here? I can't recall whether I unchecked the alpha channel rendering for that no-audio AVI -- could that be the problem?
But did uncheck it for this reeee-ely slooo-ow render.

Thanks.

Later Edit: And then it crashed while I was writing this due to low disk space on the extra drive I was doing this to. Now that was dumb.
BUT here is something that makes no sense (and why I ran out of room):

The aborted AVI is still there clocking in at 164 Gb.
How can a file that is half the resolution of the AVI it's rendering out be 4x larger??
Audio does not take up that much room.
And trying to play it... all black, no sound.

Something nutty is going on here...

Basic Sys Specs:

Windows Version: 7 Home Premium 64-bit
Processor:AMD X6 1090T Phenom II Black Edition 6x3.2 Ghz - no overclocking
RAM:16 Gb. DDR3
Hard Drives: Multiple SATA2 7200 Rpm.
Sound Card:M-Audio Delta Audiophile 2496 (Analog I/O)
Video Card:nVidia GeForce 430 GT

Comments

ushere wrote on 7/6/2012, 3:24 AM

shouldn't that be half res @ 480, not 460?

Soniclight wrote on 7/6/2012, 3:26 AM

T'is. Just a typo :)
Corrected.

Soniclight wrote on 7/6/2012, 4:13 AM

UPDATE...

OK, rebooted, started over. CPU still isn't on full tilt, but... it's already at 15% after +/- 10 minutes of rendering (according to my clock, not the never-accurate application "time remaining..." info). So it appears that things are back to normal. I suppose nutty stuff happens (that humongously huge 164 Gb output file that was only about 65% of the video on that wacky render which was all black and no audio still puzzles me...)

SEE my next post...
Still no-go.

ushere wrote on 7/6/2012, 4:50 AM

be interesting to guess what percentage of 'bug', 'crash', 'problem' postings etc., written here are originally written in 'panic' mode.

i for one have done so, most often under the influence of a 'senior moment'. that said, my swap media was a JUSTIFIED panic moment!

Soniclight wrote on 7/6/2012, 5:31 AM

Got to go to bed, etc., but truth is, this is NOT resolved.

It all started well on second render, but then Vegas got that error again, and the aborted AVI render is now 174 Gb. which is why it crashed -- ran out of space on this drive too. I can understand the latter, but the insane file size with nothing but black frames and no sound DOES NOT make any sense.

Again: It's half the resolution of its video component track, yet more than 4 x the file size even when not fully rendered.

TheHappyFriar wrote on 7/6/2012, 5:44 AM

Are you rendering the selected area or whole project? Sounds like you might be doing the whole project and, for some reason, it thinks it goes on quite a bit.

Soniclight wrote on 7/6/2012, 6:06 AM

Yes, the whole but as stated in my opening post, it's only a 6:05 minute project - pittance compared to what probably most of you throw at Vegas.
That can't be the problem:

Only 3 tracks respectively with one AVI and two WAV events. No FX, no transitions.
No compression besides rendering at 1/2 rez of the one AVI event.

And/but...

Everything worked fine when that one video event was a rough cut 960 x 480 WMV a couple of days ago. Must be the uncompressed AVI messing things up. But it shouldn't for it took only 3 hours and 60 Gb to render the original video work project file that had all the FX and many tracks but no audio.

videoITguy wrote on 7/6/2012, 6:27 AM

Not sure at all certain what you are attempting - but this 1/2 rez stuff bothers me.... please select a normal template render out with ordinary settings to say a highly lossy and speedy codec so you can see if this timeline really works.

Odd dimensions are not a go for many codecs.

Soniclight wrote on 7/6/2012, 6:32 AM

This 1/2 rez may not be a standard resolution but it conforms to 16x image scaling -- the optimum for quality resolution. Resolution isn't the problem, I've used this size many times and have several render presets with it. And this is an uncompressed AVI render, not some complex codec going on. One uncompressed AVI video event total, one uncompresssed AVI out - should not be a problem.

MarkWWW wrote on 7/6/2012, 12:01 PM

What does MediaInfo say about the output .avi?

Might give a clue as to what is going on.

Mark

robwood wrote on 7/6/2012, 12:50 PM

are you rendering in 32-bit or 8-bit?
if 32-bit, you might wanna try a render in 8-bit to see how long it takes and what the file size is.

Soniclight wrote on 7/6/2012, 3:14 PM

Project is in 8-bit - I don't use 32-bit for I have no need for it (I don't do pro broadcast, etc. stuff).. I deleted the nutty output file so can't look at it with MediaInfo. I'm trying a render now with an older stand-in 960x480 WMV as the video event/track and see if that works. If it does, it's the uncompressed AVI event that's been the problem.

A bit later...

I aborted that render for the output file was already 55 Gb. at only 25% render. Maybe it is rendering at 32-bit even though "use project settings" (which is at 8-bit) is in the render out uncompressed settings. This time the output file was automatically deleted so I couldn't MediaInfo it.

May be a .veg corruption, so I'll try a new one from scratch see what that does...

Soniclight wrote on 7/6/2012, 5:24 PM

OK, looks like it may have been some .veg project corruption for with a new virgin 3-track one I've had these results:

- Using the old 960x480 WMV rough cut as video event took 20 min. to render to a same-resolution uncompressed AVI 15.7 Gb. file

This tells me that the video event source file size affects render time: if I use a 1920 x 960 uncompressed video event, it will take probably 4x longer to render. But at least the result won't be the insane size that happened in the original .veg.