Thanks for the amazing tool, this makes using actions and FX quick and snappy!
I noticed that if "Virtual MIDI keyboard: Send all input to VKB" is enabled, you cannot type certain characters into the palette since they get intercepted by the Virtual MIDI keyboard. Is there any workaround for this? I use that option since I don't have physical MIDI keys and use my keyboard as a substitute.
Hi! I think it is possible: the extension could temporarily turn "Send all input to VKB" off when it is opened, then restore it after the window closes. I might look into this at some point, but this is a low priority project right now
Until then the best I can think of is to set up a keyboard shortcut that is never used by the VKB (one of the F-keys for example) to easily toggle the "Send all input to VKB" action.
Awesome tool to have come across, something I have been needing for a while!
Feedback: When searching, I feel the results could be more refined. Perhaps putting "quotes" around the search term (similar to Google search) will search for that specific word/phrase. Or perhaps just have that do it by default? Right now it seems to have a few strange result possibilities as showcased below:
1. (red box) while it found a relevant action, instead of using the "t" in "take" it uses the "t" in "to" and then the "ake" in "take" which is a tad silly
2. (cyan box) this is the bigger issue imo, these search results don't have any relevance to the input and is pulling the results from individual letters in several very separate words
This isn't a dire issue or anything, a minor annoyance at best, and just something that would make the searching/results even better. Absolutely loving having this tool in my arsenal now and will definitely be getting plenty of usage out of it. Thanks a ton for your hard work on it, can't wait to see what else you work on!
I think the quote thing can totally work. Like search for the exact pattern if it has quotes, do the current fuzzy matching if it doesn’t.
I get why you would find the red and cyan matches less intuitive but that’s just how fuzzy matching works: it looks at characters, not words. But it might be possible to tweak it so matches like your cyan example get ranked lower (or excluded)
Hi! there is no way to manually adjust scaling for the extension. It will set its size based on screen size and system settings like display scale factor. Does it appear too small on your screen?
Hi, yeah I have a 4k screen, so the text feels like maybe a 6 or 8 point fontsize, very tiny. I can still get commands though cuz the filter is really awesome, just really have to squint. Thanks for the reply, I do love the plugin, and Emergence as well!
I did some testing (also have a 4k screen) but have not been able to reproduce the issue so far. Maybe you can give me some more details about your system? Knowing these details would be helpful for further testing
are you using the latest version of the extension (1.0.2)?
Which reaper version are you using?
What is your operating system?
If windows, which hidpi mode do you use? (in Preferences -> General -> Advanced System/UI tweaks -> HiDPI mode)
I believe is latest version, just downloded last week. OS is Windows 10, display resolution is 3840x2160, I have 3 screens. Display Scale Factor is 1.2. HiDPI modes is on MultiMonitorAware the recommended setting
Hi! the extension was released before reaper had clap support so it does not know about clap plugins yet. I have plans for adding this in the next update
The extension only checks those .ini files and does not scan the file system to check if the plugin file actually exists so I guess that explains why some deleted plugins might stick around until the plugin list is re-scanned.
Can you tell me which clap plugins you tried to load? and in which reaper version? mac or windows?
I tried a couple in recent reaper versions (6.75-77) including chowtapemodel, fluctus by nakst, some fullbucket stuff and these seem to work fine so I’m not sure whats going wrong there.
← Return to extension
Comments
Log in with itch.io to leave a comment.
Thanks for the amazing tool, this makes using actions and FX quick and snappy!
I noticed that if "Virtual MIDI keyboard: Send all input to VKB" is enabled, you cannot type certain characters into the palette since they get intercepted by the Virtual MIDI keyboard. Is there any workaround for this? I use that option since I don't have physical MIDI keys and use my keyboard as a substitute.
Hi! I think it is possible: the extension could temporarily turn "Send all input to VKB" off when it is opened, then restore it after the window closes. I might look into this at some point, but this is a low priority project right now
Until then the best I can think of is to set up a keyboard shortcut that is never used by the VKB (one of the F-keys for example) to easily toggle the "Send all input to VKB" action.
Awesome tool to have come across, something I have been needing for a while!
Feedback:
When searching, I feel the results could be more refined. Perhaps putting "quotes" around the search term (similar to Google search) will search for that specific word/phrase. Or perhaps just have that do it by default? Right now it seems to have a few strange result possibilities as showcased below:
1. (red box) while it found a relevant action, instead of using the "t" in "take" it uses the "t" in "to" and then the "ake" in "take" which is a tad silly
2. (cyan box) this is the bigger issue imo, these search results don't have any relevance to the input and is pulling the results from individual letters in several very separate words
This isn't a dire issue or anything, a minor annoyance at best, and just something that would make the searching/results even better. Absolutely loving having this tool in my arsenal now and will definitely be getting plenty of usage out of it. Thanks a ton for your hard work on it, can't wait to see what else you work on!
Hey! Thanks for the detailed feedback
I think the quote thing can totally work. Like search for the exact pattern if it has quotes, do the current fuzzy matching if it doesn’t.
I get why you would find the red and cyan matches less intuitive but that’s just how fuzzy matching works: it looks at characters, not words. But it might be possible to tweak it so matches like your cyan example get ranked lower (or excluded)
Just found this, super cool extension! Wondering if there's a way to scale the UI for 4k screens?
Hi! there is no way to manually adjust scaling for the extension. It will set its size based on screen size and system settings like display scale factor. Does it appear too small on your screen?
Hi, yeah I have a 4k screen, so the text feels like maybe a 6 or 8 point fontsize, very tiny. I can still get commands though cuz the filter is really awesome, just really have to squint. Thanks for the reply, I do love the plugin, and Emergence as well!
I did some testing (also have a 4k screen) but have not been able to reproduce the issue so far. Maybe you can give me some more details about your system? Knowing these details would be helpful for further testing
Thanks
I believe is latest version, just downloded last week. OS is Windows 10, display resolution is 3840x2160, I have 3 screens. Display Scale Factor is 1.2. HiDPI modes is on MultiMonitorAware the recommended setting
I am also having this issue.
It's a really cool extension and I'd love to be able to use it but the text isn't legible for me.
Hate to be that guy, but..
.. when typing `?` to enter the `Help` menu,
.. and in the first sentence under the heading `Usage`,
.. the word `deisred` should be spelled `desired`.
Just trying to help.. and thx for this superb Reaper extension! :)
I will fix that in the next update Thanks for the feedback!
Hello!
This is a great extension!
One small issue I've noticed: CLAP plugins do not get indexed for 'f'.
Hi! the extension was released before reaper had clap support so it does not know about clap plugins yet. I have plans for adding this in the next update
Hey! clap is now supported in the new 1.0.2 version!
Thank you very much!
Small issue: Previously installed CLAPs that have since been deleted are still in the index.
After purging deleted plugins from reaper-clap-*.ini and reaper-vstplugins64.ini, I now have a very clean plugin list for the extension😀
Sadly, I just noticed that trying to add CLAP plugins just adds a blank track😕
VST2 and 3 works fine.
Thanks for the feedback!
The extension only checks those .ini files and does not scan the file system to check if the plugin file actually exists so I guess that explains why some deleted plugins might stick around until the plugin list is re-scanned.
Can you tell me which clap plugins you tried to load? and in which reaper version? mac or windows? I tried a couple in recent reaper versions (6.75-77) including chowtapemodel, fluctus by nakst, some fullbucket stuff and these seem to work fine so I’m not sure whats going wrong there.
Hi!
I'm on Reaper x64 6.75 / Windows 10 x64.
EDIT: Figured it out!
All my CLAPs have custom names. Custom names work fine for VST but not for CLAP (reaper-clap-rename-*.ini)
Removing the custom name lets me add CLAPs just fine!
Neat! Will try this out.