Page 1 of 1

midi channel issue

Posted: Thu Sep 20, 2018 7:22 pm
by richbass
PC running win10
QLC+ 4.11.2
running midiox v7.0.2.372 to analyse the midi messages coming in to the pc

using roland um-one usb midi cable mk2 connecting to Boss es5 switcher pedal

3 banks of 5 on the es5 sending the following midi data to qlc+

bank 1 is all on midi channel 1
sending Program achange 0 on pedal 1
PC 1 on pedal to 2
PC 2 on pedal 3
PC 3 on pedal 4
PC 4 on pedal 5

Bank 2 is all on midi channel 2 and sends the same program change data

Bank 3 is midi channel 3, same pc data

I’ve confirmed using midiox that the data being received at the pc is the same as I’ve configured on the es5

On input/output screen, selecting the um-one midi input device... changing the midi channel acts as a filter, only allowing through data from the selected midi channel. Working as expected.

I created a profile for the es5 and under channels clicked the auto-learn wand. Only the correct midi channel was ‘heard’, and the correct PC data was entered, but regardless of the midi channel used the pc data always uses midi channel one in the profile editor.

e.g. Midi channel 3 is used by the es5
midi channel 3 is selected for the um-one in the ‘configure midi plugin’ window
during autolearn for the es5 ‘input profile editor’ all pc data is assigned to midi channel 1

In far fewer words...
‘configure midi plugin’ filters so that qlc+ only hears the channel you want it to, but ‘input profile editor’ (or some other process) shifts all channels to midi channel 1

Re: midi channel issue

Posted: Thu Sep 20, 2018 8:51 pm
by siegmund
Maybe this is just some misunderstanding. I guess you configured MIDI input in universe 1? Then the input selection widget will tell you that the values are coming from universe 1. Note that universe does not correspond to MIDI channel, since you already figured out you can select a specific MIDI channel on each universe.
Anyway, if auto-learn is working and the buttons trigger as desired - why bother?

Re: midi channel issue

Posted: Fri Sep 21, 2018 11:54 am
by richbass
At present I have found a work around for this, you’re absolutely right, but if I expand to more than one midi controller (possible)...

I am currently using universe 1, and only universe 1.

The issue is not related (I don’t think) to which universe is being used.

The issue I think will arise when more than one midi controller is used on different midi channels. If some part of the software is adjusting the midi channel such that the profile editor things all inputs are on channel 1 then there will be erroneous operation

Example:
You have two midi controllers each on a seperate midi channel (1 & 2), each triggering a different group of fixtures. They are sending the same program change messages, but because they are on different channels it shouldn’t matter. But if some part of the software makes the profile editor think everything is on midi channel 1, now both controllers appear to be sending the same messages on the same midi channel. Problem time.

Re: midi channel issue

Posted: Sun Sep 23, 2018 9:36 am
by edogawa
Just my few cents:

I am regularly using up to three Korg NanoKontrol2, and eventually also a M-Audio Axiom 61 or a Behringer BCF2000 as input controllers, as I often need quick and direct access to many dimmer channels and parameters of intelligent lights in rehearsal situations theater. I never care about adjusting MIDI channels.
Over USB they all appear as individual MIDI ports, and as only one controller is allowed per universe, I connect them to different universes in QLC+. So they always are distinguishable when auto-assigning faders/knobs/buttons...