Better support for VSTs not found

[woodslanding]

Since we know every vst will have:

Audio ins and outs
Midi ins and outs
Parameters and Param Names in and out

etc.

Can we have a 'not found' vst that shows meaningful connections for ins an outs?

I do a lot of work on wkps on my laptop, which does not have most of my vsts installed. It would be nice to be able to wire to a 'ghost vst' which will be correctly recalled when I move the patch back to my other computer...... I realize wiring to specific param nums is impractical (some of my vsts have upwards of 5k parameters) but at least audio, midi, and params arrays could work.....

This would also be helpful for addons, etc.... Maybe it could be an actual 'Simplest Possible Vst' that is included in the build, and automatically substituted if the real vst is not available....

For that matter, I suppose it could even have 9999 parameters-- and a gui with a textfield for param number, and a knob for value......

[gurulogic]

Good suggestion! +1

[sm_jamieson]

Very good idea.

[oli_lab]

+1

[x.iso]

+1

[senso]

humm...the problem is that in the general case vst's can have 0,1,2,16 audio in or out.
and it seems to be too complex for what it does.
you can use a simple volume module or create a fake vst with a script, then just replace it with a drop?

[woodslanding]

But any time you open a patch, can't HH determine which ins and outputs were originally cabled to on the vst?

... if the idea is just to have a meaningful view of existing cabling.

But yeah, maybe not worth the trouble.