Access Global Script "handles" from the Local Rackspace script

Is it possible to access Global Script widget handles from the Local Rackspace script ?

I have been using now for several years my Global Rackspace as my main mixer for all my plugins used in the rackspaces, and controlling the levels of the global mixer from within the local rackspace. That works flawless, but to actually have a visual feedback of the meters, I always need to switch to my global rackspace. As I cannot choose where my global rackspace is viewed in setlist view (top / bottom / default visible), and besides that the global rackspace takes almost all available space, I’m trying to get my meters in the local rackspace.

So I’m hoping there is a way to access Global Rackspace widget values from the local rackspace.

I found several topics in regard to this, but the proposed “workaround”: use the global rackspace, is not really an option for me.

I tried using OSC, on the meters but it seems they don’t send out any OSC messages
I tried also with External Widgets, but that only seems to work between “local” rackspaces, but not between global rackspace and local rackspace (please correct me when I’m wrong)

I was wondering if there are any other options.

The meter widgets are special - unlike other widgets, meter widgets explicitly query the gain value of a mixer channel rather than being informed of a change.

@rreuscher like @dhj said, you can’t get the level meter display values this way

However,

  1. Yes, there is a way to get global rackspace widget values with scripting, look for the BindExternalWidget and GetExternalWidgetValue functions - it won’t work for this specific use case but does exist
  2. If you want to see some levels from the global rackspace in a “local” rackspace, you can do it by routing signal from wherever you want to measure it to a “To Rackspaces” block, then in the “local” rackspace just use a meter to display that signal using a “From Global Rackspace” block.

It is clear now that it will not be possible using the meter widgets. I might go the route of creating a simple plugin myself to forward level values to local rackspaces.

With regard to “1”: How do I “BindExternalWidget” to the global rackspace ? What would be the name of the rackspace… (have not tried it yet, maybe its just as simple is “global”)

Regarding “2”: That might be a bit overkill, but then again if it does not put any significant load on the system, that might be an option.

It’s just a connection, and you should have it anyway since you have some audio in the global rackspace?

No, As the Global rackspace is my “Summing Bus” and processing for my FOH and Monitoring, there is no audio flow from Global to Local. But I can do that.

@Frank1119 created a plugin that allows you to map a meter widget to incoming signal. It may be of use to you.

@Frank1119 that was exactly what i had in mind, so why inventing the wheel twice.
Today I finally found some time to download and test your Magnitude vst3. Unfortunately it fails to load in Gigperformer. Do you have any idea why it might fail ?

Are you on Windows?

You might need to unblock it: in explorer right -click on the .vst3, choose properties. If it is blocked, you see that on the bottom of the properties dialog, along with an option to unblock

I have both, but this one I’m testing on windows, yes

There’s no Mac support, because I can’t notarize the executable. I can compile it for, but then you have to disable the mac-security check for this library, somewhere, somehow

Or you import the juce project and compile it with xcode

As I will run it mainly on my live setup (which is Windows), I try to load it in windows, but it fails in Gigperformer. I assume i just need to place to vst3 file in the Common Files\VST3 folder ? Or am I missing something…

That should do. Did you check whether the file is blocked?

This is what I can see:

What do you mean with “Blocked” ?

In explorer. Not in GP :nerd_face:

What does it take to sign the executable on a Mac to be reusable? Does it require some sort of a paid developer account?

Yes. And a lot of hoops to jump through.

It was indeed blocked. Unblocked it, but still fails to load in Gigperformer.
Is there some trace/log file in GigPerformer that would show a more detailed error message ?

You still have to remove it from the failed (red) list in GP. Right click on it in the GP Plugin Manager and Remove from list, then rescan.

1 Like

Did “all of the above” but without success. Will investigate a bit further this weekend.