Page 1 of 1
Virtual Console Fader Names feedback OSC
Posted: Wed Aug 01, 2018 2:24 pm
by Sqeegie
I'm using on Mac OS 4.11.2 and using Lemur 5.3.5 for the OSC interface. There is an option on Lemur to pull track names for DAW programs, either through midi or osc. But is there a way to pull fader names or values from the Virtual Console faders being used? If so, how does one do that? I'm not sure of the path to put in for it.
Re: Virtual Console Fader Names feedback OSC
Posted: Thu Aug 02, 2018 9:09 am
by GGGss
Sqeegie wrote: ↑Wed Aug 01, 2018 2:24 pm
an option on Lemur to pull track names
??? pull track names???
Sqeegie wrote: ↑Wed Aug 01, 2018 2:24 pm
But is there a way to pull fader names
??? Pull fader names ???
Since when can OSC send/receive ascii characters?
Re: Virtual Console Fader Names feedback OSC
Posted: Thu Aug 02, 2018 12:44 pm
by mcallegari
OSC data paths are arbitrary, so I have no idea how Lemur can do that unless it already knows how a DAW formats the OSC paths.
In any case there's no such thing in QLC+. OSC data paths are translated into unique "channel numbers" and used as triggers just like all the other plugins.
@GGGss yes, OSC can actually send/receive arbitrary ASCII strings. See specs:
http://opensoundcontrol.org/spec-1_0
Re: Virtual Console Fader Names feedback OSC
Posted: Thu Aug 02, 2018 1:45 pm
by Sqeegie
I figured that might be the case. In my particular set up, I have a main fader setup and was curious if in the Virtual Console I had a Fader Name of Red and lemur or touch osc could read the fader name and send the name back to the layout. Switch to a different page that the main fader had the label of Crazy. The same fader on the layout would read that name and change it as if it were a DAW. Thats all good. I figured I would ask. I'm trying to create a general purpose layout in lemur and touch osc and wondered if it could pull that. I appreciate the response.
Re: Virtual Console Fader Names feedback OSC
Posted: Thu Aug 02, 2018 7:00 pm
by janosvitok
The problem here is, that all plugins try to emulate plain DMX. In other words, OSC data is mangled in the plugin so that it can appear to the rest of QLC+ as much as possible as a set of 512 numbers from interval 0..255 (MIDI and OSC are a bit hacked so that there may be more than 512 numbers/channels).
The advantage is that this allows uniform handling of any protocol (DMX, artnet, OSC, MIDI,...) and allows using any input either as control source or as source of DMX data.
Therefore, to support sending names, either the protocol has to be extended or some clever hack must be devised.