Unfortunately update does not fix inability to use Red Dragon r3d files, Sony have known about this for at least 9 months

All good here. Video driver issue/interaction maybe ?

geoff

>>>Works fine here; even with previous version.<<<


I'm talking about the Master Bus under View>Window>Master Bus.
Dock it next to your preview window and move the volume slider. It'll freeze Vegas so be prepared to crash it.
The workaround is to NOT DOCK the panel.

Works here docked next to preview window--no problem. Even tried the default layout (Alt-D-D) and it still works. It's never been a problem for me.

wwaag

Obviously by now Paul, you must realize that the problem is not with Vegas,
but an issue with your system configurations.

This update, combined with Nvidia's 353.06 drivers on my GTX770, have removed the lingering bad taste I had since VP13 was released.
My current project, a mix of 1080p50 and HDV 1080i on a 25i timeline, with a few filters here and there, went from a preview rate of about 12-13fps to 25! Yay!

Works fine here, docked anywhere on the screen; it has worked since V13 was first released.

Jack

@Steve , JackW and Paul ,

I got confirmed in writing some 6 months ago by the tech people of SCS this mouse freeze master audio bus being a known bug and that they would resolve this in the next update.
Apparently NOT. ( this update is also very minor )
I also dock this ( since V13 ) in order to prevent mouse freezing.
( am using tripple monitor lay-out for ages , audio master bus in second monitor )

Wilvan, If this was a bug, Everyone would be having the same issue, not just a
selected few! Every hiccup Vegas has, is not always a bug. One can be, at times a
conflict with something installed.

Maybe using multiple screens is the problem, but what gets me is that it used to not do that up to about version 11* and I've always worked with 4 monitors, so if this wasn't happening and then was, I'd call it a bug (and now wilvan confirms this). There have been others who reported this bug. Just because it doesn't happen to most doesn't mean it's not a bug -- same logic. I think the bug would appear on many more computers but not too many users even know about the Master Bus because it's a feature that becomes very useful only when you work with multiple screens.

*EDIT It actually still works in v12; the bug started with the first intro of v13.

Paul, I use 3 monitors, and I didn't catch your issue:



I tried move the Master Bus window to several dock areas, and works without any issues...

I use 3 monitor and never had an issue with the Master Bus. I would look into audio hardware or driver issues.

but not too many users even know about the Master Bus because it's a feature that becomes very useful only when you work with multiple screens.

Can you explain how the use of Master Bus is linked to multiple screens?

Thanks, set; so this indicates that multi-monitors is most likely not the issue. Isn't that just the general nature of all bugs? This is what beta testing was established for; so that features could get tested on all sorts of combinations of software and hardware that developers could never cover.
Otherwise, the developer's credo would be whatever works on our computers goes -- may everyone else fend for themselves. The same applies to beta testers; they cannot cover all systems either, so software companies have an army of beta testers (MS=8,000)

But once more, someone on this thread wrote that SCS has confirmed this as a known bug, so that should pretty much settle the issue whether it's a bug. I pretty much resent the quick assumption of some users that anyone who experiences an issue and reports it on the factory user's group must have a mess in their setups and should deal with that in the privacy of their mess. After all, contributors to user groups are just the next tier of beta testers and I see nothing wrong with that.

>>>Can you explain how the use of Master Bus is linked to multiple screens? <<<

Because the block of sound components can end up too far away from the preview window for comfort. One needs to have a proxy volume controller close at hand because for some it becomes an integral part of tweaking edits. Keeping this unit undocked is a small price to pay for an otherwise well working complex of complicated features. I suggest we stop beating the dead horse.

The best way to check whether a problem is due to a bug introduced into a later version or is due some other conflict is to go back to the old version and see if it is still OK.