Q Light Controller+

Hello,

How to handle midi-in and midi-feedback is clear to me.
But I cannot find a way to send a midi-message from QLC-4 as is.
Can anybody shine some light for me?
Or is it not possible?

Thanks, Paul

I've tried that out recently in Linux and just confirmed that it works, using KMidimon connected to QLC+ output of Universe 1:

- start KMidimon (Drumstick MIDI Monitor)
- start QLC+
- find the KMidimon input line in I/O tab/Output column (it's stupidly called "input" here :/) and checkmark the button
- while the KMidiimon line still is selected, click the Toolbox icon to configure the MIDI plugin, and choose what type of message to use (CC, NoteOn/Off or ProgramChange)
- go to SimpleDesk, move a fader and see incoming messages being printed in KMidimon.

I can't tell for Win or Macs, never tried it there.

Interesting.

By midi message do you mean SysEx?

Is that question for me?

No, as I wrote I mean Continuous Controller/Note/Program Change messages, as offered in the plugin config dialog, these are Channel Voice messages.

Yestalgia wrote: ↑Wed Feb 15, 2023 10:04 pm Interesting.

By midi message do you mean SysEx?

SysEx is initialisation messages right? Ow boy my midi times are 40 years ago.

SysEx is a type of message to send non-realtime stuff to, or receive it from a synth/whatever MIDI device or program.

Mainly bulk dumps of memory contents (Banks/Presets/Programs/Patches whatever they are called) or to remote-control parameters you normally use the hardware controls for (to build editors/librarians). Manufacturer-dependent arbitrary messages that don't make much sense in QLC+, in my opinion.

edogawa wrote: ↑Thu Feb 16, 2023 11:12 am Manufacturer-dependent arbitrary messages that don't make much sense in QLC+, in my opinion.

(Off topic)
One of my goals this year is to try to build a knowledgebase of how different manufacturers implement "scribble strips"

I want to do this to enable VC widgets like faders to send their corresponding function to the scribble strips on a midi controller.

There are a bunch of manufacturers doing this already. I've already been able to make it work on a FaderPort16.

Thanks everybody for your info.
However, it’s is not clear to me how?
) where do I store a midi-out message?
) how do I send the message by using a function or button or script? Or what?

Maybe Massimo chime in?

Thanks, Paul

Why? once you have set it up as described, channels in this universe are mapped 1:1 to whatever MIDI message you selected...

Ch 1 <level> -> CC or Note or PC #0 <value>
Ch 2 <level> -> CC or Note or PC #1 <value>

Value will be level/2 because DMX has 8 bit, MIDI has 7 bit resolution.

I don't know what happens for channels above 127, as that is where the CC/Note/PC number range ends.

The problem here is that Paul (SPS) only poses a general question, he doesn't tell us what he wants to do with Midi from QLC.

He should realise that QLC basically was designed to send DMX information to fixtures.
QLC will accept Input From Input Devices (with MIDI devices amongst them) and can even provide Feedback to them.

If you want to use a MIDI device to be Output for QLC you basically have 2 directions to go:
1. treat it as being an input device (so define it in the Input/Output Section and check the FeedBack box).
Then on your Virtual Console create Some buttons (that work on Dummy Scenes ) select the Exterenal Input and then define the FeedBack Value you want to send.
This option is quite limited because the DMX values you provide will be divided by 2 to generate MIDI out of it.
This means you can only send Control Changes. Notes and program Changes are out of this range.
I guess you could also create sliders (that work on specific channels of a Dummy ficture), but i never Tried it.

2. treat it as a Fixture.
To be sure not to mess up with other fixtures in QLC it is best to create a seperate universe and only use it for this Fixture.
Now you need a fixture definition that will work on a Midi device. When i did my search on the available fixture defiInitions i only found one for a Novation LaunchPad.
As i needed it for an AKAI APC Mini i adapted it to work on my AKAi ()
It took me quite some time to get it working. The trick is to use Override Global Settings in the fixture Definition.
You need to use this option to make it work, but To be Honest i can't explain why (I guess because 180 degrees is half of 360 degrees, it will extend the range of MIDI values, that way
making values above 127 available).

Be aware that this fixture definition only works for NOTES. Furthermore It worked on my AKAI, which is on midi channel 1.
(no idea how to change the Midi Channel. It might even be that it sends on all 16 channels, meaning that it will interfere with your other MIDI devices, which could be solved by
adding an extra "midi interface" which doesn't have to be a fysical one if you use a MIDI over USB Interface. There is still a lot to figure out......).

If you create an extra fixture definition for channels 0 - 127, (128 generic dimmers might probably be sufficient) to send Control Changes and combine it with this AKAi ficture definition (for Notes an program Changes), you might get somewhere.



When i created this fixture definition i was at first proud of myself that i could get it working, but when i then found out that you cannot use a midi device for OUTPUT AND FEEDBACK at the same time i regretted having spent time on it (i didn't want to give up the feedback option for it).

Maybe this information will bring you closer to what you want to achieve.

I'd really appreciate if you would spell correctly and consistently fixture, not ficture, thanks.

Thanks everybody for your input.
Finally it came clear to me that it is deadsimple.
) Assign your midi device to an universe output. (I use Loopmidi to send values to my sound program Multiplay)
) DMX values of that univers will be send as midi (values 0-127 ).
) Using loopback can create all what you want!!

simple (and genius work from Massimo)!
Paul

Hey SPS sorry for disturbing but I am in the same problem you had. I hope you are interested to help me to do the same you did. Thanks for your time! best regards Emil

emilev wrote: ↑Wed Jul 05, 2023 6:25 pm Hey SPS sorry for disturbing but I am in the same problem you had. I hope you are interested to help me to do the same you did. Thanks for your time! best regards Emil

Hi Emil!

First what you need is a midi plugin for midi-output from qlc.
Since I use Multiplay as a cuesystem for music on the same laptop as qlc, I use Loopmidi as software midi interface.
In loopmidi I created a port (eg. qlc to mtp).
If you have done that and you start qlc, you will find your midiport in the IO tab.
Select a empty universe and select the midiport for output.
Now, create some dimmerchannels in that universe
Create a function for dimmer 1 with dimmer up
Create a button on virtual console with the function.
Thats it.
If you activate the button, the universe will send a midimessage : Channel 1, Note : 0, Value 127
If you de-activate the button, the universe will send a midimessage : Channel 1, Note : 0, Value 0
(Note 0 is for dimmer 1 as tecnically the universe starts with 0)
So, you can use up to 128 dimmers to generate 128 different midicommands.

Hope this helps.

Paul