feature that i badly want for all U-He plugins
-
- KVRian
- 737 posts since 20 Sep, 2006
when im using a u-he plugin like diva or bazille etc and i click on the plugin in FL i want to be able to edit the sound in the plugin AND STILL be able to hit the space bar and have fruity loops play. As it stands now all U-He plugins i have take control of the space bar and im not able to play it. I have to click out of the plugin and hit space (to get FL to play) or i have to click the play button. Really annoying and time wasting. I would LOVE IT if this was fixed. Seeing at the space bar doesnt do anything unless im typing in a preset name i think this would hopefully be an easy fix. Let me know Urs...thanks.
-
- KVRian
- 574 posts since 20 Aug, 2013
That's not a u-he problem, but one of the generic kind.
FL Studio "wraps" plugins inside a separate process, which is like opening two unrelated applications.
The upside is that it'll only bring the wrapper process down if a plugin crashes, which is why FL Studio is liable to have several "plugin crashed" dialog boxes open in the background when exiting the main program, but is less likely to completely crash itself if a plugin misbehaves.
The downside is that focus is "stolen". If you open Notepad and Word side by side, the keys you send to Notepad won't do anything in Word - and vice versa, if you switch the focused application. It's the same with bit bridges and wrappers.
Unfortunately, there's not really anything we can do against that. I assume (but wouldn't know for sure) that the "Don't allow keyboard focus" option will simply forward keystrokes recorded in the wrapped process to the main FL Studio process, which would be an internal and very welcome workaround inside FL Studio itself and probably the easiest way of solving this issue.
FL Studio "wraps" plugins inside a separate process, which is like opening two unrelated applications.
The upside is that it'll only bring the wrapper process down if a plugin crashes, which is why FL Studio is liable to have several "plugin crashed" dialog boxes open in the background when exiting the main program, but is less likely to completely crash itself if a plugin misbehaves.
The downside is that focus is "stolen". If you open Notepad and Word side by side, the keys you send to Notepad won't do anything in Word - and vice versa, if you switch the focused application. It's the same with bit bridges and wrappers.
Unfortunately, there's not really anything we can do against that. I assume (but wouldn't know for sure) that the "Don't allow keyboard focus" option will simply forward keystrokes recorded in the wrapped process to the main FL Studio process, which would be an internal and very welcome workaround inside FL Studio itself and probably the easiest way of solving this issue.
-
- KVRAF
- 24455 posts since 7 Jan, 2009 from Croatia
If that didn't fix it, then nothing else will. This is a host-side thing, not plugin-side, AFAIK.
-
- KVRAF
- 26995 posts since 3 Feb, 2005 from in the wilds
Use another hostddeez wrote:unfortunately that idea didnt fix the issue...any other ideas?
or... wouldn't a midi controller with transport still work when spacebar doesn't?
-
- KVRAF
- 24455 posts since 7 Jan, 2009 from Croatia
It would.pdxindy wrote:or... wouldn't a midi controller with transport still work when spacebar doesn't?
-
- KVRian
- 703 posts since 28 Oct, 2014
well this is an issue, thats been annoying me for a very long time. in fact i didnt update zebra in over a year or two, simply because of this problem.
so here's how it went for me:
zebra used to work fine. i could load it into fl studio, and use the mouse wheel to scroll-change the synth knobs, and could also push the spacebar to start and stop the song.
then steinberg released an updated version of the vst structure, or platform whatever its called.i think it went from vst 2.3 to 2.4. then when urs updated zebra with that new updated vst structure, the synth was suddenly a nightmare for me to use. spacebar no longer worked in fl, unless i stopped the synth getting keyboard focus. but when i did that, i was no longer able to use the mouse wheel to scroll/change the synth knobs.
and thats the annoying situation im stuck with atm.
plenty of other synths using the new vst structure work fine, but dim pro is another one that got updated when the new vst thing came out, and that also behaves like zebra, so there is something in common with dim pro and zebra, that other synths dont have a problem with.
so here's how it went for me:
zebra used to work fine. i could load it into fl studio, and use the mouse wheel to scroll-change the synth knobs, and could also push the spacebar to start and stop the song.
then steinberg released an updated version of the vst structure, or platform whatever its called.i think it went from vst 2.3 to 2.4. then when urs updated zebra with that new updated vst structure, the synth was suddenly a nightmare for me to use. spacebar no longer worked in fl, unless i stopped the synth getting keyboard focus. but when i did that, i was no longer able to use the mouse wheel to scroll/change the synth knobs.
and thats the annoying situation im stuck with atm.
plenty of other synths using the new vst structure work fine, but dim pro is another one that got updated when the new vst thing came out, and that also behaves like zebra, so there is something in common with dim pro and zebra, that other synths dont have a problem with.
Last edited by _al_ on Sat Nov 08, 2014 8:34 am, edited 2 times in total.
-
- KVRian
- 703 posts since 28 Oct, 2014
_al_ wrote:ok, good to know, thanks! hopefully its fixed on my comp too.Chapelle wrote:The mousewheel issue when the keyboard focus option is checked occurred here, too._al_ wrote:spacebar no longer worked in fl, unless i stopped the synth getting keyboard focus. but when i did that, i was no longer able to use the mouse wheel to scroll/change the synth knobs.
and thats the annoying situation im stuck with atm.
It does work fine with the latest rev. of Zebra2 here, though (rev2709 from this thread: http://www.kvraudio.com/forum/viewtopic ... 1&t=419732)
is that link a beta version? if so, im gonna have to wait until its on the uhe site. a bit too risky for me, even though i know uhe beta's are stable.