OmniSource with Engine Lighting?

I’m testing OmniSource on a RANE SYSTEM ONE in my studio. Engine Lighting (EL) works well in standalone mode, and Serato DJ Pro (5.0 Beta 950) works well with SoundSwitch on my laptop. However, my working setup requires a Control One and manual switching between USB 1 (Engine) and USB 2 (Serato). With a SoundSwitch USB dongle, I haven’t managed to make lighting follow source changes.

I understand that djay Pro (5.6.9) is not yet supported by EL. However, I tested TIDAL through Engine and observed lighting that appeared to pulse in time with the music. Could similar beat-driven lighting work with djay Pro playing local tracks from a phone or computer, even without track-specific scripts? What technical limitation prevents this?

Most DJs will primarily use either Serato or Engine, but lighting continuity still matters when switching sources or handing over to another DJ—for example, someone bringing rekordbox-prepared tracks or using a streaming service.

If a club owns a PRIME 4 G2 with Auto Loops and Static Looks configured for its installed lighting, and uses a Control One as the lighting controller, similar to a Wolfmix, those controls should ideally remain available regardless of the music source. Track-specific scripts could depend on supported integrations, while Auto Loops remain beat-synced and Static Looks stay accessible across sources.

Seamless lighting integration would make OmniSource much more practical during live sets, especially in clubs with permanently installed lighting.

SoundSwitch already offers MIDI Sync In as a source. Could Engine Lighting also synchronise Auto Loops with the active OmniSource input, either directly or via MIDI Sync In?

Is automatic lighting switching between Engine and Serato currently possible? And once Serato support becomes available on the PRIME 4 G2, will its built-in DMX output support both Engine Lighting and laptop-based SoundSwitch, or will an external interface and manual switching still be required?

Hi,

as far as I understand it, Engine Lighting itself doesn’t really care where the audio source comes from.

When a track is loaded, Engine looks at the track’s metadata to see if there is a reference to a lighting script.

For example:

SOUNDSWITCH_ID : {0A3BC925-0946-46DA-B978-28E16A418F5C}

If such a reference exists, the script is loaded and runs time-synchronized with the track.

If there is no script reference, Engine Lighting can fall back to the beatgrid. The beatgrid should either be provided by OmniSource, or, for completely new tracks, Engine OS can analyse the track itself – which is also what happens with streaming services.

From that point on, the Auto Loops can run according to how they are configured.

The Control One is basically a MIDI controller specifically designed for SoundSwitch. It doesn’t actually generate the lighting effects itself. It provides the controls for SoundSwitch, including access to the Auto Loops and Static Looks. There is also some storage for Auto Loop settings, although that is unfortunately quite limited.

So I’m not quite sure what the actual problem is in your scenario.

My understanding would be that any audio source supported by OmniSource should also be usable by Engine Lighting, at least for beat-synced lighting such as Auto Loops. Track-specific scripts would of course depend on whether Engine can identify the corresponding track and its script.

Maybe I’m missing something about how OmniSource handles the external sources, but I don’t see an obvious technical reason why Engine Lighting would need to know whether the beat is coming from Engine, Serato, TIDAL, etc., as long as OmniSource provides a usable beatgrid.