VEGAS Movie Studio 17 Update 3 (Builds 176 & 221) - General Discussion

Comments

david-h9346 wrote on 5/21/2021, 2:18 AM

@VEGASderek are you or anyone else in authority going to respond to all these serious issues , or do you not care about your customers ?

VEGASDerek wrote on 5/21/2021, 6:07 AM

This is a user to user forum. I'm here as a courtesy. I am not a representative of technical support. I monitor these forums simply to gauge what is going on with our customers.

We are aware of the problems with this update of Movie Studio and we working on getting an update out the door. However, doing new updates takes time. If we rush it out, we risk having an update that presents even more problems than the current update does.

And if I didn't care about the customers, I wouldn't be here monitoring the forum.

If you want a more official response, you should be contacting technical support, not ranting on a user to user forum for us to respond.

LastofAvari wrote on 5/21/2021, 3:14 PM

Creating video proxies fails after build 221 update for me. It appears to do some work for a while, but always fails with unsupported file format message even though I have MP4's with exactly the same encoding settings as before.

This build also didn't fix crashes when doing simple editing operations such as cutting clips on the timeline. Version 14 which I used before was way more stable.

Ken-Wright wrote on 5/23/2021, 11:20 AM

I have tried the updates, nothing now works. I had an issue a couple of weeks ago when every time I tried to add a video clip the programme crashed. After uninstallation of the last Windows update, the problem was solved.

Now I am back to square one. Even after I add an update, the programme is still showing a box “an update is available”.

Any ideas?

JW-Curtis wrote on 5/24/2021, 7:22 AM

My entire program freezes with any edit that I try to do on it. It is so frustrating.

JW-Curtis wrote on 5/25/2021, 12:38 PM

So when is the correct update actually going to be released to fix these problems?

Dav_Grove wrote on 5/25/2021, 5:04 PM

Just want to give some positive feedback regarding the SW update build 221 for Movie Studio 17.0 .Platinum So far it seems more robust like the older versions of Movie Studio from years ago. I have had no crashes, freeze ups, lock ups, or any other issues so far. Also Movie Studio now seems to be less CPU hungry during rendering. Before the 221 SW update it would consume between 95 to 100% CPU. Now uses 60 to 70%. Also my PC is no longer the latest and greatest model out there, over seven years old..

JohnCorda wrote on 5/25/2021, 5:06 PM

JW-Curtis - the answer is clearly never. Build 220 of VMSP working well enough for a half hour then crashes (as usual, and keeps doing it every minute). New update fixes crashes? Okay I go get it.

I just installed the 221 update manually (weak internet down here in my studio), load my current project, and immediately hard locks and crashes again. WTF I can't get ANYTHING DONE LIKE THIS

Some of my projects can get complex, but it matters not - even a simple one with a few longish .mp4 files and wav audio and no effects yet - still freezes up and its Ctrl Shift Esc to End Task the program.

I'm seriously ready to try an alternative.

JohnCorda wrote on 5/25/2021, 5:19 PM

My computer isn't a potato

Windows 10 Pro 64
16 GB Ram
Intel i7  3.2 Ghz
Geforce GTX 1080

I even installed the Nvidia studio drivers for my video card

I've had crashes since v16

Joe-Engel4655 wrote on 5/26/2021, 12:02 PM

So just to provide an alternate experience with downloading and installing the new 221 update. I have 204 VMSP installed on two systems, a 10 year old HP laptop and a new (description in signature) desktop. With some trepidation I auto installed on both systems. To my surprise and delight the download went very quickly (5 minutes) on both systems. The auto install process worked perfectly and I was able to immediately (they even got the desktop shortcuts right) successfully restart on both systems. The re-registration went through smoothly.

It seems to start more quickly and everything was back up as expected. To be fair, I have not pressure tested the build stability yet, but insofar as the download and auto-install it's all good.

Last changed by Joe-Engel4655 on 5/26/2021, 12:03 PM, changed a total of 1 times.

Gigabyte Aorus Z490 MB with 32GB of 1333 DDR4 Ram

Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz,

