9.0b is here ....

Whitlam wrote on 8/28/2009, 2:39 AM

Doesn't fix the issue with 1920 x 1080 50i PAL renders which are unplayable (video slow, sound normal) in any media player and can't be burnt as a DVD (same issue - slow choppy video).
The issue was reported and accepted as a problem by Sony, unfortunately it hasn't yet been fixed.
Back to 1440 x 1080.

A. Grandt wrote on 8/28/2009, 6:32 AM

I doubt you'll see any bugs fixed apart from those mentioned in the release notes.
As mentioned. this point release was only to fix some fatal flaws in 9.0a nothing else.

It is good to see that people are trying to stress 9.0b, I'm just hoping that no new fatal ones will crop up in it. As a software developer my self, I can only say that we all have major screw-ups in our baggage, but we do try to avoid the encores.

A. Grandt wrote on 8/28/2009, 6:35 AM

Whitlam wrote:

I haven't seen that one before.

What are your settings, and/or do you have a link to an existing discussion on that topic?

xjerx wrote on 8/28/2009, 6:57 AM

Dang...nothing new for RED.

Spot - Do you know when or how Sony will implement RED's SDK with the new color science?

Jeremiah

baysidebas wrote on 8/28/2009, 7:23 AM

Reminds me of a scatological joke from the 60's where the punchline was a headline in the Daily News: "Shit Storm Hits Japan, Cork Kills Three."

busterkeaton wrote on 8/28/2009, 8:10 AM

If you ever worked in a software company, you know that a major release in August is pretty unusual, because it's when you probably have the most workers in various departments on vacation.

My guess is that all the other bugs that got fixed besides the text bug, were already identified and ready for the next release, when they realized they needed to fix the text bug ASAP.

JJKizak wrote on 8/28/2009, 10:17 AM

They didn't mess up the blue snaps so I'm happy. Someone is bound to see the humor in this.
JJK

DJPadre wrote on 8/28/2009, 10:57 AM

DSE, as much as i luv and respect ya to bits, I just have to respond to this...

"I would expect you'll see a slower, more developed release that hopefully has some Beta testing behind it."

This SHOUD have happened since V6... Since V6 weve had newborn launches of new version puke consistantly. This IS a Beta issue and if testers did their jobs, and Sony took responsibility for the investment WE make, then none of this would be happening.
All NLEs' have issues, but your comment above just cements the fact that Vegas itself could be better managed.

"That said, please keep writing how easy it is to find/fix bugs in an app of this magnitude. "

Who else if going to do it? Sony?? The flipside to that, I dont see why thousands of hours of investment productivity (ie $$$) needs to be lost by investors, simply because Sony are skimping on R&D

OK reponse over... flame all you like... back on topic...

it seems the red frames are still there on the timeline with HDV mt2 interlaced PAL.. oh joy...

Brad C. wrote on 8/28/2009, 11:21 AM

DSE, as much as i luv and respect ya to bits, I just have to respond to this...

The answer you seek is really quite simple. You and the relationship you have with Vegas is like a battered girlfriend to her abusive boyfriend. If Vegas has been doing you wrong ever since V6 (forever ago), then why do you keep coming back if you know things haven't changed (to YOUR standard)!? If we tell battered girlfriends/wives to leave their men, never look back, and find someone better.....then maybe it's time you found a better NLE developer that treats you the way you feel you need to be treated, and never looked back. There's something psychologically wrong with people who are stuck in a vicious cycle of being mentally or physically mistreated and yet they keep coming back for more. I don't get it.

Are you scared to jump ship or what?

The lack of patience with some Vegas users is astounding.

LReavis wrote on 8/28/2009, 12:17 PM

IMHO, Vegas is well-worth the inconveniences. However . . .

Last night I tried to open 2 VEGs that I'd been working on in 9a. My short .VEG went OK, the long VEG crashed. When I saw that it crashed every time while (for some reason) redrawing the waveforms & frames, I canceled that process as soon as it started, then un-checked the Waveforms and Frames box in the View menu. After rebooting, all opened OK.

