Audio levels midi controls

[Olivier Goliard]

Hi there ! 

It should be good to have a native midi mapping for audio levels (cues output) as the midi for lights, because sometimes a bit of "live" mixing with real faders could be good.

Any solutions for this ?

The OSC Cue/n/level command has a strange delay behavior...

Thanks a lot !

[micpool]

I think the main problem is that the lighting dashboard actually represents the current output levels of all the instruments in a QLab lighting patch, whereas there may be many level sliders in many audio cues controlling what is being heard.

It's possible to use /cue/selected/ within an OSC message to change level of the selected cue.

The 'strange delay' is usually only because the updating of the slider display is a much lower priority than actually changing the level. Can you hear a delay or is it just the slider that is slow to respond?

Mic

[Olivier Goliard]

I don't hear any delay, it's just the slider response that is strange, in the setup I tried, with a nanokontrol and osculator, the Qlab cue slider respond only if I stop the controller slider movement... so a smooth fade is impossible.

We had a "bump" solution with network oscillator cues triggered, but with implement +2 (or any value) dB each time we trig the osc cue, but this is just good to set the volume in a rehersal situation. and mixing with this means a trig trig trig button as an old school arcade game !!

The midi slider easy setup for controlling live cue levels is the only thing that make us using ableton live instead of Qlab for mixing during a show.

I'm working on a theater small show where i need to mix 8 stereo audio cues "live" to have a random interesting result, and in this situation Qlab is still limited.

For now I must use Audinate DVS with a CL5 to send 16 tracks on different desk faders for mixing levels, but some venues don't have Dante. So a 2tracks output with a good midi sliders control in Qlab should be great !

Please escuse my bad english, I hope you understand something ! (My bad, I'm french)...

Thank you.

[micpool]

I'm obviously still missing something here...

My understanding is you have 8 audio cues, and you want to map the master slider of each cue to a different MIDI controller.

If QLab were to have that functionality built in you would need a separate MIDI map for every cue to be able to do that.  Because QLab doesn't have that capability, you have sensibly opted to use OSCULATOR to convert incoming MIDI cc messages to outgoing OSC messages sent to QLab port 53000

This works well, except there is a delay on the slider levels updating.

If you have 8 cues running you would only be able to see the sliders for 1 cue at a time, and  your MIDI cc faders indicate the level of all cues anyway. If you are in show mode you can't see any sliders, so the  visual slider update delay won't be a problem 

I have attached an OSCULATOR workspace which uses MIDI cc1-8 to control the levels in any cue labelled x.y  where y is the point number of the cue to be controlled.

e.g MIDI cc 4 would control  the master slider of cues 1.4,  22.4, 999.4 etc.

There is also a QLab bundle with 2 group cues. Q1 has 8 child cues with spoken numbers 1 to 8, and Q2 has 8 choral aahs on different notes.

Using a MIDI controller the response seems immediate, continuous and  reasonably smooth.

Doesn't this achieve everything you need?

Mic

[Olivier Goliard]

Look like you don't miss anything here !

Your totally right, I was trying this in the middle of another show, so in a "visual" mode, assuming audio signal was corresponding to slider movement on screen !

My bad... I's definitively bad idea to make sound with the eyes !!

So your answer is still accurate and interesting in many ways to me, now I know how to assign different cues on a single midi slider, and it's great stuff !

Thank's a lot.