Launching Music Maker 64bit causes windows 10 to shut down.

Brian-Robichaud wrote on 11/26/2021, 11:27 PM

This happened when I changed/added a VST location in the last settings tab. Right then windows 10 went to the shut down screen and my computer turned off. I uninstalled Magix Music Maker 64bit and continued to use the earlier version that was still on my computer. I actually am more used to the earlier version and would say the 64bit layout needs some work as some info like displaying BPM on sound loops seems to not be working correctly.
Anyway I reinstalled the 64bit version which I believe to be the latest version because it was straight from download and the same thing. Clicking the desktop shortcut the program begins to launch but when it is scanning for plugins my computer just shuts off. It goes to the proper windows 10 shut down screen and just turns off.
I can't explore this problem too thoroughly as it really is annoying to have to restart my computer every time I try to launch the program. I've not had problems with any other programs and my windows 10 version is completely up to date from the official windows update settings.
Anyway I thought I'd just throw that out there in case anyone else had run into this problem and found a solution or just to help make the company aware there does seem to be a problem with the 64bit version of Magix Music Maker.
Just as a side note, I've had a lot of fun with Magix Music Maker and consider it a great product.
Thanks,
Brian Robichaud

Comments

SP. wrote on 11/27/2021, 3:42 AM

@Brian-Robichaud

Do you know which path was added that is now causing the problems? Just try to move or rename it before you start Music Maker.

You can reset the VST scan settings by editing the textfile VstScanSetup_x64.ini in C:\Users\YourUserName\AppData\Roaming\MAGIX\mm30 which contains all your VST scan paths.

You can remove the scanned plugins by editing or deleting all the textfiles named plugin_scan_state_VST2_x32.scan, plugin_scan_state_VST2_x64.scan, plugin_scan_state_VST3_x32.scan, plugin_scan_state_VST3_x64.scan.

If you delete the Musicmaker.ini file the program settings will be reset to the default settings.

Brian-Robichaud wrote on 12/16/2021, 9:09 PM

Hi,

(Sorry it has taken me so long to get back to this and try your suggestions)

I tried your suggestions, and still my computer shuts down when I when I try to start the 64biut version, it is when the program is scanning the folders while starting. Looking through the Musicmaker.ini file some of the folders had forward slashes in the folder path instead of backsword lashes... weird considering I used to program to search for folders I didn't enter anything manually.
Anyway editing or deleting these files didn't work and I can only try so many times as having the computer shut down on every attempt is a little bit too much to deal with.
I've already tried uninstalling and reinstalling the program so I'm not sure what else I can do.

johnebaker wrote on 12/17/2021, 11:35 AM

@Brian-Robichaud

What is your computer specification - see this topic for details of what is required and please quote processor and graphics card make/model in full.

It would help us to help you if put the specification in your Profile, Signature

John EB
Forum Moderator.

Brian-Robichaud wrote on 12/17/2021, 11:45 AM

Hi,

AMD 5600G CPU/APU

32Gb 3200Mhz corsair vengeance DDR4

WD 500Gb .m2 SSD as main hard drive

ASUS Prime motherboard with RealTek audio

Windows 10 with Automatic updates on and up to date.

Just to once again mention the program worked 'fine' before adding a VST path in the settings. When I say 'fine' I would say the UI in the 32bit version is a much smoother experience.

johnebaker wrote on 12/17/2021, 2:10 PM

@Brian-Robichaud

Thanks for the specifications.

. . . . the program worked 'fine' before adding a VST path in the settings . . . .

Having ruled out a potential issue with the hardware.

Are there any 'illegal' characters in the folder name or the VST files names - eg any of the keyboard top row characters (keys 1 to 0 and the +/= key) except the underscore and hyphen (minus) key, and all characters to the right of the alpha character keys

Try removing the contents of the VST folder that was added, and then start Music Maker (MMM). If the program launches OK, then the issue is with one or more of the VST's. In this case you need to isoalte which VST is causing the issue, eg add VST's, a few at a time, and start MMM, repeat the process until it crashes then remove, this will give you a small group which you can checked by removing one at a time to locate the offending VST.

John EB

Brian-Robichaud wrote on 12/17/2021, 2:30 PM

Non of the plugins seem have any of those characters in their names. The folder(s) that I added were either the steinberg folders or C:\Program Files\VST and C:\Program Files (x86)\VST. Either way the plug ns don't present any problems with the 32 bit version or with Ableton 11 Lite or Ableton 10 lite. I may try emptying out these folders and giving that a go, but once again each time I try anything my computer shuts down entirely which is very inconvenient.

Brian-Robichaud wrote on 1/13/2022, 10:02 PM

Hi,

I cut the folders with the plugins and pasted them to a temp local. Started the program, it worked, and hit the reset to defaults button. Then I pasted the plugins back and restarted the program and it worked.
Thanks for the ideas and suggestions.
Very glad to get the 64bit version working again.
Once gain thansk very much.