Hello i hope everyone is doing well. As we know Vegas Pro 23 build 356 was taken down and i cant download it, will it be possible for anyone to share the setup file for Vegas Pro build 356 i want to try it out for my self. Cause some users don't seem to have major issues as discussed in the forums.
@Abdali I am still using build 356, but sharing a build is up to the Vegas team themselves.
I am sure they have had their reasons to take down build 356. However I agree with you that it should still be possible to download it, perhaps move the build under a "beta" section with a disclaimer it has issues or an explanation of some sort, and obviously without support to use at your own risk...
Also, a silent retreat of an official build with no explanation feels uncomfortable to say the least.
However I agree with you that it should still be possible to download it, perhaps move the build under a "beta" section with a disclaimer it has issues
Which build is without issues...?
Vegas team will have good reasons to withdraw build 356 and it makes no sense to keep on using it and discussing it's issues. Nothing wrong sofar using build 302 for editing your projects.
If they still had the build up, there would for sure, be a wealth of questions and comments about it, along with people reporting bugs on a build that is not really being supported.
But... I can see @bitman point of having it listed as "experimental/beta only". But we know how that will turn out. People reporting bugs and complaining.
I found b302 unusable for heavy duty envelope editing but was able to get by with b356. There might be other fixes in it that might be important to other users. If the developers use b356 as a starting point for the next build, discussion of its pluses and minuses might be useful to them. I personally think development would be advanced if all tentative/experimental/beta builds were exposed to public scrutiny.
Since we're all speculating with no internal knowledge of the actual reason for banishing build 356...
@Howard-Vigorita said: "If the developers use b356 as a starting point for the next build..."
Opinion
If build 356 was so problematic that it had to be pulled, it's very unlikely that it would be used as the base for starting a new build. It's more likely that the team would retreat farther back and assemble updated modules on an earlier build.
/ Opinion
Warranty Information
All my posts on this and other fora come with a double your money back guarantee.
VEGAS Derek stated it was due to the cursor update issue so while other parts will likely be carried over from 356 that one shouldn't. There were some really worthwhile fixes.
Since we're all speculating with no internal knowledge of the actual reason for banishing build 356...
@Howard-Vigorita said: "If the developers use b356 as a starting point for the next build..."
Opinion
If build 356 was so problematic that it had to be pulled, it's very unlikely that it would be used as the base for starting a new build. It's more likely that the team would retreat farther back and assemble updated modules on an earlier build.
/ Opinion
Warranty Information
All my posts on this and other fora come with a double your money back guarantee.
You think we'll get an updated fix based on the earlier builds anytime soon?
>anytime soon?
One would like to think so - but I suspect that the dev team are being very cautious. They don't want to release another update that has any serious failings as that would be a PR nightmare. I think we just need to be patient, frustrating as it might be.