gpu rant!

ushere wrote on 1/24/2013, 1:56 AM
sorry, don't know where else to rant?

so, NOTHING has changed re pc since my last, almost identical arty-farty video..... gpu ON, but not render assist.

so, after scratching my head as to why my 3 large jpgs (13800X1020) kept crashing my renders, i thought, corrupt files. into ps, export as png (yes, i was being lazy not converting first as i usually do). still same crashing at the same spot. ok, getting irritable to say the least. scrap all keyframes on all moves, simple dissolves. still crashing.

of course, since my last job had even BIGGER stills (png), i completely forgot about having gpu ON.

about to throw the pc through the window and reload ppro cs6 (ugh) it suddenly occurred to me to check EVERYTHING know to man with regards to vegas - you can see how the thought of ppro scared me.

gpu OFF and i'm back in love with vegas,

FOR GOODNESS SAKE SCS, GET THIS BLOODY GPU CR*P SORTED OUT.

i mean i read about 6XX having problems but my lowly 550ti should surely be bullet proof.

ok. rant over.

no need to reply, but if you wanna shout, this threads as good a place as any ;-)

Comments

ritsmer wrote on 1/24/2013, 2:34 AM
rant=off ...

... but - something strange IS going on:

After some troubles with the newest drivers for my cheapo Nvidia GTX 450 my old faithful Vegas 11 32 bit setup seemed to behave nice and stable again and with GPU assist ON as always.

Thinking that is was time to try out my Vegas 12 I installed it yesterday morning and played around a little and then continued my serious work on the always so faithful Vegas 11 32 bit..... but now:

at the very first render thereafter (to my always used standard format mpeg2 1080 50i at 31 Mbps) a lot of pixelations with mostly green and red colors popped up all the time in the rendered video. As I did not believe my own eyes I played it through different hardware - but the pixelation was in the rendered video.
Thinking that these sudden errors in rendering with Vegas 11 32 bit might - though most unlikely - have something to do with the new installation of Vegas 12, I uninstalled/deleted/registry etc. etc. both V11 and V12, booted the machine and installed Vegas 11 again.
Result: now Vegas 11 renders again without pixelations.

I do not want to rant about anything in particular -just wanted to tell about this quite surprising experience - and having worked for a living with computers and later PCs for the last 40 years I am quite sure what happened.
videoITguy wrote on 1/24/2013, 4:44 AM
It has been documented ever since the october release of VPro12 that you cannot have working concurrent installs with VpPro11. Working is the keyword, because if you are willing to alternate software drivers, and settings, you can get them to alternately behave on the same PC.
ritsmer wrote on 1/24/2013, 8:01 AM
- so I will just keep my rock stable V11 by itself on my PC until building a new machine in the autumn :- )
mark-woollard wrote on 1/24/2013, 9:44 AM
By "working" do you mean running?
VidMus wrote on 1/24/2013, 2:30 PM
There seems to be a size limit when it comes to *.jpg's.

With 4 meg jpg's and the preview mem set higher than 200 and GPU=on I would get a crash. With the preview mem set at 200 I did not get a crash.

However, you are working with a lot larger pics than I was so even with the default 200 it would probably crash anyway.

I think this is an Nvidia/GPU problem as in how much it can handle instead of a Vegas problem.

So the actual fix probably should be done by Nvidia instead of SCS and I sincerely doubt if Nvidia will do anything to fix this.

So the monster pics will need the GPU to be off.

A suggestion, render the pic portions of the projects first with a lossless codec and GPU=off, add those pic video clips to the main project and then do a final render with GPU=on.

I hope this helps,
Danny Fye
www.dannyfye.com/ccm

ushere wrote on 1/24/2013, 3:53 PM
@ danny - very true. fortunately i'm doing ok with gpu off on these large jpgs. although i've actually converted most of them to png.
my preview ram is 200.
Zeitgeist wrote on 1/24/2013, 4:04 PM
I use V12 & V11 & V10 on the same machine swimmingly, so the "document" needs a footnote. The only difference here is v12 has the preview ram set to 0. There are a lot of red herrings about why V12 has problems but the common factor is always V12. We all know that in varying degree. In time there will be an update & V12 will be more stable.