mcallegari wrote: ↑Mon Sep 02, 2019 2:13 pm
In my view, this feature should be always active and there should be no need to map nothing to anything. So your dialog to map inputs to the scene editor makes it only an additional usability burden to the users.
The only thing that I see missing right now is "signal tags". For example, I need a way to understand from an input profile which button is "next page" or "previous page". This can be trivially solved during input profile editing. (reviewing them is also trivial since they are only 28)
Faders, instead, should be automatically mapped, based on ascending channel number.
* some people dont want to use this feature and it can be confusing for people wo just upgrade. so it needs an enable/disable switch.
* editing the input profiles as well would give you just more code for review. i can add support for that but that needs also additions to the input-profile-editor and so on.
* the same is with automatic assign faders to channels. for example the profile "Akai-APCMini.qxi" has 9 sliders which one should i use. the "Behringer-BCR2000.qxi" has none but it knobs that you can use. what wit a mix of knobs and faders? my midimix (as seen on the picture) has many knobs and buttons and faders. how to map these automatic?
mcallegari wrote: ↑Mon Sep 02, 2019 2:13 pm
- what about LED bars with 50 channels? Is this features helpful or not?
- what about crossing channels among fixtures? e.g. a fixture with 11 channels and an input device with 8 faders. First 8 channels will be selected. Hit "next" and then what? 3 + 5 channels or 3 only and then at the next "next" other 8 channels will be selected?
As i wrote i created channel-banks. bank 1 has channel1-8, bank 2 has channel 9-16, bank 3 has channel 17-24 and so on. currently i can use 64 channels. switching channel banks this way is the standard way for working with a DAW (for what most of the MIDI-controllers are made for)
mcallegari wrote: ↑Mon Sep 02, 2019 2:13 pm
- how about feedbacks for motorized faders?
in my code is already feedback for buttons implemented. adding feedback for faders should be no problem.
mcallegari wrote: ↑Mon Sep 02, 2019 2:13 pm
- how about controlling other features of the software? v5 has quick tools (dimmer/pan/tilt/colors/macros/etc) I'd like to control those too. Basically every button/fader of the UI should be controlled via this -always active- feature.
i wrote this piece of code for version 4. here most features are controlled by simple faders. implementing presets for version 5 is a diferent work.
mcallegari wrote: ↑Mon Sep 02, 2019 2:13 pm
- how about multi screen where editing and virtual console are open at the same time? Will they both respond to input devices signals or only the active window will? Confusing?
one of the first things i added was the call "if(m_doc->mode() == Doc::Operate) return;" in sceneeditor.cpp:1721 to only allowing hardware based editing when you are not in the live mode.
mcallegari wrote: ↑Mon Sep 02, 2019 2:13 pm
- does it make sense to implement is also in v4? (double effort)
it is implemented in the v4 becouse this is the current working version and i wanted this feature for me.
i know these things are not easy but if we dont start we cannot finish. i will do my best to help you and this is not just dropping a few lines of code o you.
-Chris
