MuLab 10.1.25

[MuTools]

I still don't understand what you mean.
Please make a simple screen video demonstrating the issue.

[sl23]

Step by step:
1. Add a synth, record a part just so you have something in slot 1, I imagine it's the same with or without a synth part, but humour me.
2. Add FX to slot 2 and make some automation to a sub track.
3. move the FX to slot 3.
4. Add a second FX to slot 2.

Notice the automation doesn't follow the plugin it stays with the target as rack slot 2. Whereas I think it should be locked onto it's original plugin, no matter the rack slot it is in.

Ok, here you go:
Notice the sub-tracks of track 1 in the composer are:

• Slot 2: Uhbik Runciter with each controlling an automation sequence: Cutoff, InputDrive and Resonance.

I then move Runciter from Rack Slot 2 to Rack Slot 3.

• Notice how the names change to Rack Slot 2

Then I add TAL Reverb to Rack Slot 2, as an example, could be anything though.

• Now you see the names of the Sub-tracks renamed to Slot 2: TAL Reverb

Automation is now broken.
-

GIF 30-09-2025 15-39-44.gif

Is that a better explanation or would you like me to elaborate further?

[MuTools]

If i record a plugin parameter i get an automation track pointing to the plugin itself, not the rack slot.

So how do you get to the point that you have tracks pointing to rack slots instead of tracks pointing to the plugin inside a rack slot?

Can you give me a step by step to that?
Preferably starting from a new project.

[sl23]

Tbh, I have no idea how I did that, I made the track about 2-3 years ago. I Updated the track with VST3 Uhbik's yesterday and this one was the only one with automation, which I did earlier. All I did to relink the track to the Target module was R-click the track to select Choose Target Module. The only possible thing I could choose was the track: Acceleration > Slot2:Uhbik Runciter. There was no other choice. Then I had to reassign the Cutoff, etc as they were selected, but not working, when I R-clicked a sequence to Choose Automation Type.

Shall I send the project, with only track 1 saved? Maybe you can see what's going on then.

[MuTools]

Tbh, I have no idea how I did that, I made the track about 2-3 years ago. I Updated the track with VST3 Uhbik's yesterday and this one was the only one with automation, which I did earlier. All I did to relink the track to the Target module was R-click the track to select Choose Target Module. The only possible thing I could choose was the track: Acceleration > Slot2:Uhbik Runciter.

Ah, that's the answer to my question, thx.
In fact it's about a bug: The Choose Target list should not only include the rack slot, but also the module (eg. plugin) inside that slot, and also any deeper childs of that module. Will be fixed in the next update! Thx for spotting this case!

So that's the reason why the automation doesn't follow the module because the automation is routed to the rack slot instead of the module inside that slot. Do you see what i mean?

So it's a matter to tell the automation track to target the module (plugin) itself.
That can easily be done by drag-dropping the module onto the track.
Once the track targets the module itself then moving the module to another slot will preserve the automation because the automation points to the module itself, not to the slot.

Hope this clarifies it all.

And that "Choose Target" list bug ie. incomplete list will be fixed.

[MuTools]

PS: Thinking loud:
Maybe the Track -> Choose Target can be removed so to simplify things.
Then changing a track's target module is always done using drag-drop, which is more intuitive.

[pljones]

PS: Thinking loud:
Maybe the Track -> Choose Target can be removed so to simplify things.
Then changing a track's target module is always done using drag-drop, which is more intuitive.

No! I'll often have quite a set up in place and it's a lot easier just being able to right click and go "Oh, I meant that to go ...(drill down)" (once the drill down works) and fix it, rather than (find parent, find child, find child, find module, find parameter, drag, find track, drop).

[MuTools]

@pljones: I understand.
For advanced users "Choose Target" is a good thing.
Atoh for newbies / non-geeks "Choose Target" may feel complex / confusing tech bloat.

Just thinking loud:
What about making "Choose Target" a shortcut-only function?
So it's not in the popup menu, but you can still assign a shortcut to it and then click track and press that key to do "Choose Target".
What do you think?

[sl23]

Tbh, I found it easier to use the menu option. If you hide things like this, I think it would make it harder for users to find these things out. Having this menu option can make it easier for new users to find, and then once they learn more, can then drag and drop. I for instance, never even thought about that, but it makes sense I suppose, given MuLab's ethos.

Good to know it was a bug and you nailed it, again! Thanks

[pljones]

What about making "Choose Target" a shortcut-only function?
So it's not in the popup menu, but you can still assign a shortcut to it and then click track and press that key to do "Choose Target".

I'm very much bound to right-click to access everything for an item in MuLab -- it's "the way it works". I don't use the keyboard at all (except the shift/ctrl modifiers), so this would be "unnatural" and against the ethos for me.

[MuTools]

MuLab App M10.1.10 beta is available on https://www.mutools.com/mulab/app/lates ... /beta.html

MuLab Plugin M10.1.10 beta is available on https://www.mutools.com/mulab/plugin/la ... /beta.html

What's changed:

• Track -> Choose Target: List was incomplete. Fixed.
• When doing combinations of load preset + revert + undo + redo for a MUX, it could happen that the cables to/from that MUX were accidentally lost. Fixed.
• When doing combinations of deleting modular input/output modules + undo + redo for a MUX, it could happen that the order of modular input / output jacks was reversed. Fixed.
• Refined icons for input/output modules, rack slots and plugins.
• Other small improvements.

[sl23]

I just had a minor glitch, not sure how relevant or often it is likely to appear, just thought I should mention it so you are aware...
I loaded a temp test project, changed a couple things, then reopened the same project to revert it to it's previously saved state.
When I did that the second of the three racks lost it's VST entry, ie, it went blank. I then reloaded the project and it returned, loading as normal. But this may cause users to inadvertently lose something if they save after this happens.

It has literally just happened, but I thought it was important that people should be aware of it.

[MuTools]

Is it repeatable?

[sl23]

I just tried reloading around ten times and a few more times with some of the changes I made when it removed the VST, but no, can't repeat it, sorry. Will let you know if it happens again or I can provide more info. But for now....

Btw, the only things I was "playing" with were the Choose Target Module, due to the update fix in M10.1.10, but whether it was the cause, I couldn't say.

[MuTools]

May have been a user mistake..?