06-14-2018, 10:38 AM | #1 |
Human being with feelings
Join Date: Feb 2018
Posts: 24
|
MIDI "device substring match" [skip] -QLab
Trying to get OSCii to talk to QLab via MIDI. I have OSC working but am spinning my wheels on defining the MIDI i/o in OSCii. What exactly is the "device substring match" and what does [skip] mean?
I see in the examples a simple string that says what kind of device the input is, but where do I find that for any given device? What happens when there are two or more of those devices in a MIDI network? beginner question, but one that has me stumped. Thanks, -Jim |
06-15-2018, 08:03 AM | #2 |
Human being with feelings
Join Date: Feb 2018
Posts: 24
|
So for anyone wondering the device substring is the port name as registered in the MIDI network. QLab uses "QLab" for it's MIDI In but needs to target an IAC bus for MIDI out to OSCii-bot. There seems to be a dependency on the startup order of the software for everyone to play nice. I had "QLab" as the match string but OSCii didn't see it until I launched MIDI Monitor and specifically spy'd on destinations. Will report back after thoroughly testing different start up orders.
Not yet sure how networks with multiple identical MIDI devices are handled. I/O definitions: Code:
@output OSCtoQLab OSC "localhost:53000" // QLab listens for OSC on this port @output MIDItoQLab MIDI "QLab" // QLab's MIDI IN port name @input OSCfromQLab OSC "localhost:53002" // Arbitrary port assigned in QLab @input MIDIfromQLab MIDI "Bus 1" // MIDI Cues in QLab set to target IAC Bus 1 // TODO: Change IAC Bus name in Audio MIDI Setup Last edited by James Slanger; 06-15-2018 at 08:18 AM. |
06-15-2018, 08:12 AM | #3 |
Human being with feelings
Join Date: Feb 2016
Posts: 189
|
Options->Preferences->Audio->Midi Devices in Reaper drop down menu will list the Midi devices you have connected.
Imagine there is a device here called [say] "ButtonDevice1" in this list You can then bind to this device for input as @input in MIDI "Button" The cryptic "substring devicename match" in the OSCII-bot code reference means "match a substring of the devicename" |
06-15-2018, 08:44 AM | #4 | |
Human being with feelings
Join Date: Feb 2018
Posts: 24
|
Quote:
EDIT: I've played around with startup order and everything seems stable. However, in Reaper QLab MIDI is listed as device by Snoize (MIDI Monitor publisher). Will try and remove that device and see if stability remains. Last edited by James Slanger; 06-15-2018 at 08:56 AM. |
|
06-16-2018, 03:37 AM | #5 |
Human being with feelings
Join Date: Feb 2016
Posts: 189
|
Skip explanation
The use of skip is (sort of) explained below in this fragment from sample_script.txt. It's a way of using different midi devices for the same OSCII-bot input. [skip] will let the compiler know this is intended rather than complain about none-unique devicenameforcode.
Code:
// @input lines: // usage: // @input devicenameforcode MIDI "substring match" [skip] // @input devicenameforcode OSC "*:9000" // @input devicenameforcode OSC "192.168.1.2:9000" // can use any number of inputs. devicenameforcode must be unique, if you specify multiple @input lines // with common devicenameforcode, it will use the first successful line and ignore subsequent lines with that name // you can use any number of devices, too // note: in OSCII-bot 0.4+, you can send OSC to an input device (which will return it to the last address from which // a message was received) |
Thread Tools | |
Display Modes | |
|
|