MuLab 9 Plugin Workfow

[mgiambro]

Now that MUX has become the MuLab 9 plugin and has the full functionality of the MuLab DAW, I'm curious to know how people plan to incorporate it into their workflow. For example, would you use it as a scratchpad for basic ideas and then flesh them out in the host DAW? Or maybe build the full track in the plugin and then export the audio or midi out? Maybe route individual tracks out to the host rewire style? Or maybe you'll just continue to use it as synth/effect modular environment as before?

[humanboeing]

Initially I thought I'm going to work with Reaper + Mulab Plugin combo, I'd make the arrangement in Mulab, then mix & master in Reaper. However over this beta period time I became more and more fascinated with the standalone app, I'm planning to buy it once version 9 is released and make it my main DAW.

[pljones]

Given my experimentation days are over, what will actually happen is I keep using the plugin just to host Sforzando, Kontakt and dynamics effects for the various drum kits I use, which I've got a complete Reaper set up for. I use Reaper because it works with OSC and TouchOSC, mainly - and because the UI can be incredibly minimal if you want it to be. Given the number of tracks I use, that's essential (I'm nearly at Reaper's limit). I play live music rather than compose, too.

However, I'd love to have the time to see what I could do using multiple instances with Reaper controlling the "overall structure" and Mulab having complex sounds with different instances on different tracks to provide different textures, which could be mixed. Some instances would be synced, some would be free-running. I think it's a stunningly inspiring concept.

Of course, you can do all that with MuLab standalone - why use Reaper at all? Again, probably OSC/TouchOSC automation - but much could be done using MuLab directly.

[wibem]

I'm using Mulab plugin in Reaper too. Reaper fills all my needs for customizations and is very CPU efficient. One big drawback of the Mulab standalone for me is, that Mulab has no option to set the audio buffersize. On my weak computer this option is absolutely necessary.

[mgiambro]

Thanks for the replies guys. Exactly the kind of information I'm after.

One big drawback of the Mulab standalone for me is, that Mulab has no option to set the audio buffersize. On my weak computer this option is absolutely necessary.

Can you not change the audio buffer size in the Audio Setup (MULAB > Audio Setup)?

https://www.mutools.com/info/M8/docs/mu ... setup.html

[wibem]

No, at least for MacUsers there is no system setting for the audio-core driver to set the buffersize. Some external audio units might have a driver software, with which you can set the size. But it's not possible for the internal driver and not for those units (like mine) , which come without a driver software.

[Scrubbing Monkeys]

What I would like to do is use Mulab Plugin inside of Reaper to handle all the midi and clip launching ( so much smoother than Reaper )and use Reaper tracks for audio. ( I am so used to the Reaper takes system that I almost cant record audio other wise ). I have the standalone M9 and am really enjoying it. Still demoing M9 plugin trying to figure out host sync. it seems a bit odd.

[MuTools]

Still demoing M9 plugin trying to figure out host sync. it seems a bit odd.

Please elaborate.

[Scrubbing Monkeys]

Still demoing M9 plugin trying to figure out host sync. it seems a bit odd.

Please elaborate.

Hey guys.

I am organizing my observations and will make a short video of what I'm experiencing. Hopefully today.

[Scrubbing Monkeys]

Well......I can't repeat what I was experiencing. Which was .....clicking play in Reaper did not start Mulab but toggling pause would start and stop Mulab.

Some factors that may have solved the issue are....
Today Im not drunk.....joking
I experienced this after a new install of M9.033. Restart may have solved it however I updated to M9.034 before trying to reproduce so that may have solved it as well.

All is good here