MuLab 8.0.66
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
M8.0.56 is available in http://www.mutools.com/mulab/m8/
What's changed:
Windows: Replace the current MuLab.exe and MuLab.ID by the new versions.
MacOS: Replace the current MuLab.app by the new version.
NB: Versions M8.0.53-M8.0.55 were unpublished.
What's changed:
- Menus and treelists: Arrow left closes parent group, also when pressed on a closed group.
- Quantize Adjacent Events now also in audio sequence function group.
- Oscillator layers editor: Drift parameter was not grayed for unused layers. Fixed.
- Composer: Merging non-audio sequence parts popped up an irrelevant question. Fixed.
- Right-click = Delete Notes preference: Now this is limited to right-clicking the start/end of a note.
Also [Ctrl]+clicking a note to delete it must be on the start/end of a note.
By these changes [Ctrl]+click / right-click to delete a note use a same method.
And a right-click on the body of an event can still open the context menu. - Sequence editor: Playing labeled keys (eg MuDrum keys) could play another key than expected. Fixed.
Windows: Replace the current MuLab.exe and MuLab.ID by the new versions.
MacOS: Replace the current MuLab.app by the new version.
NB: Versions M8.0.53-M8.0.55 were unpublished.
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
M8's time stretching can also be used in sampler modules.
Using more extreme stretch factors, interesting soundscapes can arise.
Using more extreme stretch factors, interesting soundscapes can arise.
-
- Banned
- 262 posts since 28 Nov, 2017 from Azerbaijan,Baku
Mister Jo pls add some hit,orchestral hit into library.Hit like this,listen it
https://drive.google.com/open?id=1r4PgT ... 64-kkHQdQN
Daw without hit ?
https://drive.google.com/open?id=1r4PgT ... 64-kkHQdQN
Daw without hit ?
-
- KVRist
- 67 posts since 26 Jan, 2016
Been playing with the step sequencer and found some weirdness. The knobs within the grid (LEN, OFS etc.) keep incrementing their value (in the digit info field) despite knob rotation reaching its full clockwise limit. Also in the Mod Group section, typing a number into the LEN box just jumps to the full 400%.
I have been experimenting with the step sequencer driving individual sequencer modules without any use of the main timeline sequencer, i.e. I don't press the play button. Both the step sequencer and sequencer respond to tempo but don't seem to line up with each other. To be specific :
I set up a step sequencer for 32 steps with one event on step One (step per beat=4 so 2 bars). I adjust the length to max and also Mod Group to max. This should create a midi-on event on step One and a midi-off event at the end of step 32? I use the output to drive a sequence module with a 2 bar sequence and thought this sequence would re-trigger correctly at step 1 as the step sequencer loops. Well it seems OK until you change to another pattern in the step sequencer when the triggered sequence runs over to the next loop of the step sequencer and stops somewhere in the middle. It's as if the step sequencer and sequencer module are running on different tempos.
Running the main sequencer seems to pull them together but I wondered why that was necessary? What I am trying to do is set up live versions of my songs whereby various step sequencer patterns switche "scenes" consisting of my various sequences. Bit like Ableton really, but I just love Mulab that I can't bring myself to use anything else!!!!
Thanks!!!
Paul
I have been experimenting with the step sequencer driving individual sequencer modules without any use of the main timeline sequencer, i.e. I don't press the play button. Both the step sequencer and sequencer respond to tempo but don't seem to line up with each other. To be specific :
I set up a step sequencer for 32 steps with one event on step One (step per beat=4 so 2 bars). I adjust the length to max and also Mod Group to max. This should create a midi-on event on step One and a midi-off event at the end of step 32? I use the output to drive a sequence module with a 2 bar sequence and thought this sequence would re-trigger correctly at step 1 as the step sequencer loops. Well it seems OK until you change to another pattern in the step sequencer when the triggered sequence runs over to the next loop of the step sequencer and stops somewhere in the middle. It's as if the step sequencer and sequencer module are running on different tempos.
Running the main sequencer seems to pull them together but I wondered why that was necessary? What I am trying to do is set up live versions of my songs whereby various step sequencer patterns switche "scenes" consisting of my various sequences. Bit like Ableton really, but I just love Mulab that I can't bring myself to use anything else!!!!
Thanks!!!
Paul
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
That's intended. Thing is that the range of the Length value is much bigger than the range of the knob. So the knob does an exponential value increase: The most relevant small values get most knob range, the bigger values are near the end of the knob range. Does this clarify it?smithoid wrote: Sat Mar 30, 2019 10:54 am The knobs within the grid (LEN, OFS etc.) keep incrementing their value (in the digit info field) despite knob rotation reaching its full clockwise limit.
I see, that looks like a little bug. I've taken note about it. Thanks for reporting this!Also in the Mod Group section, typing a number into the LEN box just jumps to the full 400%.
Please email me a little project (no VSTs pls) that demonstrates the issue. Thanks.I have been experimenting with the step sequencer driving individual sequencer modules without any use of the main timeline sequencer, i.e. I don't press the play button. Both the step sequencer and sequencer respond to tempo but don't seem to line up with each other. To be specific :
I set up a step sequencer for 32 steps with one event on step One (step per beat=4 so 2 bars). I adjust the length to max and also Mod Group to max. This should create a midi-on event on step One and a midi-off event at the end of step 32? I use the output to drive a sequence module with a 2 bar sequence and thought this sequence would re-trigger correctly at step 1 as the step sequencer loops. Well it seems OK until you change to another pattern in the step sequencer when the triggered sequence runs over to the next loop of the step sequencer and stops somewhere in the middle. It's as if the step sequencer and sequencer module are running on different tempos.
Running the main sequencer seems to pull them together but I wondered why that was necessary?
I very much understand your goal and i know you're not the only one who wants that !What I am trying to do is set up live versions of my songs whereby various step sequencer patterns switche "scenes" consisting of my various sequences. Bit like Ableton really, but I just love Mulab that I can't bring myself to use anything else!!!!
-
- KVRer
- 17 posts since 13 Nov, 2017
Another bug: The shift+scroll wheel to change velocity of events in tens seems to be missing in M8
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
-
- KVRist
- 67 posts since 26 Jan, 2016
That exponential value increase solves the problem! Although I thought the knob was fully clockwise, I was actually at some random value. I now see the figure in the info box is: number of steps x 100. Getting the correct number of steps makes everything line up as expected.
Looks like my "live" method is a go-er
One last question.... is there a way to enter a value directly for LEN in the grid? Or can I only do it by dragging the knob? The "alt" click method sadly doesn't work to get max; it just deletes the event as per a normal click.
Thanks again!
Paul
Looks like my "live" method is a go-er
One last question.... is there a way to enter a value directly for LEN in the grid? Or can I only do it by dragging the knob? The "alt" click method sadly doesn't work to get max; it just deletes the event as per a normal click.
Thanks again!
Paul
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Currently not.smithoid wrote: Sat Mar 30, 2019 1:02 pm is there a way to enter a value directly for LEN in the grid? Or can I only do it by dragging the knob?
- KVRAF
- 3161 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Me too!!!smithoid wrote: Sat Mar 30, 2019 10:54 amI just love Mulab that I can't bring myself to use anything else!!!!
MuLab is simple and elegant compared to other DAW's, even if it lacks certain features
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
M8.0.57 is available in http://www.mutools.com/mulab/m8/
What's changed:
Windows: Replace the current MuLab.exe and MuLab.ID by the new versions.
MacOS: Replace the current MuLab.app by the new version.
What's changed:
- When previewing audio files from disk, but that file was already loaded as a sample (and maybe edited), then that sample was previewed instead of the original audio file. Fixed.
- Sequence editor: [Shift]+dragging/wheeling velocity values did not step by 10 anymore. Fixed.
- Samplers: [Shift]+dragging/wheeling the stretch factor now steps by 100. (was 1000, which was too much)
- Finetuned the description of the Right-Click Notes = Delete Notes preference.
Windows: Replace the current MuLab.exe and MuLab.ID by the new versions.
MacOS: Replace the current MuLab.app by the new version.
- KVRAF
- 3161 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- KVRAF
- 1670 posts since 13 Jan, 2014
I am a little bit puzzled opening Mulab 8 beta 0.56 that program told me that my user key will expire in 10 days, I thought it was a permanent one already (at least I entered a second one after the temporary one sent to me as "Your Personal MuLab 8 User Key") ?
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe

