MuTools

Taifunk · Post by **Taifunk** » Sun Apr 17, 2016 3:07 pm

Ok, Thanks Jo.

pljones · Post by **pljones** » Sun Apr 17, 2016 4:36 pm

mutools wrote:

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".

Thanks, yes that feels a lot nicer to use. Maybe the scaling could be tweaked -- beyond 675% there's no visible movement here.

MuTools · Post by **MuTools** » Sun Apr 17, 2016 4:49 pm

It will always be a balance. I think the values around in the 0 - 200% range are the most important. But then at the same time i also took into account to give enough room to the 200% - max range. And i also took into account a as smooth transition as possible between the 0% - 100% range and the 100% to maximum. That's how the scaling was chosen. A length of 675% (i.e. almost 7 steps) will be an exceptional value anyway, i think.

Taifunk · Post by **Taifunk** » Sun Apr 17, 2016 11:31 pm

I tried to replicate the crash previously reported,really did a lot of tests but nothing happens at the moment.

Michael L · Post by **Michael L** » Mon Apr 18, 2016 12:51 am

Is there any way for a user to save Step Sequencer v 7.022 along with 7.023?

MuTools · Post by **MuTools** » Mon Apr 18, 2016 7:12 am

Hey Michael, i don't understand the question. Step sequencer files for both versions are identical.

Michael L · Post by **Michael L** » Mon Apr 18, 2016 7:27 am

Yes, it wasn't very clear! In the 7.0.23 version:

mutools wrote:Step sequencer: Length and Offset values are always displayed as knobs

In the previous version one could have all sliders. I like all sliders (while I understand why you chose both), so I was wondering if it is possible to have both "versions" of the Step sequencer?

MuTools · Post by **MuTools** » Mon Apr 18, 2016 7:29 am

Taifunk wrote:I tried to replicate the crash previously reported,really did a lot of tests but nothing happens at the moment.

Thx for the update. Such a pity i missed the necessary files to look up the crash the first time it happened, because your report came just after i started compiling M7.0.23, an unfortunate timing coincidence. Some questions: When exactly did the crash happen? Was it while you were dragging MPE points? Were there VSTs involved when the crash occurred? Were it MPE loop points? Was the sound playing meanwhile? Any other details you can remember?

I tried to repeat the crash by driving a very intense note sequence to your Phase Distortion patch while intesively editing the MPE in there. No crash yet.

MuTools · Post by **MuTools** » Mon Apr 18, 2016 7:32 am

Michael L wrote:Yes, it wasn't very clear! In the 7.0.23 version:
mutools wrote:Step sequencer: Length and Offset values are always displayed as knobs
In the previous version one could have all sliders. I like all sliders (while I understand why you chose both), so I was wondering if it is possible to have both "versions" of the Step sequencer?

No that's not supported. Just out of curiosity: Why do you like a slider display for length and offset more than the knob? I think the knob not only looks better (especially after i tried a bipolar slider for offset), but it also is a better representation of what's going on, because a knob has more left-right feel than a vertical slider and length and offset are time-line properties which is also left-right oriented. Curious for your view.

Michael L · Post by **Michael L** » Mon Apr 18, 2016 7:49 am

mutools wrote:Why do you like a slider display for length and offset more than the knob

It's a workflow thang. I first choose the key/chords, then the sequence, then change velocity/ length/ offset together. Because they are related, I tab back and forth comparing v/l/o patterns. It is way easier for me to compare "all sliders." Without that option now, I will choose "all knobs" and a knob design with a thick ring.

MuTools · Post by **MuTools** » Mon Apr 18, 2016 8:18 am

Thx for your explanation. I understand that all values on the same tab, eg all velocity values or all length values, must have the same widget to easily compare values, which is the case. What i don't understand is that you want to compare eg velocity values with length values, they have completely different units.

Michael L · Post by **Michael L** » Mon Apr 18, 2016 8:50 am

mutools wrote:they have completely different units.

True, but I create a groove in a sequence by changing velocity and length together to create the pattern I hear in my head: ba-baaaa-ba-BOOM or BAAAA-ba-ba-boom. Because I can't see both at the same time, I tab between to listen/ see the patterns. I'm sure other people do it differently.

MuTools · Post by **MuTools** » Mon Apr 18, 2016 9:55 am

pljones wrote: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...

In the next version it will be possible to save a New.MuStepSequencer preset file in your user library and then that preset will automatically be opened upon inserting a new Step Sequencer.

runaudio · Post by **runaudio** » Mon Apr 18, 2016 10:44 am

Just Messing Around

Taifunk · Post by **Taifunk** » Mon Apr 18, 2016 11:39 am

mutools wrote:
Taifunk wrote:I tried to replicate the crash previously reported,really did a lot of tests but nothing happens at the moment.
Thx for the update. Such a pity i missed the necessary files to look up the crash the first time it happened, because your report came just after i started compiling M7.0.23, an unfortunate timing coincidence. Some questions: When exactly did the crash happen? Was it while you were dragging MPE points? Were there VSTs involved when the crash occurred? Were it MPE loop points? Was the sound playing meanwhile? Any other details you can remember?

Thanks Jo and sorry for the inconvenience,
Ok if I remember correctly I opened a new project and loaded the patch
No other vst/modules or other track/sequence in mulab,one rack active and only playing the patch with the midi keyboard.
Modules active,mfo,two adsr(for the amplifier and wave index)and an mpe with modulation mapper for wi.
Start editing the mpe,set the value grid and added two point and the loop set at the start/end ,ten beat in total then added e dragged several point,no other action and mulab suddenly crashes.

mutools wrote: I tried to repeat the crash by driving a very intense note sequence to your Phase Distortion patch while intesively editing the MPE in there. No crash yet.

I did exactly the same thing, and also tried with other patches, modules and made several stress tests,zero crash.

MuTools

KVR Audio

MuLab 7.0.47