Opening/Closing documents from AMX…

[da...@davo.net.au]

Greetings…

I’m part of a team installing into a training facility. The goal is to simulate various environments… there’s a range of physical effects such as rain, smoke, wind, stars etc. that are operated by an AMX controller driving a mix of DMX and DynaLite fixtures. QLab is providing soundscapes and effects to a powerful 10.1 surround system.

The AMX controller is effectively the boss, and sends OSC commands to QLab. Am I correct in understanding there is no facility to open/close workspaces from OSC? The plan is to have a workspace for each simulated environment scenario for ease of editing. As a result there would be maybe 20 - 30 open files. Is there going to be any issue with memory management by having so many files open?

Or is there a way to open/close workspaces remotely… could we maybe use OSC to trigger a Script cue and do it that way?

Suggestions? Thanks in advance…

Cheers

Davo

[micpool]

Osculator will trigger AppleScripts from OSC.

Or

If you used different cue lists instead of different workspaces then you would only have 1 workspace open and could do all the switching within the workspace. You can still develop the system in separate workspaces if that is easier  and then just cut and paste the cues from each list into one master list.

Mic

[da...@davo.net.au]

Mic

Osculator will trigger AppleScripts from OSC.

Ahhh... will check that out.

 

Or

If you used different cue lists instead of different workspaces then you would only have 1 workspace open and could do all the switching within the workspace. You can still develop the system in separate workspaces if that is easier  and then just cut and paste the cues from each list into one master list.

I can see how that would work... however because each scenario conforms to a fairly standard format e.g. Initial State, Catalyst Event, Aftermath, Finish, Spot FX Specials etc., it makes it easier in AMX-land if each workspace can use the same Cue Number mapping for its GUI interface trigger buttons. It's not always going to be a standard 'go' type of show where you travel from A to B to C...

... but it's worth looking into how that might work.

Thanks!

Davo

[micpool]

If AMX can send OSC wildcards you can use 

/cue/*01/start  to qLab

which would start cue 01 101 201 etc.

You can then use any offset you like and just arm/disarm the cue list you want to use

number the cue lists

0000

1000

2000

etc 

and send

/cue/*000/armed 0 to disarm all

and then arm the one you want with

/cue/2000/armed 1

This would then give you an infinite number of template cellists that could fire off the same cue numbers from AMX

Mic

[da...@davo.net.au]

Hi Mic

If AMX can send OSC wildcards... 

You can then use any offset you like and just arm/disarm the cue list you want to use

 This would then give you an infinite number of template cellists that could fire off the same cue numbers from AMX

Great idea. Thanks. Will investigate further. Did a quick test with OSCulator launching Applescripts and that also shows promise. Will put both methods through their paces and report back. Thanks again!

Cheers

Davo