New Tool (3.0): Vsti From Menu

[fdsafewww]

Just installed that version with no error. I am on Windows 10.

[Ledger]

Good to hear!

thanks for letting me know

[Ledger]

v1.63

• fx search will load fx into the sampler now when the sampler and sampler devices are selected .

[Ledger]

@Skarin this version now supports VST3

Also any Mac/ Linux users let me know if any probs caused by the cross platform menu stuff that may re-appear

v1.64

• Added menus for VST3

• Menus are now properly sorted alphabetically + removed case sensitivity

[Skarin (Jon Skarin)]

Fantastic, can’t wait to try it

[Ledger]

v1.65

• Added an option in VST3 menus, when enabled only the plugs which are not doubled in the 2.4 menu are shown. i.e. unique VST3 plugs

[Ledger]

v1.68

• fixed potentially buggy behavior with “Only Show Unique VST3 Plugs” option

v1.67

• Added instruments to the doubled checklist

v1.66

To help keep a track of fx which have a VST2.4 and VST3 on your system:

• Added a menu to the renoise DSP fx loading list List Doubled Devices which will display all the VST2.4 which have the same short name as a VST3, so are likely doubled. You can confirm matches by doing a search for the individual VSTs in the renoise DSP loading list itself.

[Ledger]

v 1.7 On Tools Site

• added tool name to List Doubled Devices dialog to make it clear which tool it belongs to.

[Ledger]

v1.76

• If a plug is loaded from a search, the selected plug will now be remembered along with the search

• other small fixes

v 1.75

• Delete key now clears the whole search same as Ctrl + Backspace
  (the standard use for delete is as a forward delete but as there is no cursor in the search it can be used as a single key delete here)

• fixed a search problem to do with Lua Magic Characters left over in part of the search function:

  Scripters Note: 4th bool argument to string.find() ensures plain text searching, without Lua string patterns and magic characters.

  see http://lua-users.org/wiki/StringLibraryTutorial

  string.find(s, pattern [, index [, plain]])

v1.74

• Search is remembered when re-opening the tool if a plug was loaded from the last search

• fixed [LOAD] button that got broken 1.73

• fixed default state when a search is deleted with Backspace or Ctrl + Backspace

v1.73

• when lots of entries in results readout and using up/down arrows to scroll, the results readout will update to to the next ‘page’ so correct selection is always visible

v1.72

Some Improvements to the FX search dialog that will be added to the instrument search too. Just trying to make sure running smoothly first, so let me know if any probs:

The results box first displays the closest matches that start with the same string as your search. Plugs which have the string within their names start with a different letter are listed alphabeticaly after.

Shortcut is the same `VFM` Search And Load FX

• Added a readout box showing all plugs that match the search. Use arrows up and down to navigate through them and [LOAD] button/ Return on keyboard to load the selected as normal

• Made the search bar readout un-selectable to stop confusion as the search is active as soon as the plug is opened and has focus

[Ledger]

v1.77

• Added new upgraded search box for instruments now:

shortcut still `VFM` Search and Load VSTi

[Garf]

I think you should rename “Ed.” to “Auto open” because what does Ed. stand for?

It would be nice have it show the favorites on top of the list at first so you can quickly arrow down to your favorite plugin after invokation.

For the search VST Plugin can you create a “Make slot” checkbox beside “Ed.” so that it by default make a new empty slot automatically to put the instrument in?

This tool has become quite awesome!

[Ledger]

The Ed. stands for External Editor. This was just named as a shorthand for the API naming of the property but yes, could be a bit clearer, at least with a tooltip for explaination.

RE. the ‘Make Slot’, there was a button for this in the 1.7 and lower versions, that hilighted when you were going to overwrite an instrument, clicking would create a new slot. This will be added back fairly soon.

It’s getting to the point where I may need to add a separate options dialog, so adding stuff like favorites could make it in there too. There’s another couple of things that could maybe do with an option aswell.

In meanwhile:

v1.79

• Improved Page Up and Page Down Behavior a bit

v 1.78

• Adds support for Page Up and Page Down for browsing longer results lists

Note: you can use these or up down arrows before any search, to browse all plugs at once.

[Garf]

