UHBIK Bug saving patches in Reaper 3.301
-
- KVRAF
- 1548 posts since 12 Jan, 2010 from Copenhagen
I'm experiencing a bug Saving UHBIK patches in Reaper 3.301 on Mac OSX 10.5.8 where when saving patches I can't imput text in the text fields, strangely I'm able to drag text from one text field to another and then save the patch.. This problem occurs with UHBIK but not with Vember audios Surge 1.53, also the bug is not present in Numerology 2.2, there I can save and input text normally in UHBIK's patch save windows..
Regards
Wade
Regards
Wade
waves break, but somehow it all makes sense.
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
Wasn't Reaper one of the hosts that have an option to "pass key strokes through to plugins"?
-
- KVRist
- 299 posts since 15 Apr, 2004
I'd guess that the bug is in Reaper.
It has been a common problem(in many hosts, not only Reaper).
The Host grabs all keys pressed and try to interpret them as short keys for controlling the daw instead of forwarding them to the plugin in focus.
Another example is where you want to enter a name for a patch that included a space. But since Space was set to play/pause it only started the playback insted.

edit: Doh, too slow... as usual...
It has been a common problem(in many hosts, not only Reaper).
The Host grabs all keys pressed and try to interpret them as short keys for controlling the daw instead of forwarding them to the plugin in focus.
Another example is where you want to enter a name for a patch that included a space. But since Space was set to play/pause it only started the playback insted.
edit: Doh, too slow... as usual...
-
- KVRAF
- Topic Starter
- 1548 posts since 12 Jan, 2010 from Copenhagen
Hello Urs
I've checked VST preferences and can't find any feature that seems to relate to the passing of keystrokes to VST.
When patch saving works in Numerology it's likely a problem with Reaper.
One thing more though I've recently updated the firmware in my bluetooth mac aluminum keyboard.
Regards
Wade
I've checked VST preferences and can't find any feature that seems to relate to the passing of keystrokes to VST.
When patch saving works in Numerology it's likely a problem with Reaper.
One thing more though I've recently updated the firmware in my bluetooth mac aluminum keyboard.
Regards
Wade
waves break, but somehow it all makes sense.
-
- KVRist
- 49 posts since 5 Jan, 2004
In fact there is such a setting (though I don't think you should need to select it) but it is rather hidden away, so I'm not surprised you had trouble finding it: in the Track Control Panel, click FX and then in the Track FX pop-up window >FX>Send all keyboard input to plug-inTwoToneshuzz wrote:I've checked VST preferences and can't find any feature that seems to relate to the passing of keystrokes to VST.
However, as I said, I doubt that's the problem, as typing in and saving patch names here from Uhbik in Reaper 3.301 works fine WITHOUT "Send all keyboard to plug-in" selected. In fact, I don't really want this selected, as then NOTHING passes through to Reaper when the plug-in is in focus (transport commands included).
I'm wondering if this might be related to an earlier problem of saving patch names in Reaper from Zebra, which was simply due to certain plug-in preferences not being selected in Reaper (although these should be selected by default, they're easy enough to change by accident). This one can easily be solved by making sure that "Save full VST state" and "Save as Bank" are both selected (Under Options>Preferences>VST).
EDIT: Aaargh, I just noticed that you're on a mac (I'm on Windows here), so I suggest that, if the above doesn't work for you, you post your issue on the Reaper OSX forum in case it's a mac-specific problem.
-
- KVRAF
- Topic Starter
- 1548 posts since 12 Jan, 2010 from Copenhagen
Thanks "Badge" for the tips on fixing this Bug which lies likely in Reaper... I will look into it further and report back when I've found a solution.. Oh yes I've already posted the bug on the Reaper forum, so let's see what they come up with.. Otherwise I think Cubase is starting to look pretty good to me again.. I used Cubase way back when and their midi implimentaion and score fascilities were quite slick even then.. But I do love how slim a program Reaper is!!
Regards
Wade
Regards
Wade
waves break, but somehow it all makes sense.
-
- KVRist
- 49 posts since 5 Jan, 2004
You're welcomeTwoToneshuzz wrote:Thanks "Badge" for the tips...
Well, if my suggestions fix it for you then it's not a Reaper bug, it just means you've somehow changed the default settings (as I did, by accident)TwoToneshuzz wrote:...on fixing this Bug which lies likely in Reaper...
On occasion when encountering a problem, that thought has briefly crossed my mind, but then I've reported the problem and it's usually been fixed by the Reaper devs within a couple of days (and on one occasion, within a couple of hours!). Then I remember that Cubase takes an age to load, Steinberg's support is rubbish, that I'll be charged through the nose for upgrades that offer new features (most of which I don't need) but probably won't fix the bugs I needed fixing, that even the smallest update only happens once in a blue moon, that I would have to pay for a new dongle (which is there for Steinberg's benefit, not mine) if mine ever breaks etc., etc. Then I think.... Nah, I'll stick with Reaper!TwoToneshuzz wrote:Otherwise I think Cubase is starting to look pretty good to me again..
-
- KVRAF
- Topic Starter
- 1548 posts since 12 Jan, 2010 from Copenhagen
Hi Badge! I Know that Steinberg can be slow to fix bugs and are not that responsive to there userbase.. I'm interested in Cubase mainly for it's midi editors and score edit.. But you right it's a big program that can be slow to load, and expenive to boot.
I have checked my preferences as you suggested and have not changed them from their defalts, but thanks for the tips anyway..
Regards
Wade
I have checked my preferences as you suggested and have not changed them from their defalts, but thanks for the tips anyway..
Regards
Wade
waves break, but somehow it all makes sense.
