New Tool (3.0): Vsti From Menu

nice idea!

thnx!

+ sorry for the lill offtopic feature request:

Maybe you can do something ‘similar’ in the automation editor, namely: right mouse click and then be able to choose: open vst gui?

When you’ve added a vst to a track and done some automation drawing, you always have to go to the track dsp tab to open de vst window, should also be possible imo in the automation editor.

EDIT:

am I right, that currently only a fixed nr of plugins will be shown? Only vsti starting with a nr or letter a are present.

thanks all for feedback and testing.

a new alpha 0.54 is up with the following:

Any testing from mac and linux users appreciated particularly!

http://www.renoise.c…ndpost&p=222461

All requests are welcomed and looked at :)

How many VSTis have you got :blink:. The latest 0.54 will now go up to 1000 from previous of 100.

this could increase of course if necessary…

1599 Drevil_million_dollars.jpg

This is brilliant! Thank you.

Cool!

[quote=“Ledger, post:6, topic:31023”]
How many VSTis have you got :blink:. The latest 0.54 will now go up to 1000 from previous of 100.

this could increase of course if necessary…

1599 Drevil_million_dollars.jpg

:) I’ve got thousands, redundant collector!

  • got an error:

Cool script. You are really kicking ass these days.

Mac AudioUnit ids look like this:

  
$ rprint(renoise.song().instruments[1].plugin_properties.available_plugins)  
  
[1] => Audio/Generators/AU/aumu:AlpF:LinP  
[2] => Audio/Generators/AU/aumu:AtFr:GOSW  
[3] => Audio/Generators/AU/aumu:aut1:Alfa  
  
[..snip...]  
  

When you load them up, and populate the menus, it looks like this:

1600 AudioUnits.png

You will have to strip out the colons, as that is Renoise’s menu convention. But also, the names are ugly. :( Using the API, I don’t see a way to query the name without loading the plugin.

A tip: Instead of for VSTs = 1,1000 do, why not?

  
local VSTs = 1  
while renoise.song().instruments[1].plugin_properties.available_plugins[VSTs] ~= false do  
 -- Your code  
 VSTs = VSTs + 1  
end  
  

Cheers.

The same on the mixer for native effects and vst effects would be amazing ;)

Brilliant script by the way, one of my favs so far

Cool. It is possible to add the option “Do not show hidden plug-ins”? Or show only the plugins from one (few?) groups?

Really nice idea, I’m gonna use this all the time.

could this be added to the tools page? I think it is mature enough

Thanks all for the testing and positive feedback!

Will try and fix for next update

I`ll take a look here also

Thanks this should sort Dr Jonas` “Billion VSTs” :)

Interesting, noted.

Will have to recheck the API for this but from memory I don`t think so.

After the billion VSTs bug is sorted I`ll throw it up there.

Cheers!

neat! ;]

and a silly request, it could be useful to some if there was option/feature to also show fx’s that would then get put on the corresponding buss

v0.55
Added: support for up to a billion VSTs and more for Jonas :)
fixed: mac AU menu mess (hopefully)

I take it you mean in the right-click menu of the fx lane?

Doesn’t work. Change:

  
string.gsub(plugins[VSTs].plug_name, ":", "")  
  

To:

  
plugins[VSTs].plug_name = string.gsub(plugins[VSTs].plug_name, ":", "")  
  

And the menus are fixed.

But, the plugins no longer load.

Cheers! Script installed nicely without throwing up an error notice :) . This auto-populating like in conner’s image is that his hack of the script or can I manage the list somehow?

hi, no i mean the same way as with the instruments but instead of showing only instruments it will also (optional) show fx’s. but thinking of it…, i like your idea better.

Is 0.56 any better? If it does work then VSTs and AU`s should be mixed together however.
If there are still troubles I will try and tidy + comment the script more thoroughly and maybe you could give me a hand with an update to keep the macs happy?

New Tool (3.0): Vsti From Menu

Conners image was showing a bug, there is no user way of managing the script like this at the moment.

I may see what I can do when the bugs are ironed out.

No.

Check your PMs.

Thanks

Am I right to conclude every time you start up Renoise, this script collects all vsti entries all over again? There should be a way to store this info somewhere, like it is done in the cache.