New Tool (3.4) command_palette

[unless]

version 2.4.2

• made it so that show actions toggle when the thing is already visible and included the names in the hide actions label
• fixed a bug in one of the show actions

[dspasic (senseiprod)]

Hey, is there a way to see plugin type somehow au/vst/vst3 ? Thanks

[esaruoho]

@unless yeah it makes total sense to categorize them like VST: name VST3: name & AU: name. (oh and LADSPA, Native, DSSI…

[unless]

version 2.4.3

• shows the device type instead of an index for the DSP and plugin palettes

[dspasic (senseiprod)]

Thanks, looks way better now!

Can we have ability to press cmd+a to select all text in command pallete? ty

[unless]

Do you want this to be able to clear the input or you mean “all text” like “input and current list”, could you explain why do you need this?

[Jalex (J ∆ L E X || W Я O K)]

Yeah fast edit.

[dspasic (senseiprod)]

i meant functionality as in “select all” with cmd+a in the prompt (which i’ve typed previously) (as in cmd+a+backspace :D)

also i’m interested why it focuses ‘unload plugin’ when i type load plugin or to rephrase question: why prompt selects last/second action instead of first one? (new empty project, no plugin loaded. I’d expect this to happen if plugins is already on track)

i’d also like to see this implemented in Renoise core functionality. It’s very convenient and helpful

[unless]

The issue with cmd+a is that there is no notion of conventional selection (or cursor) in the palette, this would require other things and horizontal arrows are already used for history functionality so a selection would keep on behaving unexpectedly. It would make more sense to add just a separate way to clear the palette if anything, but I am unsure how often you actually want to delete the contents of the input, like usually you type in something, do the thing and the palette closes. I’m thinking of an option so that if the palette has input, escape would clear it first (and only close the palette on second press), would this be useful? How about cmd+backspace to clear the input?

---

The focus behaves this way because I haven’t implemented order sorting for the resulting matches (like rating what is a better match based on the text part), and the list selector tries to maintain position instead of resetting. Selecting the first could be similarly wrong here if the order of these two commands in the command table would be flipped. Currently it only prefers a match for the left “shortcode”, so if you just type “pl” you get the “load plugin” selected, the idea was that you’d use these shorthands for stuff and the search in names is just extra to find things you don’t know about yet. That said, I’ll look into improving the search.

@dspasic

I’d expect this to happen if plugins is already on track

I thought about making the entries be context aware like that but this would considerably complicate the tool and might hurt the experience in practice, for example in this case even if you have a plugin loaded, you might want to load another plugin instead of unload. So the better thing would be to more meaningfully rank the results based on your input, if you’ve typed “load p” it is safe to assume you do not want to unload a plugin, I think.

[dspasic (senseiprod)]

@unless

escape would clear it first (and only close the palette on second press), would this be useful?

this could be even nicer solution than i thought initially. Can we have this option so i can try it out for a while? Thanks

@unless

Currently it only prefers a match for the left “shortcode”, so if you just type “pl” you get the “load plugin” selected, the idea was that you’d use these shorthands for stuff and the search in names is just extra to find things you don’t know about yet. That said, I’ll look into improving the search.

thanks for explaining how it works. Now i can adapt to use it with less friction.

@unless

if you’ve typed “load p” it is safe to assume you do not want to unload a plugin, I think.

yeah, you are right. It was shallow idea from me, without too much planning

[unless]

version 2.4.4 - findings

• search results are better ordered by relevance as discussed above
• searching for characters like - and being able to input numbers as the search in the DSP device palette is fixed
• DSP devices are alphabetically sorted on open
• fixed the missing type hint characters for the selected command (like # > and =)
• fixed the search filtering in the device parameter palette
• added an option so that ESC will clear the search if there is any and exit the palette if it’s empty, this is on by default but can be toggled in the settings

[lucasobx (ᵈᵒˢ)]

I tweaked the ‘Renoise Simple MIDI File Support’ tool so it works with the command_palette

[esaruoho]

does this mean you incorporated it into commandpalette?

[unless]

Oh, cool!

Did you use the commented out code at the bottom of main.lua or inserted your code into the tool itself, or?

Being able to add commands from external tools is definitely on my todo list, but I want to refactor the tool in general and provide a clean API for others before commiting to this feature.

[esaruoho]

i would be very interested in adding some Paketti features to be available for Command Palette. If you ever get around to it, let me know and I’ll do some experiments.

[lucasobx (ᵈᵒˢ)]

I added the code directly into the tool and hardcoded the folder path in the script. It was just a quick test, there are still some things that would need tweaking, and the way the original script handles MIDI files still has a few issues that need fixing.

[GurtTractor]

Hello. When I try to type in text to search for a specific plugin in the Load Plugin part of this tool I get this error -

[unless]

version 2.4.5

• Fixing the above error, thanks for the report @GurtTractor !

[GurtTractor]

Yeah seems fixed now, thanks!

[GurtTractor]

Hello again, I’m getting this error when I try to use any of the “add pitch/volume/panning modulation” commands -