Nebula Setups 2 released (win, osx - x86/x64)

Additional software tools
fpoitevin
User Level IX
User Level IX
Posts: 91
Joined: Mon Sep 20, 2010 9:48 pm
Location: Grenoble, France

Re: Nebula Setups 2 released (win, osx - x86/x64)

Post by fpoitevin » Tue Dec 31, 2013 3:32 pm

Fantastic ! Very fast loading and improved workflow.
Thanks a lot.
f.

RJHollins
Expert
Expert
Posts: 3932
Joined: Sun Mar 28, 2010 5:53 pm

Re: Nebula Setups 2 released (win, osx - x86/x64)

Post by RJHollins » Fri Mar 27, 2015 6:40 pm

Not sure proper thread ... but still a 'feature' request.

Hi ZAB ! :D

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. :roll:

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.

Just wanted to get the thought out there ;)

Thanks
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]

richie43
Expert
Expert
Posts: 5049
Joined: Fri Feb 04, 2011 8:47 pm
Location: Minnesota, USA
Contact:

Re: Nebula Setups 2 released (win, osx - x86/x64)

Post by richie43 » Fri Mar 27, 2015 8:03 pm

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.
The Sounds of the Hear and Now
http://soundyaudio.com/

User avatar
zabukowski
Expert
Expert
Posts: 1583
Joined: Sun Mar 28, 2010 8:44 pm
Location: Ljubljana, Slovenia
Contact:

Re: Nebula Setups 2 released (win, osx - x86/x64)

Post by zabukowski » Sat Mar 28, 2015 12:36 pm

As Richie already mentioned, you can use Local tweaks to define MAGIC number for the particular setup.

Not sure, but having Magic# database inside program may be beyond the scope of the Nebula Setups !?

Well, never say never :)

Cheers

RJHollins
Expert
Expert
Posts: 3932
Joined: Sun Mar 28, 2010 5:53 pm

Re: Nebula Setups 2 released (win, osx - x86/x64)

Post by RJHollins » Sat Mar 28, 2015 5:46 pm

yeah ... it's the keeping track of the used Magic numbers that gets cumbersome.
:|
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]

kindafishy
Vip Member
Vip Member
Posts: 434
Joined: Tue Mar 22, 2011 2:08 pm

Re: Nebula Setups 2 released (win, osx - x86/x64)

Post by kindafishy » Sun Mar 29, 2015 1:03 am

RJHollins wrote:Not sure proper thread ... but still a 'feature' request.

Hi ZAB ! :D

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. :roll:

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.

Just wanted to get the thought out there ;)

Thanks
Hmmm, so if I am to understand this, you load a Neb plugin created by setups, you get it set, you close the DAW, and then when you reopen it, it might select a different Neb plugin because of the magic number? Is that correct?

Which DAW are you using?

richie43
Expert
Expert
Posts: 5049
Joined: Fri Feb 04, 2011 8:47 pm
Location: Minnesota, USA
Contact:

Re: Nebula Setups 2 released (win, osx - x86/x64)

Post by richie43 » Sun Mar 29, 2015 1:10 am

RJ is using Nebulas in some very unique ways kindafishy, he builds his own "controllers" that are GUI wrappers for multiple instances. Their functionality is similar to the newer Acquas, but only a little similar. They are actually very cool, he has a thread here about them....
http://www.acustica-audio.com/phpBB3/vi ... &hilit=nvc

For the record, I have never had my DAW choose the wrong plugin. In fact, the last time I looked, the magic numbers of all of my instances (well over 100 and rising) are the same.
The Sounds of the Hear and Now
http://soundyaudio.com/

kindafishy
Vip Member
Vip Member
Posts: 434
Joined: Tue Mar 22, 2011 2:08 pm

Re: Nebula Setups 2 released (win, osx - x86/x64)

Post by kindafishy » Sun Mar 29, 2015 1:42 am

richie43 wrote:RJ is using Nebulas in some very unique ways kindafishy, he builds his own "controllers" that are GUI wrappers for multiple instances. Their functionality is similar to the newer Acquas, but only a little similar. They are actually very cool, he has a thread here about them....
http://www.acustica-audio.com/phpBB3/vi ... &hilit=nvc

For the record, I have never had my DAW choose the wrong plugin. In fact, the last time I looked, the magic numbers of all of my instances (well over 100 and rising) are the same.
Thanks, brother! I'll check out the nvc as well.

RJHollins
Expert
Expert
Posts: 3932
Joined: Sun Mar 28, 2010 5:53 pm

Re: Nebula Setups 2 released (win, osx - x86/x64)

Post by RJHollins » Sun Mar 29, 2015 6:11 am

The MAGIC number is used by certain DAW's [maybe Cubase], and in most particular, the chainer Plogue BIDULE. Lately I use Reaper ... it uses the VST name [so non issue].

When BIDULE scans for VST's, it uses this Magic number to identify the plugins. If they all have the same Magic number, then it only registers the first one identified ... all the rest are not acknowledged ... so ya can't use them :roll:

Hey ... not my idea, but actually, BIDULE is written strict to the VST standard. [what the author told me].

Because BIDULE is what I prefer to use for my chainer to be controller via my NVC plugins, I make up a special Magic# in the custom XML file.

It all works in the end ... its just trying to remember what ###'s I have used. But actually, I now use part of the library name as the 4 letters used in the Magic#. This makes it easier to be sure they are unique. Also ... when updating the custom.DLL's with a new Nebula version, the XML file doesn't change, so the edit is only a one-time, first-time deal.

just wanted to clear this up ... hope that made sense :lol:
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]

Post Reply