Building Standalone, AU & VST – MAC

[JKervinen]

Hey,

I’ve created ctrlr for Roland JP-8080 with Upper and Lower panel edits and common edits as well.
Is there a guide how I can get this ctrlr and create Standalone, AU & VST plugins from it?

I see alot of potential in this, as I have loads of hardware and sometimes I hate to run around the studio to tweak one pot and scroll thru menus!

I’m using mac, and I have xcode tools ready.
Is this Panel / ctrlr file also possible to open up in Windows environment and do plugin from there in PC format or do I have to build the panel again from scratch?

Just need the basic how-to build a plugin out from the ctrlr panel.

Thanks,
– Jani

[atom]

Well Ctrlr comes in VST and AU versions just load Ctrlr as a plugin in your host and open the panel in that plugin, and off you go.

It’s the same program in Standalone, AU and VST, there is absolutly no difference (the standalone version has it’s own window, but it is a VST loaded in that window)

[JKervinen]

Yeah I’ve figured that out already..

To make this very simple, how can I build plugin’s like the Nord 2, Nord 3 editor for exsample and is it possible to add multiple instances of the plugin in Logic to tweak the synth in ‘Multi’ mode?

Is this even possible with v5 ?

I want to save programs and banks and be able to call them back later on ” title=”Smile” />
Also, the knobs appear as ‘modulator0, 1, 2, 3, etc etc’ in Logic. Hard to remember what is assigned to Cutoff or Resonance.
Also, if I install the ctrlr plugin to instrument channel, it won’t send out midi notes to the synth itself.

The older editors (nord 2, 3, blofeld, p08, sn2) did that.

cheers,
– J

[atom]

a) you don’t build plugins, you make panels, there is one plugin called Ctrlr that can "host" as many panels as you like (even the same panel can be loaded multiple times)
b) programs, banks calling them back, not available now
c) the names of the modulators will change if you change them
d) this is the MIDI THRU feature and it’s pending, have a look at the Changelog it’s all there.

[minimalist]

"atom":2jlrwipv wrote:

c) the names of the modulators will change if you change them.[/quote:2jlrwipv]
Can’t imagine why, but this doesn’t work in any host (maybe a bug?). In NI Maschine I experienced the same problem. The parameternames always stay like modulator0,1,2… Renaming them doesn’t work.
Particulary in Maschine this is a bit annoing/confusing, because with M. you’re not forced to be in the near of your monitor – everything you can see at the hardware is enough for producing. But then if you have 200 parameters which all are called same ("mudulat") it’s not possible to know (and remember) where a particulary parameter is.

Is it possible to fix? In Ableton the parameternames refreshing as you wrote.

[JKervinen]

True, the parameter names won’t be shown in Logic even tho I have named them from the start to finish.

[atom]

Well this is a HOST bug/feature i’m afraid i can’t force the host to re-read the names of the parameters it should do it on it’s own. If you look in Live or Reaper or FLstudio once you rename your components the corresponding VST parameters also get that name, but some host don’t ask for the name each time a parameter changes they do it once on start and remember that until the end. There is no way in the VST specs to change that, it’s up to the host.

sorry.

[JKervinen]

Damn,

Well, then you just have to remember the parameters if you’re wanting to automate.

If I’m setting channel mode to write, Logic won’t even write the knob movements on the specified track. Is this a bug and can it be fixed?
I have both panels ready now. I tried to save the program (panel setting) within logic’s program manager, but that didn’t work either.

Do I need to go backwards with ctrlr in order to create my own AudioUnit with specified synth name in it / panel already in it, like the blofeld one etc?
Can I export / import the panel in xcode to build new plugin form there?
I really would love to see the parameters right and also bank + patch management.

– J

[minimalist]

"atom":1oguaiyp wrote:

they do it once on start and remember that until the end.[/quote:1oguaiyp]
Ooh, that sounds bad! Don’t know if it’s possible, but what about a work around? If the host gets the parameter names at the moment when the plugin is hosted….. Is it maybe possible to force Ctrlr when it get hosted, to already contain a certain pannel? So that Ctrlr doesn’t open as a plain/empty plugin. Maybe there could be a function in Ctrlr like: "load this pannel when beeing hosted"? Or export pannel as VST/AU?

Or is it already possible? Honestly I don’t know the difference between "Save current pannel", "Save Ctrlr state" and "Export current pannel". Maybe you could explain with just a few words what the differences are?

[JKervinen]

"minimalist":59otq0hu wrote:

"atom":59otq0hu wrote:

they do it once on start and remember that until the end.[/quote:59otq0hu]
Maybe there could be a function in Ctrlr like: "load this pannel when beeing hosted"? Or export pannel as VST/AU?[/quote:59otq0hu]

not a good idea, if you have multiple ctrlrs open at your daw, like i have. JP-8080 and 8000 panels (4 plugins). Would probably crash the program on load ?
The only way I see this could be done; having multiple ctrlr plugins in a folder, with different id’s, and they would have the panel attached already in it.

This way they would appear as a own plugin for each panel and this is what I’m wanting at the moment (yeah right, reach for the stars mate) ” title=”Very Happy” />

"minimalist":59otq0hu wrote:

Or is it already possible? Honestly I don’t know the difference between "Save current pannel", "Save Ctrlr state" and "Export current pannel". Maybe you could explain with just a few words what the differences are?[/quote:59otq0hu]

same here. ” title=”Smile” />

[atom]

well it’s not, the whole VST process looks like this
create plugin -> read parameters -> restore state from a blob of memory

the problem is that my list of parameters is in that blob of memory and there is no way to get it before the host asks for the parameters.

[minimalist]

Grrrrrrahhhh! ” title=”Neutral” /> ” title=”Wink” />

OK, then it’s Native Instruments (and Apple’s: Logic) part to fix this! I’ll make there a feature request! ” title=”Very Happy” />
Anyway, the most important issue is (for us fuc…. Apple users) to have a non-crashing VST/AU version (when Ctrlr is automated).

[atom]

yeah i know i’m working on that mostly. it’s weird that NI and Apple fucked it up it’s a very simple process two line of code.

[minimalist]

Nice, I really appreciate! And please don’t think that your last builds (which has been related to this issue) didn’t help – and that they just caused other problems somewhere else. Maybe a bit (but I think it’s normal that changes affect other issues).
But all in all: EVERY new build you’ve uploaded was better and better – and you really solved a lot. It felt to me that v5 needs maybe 2-3 updates more in this direction… and there is a rock solid VST/AU version. At least for a non-programmer like me.

[atom]

well the locking issue is a big one it will take some time to make it work, but i’m working on it all the time.

[Author]

Posts