Movie Studio 17 not working properly

Patrick-Prokop wrote on 10/3/2020, 12:55 PM

I've been a Movie Studio subscriber since around version 4 or 5. I have been upgrading to the latest versions as they arrive. Upon upgrading to Movie Studio 17, anything I render is very low quality and blocky. I had to revert back to Version 16 to render my movies. This all started when an 'upgrade' screen popped up while in version 17, so of course, I performed the upgrade. After that, anything I rendered was basically unusable. Version 16 still works fine but it too has that upgrade popup every time I open it ... but I don't dare to upgrade since this is the only working version I have left. Any suggestions? I am using Windows 10 Pro.

Comments

j-v wrote on 10/3/2020, 1:18 PM

Which buildnr. of the program are you using?

Look in Help/About

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

Patrick-Prokop wrote on 10/3/2020, 2:55 PM

Build 179

Patrick-Prokop wrote on 10/3/2020, 2:57 PM

Version 17.0 Build 179

 

j-v wrote on 10/3/2020, 3:36 PM

You are using Movie Studio Platinum and the latest update has a bug when "Make Movie" is used.
Development knows this and is working on it for a new update.
As a workaround you have to use File/Render as to choose the right rendertemplate for your goal (probably the same as used by Make Movie in version 16)

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

Patrick-Prokop wrote on 10/3/2020, 3:55 PM

I tried ... "Render as" and it worked. Whew, that's a relief.

Thank you

Alan-McLaren wrote on 3/15/2021, 5:02 PM

Upgraded from Platinum 12 last year, simply because of price offer. Not used it as it was solely for editing recorded live music, which is still on hold. Have spent the last several days trying getting familiar with the new editing suite. But this download dose't seem to be working. On starting up, no New Project Dialog Box appears. So not able to match project settings. No choice of rendering but Make Movie. Have went through multipule settings but the finished videos are the same. Jumpy pixelated video, on screen text flashing and out of sync video. I see comments relating to software problems. Could this be the problem? Running Movie Studio 17 build 159. Any help much appreciated.

EricLNZ wrote on 3/15/2021, 5:49 PM

Suggest you upgrade to Movie Studio17 Platinum as you have purchased the basic version. The basic version is, in my opinion, very restricted compared to platinum. As you only purchased recently Magix sales might give you a refund to use towards Platinum.

Also check your pc meets the minimum specs here https://www.vegascreativesoftware.com/us/vegas-movie-studio/specifications/#productMenu

VMS will run on less but you won't get the best out of it especially if you are using 4k.

vkmast wrote on 3/15/2021, 5:54 PM

Strongly second Eric's suggestion if you have the basic MS 17. Refund advice.

EricLNZ wrote on 3/15/2021, 5:58 PM

And @Alan-McLaren please don't double post as I note you've also started another thread with the same post.