MuLab 9.0.59 App + Plugin

[ElVincente]

Yes exactly

[MuTools]

MuLab App 9.0.39 is available in https://www.mutools.com/mulab/app/latest-binary

MuLab Plugin 9.0.39 is available in https://www.mutools.com/mulab/plugin/latest-binary

What's changed:

• MuLab Plugin: Improved sync to host DAW: Added an extra sync option "Sync Time While Playing".
• When GUI Scale was above 100%, MuLab's splash window didn't use the correct font sizes. Fixed.
• Other small improvements.

[MuTools]

Do you guys mean the case that while Reaper + MuLab Plugin are playing and you reposition Reaper (while it's playing) that MuLab Plugin doesn't follow that position change in Reaper?

Yes exactly

Pls check out M9.0.39.
When host sync is enabled and it's option "Sync Time While Playing" is enabled the composer also follows the new host position change.
Does it now all work as expected?

[padillac]

Just want to drop in and say that the Composer module is the coolest thing ever... it's how I've dreamed of working in DAWs for years. In fact it's even better because of the note action map. So, so cool.

It looks like a single composer can have 128*16=2048 different actions assigned to it?!

[MuTools]

Just want to drop in and say that the Composer module is the coolest thing ever... it's how I've dreamed of working in DAWs for years. In fact it's even better because of the note action map. So, so cool.

Thanks!

It looks like a single composer can have 128*16=2048 different actions assigned to it?!

That's correct.

[MuTools]

MuLab App 9.0.40 is available in https://www.mutools.com/mulab/app/latest-binary

MuLab Plugin 9.0.40 is available in https://www.mutools.com/mulab/plugin/latest-binary

What's changed:

• Composer modules can be saved / opened as a preset. That makes it easy to combine composers from different projects and to exchange composers with other users.
  A .MuComposer preset file is like a more extended version of a MuClip. (a MuClip only contains a single clip)
  For example you could use a composer preset with a bunch of MuDrum patterns in the Live Matrix that you can instantly merge into a new project.
• The term "part" has been renamed to "clip".
  "Clip" was already used for Live Matrix Clips and MuClips and to avoid unnecessary ambiguity now also timeline parts are called clips.
• Note Action Map editor now uses a subtle lighter/darker background color for the white/black keys. Alike the note sequence editor.
• New shortcuts for toggling between composer view and clip editor, and between compooser view and modular area.
• Shortcut "Toggle Snap On/Off" renamed to "Toggle Grid On/Off".
• Copy-pasting composer modules from one project to another could cause a crash. Fixed.
• It was possible to accidentally drag a rack's level meter out of that rack, causing a faulty rack. Fixed.
• When browsing for a MUX preset and previewing files and then do cancel, the original MUX data was restored but inactive. Fixed.
• Applied a specific speed optimization to one of the GUI sub-systems. Not sure how much effect it will have in real life, but technically it's certainly a neat optimization and it will cause the cpu to have less work which is good for the planet.
• Other small improvements.

[Jonathan Shepherd]

Great update. The composer presets will help a whole lot!

[Taron]

Love that it's raining updates lately, that's a pleasure to see, Jo! Fantastic!
I do have a problem, though: Add Automation Sub-Track Pitchbend will automatically create a screwed up sequence that should be bidirectional, but is broken:
top 100.0
mid 50.0
bottom -100.0/0.0

Then when you want to add a new sequence ( Ctrl + mouse ), it will offer STREAM | AUDIO SEQ. | MIDI SEQ. and choosing MIDI will not give you a curve sequence, but a normal piano roll.

In the past this Automation Track stuff worked quite beautifully and I don't even remember having had troubles with it. Since 9 it doesn't quite work anymore the way it used to. And I haven't found the way it may now be meant to be used?!

Maybe a simply clue will help me, but even then, I can almost assure you it probably needs fixing. Thing is, if you just want to make music, it used to just work and it probably still should. That means, even if there is a new way of doing it "right", it truly feels a bit wrong as it is right now. If I have an automation track, I kinda want to make an automation sequence on it, too. I'm sure it's a bug, really.

[MuTools]

Hey Taron, the automation track system indeed has slightly changed: In M8 the automation parameter type was defined by the track, in M9 it is defined by the automation clip. This has the advantage that you can have different automations on the same track as long as it's about the same target plugin / module. In M8 you had to create a separate track for each separate automation, which could cause waste of screen space.

That said there indeed is a bug for the pitch bend automation type. Will be fixed. Thx for reporting this.

[Taron]

Absolutely! You know I'm ruthlessly reporting what I find!
But, still, how would one go about adding a new automation sequence then? Very often I just have a measure or just a bar for some automation changes that I'll set manually. I've always done this on the fly just by holding control and dragging it on. I also find it a bit questionable that adding an automation lane puts a sequence across the entire length of the track. Has someone requested that? If there was an option not to have that happen, I'd definitely set it to not do that.

Anyway, I should probably check the new manual then to see how it should be done now. Who knows, maybe I won't miss the olden days in that regard. Secretly I'm hoping for the day when you can freely switch between curves and data under the standard piano roll sequence!!!!!! besides adding multiple controller lanes. (I'm pretty sure you know that requests will never ever stop coming! ...but that's only because you're doing such a brilliant job with MuLab!)

[MuTools]

But, still, how would one go about adding a new automation sequence then?

Once there is at least 1 automation clip on a track then drawing new clips on that track will automatically draw new automation clips as it's assumed to be an automation track.

And if all automation clips on a track are automating the same parameter then drawing a new clip will automatically be an automation clip for that same parameter.

But in M9 you can change the target parameter for each automation clip, even if it's on the same track. That's different from M8.

Ok i see there indeed is an uncovered case: If there are no clips on a track, then how to add an automation clip without doing "Add Automation Sub-Track"? There indeed is a functional gap there. In the next update, if there are no clips on a sub-track, you'll get the choice and so you can choose an automation clip.

The M9.0.41 update is expected to be available tomorrow.

I also find it a bit questionable that adding an automation lane puts a sequence across the entire length of the track. Has someone requested that? If there was an option not to have that happen, I'd definitely set it to not do that.

Then you would simply get an empty track!
And you still have to draw a new clip and then choose "Automation".
In't all that more work than simply tweaking the length of that new automation clip?
That new clip is there to make it easy for you.

Secretly I'm hoping for the day when you can freely switch between curves and data under the standard piano roll sequence!!!!!!

Valid hope. It's on the wishlist.

[MuTools]

MuLab App 9.0.41 is available in https://www.mutools.com/mulab/app/latest-binary

MuLab Plugin 9.0.41 is available in https://www.mutools.com/mulab/plugin/latest-binary

What's changed:

• When drawing a new clip on an empty sub-track, you now get the choice what type of clip you want.
• Fixed a bug in the envelope editor for pitch bend automation clips.

[Taron]

ABSOLUTELY LOVE IT, JO! Absolutely love it!
This feels perfectly right and tight now! HURRAY! Thank you for jumping right on it, I absolutely love that, too!

[MuTools]

Thanks for spotting that bug and that workflow bottleneck Taron

[MuTools]

Tip: You can also drag-drop a parameter onto a track, that will create an automation clip for that parameter. This can be done on any track that targets that module. (that module itself, not a parent module or rack)

All MuLab tracks are hybrid.
You can put audio + events + automation onto it.
It is the track's target module that will receive + process the track's audio + events + automation.
If you put audio on a track that targets a module without an audio input, that track audio won't have any effect. You can intermix audio + events + automation clips on a track as you wish.