MuTools

janamdo · Post by **janamdo** » Sun Jul 03, 2011 9:48 am

Dimension pro VSTi and Proteusx VSTi are the same VST 2.2 synths specification

-Dimension pro starts normal up in MUlab
-Protesx does not start up normal in Mulab --> it remains a menu bar
note: it is a big screen filled with knobs sliders
Is this too big to handle for Mulab ? --> can i make a adjustment in Mulab ?

MuTools · Post by **MuTools** » Sun Jul 03, 2011 1:45 pm

If a certain VST plugin has a problem, and only that VST plugin has that problem, then chance is high that the problem is in the plugin, not in MuLab, in which case you should contact the plugin developer.

ckeyser · Post by **ckeyser** » Sun Jul 03, 2011 4:16 pm

My Proteusx VSTi is working fine in Sonar 8, X1, FLStudio 10, Orion 8, PreSonus Studio 1. (Windows 7 x64/x32)

MuTools · Post by **MuTools** » Sun Jul 03, 2011 6:24 pm

ckeyser, janamdo, do you have the same version of proteus x?

MuTools · Post by **MuTools** » Sun Jul 03, 2011 6:32 pm

ckeyser wrote:My Proteusx VSTi is working fine in Sonar 8, X1, FLStudio 10, Orion 8, PreSonus Studio 1. (Windows 7 x64/x32)

And did you try it in MuLab?

(edited: typo)

janamdo · Post by **janamdo** » Mon Jul 04, 2011 9:18 am

mutools wrote:
ckeyser wrote:My Proteusx VSTi is working fine in Sonar 8, X1, FLStudio 10, Orion 8, PreSonus Studio 1. (Windows 7 x64/x32)
And did you tried it in MuLab?

Proteusx is working normal in MUlab and win xp !
The idea is to connect Mulab with a composer what uses the GM soundbank

Initialize General Midi is a button in the composer setup screen to get the richt sound allocation in MUlab

(this function is for use in the composer why must MUlab support this in the form off a GM INit function in Mulab itself ..)

MuTools · Post by **MuTools** » Mon Jul 04, 2011 10:10 am

I'm confused:

janamdo wrote:Dimension pro VSTi and Proteusx VSTi are the same VST 2.2 synths specification
-Dimension pro starts normal up in MUlab
-Protesx does not start up normal in Mulab --> it remains a menu bar
note: it is a big screen filled with knobs sliders
Is this too big to handle for Mulab ? --> can i make a adjustment in Mulab ?

Conclusion: ProteusX is not working in MuLab Windows.

janamdo wrote:Proteusx is working normal in MUlab and win xp!

Conclusion: ProteusX is working well in MuLab Windows.

Quid?

janamdo · Post by **janamdo** » Mon Jul 04, 2011 3:10 pm

I start with to write that Vsti proteusx was not working in MUlab, but now Vsti proteusx it is good working in MUlab!.. :harp:

So this problem is solved and sorry for the confusion!

MuTools · Post by **MuTools** » Mon Jul 04, 2011 4:44 pm

Ok, good news

Now regarding the GM init function: This needs a sysex (MIDI System Exclusive) subsystem and that's not yet implemented in MuLab.

janamdo · Post by **janamdo** » Mon Jul 04, 2011 8:29 pm

For easy working with the composersoftware from Cognitone it is vital to have General Midi sounds.
I can assemble a own soundset from multiple Vsti and this is working via a program chance ( channel message) i assume? and not via system exclusive messages.
I can at least than search for a replacement Midi sound or add new not midi sounds!
That i must test in Mulab now

i try also to setup my Sw1000xg card to use this a general midi sound replacement for the composer that is much better than the inbuilt GM windows sounds.
This card has a XG tone generator ( included are General Midi sounds) and here i do need also XG init function from the device setup made in the composer software to get the General Midi sounds

MuTools · Post by **MuTools** » Mon Jul 04, 2011 8:44 pm

Yes you could setup a MuLab session that simulates a GM setup.
Then when working with the external composer app, you load this musession and things should sound fine in a snap.

MuTools

KVR Audio

proteusx VSTi in Mulab