MuLab 9.1.27 [released]

[sl23]

Thank you for the massive update. Hope you're doing OK.

One question regarding the now editable MuSynth, MuDrum, etc, will they still be available as factory default devices if we edit them? Are they write protected, forcing you to 'save as' a new version?

[oldcastle]

Hi,

I'm not sure if it's a bug, but when I click on any step, the whole column gets "selected", including the buttons.

GIF 04-04-2023 23-32-54.gif

[oldcastle]

Hei,

Screenshot (3).png

This one, I don't know if it is a bug, a request, or a misunderstanding on my part. However, when I add an instrument track, I don't see an option to add a "default" MuDrum, MuSynth, MuSampla or MultiSampla device without any preset loaded. I only see instruments. So, if I want to start working on MuSynth from scratch, I need to figure out first which instrument uses MuSynth and then work my way out from there. Same thing for the other devices, like MuDrum. I think it would be very helpful to offer easy access to MuDrum, MuSynth, MuSampla and MultiSampla in a default state (blank). Does it make sense?

[Scrubbing Monkeys]

Hei,


Screenshot (3).png


This one, I don't know if it is a bug, a request, or a misunderstanding on my part. However, when I add an instrument track, I don't see an option to add a "default" MuDrum, MuSynth, MuSampla or MultiSampla device without any preset loaded. I only see instruments. So, if I want to start working on MuSynth from scratch, I need to figure out first which instrument uses MuSynth and then work my way out from there. Same thing for the other devices, like MuDrum. I think it would be very helpful to offer easy access to MuDrum, MuSynth, MuSampla and MultiSampla in a default state (blank). Does it make sense?

I found the same and requested we continue to have those as devices along side the ability to customize if desired. I guess we could technically do it ourselves by saving a Init instance of each but I do like Mudrum having the integrated sampler in the gui. Not sure if it is possible to have it both ways. Jo will know.

[FabBad]

Hi! this is a very promising update!
Sadly i have a little time to test it, but i’ll do it when possible.
Today i was messing around with the alpha and i found a crash by trying to add a multisample element on the front panel.

Custom user patches that use MuSynth and the Sampler module in it are not properly converted in MuLab 9.1.1 alpha. The Sampler module is missing.

Is missing on the front panel but is there in the structure, so i tried to add it in it but it crashes the program without notice.

[MuTools]

Please leave a configured MuDrum available. It is quite elegant as is. I do like the access also.

In the new complete zip package that includes the factory library there will be MuDrum, MuSampla and MultiSampla template presets. Note however that these are straight MUX presets like any other MUX preset. With the advantage that they can be tweaked as you want.

When I expand a psd to show the sampler.....the sampler window is so large it doesnt fit side by side with the pads. Therefore the pads are in a window behind the sampler creating multiple clicks opening and closing windows.

What's your screen resolution?

I understand that on rather small screens this new MuDrum pad editor layout is bigger than before because both sampler sections are shown together instead of the tabbed approach in the legacy MuDrum device. Of course it would be nice if we could have a "Tabbed Group Frame" for the front panels, it's on the wishlist, and that would solve the issue of the bigger MuDrum pad editors.

[MuTools]

Custom user patches that use MuSynth and the Sampler module in it are not properly converted in MuLab 9.1.1 alpha. The Sampler module is missing.

The multi-sampler section of the MuSynth patch still is in there and it still sounds exactly the same as before and you can access it via the modular area, but you're right that the multi-sampler section has been removed from the front panel because i assumed it was mostly unused and because it was difficult to give it a nice fit in the reworked MuSynth layout. Feel free to share a mockup of the new MuSynth layout with the multi-sampler section nicely integrated.

[MuTools]

Thank you for the massive update. Hope you're doing OK.

Processing the emotions, day by day...
You also know the pain and the path, unfortunately.
Thanks again for your wise support a week ago.

One question regarding the now editable MuSynth, MuDrum, etc, will they still be available as factory default devices if we edit them?

Not as "built-in devices" anymore but the next complete MuLab zip package will still include MuDrum, MuSampla and MultiSampla template presets, but these are just plain MUX presets like the "Basic Synth" preset. You can do with MuDrum whatever you want. That's the big advantage of this new approach.

[MuTools]

I'm not sure if it's a bug, but when I click on any step, the whole column gets "selected", including the buttons.

Yes that's how it is: When a step is deactived it gets hidden, just like in M8.x and M9.0. If i'm missing something pls let me know.

[MuTools]

Hei,
This one, I don't know if it is a bug, a request, or a misunderstanding on my part. However, when I add an instrument track, I don't see an option to add a "default" MuDrum, MuSynth, MuSampla or MultiSampla device without any preset loaded. I only see instruments. So, if I want to start working on MuSynth from scratch, I need to figure out first which instrument uses MuSynth and then work my way out from there. Same thing for the other devices, like MuDrum. I think it would be very helpful to offer easy access to MuDrum, MuSynth, MuSampla and MultiSampla in a default state (blank). Does it make sense?

MuDrum, MuSynth, MuSampla and MultiSampla are now normal MUX patches and so indeed there is no separate "Devices" group anymore. The next complete MuLab zip package will include MuDrum, MuSynth, MuSampla and MultiSampla as presets in the Instruments/Templates sub-folder.
I've attached a little zip with these presets. You can put them in MuLab/App/Library/Mux/Instruments/Templates and then you can easily insert eg a blank MuDrum.

Edit: I've removed the zip file as it contained an error. Will share the corrected versions soon.

[MuTools]

I found the same and requested we continue to have those as devices along side the ability to customize if desired. I guess we could technically do it ourselves by saving a Init instance of each but I do like Mudrum having the integrated sampler in the gui. Not sure if it is possible to have it both ways.

With this new approach you can customize MuDrum in any way you like and save it as a preset. So you can also have different versions of MuDrum: Eg a simple version with minimized editors, or a maxi version with certain pads even including other front panel components like a step sequencer or filter section etc. You have much more control over MuDrum, MuSynth, MuSampla and MultiSampla now, also over their names.

[MuTools]

Is missing on the front panel but is there in the structure, so i tried to add it in it but it crashes the program without notice.

Can you please give me the step-by-step for repeating that crash? Thx.

[Scrubbing Monkeys]

Thanks for the reply and the templates Jo. Still getting use to the idea of new possibilities.

[sl23]

All I was thinking, as someone also mentioned above, was that perhaps it would be a good idea to make it so the default MuDrum, MuSynth, patches couldn't be altered. Meaning, yes they are now standard MuX patches, but make it so you can't save them, as in overwrite the default. Forcing you to 'SaveAs' creating a new file as it were.

Because if we mess about with the default patch and save it, weve lost the default starting point. Hope I made that clear enough?

[oldcastle]

All I was thinking, as someone also mentioned above, was that perhaps it would be a good idea to make it so the default MuDrum, MuSynth, patches couldn't be altered. Meaning, yes they are now standard MuX patches, but make it so you can't save them, as in overwrite the default. Forcing you to 'SaveAs' creating a new file as it were.

Because if we mess about with the default patch and save it, weve lost the default starting point. Hope I made that clear enough?

Good point. I think that's the way to go, otherwise I will need to keep replacing the default patches over and over