Next, I tried to render it. It rendered until it got 6 min. 34 sec. into the timeline, then crashed. About the same as Vegas 8b, but not as good as 9a (as I recall). No worry - I plan to go to 64 bit Win7 on Oct. 22 and use Blink's memory fix.

Reboot, reopen, tried again with "Waveforms & Frames." After half an hour (at least), all finished and no crash. But I saw some red events on the TL and when I tried to play one, it played and played and played - Vegas had crashed and I could only get rid of it with the Windows Task Manager.

Conclusion: It seems that 9b is a little less stable than 9a for me.

Running 32 bit on WinXP, Q6600, 4 Gig RAM, Asus P5B.

A. Grandt wrote on 8/28/2009, 1:08 PM

LReavis, if the same veg crashes 8.0c, 9.0a AND 9.0b, even if it is at different places, I'd seriously consider the possibility that the veg, or the media used in it, are corrupted.

Spot|DSE wrote on 8/28/2009, 1:37 PM

Given that it's a recent release...I dunno how fast Sony will implement Color Science. I'd like to see something that emulates Scratch. :-)
Although the Vegas/RED workflow is very fast compared to most, there is still a lot of room for improvement.

LReavis wrote on 8/28/2009, 2:07 PM

all of my long/complicated VEGs crash on all 3 of my computers, including my old Intel single-core running on an Intel MB. This has been the experience of many of us and has often been posted. My VEGs that are either short and complicated, or long and not including many feathered masks, etc., render just fine on all 3 machines. But long + complex = crash. However, several others who have noted this problem have found relief with the same VEGs running on 64 bit OS with Blink's memory fix. That's why I already have paid for Win7 - just counting the days 'til Oct. 22

DJPadre wrote on 8/28/2009, 8:52 PM

I dont ant to sway off topic so i'll be quick (i promise)

"You and the relationship you have with Vegas is like a battered girlfriend to her abusive boyfriend. "

LOL

If Vegas has been doing you wrong ever since V6 (forever ago), then why do you keep coming back if you know things haven't changed (to YOUR standard)!?

((I dont have an issue with Vegas in general, I have an issue with the way its evolved.. compared to others))

There's something psychologically wrong with people who are stuck in a vicious cycle of being mentally or physically mistreated and yet they keep coming back for more. I don't get it.

