Comments

Grazie wrote on 3/28/2017, 11:58 AM

Mathias, I really appreciate your Official notification I really do.

Nick Hope wrote on 3/28/2017, 12:05 PM

Thanks for the update but everything on the lists is from update builds 201 and 211, not this one.

Grazie wrote on 3/28/2017, 12:25 PM

Thanks for the update but everything on the lists is from update builds 201 and 211, not this one.

Really? Care to comment Mathias. And as Nick hadn't asked, what is in this update? Or Nick, care to comment?

Nick Hope wrote on 3/28/2017, 12:34 PM

I don't know, but I can see immediately that this is fixed, which makes me happy.

Jam_One wrote on 3/28/2017, 12:57 PM
  • The selection rectangle now shows up for each tool that includes a color picker.

This is something new, and God bless you for this!

 

  • VEGAS Pro no longer exhibits random crashes upon closing the application

That's a negative.
Vegas is still having hard times unloading Vegasaur.Extensions.2.dll
The "crash-on-exit" thing still happens when the Vegasaur's DLL is present in Application Extensions folder.
(Same about the previous versions of Vegasaur.)

Last changed by Jam_One on 3/28/2017, 1:09 PM, changed a total of 2 times.

Win 7 Ultimate | Intel i7-4790K @ 4GHz | nVidia GTX 760 4GB * 2

SSD | 32 GB RAM | No Swap file | No Overclock | GPU-in-CPU OFF

t.A.T.u. F.o.R.e.V.e.R.!

 

Nick Hope wrote on 3/28/2017, 1:13 PM
  • The selection rectangle now shows up for each tool that includes a color picker.

This is something new, and God bless you for this!

New in build 201 (actually restored functionality from the distant past).

  • VEGAS Pro no longer exhibits random crashes upon closing the application

That's a negative.
Vegas is still having hard times unloading Vegasaur.Extensions.2.dll
The "crash-on-exit" thing still happens when the Vegasaur is installed and its DLL is present in Application Extensions folder.

Previously reported for build 201. I still get some crash-on-exits too, but not as many as in the past.

MathiasH wrote on 3/28/2017, 1:38 PM

Hi everybody,

Thanks for the update but everything on the lists is from update builds 201 and 211, not this one.

I'm very sorry but this is a mistake I have personally made while posting. Unfortunately I'm already at home and don't have access to the patch notes. I will correct this as soon as I'm in the office tomorrow. (CET here)

Please bear with me.

Best regards,
Mathias

Grazie wrote on 3/28/2017, 1:45 PM

Thanks Mathias. I'll look forward to comparing.

Xerxeth wrote on 3/28/2017, 3:16 PM

Is "VEGAS Pro 14 Edit Steam Edition" ever going to get these updates pushed to the Steam client? We're still on Build 189.

Also, I was manually browsing some older posts and I read something along the lines of: "The Steam Edition and 'Normal' version are different versions... The currently available build 211 available here are for 'Normal' Version."
That really doesn't seem like the case, as I'm still able to manually update it myself.

So now my Steam version is on Build 244, I just don't understand why these patches couldn't be pushed the Steam version... There's owners of the Steam version that are upset that they're getting a dated version for full price and don't know how to manually update. 🙁

cinefilm wrote on 3/28/2017, 4:08 PM

Rendering a file in version 211 works fine, in build 244 it states "invalid argument" and crashes.

LeyshonUSMC wrote on 3/28/2017, 9:43 PM

Rendering a file in version 211 works fine, in build 244 it states "invalid argument" and crashes.

I just updated and I am having the exact same problem. Now I can't render anything. I am going to roll back to 211 and hopefully it works again.

Grazie wrote on 3/28/2017, 10:10 PM

Rendering a file in version 211 works fine, in build 244 it states "invalid argument" and crashes.

I just updated and I am having the exact same problem. Now I can't render anything. I am going to roll back to 211 and hopefully it works again.