Just found a few quirks in the regular expression matching:

Searching for “kontakt” give two choices which appears fine as I for some reason have both VST2 and VST3 installed but both open the VST2 version of the plugin.
I noticed that when I right click on an instrument slot and “Load VST3…” then check the Only show unique VST3 plugins that Kontakt then disappear there, maybe this is somehow related?

Beginning a search with “a” shows “Analog Lab V” twice despite I only have the VST3 installed, as soon as I write “an” only one choice is shown. (I have Arturia Analog Lab V intro installed).

Regular expression matching is a gigantic headache for me so I wish you good luck if you try figure this out

[Ledger]

Thanks for reports,

@Garf

both open the VST2 version of the plugin

Yes, caught this one before, will probably be adding some pre/postfix when a plug us doubled, and then choosing the VST3 plug should load that correct one

@Garf

then check the Only show unique VST3 plugins that Kontakt then disappear there, maybe this is somehow related

This sounds like it’s working ok as that option filters anything already available as VST 2.4 in your plug folder. i.e. you only want to use the VST3 that are not available as 2.4 anymore. Some devs seem to like to force install VST3 on top of the 2.4 – bit of a mess being between the two standards.

@Garf

shows “Analog Lab V” twice

missed this but have managed to replicate. I suspect it has something to do with a string.sub that’s still in there which doesn’t allow for plain text operation and runs into Lua ‘Magic Characters’ again. Hopefully shouldn’t be too hard to fix if it is that

EDIT: think I found it, the search is matching the first A for the top entries (which always start with the search letter). There is a second match that looks in the rest of all the plug names. Just need to filter the already added ones.

@Garf

I wish you good luck if you try figure this out

Thanks! it’s a pain but will be good to have working properly!

[Ledger]

v 1.81

• fixed [Load] button that got broken

v 1.8

• Improved search to filter out doubled entries

• Added support for Home and End keys

• Added tooltip to “Ed” Checkbox

• Tool Now opens showing all available plugins rather than a blank results box

known issue labeling and loading of doubled plugs in different formats like VST2.4 vs VST3 still not supported, but this version could do with a bit of testing for the basics as I needed to re-structure a lot of stuff.

The new instrument slot button will still return later too.

---

////

All current updates are to the search boxes with these shortcuts

`VFM` Search and Load VSTi

`VFM` Search And Load FX

////

[Garf]

Nice! Not sure if Renoise is causing this as it just crashed prior to installing your tool but it crash when clicking Load!?

.\Search Instrument GUI.lua:630: variable ‘load_plug_from_short_name’ is not declared
stack traceback:
[C]: in function ‘_error’
[string “local mt = getmetatable(_G)…”]:29: in function <[string “local mt = getmetatable(_G)…”]:24>
.\Search Instrument GUI.lua:630: in function <.\Search Instrument GUI.lua:618>

[Ledger]

Thanks, I always seem to forget to test the load button as I’m usually using return for load.

It got broken as had to rescope everything in restructuring. Was just a prefix missing on the function there.

1.81 up in post above should work:

[Ledger]

v1.82

• search box should refresh last search state better now on re-opening

• removed references to old unecessary function that could fire an error

[Garf]

Great. I’ve bound SHIFT+’ to search instruments and CTRL+’ to search FX and it works so nice and quick.

I look forward to the make slot feature, hope you can make it automatically make a new slot, maybe only if the currently selected instrument slot isn’t empty?

@Ledger

Thanks, I always seem to forget to test the load button as I’m usually using return for load.

I don’t use the Load button either but you asked for a bit of testing and that was the least I could do

[Ledger]

@Garf

I don’t use the Load button either but you asked for a bit of testing and that was the least I could do

It’s appreciated, I guess someone may click it one day!

@Garf

hope you can make it automatically make a new slot, maybe only if the currently selected instrument slot isn’t empty?

Yes this shouldn’t be difficult to have as an option.

Also plan to add a random button/ shortcut to suggest a random plug from the results readout. Already got the main function done for that from Random Plug. So hopefully not to much drama to adapt it in.

The core functionality of the search seems to be more or less nailed down now at least. Just the VST3 thing to sort out and a couple of things for polish I want to try too.