Wich template would you like to be added?

ethnix73 · Unread post by **ethnix73** » 19 Nov 2009, 18:01

Olivier asked me to create a few template for the upcoming V5.

To be the most helpful with the communty, could tell me wich template would you like to be added?

woodslanding · Unread post by **woodslanding** » 20 Nov 2009, 04:01

What are the templates used for, besides the input and output context menus?? I'm still trying to get a handle on what they might be useful for--I didn't even discover them until a couple of days ago.....

The one thing would be buss send and receive for everything. But I think most terminals already have that.

ethnix73 · Unread post by **ethnix73** » 20 Nov 2009, 12:16

Yes woodslanding, Templates are used for the inputs and outputs context menu. As they're using the internal message language, they're quite powerfull...They can really speed up your patching because you can have some kind of "pre-made routine". For exemple, if you drag a cable from a midi in, you can create automatically a midi filter module wired to a piano roll module...

I will have a look to see wich terminal does not have bus send and receive templates, and add them.

amiga909 · Unread post by **amiga909** » 20 Nov 2009, 14:09

how about a 'replace with...'?
this wouldnt generate new module(s). instead the selected module is replaced by an equivalent module.

for example: module round

Code: Select all

fader
oscillopscope
data outlet
send to bus
----------------
cancel
---------------
replace with -> trunc&#40;x&#41;
                      abs&#40;x&#41;
                      1/X
                      exp&#40;x&#41;

loads of questions come to mind:
which replace-with proposals should be there (everything with same inlet/outlet structure, only from same module sub-tree)?
which replacements are really needed?
the most often i replace modules is when i try different vst-plugins. automatic replacing with re-wiring would require scanning the vst-directory, handling different inlet/outlet structures, etc.!

...not sure if its a good idea!

ethnix73 · Unread post by **ethnix73** » 20 Nov 2009, 18:37

Your suggestion might be difficult with IML amiga909. There isn't any way, i believe, to know wich inlet and outlet are wired, and to wich kind of module with the IML.

Your idea is more about adding more function to the IML...interesting but not my point here. I can only create new templates with the existing IML

woodslanding · Unread post by **woodslanding** » 26 Nov 2009, 08:37

Do you know where the template for drag-and-drop of a new vst module resides?? i'd like to edit that to wire up a bunch of send and receive busses, rather than the current set of buttons and ins and outs....

23fx23 · Unread post by **23fx23** » 26 Nov 2009, 20:21

lot's of modules thats outputs array only have "array output", would be nice to have also the "display array"?

ethnix73 · Unread post by **ethnix73** » 26 Nov 2009, 20:52

ok, 23fx23, i will add this template.

ethnix73 · Unread post by **ethnix73** » 26 Nov 2009, 20:53

I will have a look woodslanding concerning drag and drop for vst

23fx23 · Unread post by **23fx23** » 26 Nov 2009, 20:55

cooool, then i need also to try myself and learn how to, could really speed up patching

amiga909 · Unread post by **amiga909** » 27 Nov 2009, 09:01

what about..
- for any audio out: mixer (N in ->1)
- for any outlet: trace value

also it could be nice if different module types were grouped (if easily possible). for example param inlets
..
LFO
step
----
data inlet
get from bus
----
user cruve sequencer
----
cancel

ethnix73 · Unread post by **ethnix73** » 27 Nov 2009, 19:16

Ok, amiga, i will add the two templates...Don't know if we can group module. I will have a look...

Welcome to %s forums

Wich template would you like to be added?

Login • Register