Hi All,
I've got a problem. I have a multipage solo frame that I have assigned MIDI keys too, and next prev page buttons. This all works in itself, but the problem is, when it is on anything but page 1, all midi buttons (even the ones outside of that frame) stop working. Ideas?
No MIDI buttons work unless a solo frame is on page 1.
-
Joe
Argh. When a that solo frame is set to a certain page, if i try and assign a midi shortcut anywhere else in the virtual console it will add (Page 4) for example to the end. Is there anything I can do or is this a bug?
-
Jano Svitok
Hi,
when you switch page on MIDI controller, the MIDI events have assigned page number as well.
This must be reflected in your buttons' external input setting (e.g. it should say "Button 1 (page 3)").
If that doesn't help to you, please post your workspace, and I'll check it.
when you switch page on MIDI controller, the MIDI events have assigned page number as well.
This must be reflected in your buttons' external input setting (e.g. it should say "Button 1 (page 3)").
If that doesn't help to you, please post your workspace, and I'll check it.
-
Jano Svitok
It is by design... now. I guess it may make sense to ignore the page part for widgets that are not part of a multipage frame.
-
Joe
Jano,
Thanks for the reply. I do not think this approach makes sense. Surely page assignments should only matter for that page? I am trying to create multiple pages for all the different combinations of lights and shutter combinations I have, So i can use the same keys to control different groups. However I always want to be able to use my sliders and say flash buttons for my other fixtures (blinders etc).
Thanks for the reply. I do not think this approach makes sense. Surely page assignments should only matter for that page? I am trying to create multiple pages for all the different combinations of lights and shutter combinations I have, So i can use the same keys to control different groups. However I always want to be able to use my sliders and say flash buttons for my other fixtures (blinders etc).
-
Joe
btw Jano, Can you think of any workarounds? The only one I thought of was putting the entire workspace inside a multipage frame, but seems like a lot of effort..
Joe
Joe
-
Massimo Callegari
Hi, I would like say my opinion about this.
The thing is, who is to be multipage ? The frame or the controller ?
When I implemented it, I had in mind the goal of allowing every external controller to become multipage. This is a pro when you have for example the Korg nanoKontrol, but as you noticed, it might be tricky when you mix things up.
When you press a button to change a page of a frame, how can the controller know to whom it is sending MIDI data ?
Or for example when you have several multipage frames with different number of pages. It gets messy.
The controller, in my opinion, should stay dumb.
A workaround I can think of, is a multipage frame with the same widgets copied in all the pages. So regardless the page you are, you will always have access to some "global" functions.
The thing is, who is to be multipage ? The frame or the controller ?
When I implemented it, I had in mind the goal of allowing every external controller to become multipage. This is a pro when you have for example the Korg nanoKontrol, but as you noticed, it might be tricky when you mix things up.
When you press a button to change a page of a frame, how can the controller know to whom it is sending MIDI data ?
Or for example when you have several multipage frames with different number of pages. It gets messy.
The controller, in my opinion, should stay dumb.
A workaround I can think of, is a multipage frame with the same widgets copied in all the pages. So regardless the page you are, you will always have access to some "global" functions.
-
Joe
Massimo,
The problem is is that I only need to change page for one of the solo frames. I don't really get why changing the page for one individual frame should affect the rest of the Virtual Console. I'm using a multipage soloframe to use store all shutter presets for different fixtures groups (So I have Moving Heads Left & Right, Scanners Left & Right, Moonflowers left & right, scanners + moving heads left & right, etc etc, in pretty much every combination you could imagine). Rather than having to assingn a key for every different shutter combination (It would be really hard to operate and I wouldn't have enough keys), I am trying to use a multipage soloframe to delegate some keys on the keyboard. If you'd like to understanding better what I'm doing, I will send you my QLC+
workspace.
Joe
The problem is is that I only need to change page for one of the solo frames. I don't really get why changing the page for one individual frame should affect the rest of the Virtual Console. I'm using a multipage soloframe to use store all shutter presets for different fixtures groups (So I have Moving Heads Left & Right, Scanners Left & Right, Moonflowers left & right, scanners + moving heads left & right, etc etc, in pretty much every combination you could imagine). Rather than having to assingn a key for every different shutter combination (It would be really hard to operate and I wouldn't have enough keys), I am trying to use a multipage soloframe to delegate some keys on the keyboard. If you'd like to understanding better what I'm doing, I will send you my QLC+
workspace.
Joe
-
Ulf
Hi,
I "suffered" the same last night.
I would agree with Joe that pagination should work on the frame it is assigned to (which is probably what you expect from the UI as a user). Then, in my case with a BCF2000 for example, I have only pages for the sliders which is enough for me at this point. If I need pages for the buttons or encoders as well, I will place them into an appropriate frame.
But, anyhow, great work on qlc+, folks! Thank you for that.
Best regards,
Ulf
I "suffered" the same last night.
I would agree with Joe that pagination should work on the frame it is assigned to (which is probably what you expect from the UI as a user). Then, in my case with a BCF2000 for example, I have only pages for the sliders which is enough for me at this point. If I need pages for the buttons or encoders as well, I will place them into an appropriate frame.
But, anyhow, great work on qlc+, folks! Thank you for that.
Best regards,
Ulf
-
Joe
I can see how that would be frustrating Ulf. For example, you might have a page full of sliders, but then want to control another parameter globally using one of the BCF2000's rotary encoders.