Trancit.
Zynewave@Trancit wrote:
But you should definetely consider mousewheel support as well for plugin windows…the mousewheel controls the window which has focus on…
I don’t know why some plugins support mouse wheel only in some hosts. As far as I have tested, I am not doing anything in Podium that should prevent a plugin editor from supporting mouse wheel.
TrancitI don´t have any knowledge of programming, but could it be, that plugins, that don´t have extra mousewheel support themselves, could benefit from this “hoovering over the dial to set mousewheel focus on that”????
And a second question:
Is it a big effort to implement midi controller mapping to Podium elements for hardware controller support???
I don´t think it´s necessary to support special controller directly in first place, but to map a midi CC to a fader or button is quite essential these days with so many brilliant controllers available 8)
Trancit
Trancit@Zynewave wrote:
I’m currently implementing support for controlling sliders/faders with mousewheel in the mixer.
One little thing more to this:
Normally (if I look at the most hosts), mousewheel alone changes bigger values, with shift or ctrl as modifiers smaller amounts…only one host makes it other way round and I have to say, this works much better:
Imho, if you want to make bigger changes to a fader or knob, it´s far easier to grab it by left clicking and move it…
So, why do we want the mousewheel: especially for smaller changes/fine tuning or slower changes it´s far easier to use the wheel and that´s the reason, why I personally find it much easier to have small increments without modifiers and bigger ones with…
On a volume fader, the mousewheel shouldn´t change the value more than 0.5db, perhaps only 0.33db…take a look at MU.LAB from Mu.Tools…mousewheel on the volume fader changes value in 0.25 increments…works pretty good!
Trancit
ninjawarrior@Zynewave wrote:
I don’t know why some plugins support mouse wheel only in some hosts. As far as I have tested, I am not doing anything in Podium that should prevent a plugin editor from supporting mouse wheel.
Maybe it is about this shortcut stealing.. Same thing than plugins steal space button. Podium lost keyboard / mouse tracking / support or something. Which is btw so annoying. I send you email about this, but i didn’t get any respond, so i guess you have no intention to fix this.. 👿
Zynewave@Trancit wrote:
I don´t have any knowledge of programming, but could it be, that plugins, that don´t have extra mousewheel support themselves, could benefit from this “hoovering over the dial to set mousewheel focus on that”????
The sentence you quoted, is that an option you have seen in another host?
Btw. I see you are using “hoover” in your posts. The correct spelling is “hover”. Hoover refers to a vacuum cleaner.
And a second question:
Is it a big effort to implement midi controller mapping to Podium elements for hardware controller support???
I don´t think it´s necessary to support special controller directly in first place, but to map a midi CC to a fader or button is quite essential these days with so many brilliant controllers available 8)
I’d estimate it would take me 1-2 weeks to implement. The problem is that there are many items on my todo list with a similar priority. I have to work on one feature at the time.
Zynewave@Trancit wrote:
Normally (if I look at the most hosts), mousewheel alone changes bigger values, with shift or ctrl as modifiers smaller amounts…only one host makes it other way round and I have to say, this works much better:
Imho, if you want to make bigger changes to a fader or knob, it´s far easier to grab it by left clicking and move it…
So, why do we want the mousewheel: especially for smaller changes/fine tuning or slower changes it´s far easier to use the wheel and that´s the reason, why I personally find it much easier to have small increments without modifiers and bigger ones with…
On a volume fader, the mousewheel shouldn´t change the value more than 0.5db, perhaps only 0.33db…take a look at MU.LAB from Mu.Tools…mousewheel on the volume fader changes value in 0.25 increments…works pretty good!
Try the latest 2.37 beta 4. So far I have made mousewheel adjust in 1 dB steps. Shift+wheel adjusts in 0.1 dB steps.
I can see your point about the reversal of the coarse/fine with the shift key, but I think there are arguments to keeping it the way it is. Using Shift for fine adjust is identical to the use of Shift for fine adjust when click+dragging a fader. Also, with the recent support for zooming mixer strips to 20%, it is convenient to use the mouse wheel for coarse adjust of pan and send, since the strip can be zoomed so small that you can’t reliably drag the knob.
Zynewave@ninjawarrior wrote:
@Zynewave wrote:
I don’t know why some plugins support mouse wheel only in some hosts. As far as I have tested, I am not doing anything in Podium that should prevent a plugin editor from supporting mouse wheel.
Maybe it is about this shortcut stealing.. Same thing than plugins steal space button. Podium lost keyboard / mouse tracking / support or something. Which is btw so annoying. I send you email about this, but i didn’t get any respond, so i guess you have no intention to fix this.. 👿
I read your email, and I still have it in my inbox. I do intend to do something about the plugin key stealing at some point. Please be patient. There are a lot of things on my todo list.
Trancit@Zynewave wrote:
@Trancit wrote:
I don´t have any knowledge of programming, but could it be, that plugins, that don´t have extra mousewheel support themselves, could benefit from this “hoovering over the dial to set mousewheel focus on that”????
The sentence you quoted, is that an option you have seen in another host?
Was just an idea… 🙁
Btw. I see you are using “hoover” in your posts. The correct spelling is “hover”. Hoover refers to a vacuum cleaner.
Thanks for correcting me…didn´t knew this before 😀
Trancit