Spent many an hour on this (mostly getting muse3 to compile and run and JACK playing ball) but at least now I can send decent midi into QLC
First the problem:
I still dont see how I can fade scenes in and out using midi.... easily
Yes I can trigger different scenes by assigning a specific note to each scene.
OR put scenes in a cue list and increment them sequentially with note events (but this is hard to program for fast changing scenes, you can get out of sync and it makes it hard to debug/ find where it fell off the rails. I found it was not consistent. Some times it would run fine other times it would miss increments.) It also means the fade in out times are set in QLC and not dependant on the note length. Change the midi tempo and its all wrong.
What might be nice, is the ability to select a cue number dependant on a control midi value. At least that way the sequence is unimportant and any mistakes or misses are repaired on the next event.
Caveat: For a simple 4 or so, slow type scene changes in a song the cue list idea is fine. But in My current case I have 100 scene changes in the first 20 bars of music;( ie pretty much scene change with each note.
Perfect world would be a midi note, say C4 to turn on a scene and then a midi control event(pitch or vol etc) to control the fade in out...but thats not how midi works?
Control events are associated to the instrument(or midi channel) I would thus need a midi ch per scene. I'd run out of ch pretty quickly. EDIT-and as we will discover has other problems
Hmm ok what else can we do
Code: Select all
[b]The only way i've gotten around this so far is to [/b]
Assign a button per note and thus per scene.[i] Edit-Assign a slider per note per scene.[/i]
Place buttons inside a frame. Set buttons to toggle(here is our problem)..the note off event does not turn off our button/scene,[i]Edit so it has to be a slider[/i]
Place a slider attached to midi control event (such as breath or pitch wheel) inside frame. Set as submaster.In your midi sequencer(time track whatever) I set the resolution(step value per bar) to 64 or higher to get smooth fades. Create a note event, then draw in a 'control' envelope.
Problem: When the note finishes, the button is in toggle mode and does not turn off. If placed in a solo frame the next event will deselect it...but if the same scene is used directly after itself it toggles off. Not what we want, perhaps the midi note off event is not recognised in button mode? I would have anticipated that the button would go on with note on and off with note off event. I manually changed it to a slider. Note on takes on a slider value of 160 and note off 0, it is now recognised ! (set the velocity in sequencer to 127 and we get our 255)
The note on event turns on the scene to full intensity but its overridden by the sub master so we can fade in and out nicely
This works, gives us a midi note to select a QLC scene and a master fader which acts to fade the scenes in or out.
Problem:
With a 100 scenes im fast running out of notes to associate with scenes. Im also running out of screen space to display all those sliders.
The solution is:
I think. To have a midi controller value of 0-127 to choose a cue list, a 2nd midi controller value of 0-127 to pick one of 0-127 cues within a cue list and attach the sub master fader as above to control the intensity of that current cue. But I am beyond myself in complexity and have no idea how or even if this can be done?
I could also of course be way off course and thinking this all wrong?
image attached screenshot of desktop for what its worth. Over simplified the fixtures and such to reduce problems.
Only a couple of sliders shown as I started to realise while this works, its not a practical solution.