Mux vst as multitimbral synth

[janamdo]

Hi,
I loaded the mux (vst synth )as VSTi
- It is monophonic ?-> can i chance into multitimbral for 16 midi channels?
- soundnames device extraction ( by Steinberg standard )--> is this possibel for this synth ?

Thanks

[MuTools]

Hi,
I loaded the mux (vst synth )as VSTi
- It is monophonic ?

No. (not yet)

-> can i chance into multitimbral for 16 midi channels?

Yes, you can use the MIDI Channel Splitter for that.

- soundnames device extraction (by Steinberg standard)--> is this possibel for this synth?

What do you mean? And which 'Steinberg standard' do you mean? Please elaborate.

[janamdo]

-> can i chance into multitimbral for 16 midi channels?

Yes, you can use the MIDI Channel Splitter for that.

Is it possible to build this in MUX (synth ), because i am using not at the moment all the modularity of MUX.
Note: a weak point although, this modularity , because it seems that there is not organised information to find how to use all this power ..it is not for the "mass"

soundnames device extraction (by Steinberg standard)--> is this possibel for this synth?

What do you mean? And which 'Steinberg standard' do you mean? Please elaborate.

I could not answer this for now..find out

[janamdo]

What do you mean? And which 'Steinberg standard' do you mean? Please elaborate.

I could not answer this for now..find out

Steinberg ( Cubase ) has set a VST standard for extracting sound banks from a VSti plugin
In the composer program i use ..when it extracts a device description from a plugin .. it probably makes a device description ( i did dnot test it on a working plugin..( no sample player ..there it is not possible ? )

The Vsti plugin must support this extract feature.

[janamdo]

The Vsti plugin must support this extract feature.

This information i found

Extracting From Plug-in
Many virtual instruments support the automated extraction of their patch list. Although this function is part of the official VST/AU specs, many developers have saved themselves the effort of implementing it. In general, this function is more likely supported by synthesizer-type plug-ins rather than samplers. The only way to learn whether your plug-in supports this is to try out.
After you pressed the Extract button, Synfire will ask you for the name of the preset (not the individual patch!) that is currently loaded by the plug-in. If for example the plug-in Reaktor 5 has loaded the synthesizer Lazerbass, you enter "Lazerbass" here. In case its a collection of assorted Strings, you may name it "Orchestral Strings". Synfire will then create a device description based on the information it can find in the plug-in.
Tip:
In case your plug-in does not support this function, you may want to request this feature from the developers. Usually it is relatively easy to implement. The more users are requesting this feature, the more likely the developers will follow your suggestion.

[MuTools]

I'm sorry but no such plans on short term.

[janamdo]

OK
Than i doing it by hand ..choosing sounds..only by hand
Only try to make a multi timbralsynth of it and doing more with the modularity (i was always interested in this and still and if there enough examples and information i can go deeper in this ) , because Synfire can using MUX automation.

I do need more examples and information what i can do with all the modules in MUX.