Idea for a new plugin - make mono synths poly

[safeaim]

Heh.. you can set up for example 6-12 instances of a mono synth in FL Studio, and then assign them under a Layer-"plugin", and then controll them all at the same time and get a polysynth-effect..And incl. you could assign one note per. instance.. Too bad for you then Borogove

[Shifrin]

NicFit posted an example EnergyXT .ext file with a midi-plugin (I think either his own or one of Niall's) and 16 instances of Triangle II to make a rather mad 16 voice version of it

Couldn't find the thread in the XT forum tho.

Shif.

[Galleoneer]

Bad idea - people use multiple copies of the synth with different patches in each copy all the time. Hopefully anyone who develops a wrapper like this will have it identify itself clearly to the synths it hosts, so if the synth chooses to not work in that context, it can do so.

technically, should be no problem. but I am still unsure if I should make this thing.

another hint:

store a static pointer table with the addresses of the running plugin instances of your plugs (works fine in phrasemaster). then you can check out wich program is loaded on each instance.

seems to be lots of monosynths and good ones too so I shall correct my statement that they are only two. Nobody knows the whole market.

-s

[duncanparsons]

There is an inherent problem tho', with having multiple versions loaded..
Part of the joy of a mono-synth is how the portamento works. If you have 6 loaded up and the incoming MIDI is multiplxed to the synths, the glissandi would be allover the shop. And whatabout the envelope triggers? In most decent poly synths you can add notes into an existing envelope, trigger a new envelope for the whole sound, or each note has it's own envelopes - you would miss out on this whole aspect.

OTW, I think it is a reasonable idea as ideas go, but it doesn't stand the test in real world thinking. Those who have wired up such system will probably discovered this (using non-"Cubase-Sucks" hosts, of course!).

Don't worry, Mr 'gove, you may remain mimsy..

DSP

[Galleoneer]

...

I dont think that this is an argument against.

1. You can always switch of glide.

2. And if not this could be rather new and interesting to have multiple gliding voices in a "synth".

3. Makes room for experimentation.

Also the envelope could be interesting.

And I also assume I could hack it in some weeks assembled from the code of the phrasemaster. If you have the host its so easy.

The question is:

Are there enough people needing this tool ?
Would I economicaly harm developers who are making one voice freeware and poly payware ? I dont want to be the bad boy for my lifetime ! You see

[Borogove]

store a static pointer table with the addresses of the running plugin instances of your plugs (works fine in phrasemaster). then you can check out wich program is loaded on each instance.

Of course, thinking about it some more, I would have no philosophical problem with someone putting 4 instances of a demo mono version set to the same program into a project and sequencing them separately.

So at that point, I've gone about 80% of the way down the staircase that I've built on the slippery slope, so I might as well go the rest of the way. No further objection to mono-poly wrappers, here.

[Sascha Franck]

Wouldn't intelligent voice dividing be the major problem here?
I know that Logic's transformers can split a signal based on voicings (lowest signal to lowest cable etc...), but it's only working so-so-ish.

Whenever I need a polyphonic version of a monophonic VSTi I simply sample it - oh yes, I'm losing a lot of realtime tweakability with that, but Kontakt actually isn't all that bad in terms of tweaking/mangling samples (in fact, it's one of the masters in that area).

Also, I still think this would blow up many CPUs - good sounding filters still cause quite some CPU useage, and while having one of them on each voice, I could imagine CPU performance to go all through the roof with 5-6 part voicings using a pad-alike patches with long release times.

[Galleoneer]

Whenever I need a polyphonic version of a monophonic VSTi I simply sample it - oh yes, I'm losing a lot of realtime tweakability with that, but Kontakt actually isn't all that bad in terms of tweaking/mangling samples (in fact, it's one of the masters in that area).

Yeah sure if thats what you want , but you could save yourself a lot work if you use Highlife. Because it make all of this automatically.

[Sascha Franck]

Yeah sure if thats what you want , but you could save yourself a lot work if you use Highlife. Because it make all of this automatically.

From what I know, Highlife is only sampling one VSTi at a time.
I do however sample layers along with effects very often.