Thanks! Hoping it helps with this Render As crash I've been having... let's see.

Really disappointed, not news codecs videos for the exportation, nothing new... bad. Sorry it's my opinion

Updates like this focus on bugfixes and improvements to existing features. Don't expect things like new formats being supported until the next version update.

Thank you for the update and the teams hard work. Although not mentioned in what has been included in the update, sadly build 353 there is still no video (Audio only) with screen capture for me sadly.

thank you for the update but

auto preview in project media must be fixed!!

it's very uncomfortable while click n hold mouse button for preview my files

Render As guaranteed crash on first try bug fixed. Thanks!

Really disappointed, not news codecs videos for the exportation, nothing new... bad. Sorry it's my opinion

In the past everybody was disappointed that we did not improve the features, performance and stability... but thanks for your feedback.

It is always like this. Whatever you do -- some people will be disappointed :)

P.S. Thanks for the new build.

I spoke too soon, render as crash for complex projects is still there. First time I tried from a fresh open, the render as dialog appeared as it should have. Upon loading the project again, doing some editing, then clicking render as, it crashed.

Thank you for the update and the teams hard work. Although not mentioned in what has been included in the update, sadly build 353 there is still no video (Audio only) with screen capture for me sadly.

Maybe you are now convinced to use the needed Windows 10?😄

I am not sure if this comment was directed at my post. Why would there be an assumption I am not on Win10?

Sorry @pioneer109  my mistake.
I accidentally exchanged you with another user.
I'll delete that comment.

I can't render even a two minute clip without the program crashing. I haven't had render problems in years (been a user for about 10 years). Now, with this update, I can't get anything out. I'm rendering two minute clips of 1080 video with nothing but a fade in and fade out--no other effects.

Version 17 crashes ALL THE TIME but at least I was able to render. Now with the 353 update, I can't even do that. I'm almost ready to jump ship. I have wasted so much time and I'm just about done.

I can't render even a two minute clip without the program crashing. .....

Now with the 353 update, I can't even do that. . . .

I'm almost ready to jump ship. I have wasted so much time and I'm just about done.

@Nerd-Sidekick - I'm rendering stuff all the time. As this is a primary function of any NLE, maybe it's your setup or your workflow that needs overhaulin'?

@Nerd-Sidekick - Also, this is your very first Post under this name - yes? You only joined last month. Is there ANYTHING we can do to help you?

However, your comments and those of others here have pursaded me to hold-back installing VP17 Update 2 (Build 353) until I'vegot my latest creation through to FINAL render.

@Grazie I've been rendering without any problem on the previous version 17 build. Something changed today after installing 353.

I'm running on a newly built Ryzen 9 system with 64GB RAM and a RTX 2080 video card with NVMe drives. So this computer smokes.

I upgraded from Vegas 13 to 17 at the same time I built the computer, so that's when I setup my account here. I also had an account on the old Sony forum.

Not sure if there's anything anyone can do to help unless there's a fix for the constant crashes for unknown/unpredictable reasons, and now the new rendering problem. Perhaps someone has suggestions for specific settings based on my hardware configuration. I'm all ears. I'd rather not have to learn another NLE, but I'm already testing Resolve.

Hello nice that there is another update but the automatic update does not work and always breaks down. Is there also a link to download it? Keeps on telling that the programma must by closed, but it's not running!

@Grazie I've been rendering without any problem on the previous version 17 build. Something changed today after installing 353.

I'm running on a newly built Ryzen 9 system with 64GB RAM and a RTX 2080 video card with NVMe drives. So this computer smokes.

I upgraded from Vegas 13 to 17 at the same time I built the computer, so that's when I setup my account here. I also had an account on the old Sony forum.

Not sure if there's anything anyone can do to help unless there's a fix for the constant crashes for unknown/unpredictable reasons, and now the new rendering problem. Perhaps someone has suggestions for specific settings based on my hardware configuration. I'm all ears. I'd rather not have to learn another NLE, but I'm already testing Resolve.

Make a thread about your issue, or it'll get buried under unrelated posts here, but the first thing I'd try is updating your GPU drivers (use nvidia studio drivers, many users have said it helped their issues). If that doesn't help, we'll continue helping in your new thread once you make it.

How stable is version 17? I have seen some of the troubling posts on this thread already indicating to me that Magix software quality is as poor as ever. I am still running Version 14 and it is stable and I am able to edit my 4K videos without any grief. I upgraded to Version 16 this time last year and it was constantly crashing and locking up my computer and required me to reset power. This in itself was troubling. The best thing I can say about installing Version 16 was that it didn't delete my Version 14 installation. I uninstalled Version 16 the same day and requested and got a refund. Before I go through that exercise again, can someone comment on the stability of version 17?

@ngjb stable enough I would assume looking at the (rather few) items they fixed in this second patch, and the fact that this second patch took a while to release, but not unplanned I assume. Just saying, if stability was a drama, and blocking, quick fixes would have come sooner I guess.

Something else and maybe a stupid question to the devs, I have Vegas post (albeit I was never able to use it due to the Boris conflict), is this update 2 version compatible with Vegas 17 Post version of Vegas 17?

I assume it does, but before installing I may well ask...

Really happy to see multilingual releases so those of us in Japan don't have to wait for the SourceNext version.

I spoke too soon, render as crash for complex projects is still there. First time I tried from a fresh open, the render as dialog appeared as it should have. Upon loading the project again, doing some editing, then clicking render as, it crashed.

Hey @fr0sty Try deinstalling all magix software, then reboot en run Ccleaner (cleaner + reg-cleaner), reboot en install the latest version of Vegas. After that, the Render As.. crash disapears. At least, this did it for me!

Cheers!

Hello nice that there is another update but the automatic update does not work and always breaks down. Is there also a link to download it? Keeps on telling that the programma must by closed, but it's not running!

Hallo Ger,
here no problem to do the automatic update on laptop and desktop.
Look how it goes on my laptop

There is always a link for downloading the new build on your Magix account.