mux as Vsti in composer

Official support for: mutools.com
RELATED
PRODUCTS

Post

Thanks for the idea for the rack panel on this way and trying out the sound! :tu:
Yes i get the same sound ( wrong import option in the composer? )
But now the challence for me in the composer to get about the same song as in Mulab!

I do not see how to apply this echo verb on the bass sound in the demo song krafty groove : were is the gain of de FX rack located?
( there is a external midi controller used (modulation wheel ..?) and this modulation wheel is controlling the gain of the FX unit ).
Solved !: That little round dial on the Bass rack rack : Send to Fx is indeed controlling the gain of the FX rack

Post

hehe its a voyage of discovery :wink:
Beauty is only skin deep,
Ugliness, however, goes right the way through

Post

Yes..also how it must be done in the composer to get the same as in Mulab :phones:

Post

Well, it is mission impossible to use the MUX vsti in the composer and do the same things as in Mulab.
Rack handling-automation must be translated into the composer.. i tried, but lost oversight with this all, because automation in the composer is only via a midi controller and once a paramater is mapped you can also draw it ( as i understand it correct).

I go back to to the midi loopback driver and connect the composer with mulab itself..works great at first sight.
Automations can be done in Mulab itself and Vst parameters are also accesible within Mulab.. i can draw the automations by hand. (if this works? )

Post

Hope you get where you want with this.
Beauty is only skin deep,
Ugliness, however, goes right the way through

Post

Yes, me too ..the composer is really for advanced composing and Mulab act as a soundmodule, composer, mixer,audiotracks and produce a song audiofile..woah.

I did a test and recorded two tracks in the composer in Mulab and it sounds great (at the end the whole song must be played in Mulab were a audio file can be made out of the song).

Only one problem with loopbackdriver how to extend to more then 16 midi channels..is there a second loopbackdriver possible/needed ?
LoopBE30
http://nerds.de/en/loopbe30.html
Image
Unfortanely can't get a bigger nice pic (how to do ? )of it with a scroll
Synfire and Mulab seems to be married now :wink:..a unique couple
==================================================================
Note the composer and Mulab with a loopbackdriver is a dead road ...not a workable setup.
I am now using the composter with a midi drone inside Mulab modulair session area..works like a charm.
For instance ..you can now easily harmonize voices with instruments in Mulab with the composer.
Last edited by janhardo on Thu Jan 07, 2016 1:12 pm, edited 1 time in total.

Post

MuLab itself only supports 16 MIDI channels, regardless of the number of MIDI Input ports you use. So having extra ports, each with 16 channels, between Composer and MuLab will not solve your problem.

Given than you have 128 MIDI CC numbers to choose from on each of those 16 MIDI channels, are you sure you need more <edit>controllers</edit> than 2048? Or is this not a problem with MIDI CC numbers but something else?
Last edited by pljones on Wed Dec 30, 2015 9:29 pm, edited 1 time in total.

Post

The composer has also the 16 midichannel in a rack as standard
With 16 midi channels you can make a lot of music.
Yes, good point : midi imput channels targets has 16 indeed
But i can assign more then 1 midi channel to one midi number ( i can have 5 midichannels 1 )

I am not a midi expert .. cannot follow the rest of this reasoning ( i do have have only a minor degree in math teaching...and amechanical engineering background :wink: )
Last edited by janhardo on Thu Dec 31, 2015 4:45 am, edited 3 times in total.

Post

There is also another problem with the exported midi from MUlab
When exported in Mulab and then imported in Synfire...takes very long time ( how long) to translate them for Synfire ( the standard GM goes fast importing them a few minutes )
But the midi export from Mulab are not GM standard?

Post

GM describes how an instrument might choose to respond to a certain subset of MIDI event messages. MuLab is not an instrument anyway and in any case, it's always entirely up to any MIDI device to decide how it responds to any MIDI event message.

Post

The composer uses GM midi's ..luckily it seems to be ok the midi export file from Mulab ( export midi file from Mulab, i assume it is then accoording the midi standard) : i did not mark the drum track during import in the composer as a static track.. the musical AI recognizition algorhytm from the composer can handle this, but it could take a hour when the drumtrack is not labelled as a static drum track.
It works great now with the right import track labelling
It seems to be a awesome combination the composer and Mulab.. i will see...

Post

Does MUX, available inside Mu.Lab I think it's the MODULAR tab?

or it is a different kind of thing? Please teach me I'm newbie

Post

cloudspell wrote:Does MUX, available inside Mu.Lab I think it's the MODULAR tab? or it is a different kind of thing?
Yes MUX Modular is everything of the sound engine, including the project modular area, which is the top level in the MUX modular architecture. Also see http://www.mutools.com/info/docs/common ... t-mux.html

Post Reply

Return to “MuTools”