Moving away from 1 Rackspace per song - What about Audio Player?

[DerBecker]

There are hidden button-widgets for every lane in every player. They are grouped together for every lane.
So if you press the visible Lane2 button it activates every player to Lane2.
As only the needed player is active and the others are muted, this works out.

But there was a script in it, it is the radio-buttons script made by Schamass.
It worked out for me, but don’t ask me how - I’m totally unfamiliar to scripting.
Just copied it and modified the number of buttons in a logical way.

I try to attach a gigfile with the principal of that player. Just click away the notification for the missing audio files and you can see how this works.

You can modify this easily to your special needs.

Global-Media-Player-principal.gig (432.5 KB)

[vangrieg]

@DerBecker

There are hidden button-widgets for every lane in every player. They are grouped together for every lane.

Ah, ok, got it, thanks!

[vangrieg]

Just in case, there is another solution - if instead of loading all backing tracks into audio player slots and instances you just save per song presets of audio player, you can have just one track loaded in memory and can switch the backing tracks automatically when changing songs:

Reusing Global Rackspace components across songs

I must admit I’ve not thought about using the GP plugin presets as a way to load files per song. But it does work… ‘Gig Scripts’ can detect when a song has changed, but this level of script cannot interact directly with widgets or plugins. So instead, you can get the Gig Script to send an OSC message that contains the selected song name. This OSC message is received back by GP, and detected within the ‘Global Rackspace Script’ (which CAN interact with plugins). The Global Rackspace Script then…