midi out control
midi out control
Hey claude,
I start to learn to use lxconsole, i would like use with lx a usb/midi controller (bheringer BCF-2000), this controller is motorised.
I nead midi out control,
what it si possible?
Thank you
Timothé
I start to learn to use lxconsole, i would like use with lx a usb/midi controller (bheringer BCF-2000), this controller is motorised.
I nead midi out control,
what it si possible?
Thank you
Timothé
I try to be comprehensible, it's hard (i wish i was born in an english country ). When you're using a midi controler motorised and Qlab with lxconsol, it could be nice the midi controler can listen lx.
Exemple: I have a fader in my midi controler who control a sub in lx, and this same sub can be activate by Qlab. If i send a midi message with Qlab, asking to put the sub @ 50, my fader in my midi controler will stay @ 0. I can't use it because if i touch it, the sub will jump to 0. So, the point is, if i have a sub control by a midi controler, and if i use it with another source (Qlab, Live…) the fader may follow the sub.
Hope it help
Exemple: I have a fader in my midi controler who control a sub in lx, and this same sub can be activate by Qlab. If i send a midi message with Qlab, asking to put the sub @ 50, my fader in my midi controler will stay @ 0. I can't use it because if i touch it, the sub will jump to 0. So, the point is, if i have a sub control by a midi controler, and if i use it with another source (Qlab, Live…) the fader may follow the sub.
Hope it help
So, you have set up a MIDI action to control a sub, presumably in response to a control change message. What you would like to have happen is for LXConsole to send out that same control change message when it is received?
Does this happen on the same or a different MIDI channel?
What prevents a feedback loop?
Does this happen on the same or a different MIDI channel?
What prevents a feedback loop?
The latest build of LXConsole 3.0.1 (6405) has added MIDI out for sub-masters.
Here's how it works: MIDI/Show Control Out must be enabled.
In the file's Setup->MIDI there must be an action defined that links the MIDI message to the sub-master using "SUB-n".
When the sub's level is changed, a MIDI message--either a note on or control change--will be sent with the value or velocity corresponding to the level of the sub-master.
Example:
An action in the table is defined as trigger = 130 and Action Command = SUB-1.
With External->MIDI/Show Control Out enabled, changing the level of sub-master 1 will send a control change 2 message with a value (0-127) that corresponds to the submaster's level (0-100%).
It does not matter if the sub-master's level is changed by the command line and the scroll wheel or MIDI input or OSC input. The output will follow the level of the sub master.
This will be sent to the MIDI channel defined in the preferences. If it is necessary to have a separate channel defined for this output, please let me know as soon as possible.
Here's how it works: MIDI/Show Control Out must be enabled.
In the file's Setup->MIDI there must be an action defined that links the MIDI message to the sub-master using "SUB-n".
When the sub's level is changed, a MIDI message--either a note on or control change--will be sent with the value or velocity corresponding to the level of the sub-master.
Example:
An action in the table is defined as trigger = 130 and Action Command = SUB-1.
With External->MIDI/Show Control Out enabled, changing the level of sub-master 1 will send a control change 2 message with a value (0-127) that corresponds to the submaster's level (0-100%).
It does not matter if the sub-master's level is changed by the command line and the scroll wheel or MIDI input or OSC input. The output will follow the level of the sub master.
This will be sent to the MIDI channel defined in the preferences. If it is necessary to have a separate channel defined for this output, please let me know as soon as possible.
-
- Posts: 211
- Joined: Sat Jun 01, 2013 8:23 am
- Location: Adelaide, Australia
I second this, but...
... would it be possible to get that for actual channels? as opposed to just submasters? Whether with touchOSC or BCF2000, I would love the motorised faders simply to (be able to) follow the channels; Does not have to be MIDI based, could be just OSC, but I guess while you implement one, implementing the other might not be hard ... for OSC and MIDI, it could be set in the same way as the current Submaster functionality, i.e. whatever you set in the OSC/MIDI input / action table could be what is used as address to output it (to the selected MIDI out/OSC out).
Cheers,
Freddy
Freddy
-
- Posts: 211
- Joined: Sat Jun 01, 2013 8:23 am
- Location: Adelaide, Australia
*bump* ;)
... hey Claude, just wondering -
is this somewhere up there in the future a possibility? i.e. being able to create OSC/MIDI response per channel to be sent out by LXConsole whenever the values change (i.e. when a cue runs,..)?
Or is there a good reason why this is limited to submasters at the moment?
Cheers,
Freddy
is this somewhere up there in the future a possibility? i.e. being able to create OSC/MIDI response per channel to be sent out by LXConsole whenever the values change (i.e. when a cue runs,..)?
Or is there a good reason why this is limited to submasters at the moment?
Cheers,
Freddy
Cheers,
Freddy
Freddy
This discussion should probably take place in a new thread. It is possible to do MIDI output for a single channel but it is expensive in terms of processing. To work as you imagine, it has to update very quickly ( < 40ms to not slow down the output). Its not something that's easy and is going to be in the next build tomorrow.
This appears to not be as costly in processing time (at least for a few channels) as it seemed in might. 3.1.4. (65A10), the latest build, allows channel output via MIDI and OSC, provided, the appropriate action is defined in the Setup window.
Please, do not reply to this thread, which seems to have run its original course. Please start a new thread to discuss any issues arising from this addition to OSC/MIDI output.
Please, do not reply to this thread, which seems to have run its original course. Please start a new thread to discuss any issues arising from this addition to OSC/MIDI output.