fr3udes wrote:Dear Zabukowski, i bought it because it is supposed to make my life easier but let me tell you this is WAY too OVERPRICED for a plugin manager. For the same price you have a lot of professional plugins (http://www.valhalladsp.com/ comes to my mind).
Anyway at least i would like it to work but after first launch :
I've already sent you a license and instructions (Nebula 1.3.602 or greater is required). If you have older nebula, i can send you instructions how to fix this.
Hope you don't think about Nebula Setups being 'amateurish' program ? I've answered your comment in the email, as well.
Franci (Valhalla Room, Vintage Verb and UberMod user
Not sure proper thread ... but still a 'feature' request.
Hi ZAB !
As my custom Nebula count grows [much due to the essential SetUps program, there is a aspect that I'm constantly having to manage.... the 'VST MAGIC ID #'.
Reason being, certain programs and chainers use this ID# to identify a plugin. If they have the same Magic#, only the first is recognized.
To this end, I manually edit the XML of each custom Nebula with my own Magic#.
My wonder ... if somehow this 'management and assignment' could be handled within SetUps. Having some type of database that holds all the current Magic# in use, and a way to assign a #### when creating a new custom Nebula.
RJ...If you are using the newest version of Nebula Setups, all of that can be edited from the program. There are ways to use "local tweaks", and also "global tweaks".... Everything you are asking about can be done from the app.