The two curmudgeonly gentlemen in the box were Statler and Waldorf...
(and I claim my five pounds)
I've only just purchased the 9.0 version, so am rather pleased that the update is "already" out.
I've just noticed:
"Fixed a rendering freeze when using Acoustic Mirror on a bus. "
This is probably a stupid question, so apologies. Can acoustic mirror be run now in real time?
I've never tried it, preferring Waves IR-L or the VSL's convolution verb in their Vienna Suite.
I speculate that SCS got a their best information from the new interface to report errors at the time they occur. I don't know what information is being sent but I generally take the time to "send" the error report. I just had an error occur in 9.0a on a simple copy and paste operation of a ProType Titler text graphic. It crashed Vegas but on the way out it let me send the error report. This is likely why the fixes in 9.0a were so many and so specific to many of the users here.
But I realize some of the fixes were not errors but merely user requests. One of them that I didn't see on the list (maybe I missed it) was a request that I made (probably others too) that they stop incrementing the file names generated with "Preview in Player". This left a bunch of file clutter to clean up later. No other version did this. Thanks SCS for rolling back this unneeded feature.
It seems to me to be CPU register, and a trace of the application at the point of the crash, and will often tell them exactly in which line(s) the software had an exception, which are most often caused by invalid values. Believe me, while this doesn't always tell developers why something went wrong, it gives developers a starting point to hunt the bug, or in case of bad media add checks to detect that the media is bad, rather than having the application fall over.
And it is a hell of a lot better than having to only rely on a user trying to remember what steps preceded the error :)
It's a very powerful tool because it shifts the burden from the user to the developer. It's pretty common for users not to report problems. It's also very common for support systems to dissmiss trouble tickets simply because the user gets fed up and stops responding. From a support reporting perspective that's another problem 'fixed' and another gold star for the support team.
When it's your code reporting problems in your code it's kind of hard to hide the true number of problems users are having.
logiquem, is sluggish time line HD for you? By sluggish do you mean playback and/or playback startup or the actual time line? I have probelms with a large SD project. My time line responds to clicks seconds after I do them. 90 percent of the time it is slow to respond to commands. On small projects Pro 9 works perfect.
I just pulled a project into 9.0a that was created in 9.0. It included two volume envelope points directly above each other. During preview, a loud pop. Rendered with AC3 Pro it became an ear splitting screech. This definitiely did not happen to me under 9.0
My workaround was to move one of the envelope points just a smidge, and the pops and screeches went away. But now I have to listen all the way through my projects as I bring them into 9.0a to make sure I haven't got a problem going out the door.
Finally --- Thands Dxdy. I've had this little problem of the LOUD POP on two volume envelopes on a 90 degree line.
I started a new thread to see if anyone else is seeing this. SCS didn't seem to think it was a problem rather something that could be reproduced in all versions of Vegas. I think it's unique to 9.0a ..
And the 9.0/9.0a generated text problems has me jumping back to 8.0c. Good luck, SCS, still some work to be done on 9.0. I'm sure they'll figure it out.