((I think you're missing my point, but moving on... ))

Are you scared to jump ship or what?
((err... i use every NLE on the market fo a variety of work, thats not the problem. The problem is that Vegas IS probably the most efficient NLE on the market. Whta it lacks can be worked around, however it still doesnt fix teh issue of R&D, which it sorely needs))

The lack of patience with some Vegas users is astounding.
((I have to disagree with that. Thre are at least a dozen used that I know who are still on V8 after v9 has let them down. When was V9 released???
The point is that patience in this game is not a virtue when there are so many cheap and nasty competitors out there. By competitors i refer to our comeptitors as content creators, AND competition as NLE investors.
Sony has a tightly knit loyal group, but the only REAL means for expansion is to bring people over who jump ship. To be able to execute THAT is nothing to sneaze at...

ok back to topic...

AVCHD issue also seen here...

xberk wrote on 8/28/2009, 10:20 PM

Working in 9.0b 64bit since yesterday. No new issues yet for me. In fact, very smooth. UNDO working as it should. No gen media problems. But keeping a watchful eye and saving as I go. Good work habits developed under 9.0a .. Happy camper so far.
- Paul

Grazie wrote on 8/28/2009, 10:37 PM

Paul: "But keeping a watchful eye and saving as I go" - unless you haven't already, try out Edward Troxel's Auto Save. Saved my backside on many occasions! Oh yes . . . .

Working well here too. I can now get my text stuff done that was hanging over from 9>9a. I'm keeping the "Nested Audio Proxy file workaround" employed though.

Grazie

DJPadre wrote on 8/29/2009, 12:23 AM

the issue with autosave can be resolved by creating differnt temp directories for each version of vegas. I had to work that out when v7 was released...

one other thing, does anyone know if they sorted out the workspace layout reset issue?
Each time i launch v9, the workspace layout resets to default.

I have to manually go in and load up my own workspace

PeterWright wrote on 8/29/2009, 1:01 AM

That must be a setting somewhere, DJ - mine always opens how I last used it. I do have automatically open last project enabled, so don't know if this affects it.

ritsmer wrote on 8/29/2009, 1:24 AM

Promised to report back on my 9.0b issue.
After installing 9.0b on my brand new XP Pro x32 built Laptop (with absolutely NO viruscheckers, updaters or anything running) V9.0b "Stopped Working" opening the problem 9.0a veg from my main machine.

Having a lot of earlier backups of that project I went back some time and started opening. All opened without problems.
Then I tried the problem-veg again - and now: Ok no problems. Aha: must be some kind of a little green Gremlin.

Then I went back to my main machine (MacPro double Xeons Win 7 x64) and gave it a Maximum Pest Control shot:

-Restored to before installing V9.0b
-Uninstalled V9.0a x64
-Installed V9.0b x32 over existing V9.0a
-Applied the 2 GB Blink Hack
-Deleted each and every *.sf* file on all 4 harddisks

And: Vegas 9.0b now runs great. Have not seen any problems. Can open all old vegs. V9.0b can even open my old V8.0c vegs which 9.0a didn't like.

And Vegas 9.0b works great. Besides all the other improvements I really like the speed - i.e. previewing AVCHD 1280x720p directly on the timeline with stable 29.9 Fps in Preview, Full and only 12-20 percent CPU-load.

Edit:
PS: Yes, yes: I know. Should have applied the 5 steps above one-by-one to see where the problem was - But sometimes you feel like shooting first and asking later :-)

DJPadre wrote on 8/29/2009, 5:35 AM

"That must be a setting somewhere, DJ - mine always opens how I last used it. I do have automatically open last project enabled, so don't know if this affects it."

Ive got it set here too... i think its reverting or referencing a V6 layout which I might have to nuke... I'll be checking this later this evning...

In the past Vegas 8 used to access settings saved within otehr Vegas directories. Vegas 7 doesnt have this issue (of accessing settings from other vegas intals)
Problem though is if i uninstal v6 or v7 i lose all my preset render settings and any other preset (non fx) so i need ot keep the lot intsalled even though i dont want to

DJPadre wrote on 8/29/2009, 5:39 AM

Promised to report back on my 9.0b issue.
After installing 9.0b on my brand new XP Pro x32 built Laptop (with absolutely NO viruscheckers, updaters or anything running) V9.0b "Stopped Working" opening the problem 9.0a veg from my main machine.

Having a lot of earlier backups of that project I went back some time and started opening. All opened without problems.
Then I tried the problem-veg again - and now: Ok no problems. Aha: must be some kind of a little green Gremlin.

Then I went back to my main machine (MacPro double Xeons Win 7 x64) and gave it a Maximum Pest Control shot:

ritsmer, can i ask, was the project HDV?
If so, did you try removing teh SFK and SFL files?
I foudn that Vegas (8 and 9) sometimes flakes out with corrupt HDV, so the generation and moreso, the reopening of these files locks the program.
The fix to this... V7...

TheRhino wrote on 8/29/2009, 7:36 AM

NEED HELP...

I have a stable I7 system running 8.0c on Vista64 SP2 flawlessly. I waited until 9.0b so there are no previous versions of 9 on my system.

I get an error when I try to render ANYTHING, even a short segment from a brand-new project. I tried re-installing MS Visual C++ 2008, Vegas 9.0b, etc., etc. The 32 bit version of 9.0b appears to work, but I get the error message in the 64 bit version as soon as I hit "Render As"...

Fault Module: C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4\MSVCR90.dll

ANY IDEAS?

ritsmer wrote on 8/29/2009, 9:51 AM

@ DJPadre: yes - it is 1280x720p 30 Fps AVCHD Main profile and same size m2t. And yes: as I described above I have -among other things- deleted all *.sf* and now V9.0b seems to work very well here.

ritsmer wrote on 8/29/2009, 9:58 AM

@ TheRhino: If you do not really need V9.0b in both versions on the machine then just uninstall the x64 version and enjoy editing - and so among other things also use all the 3.rd party plugins that are not yet in x64 versions.