MuLab 10.2.29 beta

[FabBad]

• New "Audio Gate"

Nice
Also, found a bug on that new module, it stopped receiving MIDI notes after inserting a module or whatever on any other place, racks, MUX'es, etc. I Have to turn off and on the parent MUX to bring back the correct behavior.

[MuTools]

Quick UX observation: The save dialog appears every time I quit, even if I've just saved. If I save and then immediately use the 'X' button, Ctrl+Q, or the menu to exit, I expect ML to close without prompting me again.

Please see https://www.mutools.com/info/M10/docs/m ... swers.html
Search for "I just saved my project".

[oldcastle]

Quick UX observation: The save dialog appears every time I quit, even if I've just saved. If I save and then immediately use the 'X' button, Ctrl+Q, or the menu to exit, I expect ML to close without prompting me again.

Please see https://www.mutools.com/info/M10/docs/m ... swers.html
Search for "I just saved my project".

Noted. Thanks for the explanation.

[MuTools]

• New "Audio Gate"

Also, found a bug on that new module, it stopped receiving MIDI notes after inserting a module or whatever on any other place, racks, MUX'es, etc. I Have to turn off and on the parent MUX to bring back the correct behavior.

I removed my previous replies because after some further testing around what you described i discovered something else, not related to the Audio Gate, but the Audio Gate now brings that issue to the front. Will research this further.

[FabBad]

• New "Audio Gate"

Also, found a bug on that new module, it stopped receiving MIDI notes after inserting a module or whatever on any other place, racks, MUX'es, etc. I Have to turn off and on the parent MUX to bring back the correct behavior.

I removed my previous replies because after some further testing around what you described i discovered something else, not related to the Audio Gate, but the Audio Gate now brings that issue to the front. Will research this further.

Yes, I noticed that, maybe was something aside the module, so what you say makes me stop trying to reproduce in which it was resulting in something random or quite complex, at the point to no reply because of this.

Also, I little bug, in that module, is when typing the attack value and then hit enter, the first note is not changed but yes after the consecutive notes.

[MuTools]

Yes, I noticed that, maybe was something aside the module, so what you say makes me stop trying to reproduce in which it was resulting in something random or quite complex, at the point to no reply because of this.

It's indeed a quite serious event processing bug elsewhere, but now it got highlighted by how the Audio Gate works. That's why i first was confused about your report as i didn't immediately see the reason in the Audio Gate itself. Anyway, thx to your report that serious event processing bug has been discovered

Also, I little bug, in that module, is when typing the attack value and then hit enter, the first note is not changed but yes after the consecutive notes.

I don't think it's about the "next note" but when changing these values the new process values are calculated with a little delay (750 ms). That's often when doing edits to avoid UX lags when quickly wheeling to another value, as you don't want heavy updates on each and every value in such case. But in this case it doesn't hurt to do immediate updates, so this has been finetuned in M10.2.11. Thx.

[MuTools]

MuLab App M10.2.11 beta for Windows 64 bit is available:
https://www.mutools.com/mulab/app/lates ... /beta.html

What's changed:

• When a module was switched off but still receiving events from the composer, then this caused a stack up of unprocessed events. This not only could lead to some unexpected behavior upon switching that module on again, but if the switched off situation lasted long (depending on how many events were sent) it could in the end even lead to a ceasing of almost all event processing. Fixed.
• Finetuned some things in the new Audio Gate.
• Sequence editor: When a velocity bar was mouse-wheeled from velocity 1.0 to 0.0 then it was displayed as "-0.0". Fixed. (FYI: It are things like this that are often listed as "Other small improvements")

[Bax9]

MuLab App M10.2.9 beta for Windows 64 bit is available:
https://www.mutools.com/mulab/app/lates ... /beta.html

What's changed:

• Drum Note Processor can now be switched to a 24 pads version. The multiple of 12 still is maintained because it neatly maps to the number of keys in an octave.
• Drum Note Processor now plays out octaved versions of the drum keys. For example, using a 12 pad version: When C4 is received it maps to pad 1 and it sends out a C4 on output 1. When D4 is received it maps to pad 3 and it sends out a C4 on output 3. That's how it used to work and how it still works. But now when C3 is received it maps to pad 1 and now it sends out a C3 on output 1. (previously that was still C4) When G5 is received it maps to pad 8 and now it sends out a C5 on output 8. (previously that was still C4) Also the drum labels reflect this. This feature simply gives more musical options. Attention: This impacts already projects or presets using a DNP receiving notes outside the [C4-B4] range. This attention note is shown in an alert when opening a possible impacted project or preset.

Just one simple question:

Why do drum notes have to be spread and replicated across multiple octaves?
what good is it?

Wouldn't it be easier to create a 4x4 matrix of fixed notes from C4 to D#5?

PROS:
1. The layout would be cleaner, now it has a pyramidal structure that does not comply with the standard 4x4 pad.
2. In the "doubled mode" (24 notes), the interface is messy and unusable, the pads are thin and 24 drum sounds is probably too many.
3. Furthermore, in the current mode, you might play with a keyboard a cymbal (for example) in the far upper octaves and end up with scattered notes on the piano roll.
This, for example, is something that happens to me often, and I have to correct it on the piano roll by lowering the octave.

CONS:
none !!

I understand your idea of ​​a modular sequencer, dedicated mainly to those who perhaps draw the notes rather than play them live, but you should keep in mind that the use of external controllers is very extensive, and above all it is FUN!!
This necessarily requires a certain degree of standardization by software developers to adapt to the hardware that will connect to it
IMHO

