MuLab 8.0.66

[MuTools]

Ahh, it's an old Imperial Units metaphor!
six = half dozen

Oh ok i see

one less menu level = using a shortcut key
Thus no net benefit, n'est-ce pas?

Not sure if we're talking about the same, maybe i did not explain it not good enough.
What i mean is this: Imagine you have assigned the [D] key to the Sample -> DSP sub-menu. Then even without any menu open, pressing [D] in a sample context will popup a slim menu with only the sample DSP functions. So it's the same as how shortcuts work now but instead of triggering a single specific function it triggers opening a specific sub-menu as a main menu. Such function could also be handy for the Sequence -> Functions. Eg pressing [F] in the sequence editor could popup a menu with only the sequence functions (Transpose, Quantize, Rotate, ...)
Hope i explain it better now.

[sl23]

Ah ok I thought that moving away from the sub group would close that menu, not moving from the parent item

[Michael L]

pressing [D] in a sample context will popup a slim menu

Contextual shortcut keys, to open submenus is a neat idea! I would assign [M] to all of my favorite submenus.

[RichardSemper]

Contextual shortcut keys, to open submenus is a neat idea! I would assign [M] to all of my favorite submenus.

+1

[charlesnavi]

Auto-close on leaving an auto-opened sub-menu won't work as when you have auto-opened a sub-menu and move down to the first item in that sub-menu that would immediately close it then.

in the next version the default setting for "Open Sub-Menu Delay Time" is "Never". So the option to use it remains, but it's disabled by default.

Yeah, I guess making "Never" the default value is good enough. I agree Jo shouldn't be wasting time on this. There must be many other much more important features he'd like to work on.

[pljones]

Auto-close on leaving an auto-opened sub-menu won't work as when you have auto-opened a sub-menu and move down to the first item in that sub-menu that would immediately close it then.

In other apps (e.g. Microsoft Windows Notepad, Mozilla Firefox), a sub-menu knows it has a parent and it's when the parent changes that the sub-menu closes. Hence selecting another sibling item doesn't close the sub-menu, as the parent is the same. (And all the way up the menu tree, to check closing each level.)

For me, the new system works okay - it's less different than before, I just need to tune my open delay to the same as I have for Windows, I guess.

[sl23]

Thank you plJones for explaining better
'And, apologies for past regressions!

[wizetek]

Any plans to implement the ability to map MIDI controller to tracks in addition to racks? (Mute/Unmute/Solo/Unsolo)

There is an old thread about that here -- viewtopic.php?f=79&t=419647

Thanks for all your amazing work!

[MuTools]

M8.0.50 is available in http://www.mutools.com/mulab/m8/

What's changed:

• Fixed a bug that could cause missing notes or double notes when sequencing a step sequencer.
• Fixed a crash bug when saving a step sequencer preset while it was also opened in a front panel.
• Audio sequence editor: Right-clicking a fade in/out control now gives the option to reset the fade. This also works on a selection of events.
• Open Sub-Menu Delay preference now defaults to "Never".

How to update:
Windows: Replace the current MuLab.exe and MuLab.ID by the new versions.
MacOS: Replace the current MuLab.app by the new version.

Note: In order to fix that missing note/double note sequencing bug i had to make some deep changes in the sequencer engine. Far from ideal so close to release. But i had no choice. I'd appreciate if you guys could give M8.0.50 some extra testing time and sequence the hell out of it, especially sequencing from the composer to step sequencers, that's the most sensitive area. Please let me know if you hear unexpected double / missing note events, or anything else that sounds odd wrt sequencing. Thx!

[robbluda]

"- Audio sequence editor: Right-clicking a fade in/out control now gives the option to reset the fade. This also works on a selection of events"
It would be good, if "Reset" function also set the curve to "linear" (as it was at the beginning, before the chanche).

[MuTools]

Ok that has been added in the next M8.0.51.

[RichardSemper]

Been checking the Step sequencer. (Disclaimer - haven't used it much before)
At first i thought i was getting missing notes at the start of sequences, but then realised my notes were not properly quantised. That fixed it!

I noticed that when Tempo Factor is set to anything other than 100% the visual feedback is no longer in sync with the sound - it continues at same rate as if factor was 100%
Changing Tempo Factor during playback often causes stuck notes - requiring panic button to reset.

Also whenever an Arp pattern (1-5 from the top presets) has been loaded I cannot find a way to return to arpeggiator modes which are greyed out, so have to reload the step sequencer from scratch.[EDIT: discovered a workaround - saved a test INIT preset which allows Arpeggiator modes - can reload this]

[sdv]

I always stated I didn't need time stretching. But I never realized its uses. I just thought it was for matching loops to a tempo.

Yeah, I didn't think I'd use the slice & stretch but after seeing the new video I have some new ideas how to implement the new features.

[bibz1st]

Been checking the Step sequencer. (Disclaimer - haven't used it much before)
At first i thought i was getting missing notes at the start of sequences, but then realised my notes were not properly quantised. That fixed it!

I noticed that when Tempo Factor is set to anything other than 100% the visual feedback is no longer in sync with the sound - it continues at same rate as if factor was 100%
Changing Tempo Factor during playback often causes stuck notes - requiring panic button to reset.

Also whenever an Arp pattern (1-5 from the top presets) has been loaded I cannot find a way to return to arpeggiator modes which are greyed out, so have to reload the step sequencer from scratch.[EDIT: discovered a workaround - saved a test INIT preset which allows Arpeggiator modes - can reload this]

Yea the tempo issue is the same here, with regards to the Arp problem, its because the presets have the "Pattern Notes = Select And Play" turned on within the Options.

[MuTools]

I noticed that when Tempo Factor is set to anything other than 100% the visual feedback is no longer in sync with the sound - it continues at same rate as if factor was 100%

Fixed in the next M8.0.51.

Changing Tempo Factor during playback often causes stuck notes - requiring panic button to reset.

You're right. Now i wonder whether it makes much sense to have a tempo factor there, the step sequencer already has so many controls so it's close to getting bloated. The Steps/Beat already does almost the same and is more instantly usable. So i tend to remove the tempo factor from the step sequencer. Sounds right?

Thanks for reporting these issues.