Vegas 4.0b is available

SonyIMC wrote on 4/7/2003, 12:04 PM
Get it here Vegas 4.0b

Notable items on the audio side:

Expanded support for various sound cards with improved error handling.

General improvements to audio time stretching.

Optimized audio recording performance.

Direct Sound Surround Mapper has been added as a choice in the Audio device type drop-down list.

Keyboard modifiers have been added to allow fine adjustment of envelope points:

* Hold Ctrl while dragging an envelope point or segment to adjust the value in fine increments without changing the envelope points' timeline positions.

* Hold Ctrl+Alt while dragging an envelope point or segment to adjust the value in normal increments without changing the envelope points' timeline positions.

* Hold Alt while dragging an envelope point to move the point's timeline position without changing its value.
A problem has been fixed that prevented you from rendering to RealMedia 8 if another application had installed a different version of the RealMedia plug-in to your system folder.

A bug has been fixed that could cause Vegas to crash if you duplicated tracks during playback.

A bug has been fixed that could cause Vegas to create empty .w64 files when recording for long periods to FAT32 drives.

A bug has been fixed that prevented the active input monitor from closing if you closed Vegas while recording with record input monitoring active.

A bug has been fixed that caused Vegas to crash if you attempted to record two audio files with the same name simultaneously.

A bug has been fixed that could cause audio to draw incorrectly during looped playback.

A bug has been fixed that could cause Vegas to crash if you used the Insert menu to remove a volume envelope when a bus track has focus.

A bug has been fixed that could cause Vegas to crash when copying envelope points.


Comments

ravenmad wrote on 4/7/2003, 12:28 PM
does this fix the Amplitube Directx bug with Vegas?
SHTUNOT wrote on 4/7/2003, 12:39 PM
Hey,

When I right click in the track list area and select "preferences" the dialog opens up but with a "pop-up" also over the ok>cancel>apply area...It says "Use net notify to stay informed about sonic foundry products". Why was that added?

It hangs there for a few seconds and then disappears. Weird.

Will be testing the update now.

Later.

Ed.
pvnuk wrote on 4/7/2003, 12:45 PM
Yes but does it fix the glithes in mixdown/render bug ?!?!?

Paul
CDM wrote on 4/7/2003, 1:05 PM
yes
fishtank wrote on 4/7/2003, 2:24 PM
I asked in another post whether 4.0b would have support for multi-processor (as we had in V2 and V3) and received no response. I assume this has not been addressed yet?

Anyone with a duallie try out the new version yet??
PipelineAudio wrote on 4/7/2003, 3:13 PM
"Yes but does it fix the glithes in mixdown/render bug ?!?!?" havent gotten any so far! The previously screwed up files are rendering OK now, also no glitches in " open copy in sound forge " so far
PipelineAudio wrote on 4/7/2003, 3:14 PM
sonic IMC please find and fix the " fx muted " bug
Jacose wrote on 4/7/2003, 3:51 PM
Optimized audio recording performance.


does this mean that the playback clicks during recording bug is fixed?

what about the "program doesnt generate a playboy bunny in my bed" bug?
pwppch wrote on 4/7/2003, 3:59 PM
What is the problem with Amplitube you are having?

Peter
LooneyTunez wrote on 4/7/2003, 4:43 PM
In my tests of the new 4.0b, there seems to be no improvement in dual processor support, but I'm really happy about the other improvements/enhancements in this new build. I sure hope SF considers dual processor support an important issue, and addresses it in future builds.
RobSoul wrote on 4/7/2003, 5:11 PM
Why would you want a Playboy Bunny in your bedbug?

Rob
ravenmad wrote on 4/7/2003, 5:57 PM
Peter...
When using the directx version of Amplitube (demo)....it doesn't allow you to change any settings and eventually locks up Vegas. It appears to be something with the demo popup (which never appears) of Amplitube. I've sent a report to SF and received a reply saying it was confirmed a problem and was sent to the engineers. That was approx. a week and a half ago maybe.
klyon wrote on 4/7/2003, 6:21 PM
Is there a dedicated bug reporting email address? Using costumer support gets me nothing but polite form letters and generally useless (due to generality) information.
For instance, 4.0b still doesn't sync correctly to Reason -- using SF midi router-- though Acid does. A letter to SF costumer support got me the text of the knowledgebase article about syncing and didn't address the issue at all.
I'll find out today if the render=silence bug has been fixed; I saw no mention of it. Has no one else experienced it?
It's the oddly intermittant one where a render command *sometimes* results in an empty event; changing the driver from ASIO to MME will then usually result in a correct render. But not always: sometimes it has to then be changed back to ASIO for it to work.
djderricke wrote on 4/9/2003, 11:02 PM
I thought I read some mention of the bunnies in the 4.0c release. :)
stakeoutstudios wrote on 4/10/2003, 7:24 PM
I've never had a rendering to silence problem with any version.. seems odd, cos I wouldn't think that would be a hardware dependant bug! Maybe it's one of your plugins?
klyon wrote on 4/10/2003, 8:04 PM
No, it is only related to ASIO, not any plugins. I suppose it could have something to do with the Echo ASIO driver (I don't understand why, but I can't negate the possibility of something simply because I don't understand it...) but no other application has the problem using that driver (Reason renders fine, Cubase renders fine, Wavelab renders fine).
What I don't get is it's randomness: I haven't nailed the offending vector yet, but switching back to the MME drivers solves the problem when it occurs.
klyon wrote on 4/10/2003, 8:23 PM
Okay, I took a minute and figured it out.
The Mona has 6 output channels. The headphone output is hardwired to 1 and 2, so I use 3 and 4 and 5 and 6 for my two sets of monitors. The bug is this: when using the ASIO driver all renders will only work if the master bus is set to go out of 1 and 2. The other two pairs -- 3 and 4 and 5 and 6 -- result in silence.
The workaround would be simple -- leave the master bus on 1 and 2 -- if the Mona's internal headphone output wasn't hardwired to 1 and 2. Actually, the workaround is simple: change the master output to 1 and 2 before rendering. Unless, of course, a track is in record: that little move -- changing an output bus when a track is in record -- freezes the machine.
So there it is, definitely a bug somewhere in the ASIO chain.
pwppch wrote on 4/10/2003, 9:33 PM
Rendering to a file does not involve the hardware i/o you have set up. Are you saying that rendering to a file is dependent on how hardware ports are assigned to the buses?

Peter
klyon wrote on 4/11/2003, 2:03 AM
Absolutely, as I explained in that last post. Setting the master bus hardware output to anything other than 1 and 2 and rendering returns a blank event. It may not make any sense, but there it is. I'm just glad I took the time to figure out what had seemed like randomness.
And, it only happens with ASIO.