Comments

DJPadre wrote on 8/2/2009, 9:46 AM
yup.. .on the quad core desktop as well as the dual core laptop...

the laptop crashes, the desktop doesnt...

no signs of memory leaks either, just the red frames...
MarkHolmes wrote on 8/2/2009, 9:49 AM
Yes. Frustrating. I'm back on 8.0c,, which is flawless. Hoping that 9.0b, 9.0c, or d is the same.
erikd wrote on 8/2/2009, 12:23 PM
Yes, I got the "reds" too with 9a. I did a small project recently as a test on 9a and quickly realized that I needed to run back to 8c for safety. I won't try any real work now until 9b.

I first got on board with Vegas at 8b and it was pretty stable. Does it usually take the b version to get your work done?

Erik
FrigidNDEditing wrote on 8/2/2009, 6:36 PM
not since 8,

usually it's been a release.

Dave
[r]Evolution wrote on 8/2/2009, 7:55 PM
I am seeing them occasionally on my timeline.
Are you guys seeing these 'Reds' on your final render?
Marc S wrote on 8/3/2009, 12:31 AM
Yes, I'm getting the reds on a 2-hour multicam project (cineform 1920x1080). Also getting a decent amount of crashing especially if I'm using the secondary monitor. I'm also getting strange glitches in my rendering that I have to redo. Still hoping for a stable Vegas for long form HD projects but that may never happen.

Marc
epirb wrote on 8/3/2009, 5:09 AM
Im getting it when applying the "fill Light" filter plug... to an M2t.
Arthur.S wrote on 8/3/2009, 7:33 AM
I've put in a support ticket. Hopefully we'll get an answer.
ritsmer wrote on 8/3/2009, 7:37 AM
Got the "reds" too (Vegas 9.0a x32 under Windows 7 x64) - howewer not after having applied the "2 GB hack" from Mr. Blink.
Cliff Etzel wrote on 8/3/2009, 9:10 AM
So the question begs to be asked - Does this happen with frame based AVI's - either uncompressed or Cineform Intermediates? It seems to me that ever since I moved to Cineform, the issues of red/black frames hasn't reared it's ugly head.

From what I can tell, editing Long GOP based footage seems to cause Vegas to go thru this issue.

Cliff Etzel
Videographer : Producer : Web Designer
bluprojekt
Marc S wrote on 8/3/2009, 10:38 AM
Cliff,

I'm using cineform captured at 1920x1080 (high quality) and I'm having the problem. My project is also a 4 camera shoot with 2 hours on the time timeline so it may just be more than Vegas can handle. It does not happen all of the time and I have more problems with Neat video and magic bullet (editors version) than the red frames. Neat video is especially prone to crash my system.

I'm using a Quad on Windows 7 with 8 gigs of ram. V9 (32 bit)
Arthur.S wrote on 8/4/2009, 1:23 AM
OK, here's the reply from the support ticket. Have to say, even if it works it's very unsatisfactory. Are we really expected to re render everything Vegas captures?? By the way, what's the '2GB hack'?

"1. Add the clips to the timeline.

2. Go to File > Render As. The Save As Type should be set to "Video For Windows (*.AVI)" and the Template should be set to "HDV 1080-60i Intermediate". Now click Save. The files will be saved as an AVI that utilizes the Cineform HD V2.5 codec. It retains all the detail from the M2TS file.

If you do not see "Video For Windows (*.AVI)" and the Template "HDV 1080-60i Intermediate" in your drop-down menus, then you can render the file to MPEG-2. Go to File > Render As. The Save As Type should be set to "MainConcept MPEG-2" and the Template should be set to "HDV 1080-60i". Now click Save.

After the file is saved (either AVI or MPEG-2), replace it with what's on the timeline. Now you'll experience smoother playback and more precision over editing the project."
ritsmer wrote on 8/4/2009, 1:50 AM
Must be a way-around for users that do not have V8.0c.

The "2 GB hack" is described here:
http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=648182
Arthur.S wrote on 8/4/2009, 7:14 AM
Thanks Ritsmer, but the hack looks like for V 8.0. Not sure it's of any benefit for 9a?
ritsmer wrote on 8/4/2009, 9:06 AM
Right - but I tried it for 9.0a and it works perfectly here.
Arthur.S wrote on 8/5/2009, 3:12 AM
I seem to have solved this by reducing the amount of RAM allocated to Vegas. I did have 3072mb (From a total of 8gig). Reduced it to 2048mb, and all seems hunky dory. I'd like to use more RAM for previewing though - which I guess that hack would let me do?
Marc S wrote on 8/5/2009, 8:05 AM
Ok... I made the 2gb hack to my V9 program files and althought it's just been a couple of days, things seem to be better. Hopefully I'm not speaking to soon but Vegas seems more stable and snappy now.
ritsmer wrote on 8/5/2009, 9:08 AM
Arthut S: The 2 GB Hack is to my opinion only good for the 32 bit version of Vegas.
The 64 bit version can -by the 64 bit design- already by itself handle large memory areas.
It will not allow any version to use more preview RAM than the 3 GB you have.

I "like" the Vegas 9.0a 32 bit more for the time beeing and in order to make it (so it seems to me, at least) more stable I apply the 2 GB Hack.

"Like" = available 3.rd party plugins etc.
Marc S wrote on 8/5/2009, 10:03 AM
I'm in the same boat. I use Magic Bullet for all important projects so I'm sticking with 32 bit for now.