How to get a rack into the Composer track?

[MuTools]

This gonne be difficult , because Mulab has no "Rack" save and load default in his GUI

Yes it has: Right-click the rack name -> "Open + Save Preset".

How to load a rack? Right click and select the 'other' folder, where you can find the Rack.

I can't still follow your explanation about a "other "folder ?
Or do i miss something?

He meant: How to plugin a rack in the deep editor: Popup the module list (double-click background or right-click background -> "Add Module"), then in the "Others" group (at the bottom) there is the Rack module. Then when you have inserted and connected that rack, right-click that rack name and "Open Preset".

[janamdo]

This gonne be difficult , because Mulab has no "Rack" save and load default in his GUI

Yes it has: Right-click the rack name -> "Open + Save Preset".

Thanks
Is it not more clear to say ..> Open + Save Rack
If you open a instrument panel you can save also : Save preset
So there are different presets

[janamdo]

This gonne be difficult , because Mulab has no "Rack" save and load default in his GUI

Yes it has: Right-click the rack name -> "Open + Save Preset".

Thanks
Is it not more clear to say ..> Open + Save Rack
If you open a instrument panel you can save also : Save preset
So there are different presets

How about Mulab tracks with automation in it..will this be heard also if i open the midi file in Cubase ?

[MuTools]

This gonne be difficult , because Mulab has no "Rack" save and load default in his GUI

Yes it has: Right-click the rack name -> "Open + Save Preset".

Thanks
Is it not more clear to say ..> Open + Save Rack
If you open a instrument panel you can save also : Save preset
So there are different presets

Yes you can save rack presets in MuLab.
But you cannot load these rack presets directly in the MUX vst because the MUX vst is a MUX, not a rack. That's why you first have to insert+connect a rack in the MUX vst and then load the rack preset in that rack.

[AndreasD]

I havent tested it, but my guess is that automation from Mulab will not be taken over in Cubase. The routing and automation system is quite different.
No DAW into another DAW does this - to my knowledge.

There was an article in SoundOnSound once about bringing one project from one DAW to another. The conclusion was: Mixdown each track to audio and load the audio into the new DAW.

[MuTools]

This gonne be difficult , because Mulab has no "Rack" save and load default in his GUI

Yes it has: Right-click the rack name -> "Open + Save Preset".

Thanks
Is it not more clear to say ..> Open + Save Rack
If you open a instrument panel you can save also : Save preset
So there are different presets

How about Mulab tracks with automation in it..will this be heard also if i open the midi file in Cubase ?

Indeed, that's another problem. You could try to bypass that by using MIDI controllers to automate the parameters.

Anyway, as you see it's not that easy to transfer a full song from one DAW to another. I would not recommend it unless you are a very experienced technician and when it's really really necessary.

FYI: These difficulties are not MuLab specific.

NB: You could mixdown the tracks to audio tracks of course so to ease the transfer from one DAW to another, but that's not what you are talking about here.

[janamdo]

I havent tested it, but my guess is that automation from Mulab will not be taken over in Cubase. The routing and automation system is quite different.
No DAW into another DAW does this - to my knowledge.

As i understand it now correct, it is not possible to hear a Mulab session song in Cubase .. i cannot transfer it. ( sound and midi notes can be exported, but no automations )
Now it is less interesting for me
Thanks!

[pljones]

As i understand it now correct, it is not possible to hear a Mulab session song in Cubase .. i cannot transfer it. ( sound and midi notes can be exported, but no automations )
Now it is less interesting for me
Thanks!

Unfortunately there is no standard session format supported by all DAW software, so this cannot be avoided. The same is true of moving work between any two DAWs (sometimes even by the same supplier).