9.0b is here ....

CorTed wrote on 8/27/2009, 3:53 PM

9.0b just released

Go get it

Notable fixes/changes in Version 9.0b
Resolved an issue that could cause the contents of media generators (most often text generators) to change when the Undo command was used.
Fixed a bug that could cause Vegas to crash during startup on some computers running Windows XP.
Fixed a bug that could cause still images to appear out of focus when rotated via Event Pan/Crop.
Fixed a bug that could cause audio dropouts in XDCAM SD (DVCAM) MXF files.
Fixed a bug that could cause an error when conforming trimmed XDCAM clips on the PDW-U1 deck.
Fixed a bug that prevented some QuickTime files from reading audio properly.
Fixed a bug that prevented metadata from being imported with 720-50p XDCAM clips.

Ted

Back to post

Comments

Harold Brown wrote on 8/29/2009, 1:13 PM

My project remains unworkable because of a sluggish time line. I will need to break it up and do some nesting. Hopefully that will resolve the problem. It is SD but 50gig of video and audio files is killing it. It was working in Vegas 8 but not in 9. Time for a new machine although the old one is only 16 months old.

winrockpost wrote on 8/29/2009, 2:57 PM

50 gig of sd video should not be killing it, should not even be wounding it.

DJPadre wrote on 8/29/2009, 10:30 PM

noticed 9b now has a wind up of frame rates during playback from TL not good when u watchign it pause, then start up again only to believe your audio is now out of sync...

during playback switch from prev to draft then back again and framerate comes back (as per almost every other build of vegas)

Id rather Vegas DROP frames as opposed to playing frames out of sync....

DJPadre wrote on 8/30/2009, 3:50 AM

after further observation, it seems the red frames on the media clip on the timeline issue occurs more on mixed format projects than native single format /Ls

as an example, on a HDV only project, i see no red frames, throw some DV in there or uncompressed or whatever and ONE of those formats will puke and give u red thumbs on T/L

ritsmer wrote on 8/30/2009, 5:36 AM

@ DJ: have u applied the 2GB Blink Hack? - here it does wonders scaring away "reds".

DJPadre wrote on 8/30/2009, 6:11 AM

no.. what might that 'hack" be??

DJPadre wrote on 8/30/2009, 7:28 AM

audio sync slipping in preview... like i said before, id rather it drop frames... this is ridiculous..

9a didnt have this issue...

ritsmer wrote on 8/30/2009, 7:35 AM

@DJ: Ah? here it comes...: [Link=www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=648182]

enjoy :-)

Brad C. wrote on 8/30/2009, 7:40 AM

Blink hack worked for me. V8 and V9.

DJPadre wrote on 8/30/2009, 11:11 AM

muchos gracias senor!

Harold Brown wrote on 8/30/2009, 11:19 AM

50 gig of sd video should not be killing it, should not even be wounding it.
I agree but it just died the second I started using 9.0 and now it does the same thing in Vegas 8. Something happened somewhere along the line. I think I need to start from scratch with a new machine that is dedicated to Vegas only and use the current machine for everything else. I feel the need, the need for speed.
The problem is the editing jobs have been fewer this year so I cannot put together a new machine for a few more months. Vegas works for all of my other projects.

imaginACTION_films wrote on 9/2/2009, 12:16 AM

Just reporting that I've solved the red frames issue by setting dynamic RAM prveiew to zero and max number of threads to 1.
Vegas 9.0b 32-bit working with HDV files.

Strange, though, I was able to work on pretty huge files a year ago with 1024 dynamic and 4 threads, then the red frames started appearing. No idea why, but at least I've been able to stop them. Didn't need the blink hack at this stage.

David S
imaginACTION

DJPadre wrote on 9/2/2009, 4:07 AM

i did a similar test last night.. got rifd of the red frames by dropping DRP down to 256...

was gona post here then u beat me to it.. lol
Another hting i noticed was that playback was FAR more efficient when i turned off "adjust size and quality for optimal playback"

this seems to have fixed this issue

Christian de Godzinsky wrote on 9/2/2009, 12:03 PM

Hmm, I would not say that anything you did FIXED any issues, you just found workarounds for some serious problems still under the VP9 hood...

Hope SCS takes this seriously, there are too many complaints about this, and lots of UNHAPPY users. I myself have been "solving" some problems (crashing) by reducing down to one render thread. Come on - I have payed a premium for a quad core and the software is so crippeld that it just runs on one CPU with three idling...

Please put in an official support ticket (complaint) if you have not done that yet.

Christian

ritsmer wrote on 9/2/2009, 1:19 PM

It is not so easy:

I have 2 machines - both with XP pro SP3+ x32 and nothing else running.
Both have V9.0b x32 with 2GB Hack installed.
On machine 1 I get "reds" opening the project and "low memory" when rendering - on Machine 2 no problems whatsoever.

I noticed that on machine 1 Vegas is assigned 1,4 GB memory in the Task Manager for opening the veg - on machine 2 Vegas is assigned 650 MB.
The veg and media is 100% the same - opened from the same NAS.

My guess is that when a Windows installation gets old - Machine 1 is more than 2 years while Machine 2 is 1 week - it gets "strange" - and this is one of the reasons why I rebuild my Windows installations from scratch every 1-2 years.

And so it is quite conceivable that - reducing the number of render threads or the preview RAM - may let you run Vegas on a halfway sick Windows installation.

imaginACTION_films wrote on 9/3/2009, 6:58 PM

I definitely agree this is a workaround, not a fix.

We all know how embarrassing - and bad for business - it can be when you're working with a client to a tight deadline and you get unplayable red frames, captures that won't and disappearing titles. SCS fixed the Titles glitch but not before the client had witnessed the problem. Not good in a product called "Pro".

At least now I have a way of continuing to work without red frames.
David