Cornico, just out of interest, how did you find out about it? Do you regularly visit your user page at http://www.magix.com to check and see if you have the latest build or what?
i randomly checked for a new update, hoping for the trimmer fix. And by the way, the trimmer is now working perfectly as before, now i'm a happy customer :D
Right, your user profile on magix.com does not mention anything about the build version. You just download your Vegas setup (and you only do so because you trust your fellow forum members). After you have downloaded it and run it, it will show all your package software with checkmarks next to it. It also shows you the version and build of each. You don’t need to reinstall the other programs (unless you have some unrelated reason), so uncheck everything except Vegas itself.
Then it will download the current version of Vegas and start installing. After a while, it will notice you already have Vegas 14 installed and will ask you whether you want to delete the old “version.” By that, as confusing and outright scary it sounds, it really means the old build. Say yes. When it is done, start Vegas 14. It will ask you for your serial number, but it will also show you the serial number in plain site (so don’t this in a public place, where someone might only be happy to snatch your credentials).
It will verify (over the Internet) that your computer is authorized to run Vegas 14, and you’ll live happily ever after. Or, well, until the next build. 🕵
What's up with Magix? Why are they not announcing the new build 211 with link? It's seems so secrecy in this regards. What is new in build 211 any one knows?
They will probably have an announcement in a day or so. People on the net will scour for all kinds of info or maybe just bump into it on accident. If the file availability on some server is literally not simultaneous with an announcement you get these kinds of messages.
My quick tests found the Trimmer's 'workflow' is more friendly in 211.
Also no blank spots on dark area of ProRes media. The 23.97, 29.97, True24p, and True30p issue has been corrected. (Multiple audio track haven't fixed). But look forward for other positive and issue reports.
i randomly checked for a new update, hoping for the trimmer fix. And by the way, the trimmer is now working perfectly as before, now i'm a happy customer :D
ion-marin, I'm glad you're happy with the improvement. Just to be clear, the Trimmer is now working better than "perfectly as before." The change we made that caused you to be unhappy with the Trimmer behavior in a previous update was that we made it possible to make a choice when you start dragging within an established In/out area. In the initial implementation, if you started your drag within the in/out area, your only option was to add the section to the timeline. You could not establish a new area if you started within an existing area.
The previous build added functionality that made it possible to add to the timeline (if you initially drag vertically) or establish a new area (if you drag horizontally). This was a nice enhancement, but the part we got wrong is where we set the boundary that separates a vertical drag from a horizontal drag. What this new update features is a tweaked tolerance for what's considered a vertical drag (which was inspired by your feedback.)
So you now still have the option to add the selection to the timeline, or create a new selection, but now you have to be much more precisely horizontal in your initial movement before we will treat it as a horizontal drag and establish a new area. Seems like we got the angle about right now, thanks to feedback from you and others. Sorry for the long-winded explanation, but thanks for helping make this feature and VEGAS Pro 14 better!
In previous versions of Vegas Pro I wasn't keen on the trimmer workflow, but now I can hover scrub my cineform files fluidly, so the workflow is very fast: double-click - mouse drag- A.... repeat. Works great! Thanks!
i randomly checked for a new update, hoping for the trimmer fix. And by the way, the trimmer is now working perfectly as before, now i'm a happy customer :D
ion-marin, I'm glad you're happy with the improvement. Just to be clear, the Trimmer is now working better than "perfectly as before." The change we made that caused you to be unhappy with the Trimmer behavior in a previous update was that we made it possible to make a choice when you start dragging within an established In/out area. In the initial implementation, if you started your drag within the in/out area, your only option was to add the section to the timeline. You could not establish a new area if you started within an existing area.
The previous build added functionality that made it possible to add to the timeline (if you initially drag vertically) or establish a new area (if you drag horizontally). This was a nice enhancement, but the part we got wrong is where we set the boundary that separates a vertical drag from a horizontal drag. What this new update features is a tweaked tolerance for what's considered a vertical drag (which was inspired by your feedback.)
So you now still have the option to add the selection to the timeline, or create a new selection, but now you have to be much more precisely horizontal in your initial movement before we will treat it as a horizontal drag and establish a new area. Seems like we got the angle about right now, thanks to feedback from you and others. Sorry for the long-winded explanation, but thanks for helping make this feature and VEGAS Pro 14 better!
I\m realy glad that you are taking our feedback in consideration and use it to improve vegas functionality. Realy happy with your customer service.
The trimmer indeed works perfect. All i hope is that things will work as well in concern of video card compatibility and cuda acceleration for AVC renderig.
gary-rebholz wrote on 12/22/2016, 03:38 PM
Sorry for the long-winded explanation, but thanks for helping make this feature and VEGAS Pro 14 better!
That's the new quality we see here - a Product owner has his ear close on users side. And explain as well the backround as the function high precisely - as Gary in his webinars always did....😉