>> I'm not sure how to keep the loops, effect, sound pools, VSTs, etc.

For Magix-related items that you purchased through the in-app Store. . .
 - install MM on the new system
 - log in (do NOT try to enter your ser #)
 - some items will automatically download and install
 - many others will be listed in the Downloads window,
    and you can d/l them manually to your system (they will install automatically)
(Note: I have experience with MM 2021/22, not sure how earlier versions work.)

For 3rd-party items (not directly MM-related). . . what @johnebaker said.
 

hth,
John

Much appreciated, this looks like exactly what I'll need. Should I keep the SoundPoolDB.xml file, too?

Daniel

>> I'm not sure how to keep the loops, effect, sound pools, VSTs, etc.

For Magix-related items that you purchased through the in-app Store. . .
 - install MM on the new system
 - log in (do NOT try to enter your ser #)
 - some items will automatically download and install
 - many others will be listed in the Downloads window,
    and you can d/l them manually to your system (they will install automatically)
(Note: I have experience with MM 2021/22, not sure how earlier versions work.)

For 3rd-party items (not directly MM-related). . . what @johnebaker said.
 

hth,
John

 

More great information! I think I'll start with this, then work through archived directories John Baker has specified. That sounds like that will put it back together.

Warm regards,

Daniel

@Daniel-Hoff

If you download soundpools from within MM, then MM will automatically generate a new SoundpoolDB file. It gets updated as you bring in more soundpools.

John

@Daniel-Hoff

Hi,

Under the Soundpools folder, if you have any that were purchased before the Store started in Music Maker or purchased directly from Plantproducer and you put them under Soundpools yourself, they are not linked to the Shop and Music Maker will not tell you to download them. You have to copy these over from your old computer, and maintain a backup. Music Maker only knows about what you purchased through the in-app Store. See below - I have many Soundpools purchased before the Store started that I had to copy to my new computer.

John CB

@Daniel-Hoff

Hi,

Under the Soundpools folder, if you have any that were purchased before the Store started in Music Maker or purchased directly from Plantproducer and you put them under Soundpools yourself, they are not linked to the Shop and Music Maker will not tell you to download them. You have to copy these over from your old computer, and maintain a backup. Music Maker only knows about what you purchased through the in-app Store. See below - I have many Soundpools purchased before the Store started that I had to copy to my new computer.

John CB

Looks like I should be okay, I started with MM 2018 I think, and it looks like mine are all from the Shop (late 2018 forward, in individual subdirectories).

So it sounds like, if I do the clean install, log in, let it do the auto DLs, grab any other previous purchased DLs - since all my stuff under C:\Users\Public\Documents\MAGIX\Common is from the Shop, it should index and recreate the XML database. Sounds like it shouldn't miss anything, but I can check and copy if it does and hope it indexes.

VSTs I can hunt down and copy. I have a plan now :)

Thanks everybody for info!

Daniel

Hi all,

I have an issue with MM2022. At a certain patch level, on a completely clean install, starting with the title screen, it moves super super slowly. It doesn't hang completely, but it may take an hour to pull up the app, so some sort of incompatibility(?). In Task Manager, it pegs everything. Again, it will eventually get through each screen, but in tens of minutes. So, a four year old Win10/64 box, Asus Z370 and Intel Core i7-8700 CPU with 32GB of RAM, all M.2 NVMe SSD. Blazing on everything else.

Now I've built a new, even more powerful box. Window 11/64, Asus Z590 / Intel Core i7-11700K.with 32GB of RAM, all NVMe SSD. Same exact behavior, except it's pegging a CPU that's three generations newer, and a brand new everything install from the OS up. Anyone have troubleshooting thoughts, because I'm not really sure how it could be cleaner, or where I might look from here?

All input appreciated.

Thank you!

Daniel

@Daniel-Hoff What performance load does the graphics card in the Taskmanager show?

This sounds like a graphics driver problem. Are your drivers up to date?

Hello,

Graphics drivers are up to date, GeForce 1070Ti, hovering around 0%. Disks / RAM / Network, etc. are also very low.

MusicMaker shows "Not Responding" btw 5-14% utilization on an idle screen, like the first Choose Your Name screen and it seems to stick to the first core.

Power consumption shows Very High, same as on other box. ResMon shows the analyze wait chain status as "One or more threads of Music Maker are in waiting status"

Below are procs Suspended and 100%. I didn't analyze to that level on the Win10/64 box but the slow-down behavior is identical.

ShellExperienceHost.exe

SearchHost.exe

LockApp.exe

MiniSearchHost.exe

SystemSetting.exe

YourPhone.exe

backgroundTaskHost.exe

Other than those, nothing that stands out?

Thank you,

Daniel

@Daniel-Hoff What happens if you disable your Internet connection before starting Music Maker?

You can try and reset the program setting by deleting the MusicMaker.ini in C:\Users\YourUserName\AppData\Roaming\MAGIX\mm30

@Daniel-Hoff What happens if you disable your Internet connection before starting Music Maker?

You can try and reset the program setting by deleting the MusicMaker.ini in C:\Users\YourUserName\AppData\Roaming\MAGIX\mm30

Turning on Airplane Mode let it get to the main loops / sounds screen! I turned it back on to log in (no licensing per previous discussion), and it DL'ed a huge array of soundpools, instruments, features, etc. and installed various things automatically or manually. Idk if it was everything, but if not, close enough :) So whatever hoses it up is in the initial screens.

I looked for the .ini file there, but there was no MusicMaker.ini file (is that a potential problem?), only the VstScanSetup_x64.ini which I left alone.

Thanks for the great tips! Even if I have to do that as a workaround, I've got a working DAW as long as I use Airplane Mode at startup.

Daniel

@Daniel-Hoff

Hi

The Music Maker ini file is in the folder

%appdata%\MAGIX\mm30 and the contents should look like this (Premium version)

If the ini file is missing, Music Maker should recreate it, if this is not happening and/or you do not have the .scan files check your antivirus Folder /Ransomware protection feature is not blocking the program from accessing this folder.

HTH

John EB
Forum Moderator

@Daniel-Hoff

Hi

The Music Maker ini file is in the folder

%appdata%\MAGIX\mm30 and the contents should look like this (Premium version)

If the ini file is missing, Music Maker should recreate it, if this is not happening and/or you do not have the .scan files check your antivirus Folder /Ransomware protection feature is not blocking the program from accessing this folder.

HTH

John EB
Forum Moderator

After using Airplane Mode to get it to start initially, it starts reliably instead of freezing, and it generated a MusicMaker.ini file. Performance still has a considerable lag (may 5-20 seconds on a given action), but works. After close, rename the .ini file, and restart, works reliably but slowly with the same 5-20 second lag on actions.

Turning off internet access w/Airplane Mode isn't needed at start any more, and just experimenting, doesn't seem to help in-app performance elsewhere. MM has generated a new MusicMaker.ini file as expected, plugin scan files are present, and everything in the directory is stamped with today's date, so hopefully no AV interference. If it's helpful, there's a crash log file with what appears to be one event per startup:

Crash.log

ASIO Boost Driver - cannot open SCM

Don't know if related.

Daniel