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”????
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
But you should definetely consider mousewheel support as well for plugin windows…the mousewheel controls the window which has focus on…
Trancit
@Zynewave wrote:
@Trancit wrote:
do you know already something new about this mousewhell behaviour???
I got a reply from the Poise developer. He said he looked at the mouse-wheel behaviour a while back, but could not find an explanation to why it behaved differently in some hosts. He’s using a development framework that handles the mouse-wheel, so he is not directly coding the mouse-wheel support. I’ve looked at it from Podiums side, and I can’t see why it doesn’t respond to mouse-wheel messages.
I have to bring this up again…
I noticed by playing around a bit with a few hosts, that every host, that support e.g. Nexus by mousewheel has the ability to move knobs and faders by hoovering the mousepointer over it…as well as with any other plugin…
E.g.: FLStudio (best mousewheel support): Hoovering the mousepointer over a fader in the mixer and use mousewheel to move the fader, hoovering over a parameter or the browser in Nexus and scroll or move it by mousewheel…
Reaper: Mousewheel by hoovering works with Reaper internals but not with plugins that doesn´t support mousewheel by themselves (e.g. Nexus doesn´t work, but Sytrus)
In Podium. the mousewheel works with none of my plugins except Synth 1 and Wusikstation…
Perhaps would be a good idea to bring basic mousewheel support into Podium as the other hosts work, because for me it´s not even possible to move a mixerfader by anything else than clicking left hold and drag…no keyboard input … no mousewheel … nothing…sadly 🙂
Trancit
@Zynewave wrote:
Beta5:
Using the mixer zoom slider will lock the zoom on the focus track. To lock zoom on a specific track, hold Ctrl+Alt and use click+drag or the mouse wheel over the strips.
The slide tool can be used on the mixer strips. Hold Shift+Alt and click+drag, or hold Alt and use the mouse wheel.
Let me know if you still have issues with the mixer layout.
Can you explain this a little bit further???
I´ve two tracks in my start project and using crtl+alt +mousewheel as well as click n drag does the same as using the slider on the left…it just zooms in or out the two tracks (track 1 is selected)
What shall locking mean??? First I understood this as being able to zoom just the selected strip in or out, but it affects both of my tracks…
Shift+alt+click n drag turns my cursor into a hand and affect nothing…
Alt+ mousewheel does nothing…
Trancit
@Zynewave wrote:
@Trancit wrote:
After a closer look to the mixer, I have to say, you should definetely work on the Solo/Mute/Record buttons… 😀
Especially when resizing the mixer channels, they are far to big and “ugly”…
I think they are by far not so important to take so much space…
I think there are plenty of users that would say solo/mute/record are quite essential in a mixer. Making them smaller would go against the button size conventions I use throughout the Podium UI. I’ve tried my best to make them not look “ugly”. Do you have any suggestions to what should be changed?
It´s not the button itself, it´s more, that it stays at full size while everything gets smaller…and of course the buttons are essential in a mixerstrip, but they are not so important, that they take nearly the most space in a small mixer channel…
What looks ugly for me is, that when you zoom out of the mixer, the level meter and it´s fader get smaller and shorter, the channel strip gets smaller but the buttons stay the same and visually getting bigger and bigger in comparison to the rest the more you zoom out…
Trancit
After a closer look to the mixer, I have to say, you should definetely work on the Solo/Mute/Record buttons… 😀
Especially when resizing the mixer channels, they are far to big and “ugly”…
I think they are by far not so important to take so much space…
Did you change the colour of selected track in the new beta??? Especially the mixer channel this blue is so dense and bright, it´s hard to see any details anymore and this bright colour doesn´t fit the rest of the colour scheme…
Trancit
Yeah, that´s what I wanted to know…thx very much…
Trancit
And I am sorry, I have to go even one step further:
How to send the audio from different outputs of the same plugin into different groups but having one “Master” group???
What I mean:
A drum vsti with 8 stereo outs shall play:
OUT 1+2= Kick
OUT 3+4= Open HH
OUT 5+6= Closed HH
OUT 7+8= Claps
OUT 9+10= Snare
OUT 11+12= Crash
OUT 13+14 and 15+16= Percussions
All of the drumsounds shall “end” in a “master” drum bus, but inside this routing I need “sub” busses for the Hihats, Claps+ Snare and the percussions, so finally it should be routed like this:
Kick => Drum group
OHH + CHH => Hihats Group => Drum group
Claps + Snare => Snare group => Drum Group
Crash => Drum Group
Percussions=> Perc Group => Drum group
Drum Group => Master
Is this possible with a single Plugin like Kontakt or Battery using the multi outs (I know, how to set up the multichannels in Podium) or do I have to use multiple instances of the plugin?????
Trancit
OK, it seems, I am not clear enough here… 🙂
I don´t want to use Kore player, I want to use an multiout vsti like e.g. Battery for the drums…
I want it as well to be hosted in a group channel like Zynewave did in the video to use the child tracks for the midi data…
But I want additionally to the video use the multi outs (which are already defined in the device mapping) for routing the different drum sounds to additional Podium channels to be able to mix the individual drum sounds in Podium and not in the Plugin…
My question was, If the “Main plugin” is hosted by a group channel, is it possible to insert the other multi outs devices to other channels e.g.:
Track 1 is a group channel hosting Battery#1 Out 1+2 and it´s childs containing the midiclips triggering the drum sounds…
on Track 2 I insert Battery#1 Out 3+4…it´s getting red and an error popup is telling me:
“A library preset is already active on a previous track mapped to this plugin instance”
Is there any way to do this…?
Trancit
Another question:
Because the midi preview works so well, especially with in sync to the project, do you plan rex support with same preview features from the browser, that would be so cool and would bring Podium at the same level with Reaper in this point…
At which I have to say, you have implemented the named notes in editor, drum editor and now the midi preview so much better and smoother than they did… 😀
Trancit