[MuTools]

Why do drum notes have to be spread and replicated across multiple octaves?
what good is it?

Because it's easy and fun to play on a MIDI keyboard.
And when you know kick is on C, snare on D, it's easy to find them back, whatever the octave.

Wouldn't it be easier to create a 4x4 matrix of fixed notes from C4 to D#5?
PROS:
1. The layout would be cleaner, now it has a pyramidal structure that does not comply with the standard 4x4 pad.

I guess you're referring to the standard 4x4 on many drum hardware?

Well a big advantage of the 'conic' 3+4+5 pads layout (and the 7+8+9 in doubled mode) is that it is easy to see where the cables go to.

2. In the "doubled mode" (24 notes), the interface is messy and unusable, the pads are thin and 24 drum sounds is probably too many.

Note that when switching an existing MuDrum preset from 12 to 24 it will practically need an update of the front panel. Front panels are never updated automatically, that would be way too complex as components can be at any place, it really needs the designer to update a panel. The 24 pads mode is rather meant to create new customized drum kit presets.

3. Furthermore, in the current mode, you might play with a keyboard a cymbal (for example) in the far upper octaves and end up with scattered notes on the piano roll.
This, for example, is something that happens to me often, and I have to correct it on the piano roll by lowering the octave.

I don't understand what you mean here. Can you please explain in more detail? What do you mean with "scattered notes"?

I understand your idea of ​​a modular sequencer, dedicated mainly to those who perhaps draw the notes rather than play them live, but you should keep in mind that the use of external controllers is very extensive, and above all it is FUN!!

Rest assured that i fully agree on the fun and creativity of music hardware!!
It's most important in music making as it stimulates The Feel.

This necessarily requires a certain degree of standardization by software developers to adapt to the hardware that will connect to it

I assume you're referring to drum hardware, right?

[Bax9]

Sure it's good to have the octaves replicated when playing drums on a keyboard, but these days I doubt a musician would play a keyboard to make a drum groove and have fun

Nowadays so many controllers integrate a 4x4 matrix with the keyboard !
Furthermore, if you want to do finger drumming, drum and bass etc. the 4x4 structure is obviously ideal.

If I use a drum pad with Mulab, the four upper pads replicate the four lower ones.
What's the point?
And I miss the opportunity to have, for example, four percussion pads to enrich the rhythm.

Or, if I switch on the 24 pad arrangement, I will use only 16 pad.

"Scattered Notes": If I play and record a keyboard groove with the kick drum set to C4, and then accidentally add a percussion piece starting at C6 (because I played a melody earlier and forgot to switch back the octave on my mini 2-octave keyboard controller), I'll end up with the percussion far from the groove on the piano roll, the piano roll view will zoom out or even I won't find the new part just recorded immediately because it's too far from the groove.

You will say that I can fix it, but my workflow will suffer a little

That said, I'm expressing my opinions in the hope of helping to improve a product that is already truly exceptional

[MuTools]

Nowadays so many controllers integrate a 4x4 matrix with the keyboard !
Furthermore, if you want to do finger drumming, drum and bass etc. the 4x4 structure is obviously ideal.

In the next update the Drum Note Processor will have many more layout options:

P7.png

I could add some more like eg. 2,3,1+2,2+2,2+3,1+2+3,3+3,2+3+4,3+3+3, but also want to avoid overkill. What's your advice?

If I use a drum pad with Mulab, the four upper pads replicate the four lower ones.
What's the point?

To be honnest i wasn't aware that on a keyboard the lower row pads are the first keys, ie it's sorted bottom-up while MuLab's DNP is sorted top-down. Thx for teaching me that. Taken note to take that into account as an option.

[Bax9]

Just great!!!
I think it's enough to keep the classic to accomodate the older view, and a new 4x4 for the pads lovers
A classic 16 pieces Is enough to have a good set of drum and percussions
It could even be used to make a MPC-like set of spare samples and grooves for live performances!

[MuTools]

MuLab App M10.2.12 beta for Windows 64 bit is available:
https://www.mutools.com/mulab/app/lates ... /beta.html

What's changed:

Drum Note Processor now has many more options:
You can change the number of pads, change the pad layout, choose bottom-up row layout, choose a different root key. All this is possible via the DNP's options menu -> Setup.

These options are also available, be it in a polished version, from a DNP on a front panel, eg. in the factory MuDrum presets. Right-click in between the pads to access that context menu.
Note that front panels are assumed to be used in a more musical, less techy context and that's why that option menu has been polished for that context.
Changing the number of pads is regarded as a techy thing because if the number of pads increases you will need to go into the modular area to setup the sound modules (eg MUXes or plugins) for these new pads.

Practical Note: If you have saved projects or presets which use a Drum Note Processor module using beta versions M10.2.9, M10.2.10 or M10.2.11 then please load and resave these files using M10.2.12 because in a next update DNP data saved with one of these 3 versions won't be recognized anymore. If you're in doubt, use the MuLab menu -> Tools -> List MuTools Files Version, a handy tool to keep your MuLab files up to date.

[pljones]

(EDIT replaced -- this was a reply to an earlier post before .12 was release. The long list has gone.)

Only thing now is the "Setup" should be available on right-clicking the DNP background as well, if possible, rather than only in the star menu. It's definitely not working on double, left or right-click

[Rodulf]

Will there be a beta for the plugin?