Hello,WasteLand wrote: ↑Wed Jun 16, 2021 12:39 pmstill problems with loading samples into Granulizer 2, they won't save, i must manually copy & paste the sample in the sample folder for users.InertiaSoundSystems wrote: ↑Sun Nov 29, 2020 1:50 pmWe might need to reach out to you about this, thanks for bringing it up!WasteLand wrote: ↑Sat Nov 28, 2020 1:38 pmthe download went very slow, and ended with "inst", so not installed, enough space (72gb), i shall try it again. but not today.. other things..InertiaSoundSystems wrote: ↑Sat Nov 28, 2020 1:14 pmbobsled contacted us on support, so what we suggested is this:
Friction is the biggest one of them all (335MB~), so make sure you have enough space to download and uncompress it. I tested it over here and it downloads/installs properly.
Please try having clean space available and try shutting the DAW down and re-downloading it.
We're trying to make sure that it’s not an issue on the software.
mainly i made my own presets.. if you load a sample via the icon, not drag & drop, didn't do drag & drop, my own sample, on a different harddrive.
i was surprised my presets weren't saved. i copied the sample to the data directory in the user folder (i guess you can make also your own folders, to structure it..), then it could be saved.
i lost 2 presets that way (i could have transferred the wav file while still in the DAW, user error, but still)... but i guess i managed to revive them, made more presets...
must map it, didn't notice until now, no modulation.. so automap, or nektar panaroma p1 or MCU (or and/and/and). so i can automate. no prob i like automation.
every plugin, has their own way of working with presets, in the end i can work with all.. why mention it? perhaps it can help..
a bit of a workflow killer.
also, i prefer; user defined location for presets. i don't mind, that the preset folder also contains the samples. i organize them quite well, but still... to consolidate them, is in my view a good thing.
but 'consolidating' does not work... without that workaround..
sorry to hear that...
What is your OS?
This may be an issue of wrong folder permissions. Do you have write access to the presets folders?
Automatically copying the audio file in the same folder as the preset xml file, is minimizing the possibility of loosing the source audio used for that specific preset and make the plugin Presets as portable as possible.
Regardless, we are working on giving the user the freedom to choose whether the audio file used will be copied to the presets folder when a preset is created or not.
Best