Someone help me out please. How can i extract the patch names from Halion 7, that it would auto populate the text labels in GP? So if i switch between rack variations, the patch names would accordingy change based on the loaded GP preset.
Unless the plugin exposes the preset name as a parameter you probably canât do that, at least with the pluginâs preset system. And while you could do something similar using GPâs preset system (which works with all plugins), itâs unclear that this is a best practice. Your rackspaces and variations should really display what youâre doing (e.g, SongX, Tremolo, Phase, Verse 2, etc)
Consider that you will normally have more than one plugin in a rackspace (multiple synths, multiple effects, etc) and so a preset name of a single plugin doesnât really make much sense.
Iâm piggy backing on this 1 year old post b/c I have the same question. My plugin DOES expose the preset name parameter and the text label does display it ONCE, but it does not update when I change presets. Is it possible to update every time the preset is changed?
At first, the label shows the correct preset name:
That was simple and beautiful as well as beautifully simple! hehe Thank you! Works like a charm! I monkeyed around with scripting it, but I was missing the txt part. Learning! Thanks again!
Taking this a little further, how would you shoot this over to another instance? The plugin and knob that is linked to the preset parameter name is in instance A and if I wanted the label to be in instance B? I donât my normal OSC linkup in the widget properties advanced tab is going to do it. Iâm guessing the OSC has to be in the script? But since the widget in instance B cannot be mapped to the plugin parameter, Iâm failing to grasp how that would work?
Awesome, glad to see there is a way! My sending instance is in the global rackspace, so I added /GlobalRackspace before the â/lblâ so it looks like: â/GlobalRackspace/lblâ. Is that right?
Iâm getting this error on the sending end:
GLOBAL RACKSPACE (Script Entity: GlobalRackspace) - - Syntax Error in âMainâ: Line 46, Col 20: Unexpected or unrecognized token:
Token recognition error at: ââÂÂâ
Here is whatâs on that Line 46:
OSC_SendString(â/GlobalRackspace/lblâ, txt)
On the receiving end, its the same error:
TweedDLX NDX (Script Entity: Rackspace) - - Syntax Error in âMainâ: Line 5, Col 47: Unexpected or unrecognized token:
Token recognition error at: ââÂÂâ
Line 5:
On OSCMessageReceived(m : OSCMessage) Matching â/GlobalRackspace/lblâ
Do I need to give more info about the OSC IP address and/or port?
In this example. you donât have to add /GlobalRackspace to the outgoing OSC address because you are simply generating an OSC String message called /lbl in the script itself. Itâs not tied to a rackspace, the callback is just saying âwhen the knob turns, send a message called /lbl with a string value via OSCâ.
Therefore, you also donât have to add /GlobalRackspace on the receiving end of that OSC message either.
Add the scripts as I wrote them and see what happens.
Iâm guessing the Syntax error is coming from the â â in the pre-formatted text. Copy/paste the scripts into a text editor first, then copy/paste the scripts into your gig from there.
Its âworkingâ BUT something interesting is going on. Its 1 off⌠Meaning, in instance A if preset 1 is selected, itâll send the name of preset 2 to instance B and âcyclesâ one name ahead. So if I had 4 presets in total, it looks like this:
Actually it seems random depending on if I am clicking forward or backward. Not sure if there is a consistent pattern yet⌠So its the correct names, but in different order.
Is the communication between the global and local rackspaces/widets via script withing the SAME instance similar to between instances? I started a new post here in the scripting category and I donât mean to double post, but it occurred to me that the same code used here might work, but I couldnât get it to work. Trying to update the caption of a widget from GRS to the caption in the LRS.
I really need to mark all those functions as deprecated. I think everyone has forgotten that there is built in support in the language itself for this.