Really?? - I'm not updating till I hear something from MAGIX.

LeyshonUSMC wrote on 3/28/2017, 10:21 PM

Rendering a file in version 211 works fine, in build 244 it states "invalid argument" and crashes.

I just updated and I am having the exact same problem. Now I can't render anything. I am going to roll back to 211 and hopefully it works again.

Really?? - I'm not updating till I hear something from MAGIX.

*Update* Rolling back to 211 worked for me. I can now render my files again.

Nick Hope wrote on 3/28/2017, 11:18 PM

That really doesn't seem like the case, as I'm still able to manually update it myself.

So now my Steam version is on Build 244, I just don't understand why these patches couldn't be pushed the Steam version... There's owners of the Steam version that are upset that they're getting a dated version for full price and don't know how to manually update. 🙁

@Xerxeth How exactly did you manually update?

Nick Hope wrote on 3/29/2017, 12:52 AM

Rendering a file in version 211 works fine, in build 244 it states "invalid argument" and crashes.

I just updated and I am having the exact same problem. Now I can't render anything. I am going to roll back to 211 and hopefully it works again.

What render settings?

No problem here with Sony AVC/MVC, MainConcept AVC/AAC, ProRes, HEVC.

PacoDeCasa wrote on 3/29/2017, 5:06 AM

same error here, in fact ALL my custom export settings are empty... if i enter to configure them all the dropdowns, checkbox... no value!

Marco. wrote on 3/29/2017, 5:12 AM

Same problem here. What's strange, when I make a screenshot of the render window, the text of the settings' menus displays fine in the screenshot. But it's invisible in the render window itself.

Dexcon wrote on 3/29/2017, 6:31 AM

... and same problem here too.  All the customized render settings are blank.  However, the default render settings (for MC AVC/ACC at least) are still there and can be customized again.  But very annoying!

Grazie wrote on 3/29/2017, 6:36 AM

I've now counted at least five Vegas Pro, I call POWER USERS, who've noted issues with this update and who've needed to backdate to the previous working build.

Can somebody from MAGIX please comment.

I'm staying with Build211.

Cornico wrote on 3/29/2017, 6:37 AM

No problem here, all default and customized templates are visible and can be changed on laptop and desktop from signature.

Xerxeth wrote on 3/29/2017, 7:11 AM

That really doesn't seem like the case, as I'm still able to manually update it myself.

So now my Steam version is on Build 244, I just don't understand why these patches couldn't be pushed the Steam version... There's owners of the Steam version that are upset that they're getting a dated version for full price and don't know how to manually update. 🙁

@Xerxeth How exactly did you manually update?

I simply applied the retail build over the Steam version, then reinstalled the Steam version. http://steamcommunity.com/app/528200/discussions/0/143387886723503186/

However, one person is saying the method I used isn't working for them.

Everything seems to be working fine, I use this with HitFilm Pro 2017 and they still work with each other.

Cornico wrote on 3/29/2017, 8:03 AM

Edit

No problem here, all default and customized templates are visible and can be changed on laptop and desktop from signature

While I had renamed my customized settings for MC and Sony AVC due to the audio bug in VMS14 on customized templates, I did not directly see that problem.
I reset those customized templates and now I see that problem at both my machines only with the customized templates of the Mainconcept AVC codec. Not with default templates.
Look for yourself

Nick Hope wrote on 3/29/2017, 9:17 AM

Me too now, but only ProRes and MC AVC custom templates that I created in previous versions. My previously-created custom templates for 9 other formats are OK. I can create a new ProRes or MC AVC custom template and it's also OK.

I've had a look in %APPDATA%\Sony\Render Templates\ where the .sft2 render template files are and I don't see anything obviously different about the faulty templates.

I tried exporting and importing a faulty template with Vegasaur Presets Manager but the fields are all still empty.

MAGIX_Eric D wrote on 3/29/2017, 9:22 AM

We are looking into the render situation and will provide news updates.  Thank you for reporting this issue.