Gigabyte Radeon RX 580 GAMING 8Gb VRAM, latest drivers

1 TB M.2 PCIE system/Vegas drive, 1 TB internal SSD current project drive, 3TB internal HDD, 10TB NAS.

Vegas Pro 19/550 (Subscription)

Windows 11 Home, Latest updates

A_C wrote on 5/29/2021, 5:58 PM

We are aware of the problems with this update of Movie Studio and we working on getting an update out the door.

Nice to know, thanks.
In the meanwhile, is there any workaround for fixing the build-proxy bug?

Malix82 wrote on 5/30/2021, 12:51 PM

oh boy. should have checked the comments here before updating.

VMSP 17 build 221 seems to crash A LOT. Noticed that a single animated gif on my timeline consistently crashes the app during rendering (but disabling resampling on it seemed to help), but still the app crashes left and right while editing.

This is borderline unusable, tbh.

edit:

so far, I've managed to crash the app by:

  • using spacebar play/pause
  • dropping a .png image on timeline
  • saving by ctrl-s
  • rendering a video
  • undoing a cut

kinda seems like any random action by user is a crash. Downgrade time.

 

    JW-Curtis wrote on 6/1/2021, 9:09 AM

    So has anyone found a workaround for all of the constant freezing with the new update (221)?

    studio-4 wrote on 6/2/2021, 9:03 PM

    As a brand new user, I bought build 221 and it's my first install of VMS on a brand new machine. Though troubling, it's interesting to hear of system crashes. I have only two applications installed this machine (3.5GHz Xeon quad-core with 32GB ECC RAM): Blackmagic's Media Express (capture utility for their Intensity Pro 4K card), and VMS. So far, I've only gotten VMS to crash once. Another time, the titler became somewhat unresponsive (i.e., slow, not frozen) to a large paste of test (perhaps 200 words), which a re-boot fixed.

    Since I'm mainly macOS (Core i7 27" iMac and Core i7 MacBook Pro), I have the luxury of keeping this an NLE-machine exclusively. The only third-party apps that I'll have on it will be Vegas, Boris FX, and the Blackmagic utility, so hopefully that will contribute to a more stable machine in the long run.

    The only outstanding issue I have is when selecting .MOV as the output format results in an error message.

    Last changed by studio-4 on 6/2/2021, 9:05 PM, changed a total of 1 times.

    asus laptop system specifications:
    Asus 17.3" Republic of Gamers Strix G17 model: 77H0ROG1.
    Ryzen 9 5900HX 3.3GHz (4.6GHz boost), eight-core CPU.
    Nvidia GeForce RTX 3060 (6GB GDDR6).
    32GB Crucial 3200MHz DDR4 (x2 16GB 120-pin SO-DIMMs).
    512GB M.2 NMVe PCIe SSD (available second M.2 slot).

    OS: installed on 7/1/2021:
    Windows 10 Home 64-bit; OS version 20H2; build 19042.1052.
    Windows Feature Experience Pack 120.2212.2020.0.

    asus laptop installed applications:
    Vegas Movie Studio 17 Platinum; version 17.0 (build 221); purchased via download 29 May 2021.
    Microsoft Edge (default browser; no plug-ins).

    asus laptop OpenFX add-ons:
    BorisFX Continuum 2021.5 (subscription).
    NewBlue Elements 3 Overlay.

    HP desktop system specifications:
    HP Z440 Intel Xeon E5-1650 v3 3.5GHz (4GHz-boost), quad-core CPU.
    32GB DDR4 ECC RAM.
    1TB SATA SSD.
    AMD Radeon RX470 4GB
    AMD Radeon R7200.

    OS:
    Windows 10 Pro 64-bit; OS version 20H2; build 19042.985.
    Windows Feature Experience Pack 120.2212.2020.0.

    HP desktop installed applications:
    Vegas Movie Studio 17 Platinum; version 17.0 (build 221); purchased via download 29 May 2021.
    Blackmagic Design Media Express 2.3 for Windows 10.
    WinDV 1.2.3.
    Microsoft Edge (default browser; no plug-ins).

    HP desktop OpenFX add-ons:
    FXhome Ignite Advanced VFX pack.
    BorisFX' Stylize Unit 2020.5.
    NewBlue Elements 3 Overlay.

    cameras/VTRs:



    Sony NEX-FS100 Super35 1080p24/50/60 digital-cine camera.
    Sony NEX-FS700 Super35 1080p24/50/60/240/960 high-speed digital-cine camera.
    Sony NEX-5R APS-C 1080p60 cameras (x3).
    Sony DSR450WSL 2/3" 480p24 16:9 DVCAM camera.
    Sony VX1000 1/3" 480i60 4:3 miniDV camera.
    Sony DSR11 DVCAM VTR.

    personal websites:

    YouTube channel: modularfilms

    photography/iighting website: http://lightbasics.com/

    Gianluca-Bianchino wrote on 6/3/2021, 10:56 AM

    Hi. I'm having a few issues

    1. Movie Studio 17 freezes and crashes often! This is a new software installed on a brand new Lenovo Legion 5, a computer specifically made for gaming and video editing (NVIDIA graphics card), which has no other graphic programs on it other than Movie Studio 17 and sound forge (purchased through Magix). Both are brand new, computer and program purchased two weeks ago (early May 2021).

    2. The new blue effects and other effects included in my purchase, which I believe to have properly installed with serial number and all, show up in my system with a red X over them. These were part of my purchase.

     

    JohnCorda wrote on 6/4/2021, 12:06 PM

    Update to my freezing/crashing - It is intermittent - Inotherwords at times it will freeze every few minutes.
    End Task, restart - (Then I have to go to [View | Window Layouts | Reload Selected Layout] to get my desired view back (upon any restart) )

    Other times, and only after a system reboot, it might not crash for 20 minutes.

    Potential workaround (and far from perfect) - Restart your computer for longer stretch of work before the freezing starts up again (memory issue?) CTRL-S IS YOUR FRIEND

    Aside: Why won't it retain the Layout I want? Even if I close and restart the program normally without crashing.

    [Found a shortcut that is quicker but still have to do it every restart - Alt D + 0 - Alt Key pressed with D and zero]

    JW-Curtis wrote on 6/4/2021, 4:39 PM

    Thanks for the suggestions and I am appalled that I have to rely more on the forum than actual people who work for Magix for fixes because all I have gotten are runaround answers and no results.

    LastofAvari wrote on 6/7/2021, 4:38 PM

    Here are steps that reproduce a freeze bug every time as far as my experience goes - 

    1. Split the clip on the timeline (Clip A turns into Clips A and B)

    2. Delete new clip A before frame previews for clip B are generated.

    3. MSP permanently freezes (further attempts of interaction with MSP cause grey out with "Program is not responding" message).

    MSP = Movie Studio Platinum.

    JohnCorda wrote on 6/8/2021, 1:45 AM

    Well oddly enough I've been using the program for hours tonight without a single crash.

    I cannot comment on what is different as the software version/update is the same

     

    Edit: Of course now one of projects hangs the program half way through rendering the video. Which is strange because I was able to render another video basically with the same project, effects, and clips from all the same footage. This second video won't render it's really obnoxious.

    Edit2: This issue where the project wouldn't render (which has never happened to me or if it did it was years ago) was resolved, there were some clip endings-beginnings that weren't necessarily lined up, and I did some cleaning up of the timeline etc and it rendered to completion.

    Finally: Still - I haven't had a crash in hours and I don't know why - I changed basically nothing with the program or the system itself. And I WAS getting non stop crashes after this update we are discussing...

    I DID resave this project into two NEW separate project files.
    I theorize that existing projects may have all the freezes with the update - and new projects may be benefiting from the fixes applied to these issues.

    I will report back on this.

    Edits 3,4, and 5: My editing freezes are low to none, but my rendering freezes (have to End Task) which never happened before, are high. Sometimes cleaning up the clips (I've rendered complex multi clip with fx and clip cuts and edits to the NTH degree before without issue) OR restarting the rendering and I get lucky and it finishes.

    gbt20317 wrote on 6/8/2021, 6:12 PM

    This is in regard to one of the things update 221 was noted as having fixed, which was the problem with .MTS and .M2TS video files that include the 5.1 Surround Sound AC-3 audio stream option crashing VMSP 17 when opening them for editing due to a bug introduced by the "great" Windows 10 OS. I can load these files into VMSP 17 successfully and work with them. However, I’ve found VMSP 17 still crashes if I open the MAKE MOVIE/SAVE TO HARD DRIVE panel and choose the AVCHD option (as VMSP 17 recommends) even if I’ve turned off 5.1 Surround Sound AC-3 audio stream option and record in plain 2 Channel Stereo mode, prior to recording my video. I've made note of this to Magix's support but they've just ignored my concern, I guess because they consider the issue fixed and not worthy of further support. I can't really blame them, because before I discovered the information concerning why this was happening, I KNEW Windows 10 was somehow at the bottom of it! I can't really put blame on Magix as their responsibility is to their product, not fixing Microsoft Update created issues!

    Dr Zen wrote on 6/9/2021, 1:03 AM

    This is in regard to one of the things update 221 was noted as having fixed, which was the problem with .MTS and .M2TS video files that include the 5.1 Surround Sound AC-3 audio stream option crashing VMSP 17 when opening them for editing due to a bug introduced by the "great" Windows 10 OS. I can load these files into VMSP 17 successfully and work with them. However, I’ve found VMSP 17 still crashes if I open the MAKE MOVIE/SAVE TO HARD DRIVE panel and choose the AVCHD option (as VMSP 17 recommends) even if I’ve turned off 5.1 Surround Sound AC-3 audio stream option and record in plain 2 Channel Stereo mode, prior to recording my video. I've made note of this to Magix's support but they've just ignored my concern, I guess because they consider the issue fixed and not worthy of further support. I can't really blame them, because before I discovered the information concerning why this was happening, I KNEW Windows 10 was somehow at the bottom of it! I can't really put blame on Magix as their responsibility is to their product, not fixing Microsoft Update created issues!

    I don't know if you are the same person who I have been helping on my forum @ MovieStudioZen, but I can confirm the new bug when trying to render to AVCHD with 5.1 Audio. I have had 3 separate people contact me now, about the same bug. I've told people to stop rendering to AVCHD with 5.1 Audio.

    If rendering a video with 5.1 Audio is important for you, I recommend going into the Advanced Settings and selecting Sony AVC/MVC instead. Then go into the Custom settings and set the Audio to 5.1. Using this option is working OK for me and does not crash the program.

    If you are only working with 2x Channel Stereo, go into the Advanced Settings and use MAGIX AVC/AAC to render your videos.

    Dr Zen wrote on 6/9/2021, 1:15 AM

    Create Video Proxies bug in Build Version #221

    The release of build version #221 for Vegas Movie Studio Platinum 17, has introduced a new bug that is causing the creation of Video Proxies to fail.

    Video Proxy renders, but then fails at the end and produces this error report.

    An ever increasing number of people has been asking me about this new bug on my own forum.
    I can confirm this bug is real and that Magix knows this new bug exists.
    I am hoping this bug is fixed soon and not forgotten about or ignored.
    The Video Proxy feature is a major organ in the body of VMSP17.

    Personally I have found Vegas Movie Studio Platinum 17 to be one of the best versions of Vegas Movie Studio during it's 17 incarnations. The last version that was a real gem, was version 12!!!

    robbif2 wrote on 6/9/2021, 9:54 AM

    @Dr Zen, thanks for the update...and all you do!
    I'm still on Build 204 and very sympathetic with all who are suffering with the latest.
    You said "The last version that was a real gem, was version 12!!!".
    I want to ask you a very serious question: Where do you think we're headed?!

    JW-Curtis wrote on 6/10/2021, 7:34 AM

    Any updates on Build Version 221 because Windows just had another major update and I am concerned on how that may actually make the problem worse?