1

ShowCue OSC not triggering snapshot XR18

Hi all

Really enjoying getting to grips with ShowCue. I have no experience and even less understanding of OSC commands, and Grega has provided me with great reference documents. I have configured Showcue and it detects my behringer XR18 mixer- so the IP address and output port is correct.

Screenshot 2024-01-11 at 10.32.38.png

Screenshot 2024-01-11 at 10.46.22.png

I can now trigger ShowCue to change a channel fader using:

/ch/01/mix/fader, 0.5 as an OSC Output Command - Play Cue

In my Behringer XR18 I have a series of audio snapshots saved for our drama production with different settings for different microphones switched on and off throughout the production.

Screenshot 2024-01-11 at 10.36.57.png

No matter what, I cannot get Showcue to trigger the snapshot command. This is clearly me missing something.

I have tried cueing the first snapshot (named 000-All-Mute) like this:

/-snap/000-All-Mute/Load

and

/-snap/load/000-All-Mute

The documentation from Behringer assumes a degree in computing science:

Screenshot 2024-01-11 at 10.51.56.png

Can anyone enlighten me what I am doing wrong please? Once I learn the correct way for one, I should be fine!

Is there anything else I need to be aware of as well, or do I simply programme each of my snapshots as a series of cues, one after the other?

Thanks all.

Follow

5 replies

Votes Newest Oldest
PH

SUCCESS!

I have finally found out how to do this. I have aged visibly, but the taste of success is so sweet.

The correct syntax is as follows. 

Example: I have a snapshot stored in memory number 5.

In the OSC output command- Play Cue, write:

/-snap/load, 5

Two things to note.

1. There is a space betwee the comma and the cue number

2. Cue numbers less than 10 are single digit. So cue 1, not 01.

Hopefully this will help others in a similar siutation. Thank you Grega for putting me near the right path. Behringer's support leaves a lot to be desired at times, although the products are superb.

Comment

Thank you for sharing this info.

it is strange to me that you have to use space after comma. So without space it does not work?

PH

Hi Grega

Thank you for your superb contiunued support. Your suggestion of the comma DOES work when I program a new cue eg Mute Main LR as:

/lr/mix/on, 0

BUT I am still not able to cue a stored snapshot. I have tried the three OSC Output Commands below with no success:

/-snapstore/01/scope, 0

/snap/01/load/01, 0

/-snap/01/scope, 1

I have posted on the Behringer Community as well to see if anyone has successfully cue a snapshot. I assume the individual application should not matter as they are all implementing the same Behringer OSC commands. Behringer documentation is known to be out of the reach to the common user, and they do tend to assume a lot of prior knowledge.

Regards

Paul

Comment

Try with comma at the end: /-snap/01/scope, or even /-snap/01/scope,1. 

Comment
PH

Hi Grega

Thanks for the suggestion. No luck I'm afraid. 

I tried:

snapstore/01/scope (I realise you have to call the memory slot, not the name of the snapshot)

and 

snap/01/load

with no luck.

The single channel fader command

/ch/01/mix/fader, 0.5

works - so the connection is good (or there is the correct information in that command).

However, I tried another command 

/lr/mix/on

to mute the master faders and that did not work either. 

I am clearly missing something...

Screenshot 2024-01-14 at 23.11.55.png

Comment

Try /-snap/01/scope to load snapshot at index 01. Doc say this command recalls (loads from memory) snapshot. Same goes for other snapshots … just change 01 to 03, 05, 10, etc.

Comment
Reply