Help Johan with Rompler expansion system
Posted: Mon May 25, 2020 8:29 am
Hi all
For some time now I’ve been helping Johan to make romplers in FS. I’ve come up with various solutions that have resulted in good plugins. These romplers are generally based around a single set of wavs external to the plugin and a preset bank baked into the plugin, with the possibility of loading more banks in the future.
But what he really wants now is way beyond my capabilities and I think would need a Ruby solution.
This is his text, in which I have tidied up the English, followed by my comments:
This is how the rompler is supposed to work:
When you first load the rompler, it should always load the Start Library expansion
And if it’s possible, if you change the expansion, then next time when you load the rompler plugin it should start with that expansion. Like you start your DAW, then load the rompler then it starts with the Start Library. And let’s say if I change the expansion from the Start Library expansion to let’s say “Bounce Expansion”, then next time you load the plugin it starts with the Bounce Expansion.
If that’s not possible, then it should always start with the Start Library expansion. Every time you load the plugin it should start with the Start Library, instead of being empty.
And it should work for collaboration as follows:
Let’s say I’m using FL Studio 9 and I have a friend who’s also on FL Studio 9. If I make a project with the same expansions as my friend has, then if he loads the project I made in FL Studio 9, it should work to open the project for him as well, if we have used the same rompler and same expansions.
By “Expansions” Johan means a folder containing a lot of samples in wav format. I believe an Expansion should also carry with it a bank of presets to accompany the wavs. Ideally this would be a single encrypted installable file with the presets and wavs embedded, like Kontakt can use for paid-for expansions.
2 examples of such a rompler would be Lethal:
https://www.lethalaudio.com/
or Nexus:
https://refx.com/nexus/
Clearly these pro synths write to the registry and probably create configuration files for telling the plugin what libraries/Expansions/Banks are installed at start up.
This is way beyond me, so if anyone can step up, Johan would be delighted.
Cheers
Spogg
For some time now I’ve been helping Johan to make romplers in FS. I’ve come up with various solutions that have resulted in good plugins. These romplers are generally based around a single set of wavs external to the plugin and a preset bank baked into the plugin, with the possibility of loading more banks in the future.
But what he really wants now is way beyond my capabilities and I think would need a Ruby solution.
This is his text, in which I have tidied up the English, followed by my comments:
This is how the rompler is supposed to work:
When you first load the rompler, it should always load the Start Library expansion
And if it’s possible, if you change the expansion, then next time when you load the rompler plugin it should start with that expansion. Like you start your DAW, then load the rompler then it starts with the Start Library. And let’s say if I change the expansion from the Start Library expansion to let’s say “Bounce Expansion”, then next time you load the plugin it starts with the Bounce Expansion.
If that’s not possible, then it should always start with the Start Library expansion. Every time you load the plugin it should start with the Start Library, instead of being empty.
And it should work for collaboration as follows:
Let’s say I’m using FL Studio 9 and I have a friend who’s also on FL Studio 9. If I make a project with the same expansions as my friend has, then if he loads the project I made in FL Studio 9, it should work to open the project for him as well, if we have used the same rompler and same expansions.
By “Expansions” Johan means a folder containing a lot of samples in wav format. I believe an Expansion should also carry with it a bank of presets to accompany the wavs. Ideally this would be a single encrypted installable file with the presets and wavs embedded, like Kontakt can use for paid-for expansions.
2 examples of such a rompler would be Lethal:
https://www.lethalaudio.com/
or Nexus:
https://refx.com/nexus/
Clearly these pro synths write to the registry and probably create configuration files for telling the plugin what libraries/Expansions/Banks are installed at start up.
This is way beyond me, so if anyone can step up, Johan would be delighted.
Cheers
Spogg