@ GiulyProd ,,,, You say in your post that you are the post-production chief at your company in France (from a Google search, could it actually be Monaco?), yet you choose as a senior representative of your company to use offensive language in your post on a public forum. I think that is not very professional.

How can you sell-it 699€ seriously ? This is the software the most instable I never used.

amazing isnt it?! and you can get resolve for half the price. i read they are a small team working hard to revive vegas, but its been quite some time and major issues haven not been solved..why dont you hire more capable programmers to help you on your task? surely the price you're selling and the customers support are enough i believe.. unless you are greedy

I think that is not very professional.

Well, neither is the software in it's current state. I have upgraded to every version since SVP7 up to VP14 which is unusable due it's terrible icons. The short time I could test VP15 it was a disaster and with the long and growing list of issues with VP15 I lost confidence in the software. I have moved on to Resolve Studio and use SVP13 when ever I need a fast cut or scripting. What a sad story this is.

@ GiulyProd , I think that is not very professional.

Oh.

And is it professional to sell a software called "Vegas PRO" with professional price when it is completely buggy and unsuable with customers ? I challenge you to find just one serious production company who still using Vegas in professional conditions.

Vegas is became amateur. Even an iOS video edit application is more stable than that.

PLEASE PLEASE post a HUGE FRICKIN STICKIE whenever this MAJOR, software debilitating glitch gets patched. 15 is 90% unusable right now.

Just for the record; I'm still getting the occasional black clip when rendering from a 1080 AVI project to an Mp4 file -- such a drag after so many years. Why? Does anyone yet know the cause of this?

Does deleting the UNDO HISTORY cure this?

You mean in my online browser?

PLEASE PLEASE post a HUGE FRICKIN STICKIE whenever this MAJOR, software debilitating glitch gets patched. 15 is 90% unusable right now.

Yes. I don't know why they don't retract the current version. I never upgraded to it, but from the responses this memory leakage thing is likely the worst bug in any magix version of vegas.

You mean in my online browser?

No, inside VEGAS "UNDO" pull down, you can right click and nuke all the undos.... tried it, it doesn't help

That's interesting to know and next time I must try that. It sort of makes sense to me only because what always works and prevents the black events from happening is when I exit Vegas first and render immediately upon reopening -- I just didn't think of doing that this time because I was in a hurry and I've been getting these black events very rarely since MAGIX took over from Sony. Thanks for your replies.

There seems to be some sort of GPU memory leak going on... up until now Neat Video worked great with VP15, but now it complains about not having enough GPU memory when you go to render, crashing the render. It says to turn down GPU memory usage, but even when dialed back to 25% in Neat Video's preferences, it still crashes. I am not rendering using NVENC, since that no longer works after the new update. My GPU is a GTX970 4GB.

I will file more detailed reports as soon as I can deliver this project. I plan on going back and recording video of every crash happening in hopes I can help Magix isolate the issues causing them.

@frosty ...

On 1 March in this thread, MagixDerek posted

Thank you, everyone, for the information and the specific details. With this information, we have identified some resource leaks that are likely causing the problems being seen with the reported UI slowdown. We are working very hard on fixing this and will have this go through our QA process with hopes of getting an update out quickly.

Again, thank you for everyone's support in helping us try to identify this problem.

Thank you, everyone, for the information and the specific details. With this information, we have identified some resource leaks that are likely causing the problems being seen with the reported UI slowdown. We are working very hard on fixing this and will have this go through our QA process with hopes of getting an update out quickly.

Again, thank you for everyone's support in helping us try to identify this problem.

Looking forward to this happening.

@frosty ...

On 1 March in this thread, MagixDerek posted

Thank you, everyone, for the information and the specific details. With this information, we have identified some resource leaks that are likely causing the problems being seen with the reported UI slowdown. We are working very hard on fixing this and will have this go through our QA process with hopes of getting an update out quickly.

Again, thank you for everyone's support in helping us try to identify this problem.

 

@Dexcon I think Magix meant they have doc on the UI resource leak. This is a GPU memory leak during render. Perhaps the leak occurred during editing before rendering and is the same bug. Or did the error occur after render began?

Now that I got my Vegas Pro 14'ish outlook back from the view menu - thanks for that, I had to redo my window layout and can no longer locate the time display that I desperately need when editing with two monitors! It is not in the View menu under any of the options. It's called "Time Display" in the Vegas Pro Help/Manual and used to be detachable to drag it to another display or so, but now it's just GONE. I mean, what gives!? All the other windows can be found from under the View menu. And yes, I'm using the latest build of VP15 (build 311) and only after I selected the Vegas Pro 14 view just now (which is great in of itself), I can no longer make the timecode/time display visible by any means that I can think of. Thank you for your advice in advance.

So, I finally crashed my way through the project I was trying to finish. I went to render it. I use Neat Video, which uses GPU acceleration. I had it set to use 75% of available GPU RAM at first, and this worked just fine until update 311. Now, I can't use Neat Video at all, even if I dial GPU RAM usage back to 25% in Neat Video settings. It still crashes saying not enough GPU memory.

So, I disabled neat video. After that, NVENC hung as usual after a few frames (it's been doing that since update 311), but then so did Mainconcept CPU only. So, I went in and disabled timeline GPU acceleration, and that seems to have helped, but now, I have a 32 hour (!!!) encode for a TEN MINUTE VIDEO. I'm rendering one frame every 6 seconds.

This is just ridiculous. This wouldn't fly in a $20 product, much less an $800 one that claims to be for pro use.

As soon as this render finishes, I'm breaking out the camera and I'm going to start filming Vegas crashing and posting the videos here for all to see. Hopefully that will help isolate some of the issues.

I can no longer make the timecode/time display visible by any means that I can think of.

Wouldn't loading (View>Window Layouts>)Default Layout get you started again? (It should restore the main docked areas to their default places.)

"As soon as this render finishes, I'm breaking out the camera and I'm going to start filming Vegas crashing and posting the videos here for all to see. Hopefully that will help isolate some of the issues."

Don't upload camera video of the crashes. Use OBS capture on another machine and RDP into rendering machine.

I have used Vegas Pro and Sound Forge Pro for over 10 years...both have always been rock solid. Vegas Pro 15, build 311 wont stop crashing. It started when I went to render a project (only HD) just a few tracks and all of 1 minute in length. I have re-installed, taken out all VST's, made sure my Windows 10 64bit Dell XPS (massive horsepower) was all up to date. Most of the time I cant even load a project now, maybe up to 20-30%. In the 5% of attempts it will load, and maybe play. will never render and crashes again. Sorry, but you have problems with build 311. If it is not fixed soon, I too will be leaving Vegas...with a heavy heart. Please get this fixed...

Not sure what to do about this release---the so4compoundplug.dll problem was actually a solution to a problem I was having with V13 and V14....

I have used Vegas Pro and Sound Forge Pro for over 10 years.....Vegas Pro 15, build 311 wont stop crashing. It started when I went to render a project (only HD) just a few tracks and all of 1 minute in length.

@rob-german : Are you opening a project previously created in a different version of VP? What happens if you start with a new project and insert Media? Can you open and close this NEW.VEG?

Is this the first MAGIX Vegas for you?