I couldn't agree more John. I thought I was OK having carried out a system restore and reverting back to version 24.0.1.221 but unfortunately I was wrong.

MS is now very tempremental, locking up at the slightest excuse. Obviously some files have been updated that would like the new version and are rebeling by having to use the old version.

I sent an email to both ABSoft (Neat Video) and Magix a couple of days ago but no reply yet.

What is even more alarming is that every time I load up MS2025, the popup appears offering me the version 24.0.1.227 update - I haven't cancelled it because I want to see how long this takes.

AndyW

Wow, frightening. No sooner do I post the above than I receive an email from ABSoft.

I told them I wasn't very pleased with the situation.It's quite a long email so here is the important bit:

"Yes, I am also not happy with Magix and their behavior. They told me that they found the cause of the problem and are going to fix it and release an update (last week). Yet there is nothing so far."

The more people that complain to Magix the better.

AndyW

@me_again

Hi Andy,

Thanks for the update.

I just wrote up a nasty to Magix using the form in my account. When I clicked on send, poof, I was logged out and no ticket was raised. Fortunately, I decided at the last second to copy the text to the clipboard. I'll do it again through Support in this forum.

For what it's worth, I added in a couple of other complaints - the PTF problem in VPX not working properly since 2023, and the Sound Forge Audio Cleaning Lab 4 problems. It's ridiculous that Magix has not corrected these bugs. SFACL4 should work and work with VPX/MMS like every previous version of ACL.

As you pointed out, I, too, noticed that the patch is still being offered - on my laptop. I pointed this out to Magix. Why keep pushing out a defective patch!

John CB

Latest update

Changes - version 24.0.1.227:

Feature:

- AI smoothing available under video effects

Stability:

- Fixed crash during automatic shutdown after export

- Fixed crash when loading a project with an empty arrangement window

- Fixed crash when removing a CPU-intensive OFX AI effect during playback

- Fixed crash when drawing thumbnails - Fixed crash when scrolling quickly with many elements in the folder

- Fixed crash when importing files with AC3 audio

- Certain HEIC files are no longer imported in black and white

- Various minor stability adjustments

AndyW

Hi all, is this the full list of updates?

I don't want to cause a stir or have any kind of pissing contest but reg these frustrated comments, the update list above, what I read in the other post about MMS/VPX speculated future & the unmentionable V___s P__ 👿 was mentioned ..

So I just want to share info of how VP is doing vs the update above....

I upgraded to VP22 from VP21 on the 29/07/24, VP21 had 6 build releases, 315 was a patch for 314 so 5 releases really, VP22 has had 5 update releases, 239 was a fix for a variable frame issue that was in 237 so again 4 releases in reality.

VEGAS Pro 22.0.0.239

VEGAS Pro 22.0.0.237 (note this bug)

VEGAS Pro 22.0.0.194

VEGAS Pro 22.0.0.122

VEGAS Pro 22.0.0.93

Each release over the last few yrs has looked like this (pic below), a lot of it is bug fixes like the MMS list above & there's been major changes in VP over the last few yrs so the comparison maybe disproportionate, but I see a lot of work being done on the VP side of Magix & dare I say minimal work done on the MMS side.

vegas-pro-vegas-post-release-history

@Gid

Hi,

The patches for MMS/VPX are listed under MAGIX Hub, New Features or by clicking on the Feedback button in the top menu:

That's it, that's all.

As we know from the Vegas forum, during insolvency, the Vegas Team was able to increase its staff.

On the Magix side in Germany, staff was decreased by voluntary retirements, or rather, many people just quit. The Samplitude/Sequoia team was the most active, with upgrades and many patches released, along with a lot of involvement on their forum (not this forum). So, one could compare the attention that Samplitude/Sequoia got with Vegas. Second, was Music Maker that had quite a makeover in the way that effects were accessed, amongst other changes. Last and least were the video/photo programs. PhotoStory got more attention as it has some features that are yet to be implemented in VPX/MMS. The other programs languished.

