MuLab 7.0.47

[MuTools]

Hope you gonna like it cause it's only the very background that has been added to the click=select area. New version is expected to be available tomorrow.

Yes, that's what I was expecting - not the slots, just the background.

To be honnest after sleeping over it i have doubts about that click rack background = focus rack thing i impulsively implemented yesterday. Because it is unclear (the very background areas are all very small cause most area is taken by controls) and thus unexpected behavior. To step back to the original issue: You find that there are too few pixels to select a collapsed rack via its title. But there are more pixels (21) to select a collpased rack than there are pixels (12) to collapse/expand it and to switch it on/off. So in fact i don't see the issue. Pls elaborate.

[MuTools]

To be honnest after sleeping over it i have doubts about that click rack background = focus rack thing i impulsively implemented yesterday. Because it is unclear (the very background areas are all very small cause most area is taken by controls) and thus unexpected behavior. To step back to the original issue: You find that there are too few pixels to select a collapsed rack via its title. But there are more pixels (21) to select a collpased rack than there are pixels (12) to collapse/expand it and to switch it on/off. So in fact i don't see the issue. Pls elaborate.

PS: In fact the areas that would be added if clicking the very background would also focus a rack are not bigger than the area at the right of the on/off switch of a collapsed rack. So it really makes no sense to add that background area. My apologies for my mistake.

[nenneb]

When inserting/replacing instrument I find effects, intstruments, modules and even VST as common.
Where is the "USER" gone?
Where do I find my private patches?

[MuTools]

Maybe you did not yet copy your user settings from M6 to M7?
See http://www.mutools.com/info/docs/mulab/ ... ation.html

[MuTools]

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

What's changed:

• Upon loading and there are missing VST plug-ins, there now is an extra option "Ignore All".
• Fixed a little bug when switching the snap marker in an audio file.
• Fixed a little UI bug in the Add Instrument Track dialog panel.
• Audio and sequence part property panels had a rather redundant edit button. Removed.
• When maximizing an editor window, it now takes the size limits of the editor into account.
• When opening/dropping a step sequencer preset, the step sequencer window was not resized to the saved size. Fixed.
• MUX front panels now have an explicit button to toggle front panel editing.

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.

[runaudio]

thank you for update like the toggle feature on front panel

[pljones]

I was imagining a change between and in terms of clickable area. But, as I say, I've gone with a single fixed-focused module routed to all racks, so it's not so important now. It wasn't the best solution anyway, as it still needed an extra click just to focus, which I've now got rid of.

The "Ignore All" option is good to have - my 100-VST project loads very quickly with no VST . (The only thing I'm not sure about is whether the VSTs should be deleted, as they are, or loaded in some "unknown location" state, so they can be recovered at some point. But it's okay as is.)

[bibz1st]

2). Would it be possible to modify the Randomizer module, so the 8 different "assignments", would be with individual minimum and maxium values.

Cheers

I see what you mean now, there is definitely something not right with the Randomizer has sbj has pointed out wrt setting min and max.

[runaudio]

i love the step seq so much its great for getting your ideas down really fast but wish you were able to preview the sounds on it

[MuTools]

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.

Would it be possible to modify the Randomizer module, so the 8 different "assignments", would be with individual minimum and maxium values.

It is already like that, but there indeed is a bug in the editor. Will be fixed in the next version.

[runaudio]

any you could Change the knee on the compressor change from % to db i have been asking for this M6 please and thank you people on here ask for something and they get it then for i ask for one little thing not cheeky about it asked nicely and dont get one simple thing GOD I GIVE UP

[MuTools]

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?

[MuTools]

i love the step seq so much its great for getting your ideas down really fast but wish you were able to preview the sounds on it

Step sequencer:
You can monitor a lane by [Alt]+click on the header.

Also note that you can name a lane in the lane setup = double-click lane header.

[runaudio]

Thank you very much i really appreciate it

[MuTools]

any you could Change the knee on the compressor change from % to db i have been asking for this M6 please and thank you people on here ask for something and they get it then for i ask for one little thing not cheeky about it asked nicely and dont get one simple thing GOD I GIVE UP

http://www.kvraudio.com/forum/viewtopic ... 9&t=357048