MuTools

MuTools · Post by **MuTools** » Fri Apr 15, 2016 10:11 pm

Thx for reporting this. Fixed in the next version. Sorry about the inconvenience.

Taifunk · Post by **Taifunk** » Fri Apr 15, 2016 10:52 pm

Thanks ,no problem

a bit off topic:
I just finished to optimize the PC and the system, now using a multicore setup,works everything great and perfect, I also edited the post in the other thread.
I solved many problems,Thanks for the advice Jo.

MuTools · Post by **MuTools** » Sat Apr 16, 2016 11:58 am

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

What's changed:

Just clicking in a waveform is not interpreted as a change anymore.
Step sequencer: Fixed a practical issue wrt mouse-wheeling velocity values.
Step sequencer: Moving a lane up/down now also moves that lane's steps.
Step sequencer: Moving a lane up/down now is an undoable action.
Step sequencer: Copying a lane definition up/down now is an undoable action.
Fixed a problem with pasting a color value into a color box that is set to auto color.

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.

runaudio · Post by **runaudio** » Sat Apr 16, 2016 12:17 pm

Step Seq midi cc vel is val mistake

MuTools · Post by **MuTools** » Sat Apr 16, 2016 1:00 pm

How do u mean? Sorry if i'm missing something obvious.

runaudio · Post by **runaudio** » Sat Apr 16, 2016 1:08 pm

Sorry my Mistake

Taifunk · Post by **Taifunk** » Sat Apr 16, 2016 4:41 pm

Thanks for the update Jo

pljones · Post by **pljones** » Sat Apr 16, 2016 7:49 pm

Trivial minor inconsistency:
Add Module->Modules->Convertors->(a list of converters). (The latter passes spell check

.)

Trivial point of irritation:
Why can't the Module menu open at the current module when I select "Replace"?

Fun thing to try:
Rack 2 - sine wave generator at -6dB, 440Hz
Rack 3 - sine wave generator at -6dB, 440Hz
Now try to get 0dB on Master - you need to enable both sine waves so they're properly in phase. I've got anything from -28dB to -0.2dB

MuTools · Post by **MuTools** » Sat Apr 16, 2016 9:20 pm

pljones wrote:Trivial minor inconsistency:
Add Module->Modules->Convertors->(a list of converters). (The latter passes spell check .)

Fixed in the next version. Thx.

Fun thing to try:
Rack 2 - sine wave generator at -6dB, 440Hz
Rack 3 - sine wave generator at -6dB, 440Hz
Now try to get 0dB on Master - you need to enable both sine waves so they're properly in phase. I've got anything from -28dB to -0.2dB

Sounds logical as these sines are out of phase and so adding them can go from -oo dB to 0 dB.

pljones · Post by **pljones** » Sat Apr 16, 2016 10:07 pm

Yes... what got me confused was managing to get above -1dB for the first six goes... and then around -30db for the next few. That's just what random chance does, of course. Gut instinct looks for patterns when there are none, so I started off thinking they were meant to be in phase but not quite right - until I got the way off 0dB ones, of course.

pljones · Post by **pljones** » Sat Apr 16, 2016 10:45 pm

More minor bits...

Set the step sequencer tab to "Len" to adjust the gate length. Use the mouse to increase the value until it stops rising. Or until you get bored...

Switch the indicator to knob mode. The knob goes to 100 at the end of its natural range... but just carry on dragging... Same with offset (but bidirectionally).

It would be handy to know (either on screen or in the docs) what the units are for the gate length, too.

MuTools · Post by **MuTools** » Sun Apr 17, 2016 7:33 am

pljones wrote:Set the step sequencer tab to "Len" to adjust the gate length. Use the mouse to increase the value until it stops rising. Or until you get bored... Switch the indicator to knob mode. The knob goes to 100 at the end of its natural range... but just carry on dragging... Same with offset (but bidirectionally).It would be handy to know (either on screen or in the docs) what the units are for the gate length, too.

That's intended. The length and offset have no real upper limit. They're expressed in percentage of 1 step length. And 1 step length is 1 beat divided by the number of steps per beat. The slider/knob indicator can only show up to 100% = 1 step length. But you can scroll to higher values, eg 200% = 2 steps, which are shown in the value display. Does this clarifies it?

MuTools · Post by **MuTools** » Sun Apr 17, 2016 9:21 am

An alternative could be to display lengths and offset relatively to the pattern loop length, as that's the practical maximum. But the consequence then is that most gate lengths will be displayed as very low values, cause, for example, if you have a 16 step pattern a 50% gate length is displayed as 50%/16 = only 3% of the slider/knob range. It doesn't look ok to me, i tried it. Even when gate length = 100%, then the slider box looks almost empty in 16 step pattern.
Thinking further, a compromise could be to always display the length/offset values relative to 1 beat. So if Num Steps Per Beat is 4, then a 50% length will be displayed as 50%/4 = 12.5% of the slider/knob range. You can still tweak the value higher (up to the pattern loop length) but the slider/knob won't be able to show values beyond 1 beat, like it is now (but now the display max is 1 step). Attached a screenshot that shows length values relative to 1 beat. Shown values are 50%, 100%, 200% and 300%. What do u think?

p1.png

NB: For now i'll keep it as is thus a length value of 100% is displayed as 100% slider/knob value.

pljones · Post by **pljones** » Sun Apr 17, 2016 9:27 am

I thought that was probably the reason but it's not the clearest user interface to use... Particularly in "knob" view, the "upper limit" on the knob feels "broken" as it stops moving yet the value continues changing. Maybe the knob should just keep spinning freely as its position currently can be "non-indicative"? I'd also suggest the "graph" view display left to right for Length and centre outward left (negative)/right (positive) for Offset, rather than just the vertical fill. That might also help give a sense of what's going on.

With your alternative, I can see the downsides you mention -- 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). Maybe add a red line (like when a level meter clips) to show that the step's actual value has gone above one step.

It would also be easier if I could type the value in. As it is, if I want to make a very large change, I have to scroll a long, long way. Could you add an "Edit {whatever}" to the right-click menu ("{whatever}" being the selected tab), that then prompts (similar to other controls)?

It's got a lot of depth (which I've yet to explore!) whilst also allowing very simple enhancements to existing patches that are very creative.

MuTools · Post by **MuTools** » Sun Apr 17, 2016 9:34 am

pljones wrote:Particularly in "knob" view, the "upper limit" on the knob feels "broken" as it stops moving yet the value continues changing. Maybe the knob should just keep spinning freely as its position currently can be "non-indicative"?

What do you mean with "keep spinning"? A 360 unlimited value range and the knob value index keep going around and around while you scroll up? But then the knob has no usable value indication at all, right?

MuTools

KVR Audio

MuLab 7.0.47