MuLab 7.0.47

[sbj]

1). When I use the new freeze function, it would be nice if I could tell MuLab the lenght of the freeze (e.g According to the loop markers).

Why? I mean for you can't "partially" freeze a rack.

O.K I see. It is no big deal. I just thought it would be possible
to define the lenght.
Sometimes I have a lot of files I don't use, placed to the right so
it makes a long file.
But it is a great new feature and I can of course, just cut the
redundant part and delete it.

Cheers

[runaudio]

[MuTools]

O.K I see. It is no big deal. I just thought it would be possible
to define the lenght.

Tehnically it is possible.

Sometimes I have a lot of files I don't use, placed to the right so
it makes a long file.

Ah i see. I prefer to avoid a dialog, but will reflect on it.

[sbj]

Ah i see. I prefer to avoid a dialog, but will reflect on it.

O.K Thanks for considering it

[runaudio]

nice to see other peoples request getting considered i know feature feature

[Taifunk]

I was able to recreate the error previously reported, this time has not disappeared inputs, but it appeared an input in musynth. Edit:I attached the patch

The Musynth having a modulation input, that's indeed a strange and serious issue! How can i repeat that? Any hints on the type of actions you do when such inputs appear/disappear?

while I built the patch I noticed this ,It has often happened dragging the module from the rack
the step sequencer inputs/output disappeared and reappeared after
the modulation input in musynth it is still there when I open the patches I posted.
Tomorrow I will try to do some tests and capture the problem

[MuTools]

Eager to solve this. Pls let me know every bit of info that can help narrowing this down.

[Taifunk]

OK Tomorrow I'll try to spend some time and try to let you have it all.

[Taron]

Huh? I'm missing all the fun here?! Sorry I've been so distant for a while again. I will surely check it out! How exciting!

Right off the bet, though I haven't checked anything about it, yet. The handling of notes in the pattern is weird with moving notes. You have to hold Ctrl to indicate you want to move a note, but let go of Ctrl not to copy it. I hope that is a preset one can change back to the old ways again?

Other than that, it looks beautiful, some nice improvements there!
The demo song has every single sound clipping, which is kind of odd. It's still all begging for a simple limiter, but you should at least try not to hammer the sounds in the default song like that.

[MuTools]

There is a new M7.0.6 in http://www.mutools.com/galaxa/

What's changed: Fixed a couple of bugs in the Parameter Value Randomizer.

How to update:

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.

[Taron]

Pattern editor mouse cursor:
OH, I just noticed that the mouse cursor just changes to eraser when you hover over a note in the pattern editor, even while it still acts properly and allows to move a note.

I would consider that a "bug" or at least a mishap.

[pljones]

That's a long time feature, I think?

There's a setting for arrow/pencil for the default tool - I had mine switched from the default in M6. Check if that's why you've a different feel.

[Taron]

Whether arrow or pencil is default, if a click drag is about to move a note (as it does and as it should), it shouldn't show an eraser cursor, you know. And this is the default with which it starts. Even I, a veteran mulab user, was scared to touch a note, haha.
Thanks for the tip, though.

[MuTools]

The demo song has every single sound clipping, which is kind of odd. It's still all begging for a simple limiter, but you should at least try not to hammer the sounds in the default song like that.

Which demo song?

[pljones]

I just checked M6 and I get an eraser when I hover over a note. Press ctrl and I get an arrow. Weirdly, in M6, even the arrow erases the note... but in M7 that's fixed.