MuLab 9.0.59 App + Plugin

[wibem]

Curious for your thoughts & feelings on M9 Plugin.

I'm having great fun using the Step Sequencer device within the plugin device to drive Bitwig instruments. It's so easy to duplicate a track to achieve parallel sequences. I also appreciate the fact that the plugin encourages you to explore the build in synth sounds within MuLab. There is so much to explore, but I love the fact that the workflow feel fits so well with Bitwig.

So, it seems that the event output of the Mulab plugin is working in Bitwig. I still have no success with Reaper to get the midi data out of the plugin. I've tried a midi monitor, but there is no midi, which is coming out of the plugin. What was your procedure to get the midi events into the daw?

[carlca]

Okay, I first loaded up the MuLb plugin in Bitwig so that its MIDI output would drive the Polymer synth (that's the third device show below).

Screenshot 2022-02-11 at 22.51.54.png

What I did in the MuLab plugin itself was to select the Basic Step Sequencer from the list of Effects devices...

Screenshot 2022-02-11 at 22.55.43.png

resulting in this...

Screenshot 2022-02-11 at 22.55.06.png

I hope that makes sense. Feel free to fire any more questions at me, but be aware that I am pretty much just discovering things as I find them, with no great plan behind my actions

[carlca]

I should point out that I had to have the clips in Bitwig actually running and supplying a basic MIDI pattern for the MuLab to be triggered...

Screenshot 2022-02-11 at 23.05.04.png

[wibem1]

So, you aren't using the composer module in Mulab plugin? I tried to do this and sent midi data from there into the host ( Reaper), which didn't work ( for me at least). Has anybody success with getting midi events from the composer module to the host?

[paradiddle]

Yes using it in audiomulch. made an empty track in composer. right click choose target module and then event output. I also made an vst midi input to composer.

Every thing works but As soon as I press record in mulab it starts by itself. I'd like for mulab to wait for me to press play in the host before recording. Must be something that I missed. It's awesome though cuz when I move audiomulch's playhead, mulab follows.

So, you aren't using the composer module in Mulab plugin? I tried to do this and sent midi data from there into the host ( Reaper), which didn't work ( for me at least). Has anybody success with getting midi events from the composer module to the host?

[paradiddle]

Just made a quick demo for an audiomulch user groups. Hope it's not a prob me posting vids as I've seen some vids and screenshots in this thread. Just selling mulab to peeps haha. It's pretty awesome!

[humanboeing]

So, you aren't using the composer module in Mulab plugin? I tried to do this and sent midi data from there into the host ( Reaper), which didn't work ( for me at least). Has anybody success with getting midi events from the composer module to the host?

For me its working in Reaper.

[carlca]

So, you aren't using the composer module in Mulab plugin? I tried to do this and sent midi data from there into the host ( Reaper), which didn't work ( for me at least). Has anybody success with getting midi events from the composer module to the host?

For me its working in Reaper.

I'd be interested to find out how. After doing it in Bitwig, I tried it in Reaper, but, like @Wibem1, I couldn't persuade the MIDI notes to actually make any sound...

[humanboeing]

Mulab sequence powering ReaSynth looks like this. One important thing to keep in mind is that if you drop an instrument into the rack the ReaSynth won't play, that's because most instruments don't have an event output so the event signal flow inside the rack is broken.

[pljones]

(Hm, I've not got screen recorder in MuLab Plugin?)

1. Start Reaper
2. Insert a track
3. Add MuLab VST Effect (or Synth, guess it makes a difference...) as the first effect
4. Add another instrument as the second effect (I used MDA ePiano)
5. Open the Basic Effect modular area (NOT the MuLab main modular area)
6. Delete the audio path modules
7. Add "Initial Event Generator" to the modular area
8. Add "Step Sequencer" to the modular area and connect it to the "Initial Event Generator" (input) and "Event Output 1" (output)
9. Open up the "Step Sequencer" and fill in your sequence
10. Hit "Play" in Reaper

For me, that triggered the ePiano with no input events at all.

Unfortunately, stopping Reaper left the "Step Sequencer" running until I turned the module off...

Next:
1. Replace "Step Sequencer" with "Composer"
2. Insert (plain) track
3. Add a MIDI Sequence part
4. Edit it and add your MIDI Sequence
5. Hit "Play" in Reaper

And nothing happens.

Next:
1. Add a Rack
2. Switch to "Show Event Output"
3. It says: "No Event Output", which could be a problem...
4. Switch it to "Event Output 1"
5. In "Basic Effect" modular view, add an Event Monitor and connect it to the Composer output
6. Hit Play in Composer...

And nothing happens.

Well, the track target? That's not set. Oh - I'm offered "Event Output 1" here!

That gets me the output!

... Unfortunately, that's having manually hit Play in Composer. Hitting Play in Reaper gets no effect, even with "Initial Event Generator" connected again.

I tried "Live Sync" mode of "Start" and "Sync", neither helped.

(Noted that the module right-click menu seems... over-populated: some of the items probably only "make sense" with the Composer open.)

[humanboeing]

... Unfortunately, that's having manually hit Play in Composer. Hitting Play in Reaper gets no effect, even with "Initial Event Generator" connected again.

Try messing around with the host sync options (left click on the button)

[pljones]

Gah! Thanks, I could not see Host sync... (Despite it being clearly there...)

[pljones]

OK, based on the above, I'd suggest for Composer:
- start with Host Sync enabled
- target audio output 1 and event output 1 by default for each track
- if a rack gets added because a synth track was added, target both output from that, instead (for that track)

(Basically, make it as easy as possible to replace "Step Sequencer" with "Composer" - because the "Composer" is a sequencer, just as much as the "Step Sequencer" is, so it shouldn't feel like a lot of work (which it currently does) to switch.)

[wibem]

Mulab sequence powering ReaSynth looks like this. One important thing to keep in mind is that if you drop an instrument into the rack the ReaSynth won't play, that's because most instruments don't have an event output so the event signal flow inside the rack is broken.

You can you use the send function in the racks to split the signal. One send is going to the sound plugin, another one is used to send midi data to event output. With this configuration I have managed to get the midi data from the Mulab plugin to the Reaper host. Indeed it's quite complicated.

[cousin_itt]

With 9.0.24 I'm still getting sync issue with Cantabile 3 as the host.
I'll contact the Cantabile developer too.
Tempo adjusts fine, start and stop work, but the position jumps on stop.
Here is a screen cap:
https://streamable.com/4fz310