Hello,
i have tried to control the next/prev page function with my BCF2000.
But it doesn't react when i presseing the buttons on the BCF2000.
Br Sven Meier
Switch to next or prev. page midi control dont work
-
Jano Svitok
Hi Sven,
I've written small tutorial for this, you can read it in the online help, section Tutorials, under name "Multipage frame tutorial". If there's anything not clear enough, just tell me and I'll try to explain.
THe tutorial is included since version 4.6.0. If you use older version, you can read it [here](https://rawgithub.com/mcallegari/qlcplu ... ipage.html) without screenshots, although I recommend to upgrade.
I've written small tutorial for this, you can read it in the online help, section Tutorials, under name "Multipage frame tutorial". If there's anything not clear enough, just tell me and I'll try to explain.
THe tutorial is included since version 4.6.0. If you use older version, you can read it [here](https://rawgithub.com/mcallegari/qlcplu ... ipage.html) without screenshots, although I recommend to upgrade.
-
Sven Meier
Okay the prev / next function now works 
Now i have tested the direct "set" funtion, the midi controller sends CC 65 1 eg. CC 65 2.
The input type is set to "Page Set", how can i connect these button with the frame ?
Now i have tested the direct "set" funtion, the midi controller sends CC 65 1 eg. CC 65 2.
The input type is set to "Page Set", how can i connect these button with the frame ?
-
Jano Svitok
The bad news is that PageSet is not finished yet. I finished it for myself in a hackish way and used it successfully at a gig, but it's not ready to publish. I'm going to finish it in few days hopefully, but some things are not clear yet.
The main problem is that MIDI operates in 0..127 range, and it is doubled in the MIDI plugin, because QLC+ internally works with 0..255 range (as DMX). Ideally, when you assign the page set to an encoder/slider, it should map the pages to the whole interval. However, the MIDI plugin doesn't know the page count, only frame does.
I see two ways out of this: either we say the max directly controllable pages is let's say 16, and the controller would divide the range in 16 intervals, or we find a way how a frame could tell MIDI plugin the page count. The latter is a bit more complicated, but also more user friendly, and would allow page prev/next buttons to wrap around (for 6 pages Prev from 1st page would go to 6th, and next from 6th to 1st).
The main problem is that MIDI operates in 0..127 range, and it is doubled in the MIDI plugin, because QLC+ internally works with 0..255 range (as DMX). Ideally, when you assign the page set to an encoder/slider, it should map the pages to the whole interval. However, the MIDI plugin doesn't know the page count, only frame does.
I see two ways out of this: either we say the max directly controllable pages is let's say 16, and the controller would divide the range in 16 intervals, or we find a way how a frame could tell MIDI plugin the page count. The latter is a bit more complicated, but also more user friendly, and would allow page prev/next buttons to wrap around (for 6 pages Prev from 1st page would go to 6th, and next from 6th to 1st).
-
Sven Meier
Okay, i think this is a great funktion
Maybe its possible to add a additional Setup page for the frame that contains a table. In the first column the Page that should be loaded and in the second the midi Signal for it.
I think its time for me to learn c++ so i could add some Features by my self
At the Moment i only can programm in avr-gcc, php , bash and Python
Maybe its possible to add a additional Setup page for the frame that contains a table. In the first column the Page that should be loaded and in the second the midi Signal for it.
I think its time for me to learn c++ so i could add some Features by my self
At the Moment i only can programm in avr-gcc, php , bash and Python
-
Sven Meier
I think the right way is move the dublication from the midi plugin to the widgets.
This will made further extensions easylier
This will made further extensions easylier
-
Joe
Jano,
I do not understand why it needs to be that complicated. If I have a row of buttons, why can't I set one to each page of the frame, and then every time the value is 127, that just triggers QLC to jump to that page, just like it would if I was triggering a function? What I'm doing is creating different shutter pages to turn on and off different groups of lights.
Joe
I do not understand why it needs to be that complicated. If I have a row of buttons, why can't I set one to each page of the frame, and then every time the value is 127, that just triggers QLC to jump to that page, just like it would if I was triggering a function? What I'm doing is creating different shutter pages to turn on and off different groups of lights.
Joe