Good evening, I've gotten 60k presets for massive but now when I try to open massive again it crashes the whole DAW/doesn't even open in standalone. Is there any way to fix this? by organizing folders or such? and to keep the 60k presets

 

use your file explorer/finder to go into the directory tree and move the folders with all your presets into a new folder your Massive cannot see when you first open it. That will solve your crashing upon load problem.

How you organize the content of that folder, it is up to how you manage your presets. It could be per genre, per pack if they came from preset packs, or whatever else.

 

I have the free packs for massive on Documents\Native Instruments\Massive while for dubstep on D:/Libraries/NI/Dubstep, and for genres on D:/Libraries/NI/Genres

 

So you could just either move the ones on D: to a new folder, and then launch Massive. Or rename the folder so it does not match what Massive is looking for when loaded. You haven't included the usual details like OS, or Massive version. I mention this because if your link does not update when you change the folder, you could just rename the NI folder to something else while you are testing.

You just want Massive not loading all your 62K presets when you launch the plugin/app. Then you can get Massive open and look at your options in the settings/preferences menus.

 

My bad, my os is windows 11 pro and my massive version is 1.7.0
Following your advice it did work, so I am grateful for that! But what I want mostly is that the presets show right here so I can find them easier (and because I am used to find them like this)

 

Your posted picture is missing!

How To Load An Expansion Preset In Massive

Note: After installing the Expansion, it is important to run Massive in stand-alone mode before using it as a plug-in in your DAW. This step is required for Massive to detect the Expansion.

https://support.native-instruments....85-How-To-Load-An-Expansion-Preset-In-Massive

 

From what I vaguely remember, when you open Massive it starts databasing. If you have a huge amount its going to take ages to sort through them, so open the standalone, check that the wheel is spinning and just leave it for many minutes.

I stopped installing so many packs, so I can't remember if it does this on every new opening. My feeling is that its a one-off, as long as you let it complete the database properly.

 

And in that same Options window you can add or delete whatever locations you have assigned it to see. After you have it rebuild the database, when you click Sounds in the browser, and then + Explorer; you can see what expansions have become available. If you got a pack that has 62,000 of something from that "company" called Composer Loops; i'd bet 50,000+ of them are junk anyway.

 

I can't remember the exact limit, but after something like 10k+ presets the database goes kaputt and it hangs on scan. Then the only way to get it back running is to wipe the database and wipe the user presets, then adding a few libraries back at a time and rebuilding the database (which shouldn't be too slow).

This is from memory though, your mileage may vary.

 

Exactly. I think there's a bit of FOMO about our collecting habits, like that amazing preset might be in there somewhere, but I've found it impossible to search huge lists. I can't make decisions at that point.

 

Indeed. I got a free copy recently somehow. Its so long since I've used it that I can't remember the plugin now, but that 10k limit sounds like my experience.

 

There's no fixed limit, but very large quantities (>10,000 presets) may slow down performance or reduce clarity.
You can save as many presets as you like, as long as you organize them well and your system is powerful enough.

 

there is nothing very productive about having 60,000 presets for one synth plugin. You will spend more time auditioning them than you would just having something close to what you need and modifying it. That "Company" Composer Loops has packs with that kind of numbers in them, and either they are using a program to automatically generate them, or they are downloading stuff from all over and then just compiling them into packs like that size.

Massive (pun intended) collections of presets like that are the same thing as Midi file packs you can see out there with 200K or 300K files in them. It's better to chop them up into more folders so they are at least somewhat indexed. Otherwise it adds a lot of lagging. You can even notice latency when you move around list controls, scrolling etc. Fixing this same issue in Serum2 was probably a lot of work that we're not going to see end up ever being done with Massive. Nexus5 does not even get like this with 30K loaded into it.