LV1 Classic + DirectOut EXBOX.SG

[Thunbo]

Subject:

Missing Globcon control when using Exbox.SG with LV1 Classic.

Proposed solution:

You can’t open Globcon on LV1 Classic, because you can’t install it - or have it running alongside the eMotion LV1 Classic software. I’ve been thinking about some solutions I’d like to share:

1: Change the Exbox.SG to have IPv4 open. That way one can open the Globcon GUI via an external browser for remote control (like the EXBOX.MD).

2: Change so that one of the four network ports is a dedicated control port and the remaining three are SG ports.

3: Access via the LV1 system inventory page, on the gear wheel; e.g. About, System Info, Clock, EARS…

4: DirectOut USB.MADI. Connecting an external computer via usb to the DirectOut USB.MADI for control.

The inconvenient solution at the time of writing:

At first I was trying to Share the Exbox from LV1 Classic to a secondary networked computer with SoundGrid Studio installed. Then assigned it to the external computer inventory, assign it to the MIDI driver of that computer (by committing ‘Assign to midi driver’), and run Globcon on the external computer to configure the EXBOX.

But this is not an option.

The ‘Assign to midi driver’ function is not available on a Shared unit. Only on the Main-host machine.

So the only alternative I have found is to have a secondary networked computer as Main-host for the Exbox, and have the Globcon control - And from there ‘Share’ the Exbox to the LV1 Classic.. But this solution has a number of complications that are not convenient…

For example; this external computer must always be connected in order to pass audio from Exbox to LV1 - and if it fails, you lose the entire audio stream from the Exbox.

And that the Exbox now must be the entire system’s Clock Master; because both LV1 and SoundGrid Studio requires a Clock Master, and the Exbox is the only common device.

All these ‘problems’ simply just to gain access to the Exbox control panel.

Thoughts:

My setup consists of LV1 Classic at FOH and Exbox.SG for playback on stage.

Mac Mini A and B run Ableton, and via SoundGrid Driver to Exbox.SG (EARS), and from Exbox.SG to LV1 Classic input.

I really believe this can become an extremely cool backing track solution. But at this point in time, with this knowledge I have now; Exbox.SG is probably not the best backing track solution for LV1. Either Exbox.MD (EARS) > Madi > Exbox.SG > LV1, or DirectOut Maven with a SG.IO network module would be preferable.. Or simply a modular LV1 setup, with Globcon access in the background.

[TYG]

Hey,

So while I agree this way of doing things is pretty inconvinient, I do have a few suggestions to improve the workaround:

A. Instead of SoundGrid Studio, use LV1/SuperRack offline editor - it’s free and is constantly updated to match the infrastructure running on your LV1C. SoundGrid Studio hasn’t been updated for a few years and may bring some unexpected behaviors to the table.

B. You are able to select a common clock master that is not the Exbox.SG, even if it is not assigned in the inventory of your secondary computer. You should be able to do so from the ‘set master’ menu in one of your I/O slots. Essentially a SoundGrid device can be a common clock master for all hosts in the setup even if it’s not actually used by all hosts.

C. The thing about not having the 2nd computer connected sounds weird - the configuration in Globcon is ‘set and forget’ as far as I remember. Maybe this is affected by using SG Studio instead of SuperRack/LV1 on the 2nd computer.

D. If you select to ‘manage device’ in the secondary computer, then map it to the midi driver of that secondary computer, then manage device again in the LV1 Classic, the mapping should stay put, as far as I remember.

Hope this helps

[wavempr]

Thank you TYG & Thunbo. Because of you, my MD & SG setup was fixed using my old modular LV1 and shared to LV1-C.

My recommendation about this issue is to create a plugin of Globcon to control the SG device in the LV1-Classics. I think it’s the easiest way.

ED