All the Open GL transitions appear on my computer.

No, it's not those, there's some other ones that was listed as "GL Transitions" (not the 3D one's) that have gone, every time I open a project now I get a big list saying "{Svfx:de.magix:glTransition} - Transition" not installed anymore, they've gone. I still have those 3D one's too although I only have 6 though hopefully they'll sort it 😊

I had a conversation for about an hour or so about it and they've opened a ticket now so they know about this so hopefully they'll fix it 😊

Here's what I think of Vegas 19 UI colors and icons:

I can repeat this again and again until dear @gary-rebholz would not hear how UI is important for everyday use.

Imagine one day you go out and see your city in black and white. You used to live in a colorful world for decades, and then suddenly it goes noir. And you can't change it back...

Sure, Vegas team did a great job with these updates adding new features.

But... Why you removed amazing UI without option to choose it?

I can't switch to V19 just because of this. I hate the interface. It's ugly. Lacks taste. Poor design.

Give us Vegas 18 interface back.

Please.

P.S. Yesterday I watched an interview with Hans Zimmer. He told that the only reason why he uses Cubase for 20+ years instead of Logic is that developers listened to his feedback.
Cubase devs were open to MUSICIANS feedback. Because musicians use that software their way.
They know what they need.

I'm feeling that Magix don't give a damn about what I'm (and dozens of other editors) asking for a year.

Hear us, our opinion matters.

P.P.S. I hope this request would be considered someday. Until then, I continue using Vegas 18.
@VEGAS_CommunityManager @VEGASYatharth @VEGASDerek

Here's what I think of Vegas 19 UI colors and icons:

 

I can repeat this again and again until dear @gary-rebholz would not hear how UI is important for everyday use.

Imagine one day you go out and see your city in black and white. You used to live in a colorful world for decades, and then suddenly it goes noir. And you can't change it back...

 

Sure, Vegas team did a great job with these updates adding new features.

 

But... Why you removed amazing UI without option to choose it?

 

I can't switch to V19 just because of this. I hate the interface. It's ugly. Lacks taste. Poor design.

 

Give us Vegas 18 interface back.

 

Please.

 

P.S. Yesterday I watched an interview with Hans Zimmer. He told that the only reason why he uses Cubase for 20+ years instead of Logic is that developers listened to his feedback.
Cubase devs were open to MUSICIANS feedback. Because musicians use that software their way.
They know what they need.

I'm feeling that Magix don't give a damn about what I'm (and dozens of other editors) asking for a year.

 

Hear us, our opinion matters.

 

P.P.S. I hope this request would be considered someday. Until then, I continue using Vegas 18.
@VEGAS_CommunityManager @VEGASYatharth @VEGASDerek

I agree with you. should be able to choose it.

In this version it does not work in the internal setting "Enable detection hardware" on False.

My GTX970 is not working in this version. They are disabled in I / O settings and Nvidia renders are hidden.

https://www.vegascreativesoftware.info/us/forum/i-don-t-have-the-nv-encoder-rendering-option--132747/?page=3#ca831878

If you have allowed the lower limit to be extended, why not the upper ???

I have needed this option for 15 years. 4,000 is insufficient.

In this version it does not work in the internal setting "Enable detection hardware" on False.

My GTX970 is not working in this version. They are disabled in I / O settings and Nvidia renders are hidden.

https://www.vegascreativesoftware.info/us/forum/i-don-t-have-the-nv-encoder-rendering-option--132747/?page=3#ca831878

At the bottom of that thread you'll see the detection method was changed. If it doesn't work for you, reply there or file a support request? It will get lost here.

@Easyweb to confirm that I have them properly installed, I uninstalled B636, reinstalled B550 and checked. Yes, they are there. I updated B550 to B636, and they are still there. See screenshot below.

@Reyfox similar in my b 550 > b 636.

@Easyweb to confirm that I have them properly installed, I uninstalled B636, reinstalled B550 and checked. Yes, they are there. I updated B550 to B636, and they are still there. See screenshot below.

Yes those are the one's I want back!! 🙁

Sorry I'm not overly technical, can you kindly help me in regards to what I need to do to get them back, I'm honestly not sure what B550 and B636 is etc.. I only bought Vegas in February/March time and installed the things that were in the email and even with that there was some stuff I installed by accident, so I'm really not sure where these are or what I need to do to install them back?

I spent an hour or so on chat with them yesterday and they didn't know how to do it, they asked me to reinstall the Deep Learning Models but it didn't fix it then they opened a ticket.

Thank you so much, I really appreciate you 😊🙏

Edit: Oh the B is the build ain't it, just looked now and build 636 is what mine is but they're missing now after the update 🙁

@Easyweb sending you a private message. No need to clutter up this post.

Like others had mentioned, settings in the Options Preferences area reset. Not a big deal in my case after googling all of what I needed to change. My custom render type survived the update.

The update process itself tends to have issues. I usually resort to letting the application download the main update setup file and then go into the Vegas temp directory to run them after I close the program. Otherwise I sometimes have issues. This time the update process tried to update the learning models before actually updating the program which seemed to cause an issue for me. I was able to get around it by running the update and then thankfully the program realized the models needed updated with my first run of 636.

Part of the issue could be whatever server they use to host these update files can't handle so many people trying to download the update at the same time. I think my first attempt resulted in a corrupted setup file but I'm not totally sure. Maybe some type of staggered update system could help if a better file host isn't possible.

Hi, I don't know if this will help but I've just spent about an hour on the chat with Eric, who was lovely by the way and spent time with me to try fix this and one of the things he asked me to do was install the deep learning models which he helped me do however it didn't fix the issue for me and he's opened a ticket.

I'm not sure if it helps in regards to your situation however when you mentioned the learning models then, this is what Eric had me install also but it didn't fix anything.

I hope this helps 😊

Thanks. I actually don't have any issues, but I described here the awkward process it took to get the software updated.

Like others had mentioned, settings in the Options Preferences area reset. Not a big deal in my case after googling all of what I needed to change. My custom render type survived the update.

The update process itself tends to have issues. I usually resort to letting the application download the main update setup file and then go into the Vegas temp directory to run them after I close the program. Otherwise I sometimes have issues. This time the update process tried to update the learning models before actually updating the program which seemed to cause an issue for me. I was able to get around it by running the update and then thankfully the program realized the models needed updated with my first run of 636.

Part of the issue could be whatever server they use to host these update files can't handle so many people trying to download the update at the same time. I think my first attempt resulted in a corrupted setup file but I'm not totally sure. Maybe some type of staggered update system could help if a better file host isn't possible.

Hi, I don't know if this will help but I've just spent about an hour on the chat with Eric, who was lovely by the way and spent time with me to try fix this and one of the things he asked me to do was install the deep learning models which he helped me do however it didn't fix the issue for me and he's opened a ticket.

I'm not sure if it helps in regards to your situation however when you mentioned the learning models then, this is what Eric had me install also but it didn't fix anything.

I hope this helps 😊

Thanks. I actually don't have any issues, but I described here the awkward process it took to get the software updated.

You're welcome, I'm glad you managed to sort it anyway and that it's all ok for you 😊

Luckily I've managed to fix mine thanks to @Reyfox who has been absolutely wonderful, I have so much gratitude for him though I've managed to get my GL Transitions back AND he's also fixed the missing render box problem I had about a month or so ago where it just randomly went missing, support did try help me for a couple of weeks with it but couldn't get it fixed and then closed the ticket however thanks to @Reyfox I now have that back as well, which I would have never been able to do without him, so again, so much gratitude and thank you so much!! ❤️🙏

Basically I had to find my original installation file B 532 and reinstall that after uninstalling the recent update, I did try the re-install of the new one as well as the deep learning models but once I installed the new one again, my GL Transitions had gone so long story short, I have to stick with the B 532 otherwise I lose the transitions I use and have other problems such as the missing render box we have too.

I completely understand how Vegas have a slim profit margin as opposed to other companies for tech support however I do hope they can do a little better with the next update because as you can see from the various responses here it's been a nightmare and caused a lot of problems, I'm just really hesitant to update again in the future now due to this, which of course I'd like to do as I'd love the new features too but with the problems it's caused I'd be too worried to do so as I'm really not that technical when it comes to fixing these things, which again is why I appreciate people like @Reyfox and others here who have been so kind to help.

I hope Vegas can just take this as nice genuine feedback as honestly, it's an incredible program but it just needs to be a little better maybe when doing updates I guess 😊

I hope all is well for everyone anyway and thank you so much to all who have been so kind to help also ❤️🙏
 

Here's what I think of Vegas 19 UI colors and icons:

 

I can repeat this again and again until dear @gary-rebholz would not hear how UI is important for everyday use.

Imagine one day you go out and see your city in black and white. You used to live in a colorful world for decades, and then suddenly it goes noir. And you can't change it back...

 

Sure, Vegas team did a great job with these updates adding new features.

 

But... Why you removed amazing UI without option to choose it?

 

I can't switch to V19 just because of this. I hate the interface. It's ugly. Lacks taste. Poor design.

 

Give us Vegas 18 interface back.

 

Please.

 

P.S. Yesterday I watched an interview with Hans Zimmer. He told that the only reason why he uses Cubase for 20+ years instead of Logic is that developers listened to his feedback.
Cubase devs were open to MUSICIANS feedback. Because musicians use that software their way.
They know what they need.

I'm feeling that Magix don't give a damn about what I'm (and dozens of other editors) asking for a year.

 

Hear us, our opinion matters.

 

P.P.S. I hope this request would be considered someday. Until then, I continue using Vegas 18.
@VEGAS_CommunityManager @VEGASYatharth @VEGASDerek

Are you talking about the (medium) grey background color and the old outline icons? Both are typical indicators for an old (Windows XP) application.

Looks like I'll be skipping this "Upgrade" too.

Here's what I think of Vegas 19 UI colors and icons:

 

I can repeat this again and again until dear @gary-rebholz would not hear how UI is important for everyday use.

Imagine one day you go out and see your city in black and white. You used to live in a colorful world for decades, and then suddenly it goes noir. And you can't change it back...

 

Sure, Vegas team did a great job with these updates adding new features.

 

But... Why you removed amazing UI without option to choose it?

 

I can't switch to V19 just because of this. I hate the interface. It's ugly. Lacks taste. Poor design.

 

Give us Vegas 18 interface back.

 

Please.

 

P.S. Yesterday I watched an interview with Hans Zimmer. He told that the only reason why he uses Cubase for 20+ years instead of Logic is that developers listened to his feedback.
Cubase devs were open to MUSICIANS feedback. Because musicians use that software their way.
They know what they need.

I'm feeling that Magix don't give a damn about what I'm (and dozens of other editors) asking for a year.

 

Hear us, our opinion matters.

 

P.P.S. I hope this request would be considered someday. Until then, I continue using Vegas 18.
@VEGAS_CommunityManager @VEGASYatharth @VEGASDerek

Are you talking about the (medium) grey background color and the old outline icons? Both are typical indicators for an old (Windows XP) application.

I’m talking about the default Vegas 18 UI. How can it be windows XP style?!

I guess some people prefer form over function. I don't care how it looks, as long as it works well.

Unfortunately, this latest version is hanging on me, so bad that I just close it down and reload. I haven't had that happen for a very long time. Mostly it's when I import a clip that has been exported from Sony Catalyst (I sometimes use the image stabilisation in catalyst) and when I try to make a proxy of that clip in Vegas.

It affects me greatly because I lose some focus on the flow of my edits. The windows layouts can be found again by going to organize layouts and adding them back in.

The previous version of the Protype Titler custom presets are not loaded properly.

The same is true even after Vegas initialization.

The four default preset is a mess. (Empty, Centered, Center Baseline, Near Baseline)

Unfortunately, this latest version is hanging on me, so bad that I just close it down and reload. I haven't had that happen for a very long time. Mostly it's when I import a clip that has been exported from Sony Catalyst (I sometimes use the image stabilisation in catalyst) and when I try to make a proxy of that clip in Vegas.

It affects me greatly because I lose some focus on the flow of my edits. The windows layouts can be found again by going to organize layouts and adding them back in.

What settings is Catalyst exporting in? Can you share MediaInfo? https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

Hi, i have a strange problem, too. If i import more than one media (video, mp4, avi. etc) file the last Vegas pro 19 Version marked all the files i just imported. So, if i had my media files in several directories i could import them and could get the whole Group into the timeline. That doesn't work in the 636 Build. It markes only one file in the List. Is it me, or a bug in the new Build? Thanks in advance.

Dirk

For layouts they should still be here: C:\Users\NAME\AppData\Roaming\VEGAS Pro\19.0\
I found mine and restored them using organize layouts.

For prefs you have to redo them- apparently there was a big (intentional) shift in the way Vegas stores them.

Other preferences (Fx) migrated for me without issue.

This is not small thing... How did this get past testing? (I QA test as part of my daily work and ghave been for 20+ years, I understand that things sometimes slip through the net but not something that will have such a profound effect.)

That's the bit I don't understand. There are beta testers here, apparently they're not allowed to tell us when they're testing a new release but they hint at it, @fr0sty is such a case. How would he not say "Guys the update just deleted all my personal settings, fix this before release or place a huge warning when loading the install file"

The same thing happened with version 532 of Vp19, I don't think it exists anymore replaced by version 550. The problems with 532 were immediately picked up by forum users. There has to be a problem with the beta testers themselves(seems unlikely) or the mechanism for giving feedback. The right people never see it?