MuLab 7.0.47

[pljones]

"Keep spinning" - yes, as you drag, the knob would not stop at all until the displayed value stops. So dragging upward, it would pass through 100% and carry on spinning, making further circuits around the dial. If the value is 250%, the knob currently points to 100%, which is the "wrong" value, so to point at wherever 250% would be would be less wrong...

Just one other thing (on the minor irritation list ) -- is there any way to get the Step Sequencer Options to save as my preferred defaults? Ideally, I'd like to be able to choose per tab whether to display knob or graph and have that saved as my preference...

[MuTools]

it could also be a little odd if the first step and the last step have the same value but work differently (i.e. you set both to 50% of the sequence length - the first one takes half the sequence length, the last one only one step).

No, not relative to the remaining sequence length but relative to the loop length. Any 50% value would be displayed the same.

[pljones]

Yes, so if the loop is 8 steps, if step 1 is set to 50% of the loop length it plays through to step 4 but if step 8 is set to 50% it plays to step 8. So in the first case, 50% means 4 steps and in the second case 50% means 1 step. Or have I still not understood? (Is the gate time not trimmed to the loop length?)

[MuTools]

Yes, so if the loop is 8 steps, if step 1 is set to 50% of the loop length it plays through to step 4 but if step 8 is set to 50% it plays to step 8. So in the first case, 50% means 4 steps and in the second case 50% means 1 step. Or have I still not understood? (Is the gate time not trimmed to the loop length?)

A step's length value is expressed in percent of the step length. So a 100% value in a 4 steps per beat pattern means: Step length = 100% of 1/4th of a beat. What we're talking about is about how these values are displayed.

[MuTools]

Thinking further: If it's important that the value slider/knob always displays a correct unlimited value (i can understand that wish), then the display value should be relative to the sequence length, no doubt. Now to counter the fact that the most frequently used step length values (around 50% - 100%) would be displayed as too low values, a non-linear curve could be applied so that the eg 100% step length value is mapped to 50% display value. Sounds like a possible solution for me. What do u think?

[pljones]

OK, got it -- I'm being very slow this morning... I managed to completely misread your earlier post. I'd agree it could allow more space using the beat rather than the step -- but that's about all. Although, I'd have thought most of the time, it would be the step itself you're interested in, rather than the beat, so getting more detail at that level would be better? (Other opinions needed!)

Anyway, I'm just thinking of the various ways a MUX front panel value can be displayed (knob, horizontal, vertical) and wondering how the various parameters could be displayed in the step sequence based on that, having really just looked at this for the first time.

For instance, I'm used to pitch being a vertical-associated value, so the Transpose value could fill from centre vertically up or down to follow the transpose amount (rather than just being a number). So could Octave.

Similarly, I see generally time-based values as expressed horizontally, hence suggesting gate time and offset be horizontal, the latter centre-out. And having some "off scale" indicator when the cell is overflowed just hints that the user needs to look at the value not just the graphic.

In all cases, an easy way to type the value in would be convenient. Double-click looks to be out (as single click toggles the cell), so the edit value on the right-click menu would be handy.

[Michael L]

OK, here's another opinion:
1. As a performance sequencer, its important to quickly scan the steps to see the pattern of Vel, Len, etc, so a consistent up/down direction helps clarity. Switching among x/y axes for different parameters would be tiring for me to compare parameters for the same steps.
2. A display that shows difference among commonly-used note lengths (eg sixteenth to whole) is important. A non-linear curve may make differences in those note lengths less visually apparent, and perhaps difficult to scan.
3. The current 100/100 scale is intuitive, but pljones' idea that the box change colour if a Len or Ofs is >100 will make a pattern of >100 easier to see. (I assume that Len or Ofs >100 will be uncommon.)
4. I don't scroll, but drag which is fast enough for me.

[sl23]

For instance, I'm used to pitch being a vertical-associated value, so the Transpose value could fill from centre vertically up or down to follow the transpose amount (rather than just being a number). So could Octave.

Similarly, I see generally time-based values as expressed horizontally, hence suggesting gate time and offset be horizontal, the latter centre-out. And having some "off scale" indicator when the cell is overflowed just hints that the user needs to look at the value not just the graphic.

In all cases, an easy way to type the value in would be convenient. Double-click looks to be out (as single click toggles the cell), so the edit value on the right-click menu would be handy.

Agreed

[Taifunk]

I am encountering a crash in mulab when using multipoint envelope as a modulation source for mfo wave index
with the following scheme: mpe/modulation mapper/mfo wave index
mulab stops completely and does not appear any error messages
I posted the patches in the other thread ,are very simple, nothing that can create strange cpu increases or strange things.
Crash suddenly appears while edit the mpe points and I can not replicate.

Edit: I forgot,
the patch has three modulation sources, an adsr, a lfo and an mpe
but the problem only happens with the mpe as a modulation source for mfo wave index.

[MuTools]

About the step sequencer value displaying: I've taken several of the above considerations into account, pls try out the next version when it is available, i expect later today. However inputting values by text in the step sequencer is not for M7.0, maybe later.

[MuTools]

I am encountering a crash in mulab when using multipoint envelope as a modulation source for mfo wave index with the following scheme: mpe/modulation mapper/mfo wave index
mulab stops completely and does not appear any error messages
I posted the patches in the other thread ,are very simple, nothing that can create strange cpu increases or strange things. Crash suddenly appears while edit the mpe points and I can not replicate.
Edit: I forgot,
the patch has three modulation sources, an adsr, a lfo and an mpe
but the problem only happens with the mpe as a modulation source for mfo wave index.

I see 6 MUX presets in that latest zip file. Which of them do i use best to repeat the crash? What steps do i have to take? Can you pls also email me the Windows crash report that states the modules name and crash address offset. Thx.

[Taifunk]

the crash happens with the phase distortion and sync preset ,when modifying various points in multipoint envelope.
I'm going to send a email with the crash report.

[MuTools]

There is a new MuLab 7.0.23 in http://www.mutools.com/galaxa/mulab/

What's changed:

• Step sequencer: Scrolling/sliding Length and Offset values now take the practical maximum value into account, which is the pattern's loop length.
• Step sequencer: The Length and Offset slider/knob display value now is not clipped at 100% anymore, but the whole practical value range is taken into account. The 100% step length value is shown as the 50% display value. The values above 100% up to the maximum are shown in a proportional way.
• Step sequencer: Length and Offset values are always displayed as knobs. (so in fact only velocity values can be switched between slider and knob)
• "Convertors" -> "Converters".

How to update:
Make sure you already have installed the complete M7.0.12 package. Then:
OSX: Replace the existing M7 MuLab.app file by the new version in the small zip file.
Windows: Replace the existing M7 MuLab.exe and MuLab.ID files by the new versions in the small zip file.

[MuTools]

As you can see the Length and Offset values now always use a knob display.
The middle position for lengths = 100% = full step length.
The middle position for offset = 0% = no offset. The Offset knob is a bipolar one. Going to the left will shift the event to the left, going to the right will shift the event to the right.

For me this updated way of displaying/editing the Length and Offset values in the Step Sequencer is fine. An improvement indeed, thx to everyone's feedback.

[MuTools]

the crash happens with the phase distortion and sync preset ,when modifying various points in multipoint envelope. I'm going to send a email with the crash report.

Thx. Replied via email.