Magix created MAGIX Capture for VPX/MMS. Why, defeats all logic. No one asked for this did they? And, Magix messed it up (no mono audio recording, records to MP3 at 44.1kHz instead of Wave at 48 kHz. Why do this instead of fixing SFACL4, making it work properly with VPX/MMS and on its own? If SFACL4 worked properly with SpectraLayers Elements, it would be fantastic; it doesn't. At least SpectraLayers can be used as a standalone. Magix sells SFACL4 separately, so there is another potential revenue stream.

Over the last couple of years, Vegas has suffered with the loss of Vegas Post - Hitfilm and Image. On the VPX/MMS side, Magix and Xara divorced. At least Xara still works somewhat to create overlay graphics/animations, but Photo Designer (Xara) and CDPrinter (XaraXtreme) both disappeared. Hopefully Xara 3D Maker will still be around for several years.

VPX/MMS got AI Smooth recently, without fanfare. In both programs, AI Smoothing still shows up under MAGIX Hub, User Feedback as started - waiting for users to like that. I guess that no one monitors Feedback.

@me_again

Hi Andy,

I quickly received a reply back from ABSoft (Neat Video). They had just reminded Magix again to fix this and Magix replied that they are trying to publish it asap and to watch for an update from Magix. I'm turning blue holding my breathe.

John CB

The latest from Magix:

"Yes. I have news about this issue. Our developer are in contact with neat video and they work on this problem. I am confident that this problem will be fixed in one of the next patches"

Whoops!

AndyW

Greetings,

It seems someone doesn't want to admit something:

https://www.neatvideo.com/support/known-issues/magix

AndyW

Seems that the NeatVideo "known issues" was from over 2 years ago with Magix fixing the issue.

@me_again, @Reyfox

Hi Andy, Tony

The NV article is referring to an issue where 'Magix may serve frames in lower resolution, which usually leads to inaccurate profiling and noise reduction' and is dated November 24, 2022

'I started In November 2024 and last did some editing to it 29 December and MS2025 after the update has crashed'

This is a new issue, and I agree it has been caused by the latest update, previous projects where I used NV were also working fine until the latest update.

John EB

@me_again

HI Andy,

It's not getting any better. Magix released patch 24.0.1.233 without fixing the Neat Video crashing problem.

There were no details, but there were with the patch for VPX, so probably the same stuff:

Changes – Version 22.0.1.255:

• Fixed crash when removing OFX plugins
• Improved AC3 audio decoding in Windows 10 and Windows 11 systems
• MAGIX Capture installation behavior adjusted

John CB

I emailed both Magix and Neat again this morning commenting on the apparent lack of importance from magix re the Neat Video crashing problem. No reply yet from Magix yet (obviously) but Vlad at Neats reply was interesting (sent to me at 8:30).

I won't post all the email from Neat Video but the salient points are:

• They are extremely "discouraged" with Magix and hope that Magix will respond soon to offer a fix.
• They analysed the update about 9 hours ago (this was written at 8:30) and sent them the new results late in the night.
• Neat agree that it would make sense to "least let users return to an older version that had no such problem" - I'm not sure if they have said this to Magix though.

I'm glad someone's on the ball.

AndyW

If there were a way to go back to a previous build, that would work until things are fixed with the current build. This is one area where Magix should have this available. In the Vegas forum, you can always go back to a previous version by downloading the installer posted in the user forum. Maybe that will happen in the future here.

Hi,

VPX has already shown its stubborn talent at its best! Now that it is closer to Vegas Pro, I could suggest to the VegasCreative team an import of projects made in MMS/VPX. I just haven't returned to Vegas Pro because in 2 years I made many projects in MMS.

@Reyfox

I have another program (DAW) where they have a webpage with all the previous builds listed along with the 'fixed list' information with downloads alongside each revision of the current program available.

So such a thing should be possible but seems rarely implemented with most developers.

You can also 'rent to buy' their program in monthly instalments for the perpetual version (They don't do a subscription version) whether you are a first time customer or getting an upgrade offer. Revisions are also frequent if needed or when people report bugs that are confirmed in the current version. Support is excellent although a reply from a moderator that is a company employee make take a couple of days or more.

Ray.

@CubeAce I can not see any reason why there isn't a link to previous builds if a current update causes issues. It should be something that can be done right away, not send a message to support and wait for a reply. And while a "bug fix" is nice, there is a lot that is not included in the public release of that list. When I beta tested, there was always a generalized list of what was done. In the beta, a more detailed list. As for "rent to buy", with Vegas, I think if you subscribe for a year, you get to keep the last version of your subscription. I could be wrong though. I do know that was true when they had a 2 yr subscription.

@Roberto-Goncalves I don't see how they could program the Vegas to import VPX projects. They are totally different programs that operate, although doing sometimes the same thing, differently. That would be the reason for keeping both on your computer. Even though you can bring in a Vegas project into Davinci Resolve, FCP, Premiere/AE using Export, it won't be bringing over anything Vegas/effect/plugin specific.

I asked Magix for a link to revert MS2025 to the previous version 24.0.1.221 for those with the NV crash problem. This is their reply:

"If you want back to the past version 24.0.1.221 you need to reinstall Movie Studio.

Please follow the steps below to reinstall the software easily and safely.
Select "Start" > "Apps and features", select your application and click on "Uninstall".

Now delete the following hidden folders:

C:\ProgramData\MAGIX\Videodeluxe23C:\Users\Username\AppData\Roaming\MAGIX\Videodeluxe23\

C:\ProgramData\MAGIX\Videodeluxe24C:\Users\Username\AppData\Roaming\MAGIX\Videodeluxe24\

C:\ProgramData\MAGIX\Videodeluxe25C:\Users\Username\AppData\Roaming\MAGIX\Videodeluxe25\

C:\ProgramData\MAGIX\Videodeluxe26C:\Users\Username\AppData\Roaming\MAGIX\Videodeluxe26\

C:\ProgramData\MAGIX\Videodeluxe27C:\Users\Username\AppData\Roaming\MAGIX\Videodeluxe27\

C:\ProgramData\MAGIX\Videodeluxe28C:\Users\Username\AppData\Roaming\MAGIX\Videodeluxe28\

C:\ProgramData\MAGIX\Videodeluxe29C:\User\UserName\AppData\Roaming\MAGIX\Videodeluxe29\

C:\ProgramData\MAGIX\Videodeluxe30C:\User\UserName\AppData\Roaming\MAGIX\Videodeluxe30\

If you cannot see the folders, open the Control Panel and select "Explorer options". Under "Hidden files and folders --> View", simply activate the option "Show hidden files, folders and drives".
Now log into your customer account at www.magix.com and click on "My products" to download the installation file for your software.

To patch your version to 24.0.1.221 use the following link:
https://ssl-update.magix.com/patch/magix-video-deluxe-2025-premium-ka1-patch-24-0-1-220--1727694942"

AndyW

Did it work?

@me_again

Something fishy going on here. As I wrote on the first page, as soon as you told us, I reinstalled MMS 2025 from My Products. It was the first version. Then, a week later, I had to reinstall Windows, which meant another reinstall of MMS 2025. This time, the My Products file gave me version 227, the buggy version. Fortunately, I didn't have an need to use Neat Video and I patiently wait for the patch for the NV issue to come out. I am now back on my main machine and have declined all updates from Mid December.

@Reyfox

Sorry don't know yet. I'm a few days away from the home 'pooter so doing this from my phone. Hateful!

AndyW

Having recieved an email from ABSoft (Neat Video) stating that they "believe" that Magix has found a solution, I emailed Magix for an update. Their reply:

"Yes, our developer-team has succeeded to fix this problem. Unfortunately i cant tell you when the next patch will be released. In the moment the final tets are in progress."

AndyW