MU.LAB 3.1 test

[MuTools]

The new MU.LAB 3.1.11 test patch is available

• ...
• Finetuned double-click detection algorithm
• ...

The new double-click detection is without doubt an improvement throughout the whole app.

But specificly about clicking the composer's time bar:

I think it's good as it is now because i think the 'double-click = add locator' feature is a good thing because it further emphasizes the consistency of MU.LAB's basic GUI rules, and that's a very important aspect.

How does this new version works for you? Does this feel nice and comfy?

[janamdo]

The new MU.LAB 3.1.11 test patch is available

He did it again..thanks !!
Optimizing algorihtms that's were it all abouts

[janamdo]

The new MU.LAB 3.1.11 test patch is available in http://www.mutools.com/mulab/chestnut

What's changed:

• New: Modular Deep Editor: Double-clicking a meta parameter knob opens its parameter map editor

There is no multiple selection of meta parameter possible ?
Ohh -- i.. understand you use the double click algorithme for this

[MuTools]

The new MU.LAB 3.1.12 test patch is available in http://www.mutools.com/mulab/chestnut

What's changed: Just another little finetuning in the mouse click behavior of the time bar. (in 3.1.11 longer clicks didn't set the play position)

If you already have installed MU.LAB 3.1.4 or later, then simply replace the current MU.LAB application file with the new application patch file.

This is MU.LAB 3.1 release candidate 3.

[pljones]

Hmmm.... Consistency question: should Ctrl-Click on the time bar create locators? Should Ctrl-Click on a locator erase it?


Unrelated...

When I change the number of beats per bar, say from 4 to 5, if I've got the composition loop start and end positions set to, say 5.1.0000 and 9.1.0000, should MU.LAB keep those settings, rather than "moving" them to 4.2.0000 and 7.3.0000? (That is, I want to loop the second four bars, not a particular range of ticks.)

[Simon Posford]

where do you put the PositionLine.zip?

[Juan Mendoza]

Hmmm.... Consistency question: should Ctrl-Click on the time bar create locators? Should Ctrl-Click on a locator erase it?

yes, definitely IMO, but in not the one

[cytone]

The new detection is working fine. I noticed that you can now add locators in the piano roll. Not sure if this is an intentional feature as it does not appear to have a right mouse click function.

[liquidsound]

I have a shortcut for "split".
I held the shortcut key down while moving (like brushing through) the cursor over the Part at a quite fast speed: Mu.Lab was splitting the part to the grid setting like a chef chopping carrots! Awesome!
This was the fastest "Unique Copy" action ever! ( if you need to create empty parts all the same length by the buckets!)
Try it. Just make a 16 bars or whatever long Part. Brush over with a Split shortcut held down and... wow!

Well. It was fun anyway....

[liquidsound]

Now that I'm thinking about it....

There is a command for "Duplicate Sequencer" if we had a command for "Share Sequencers" the Split action I just described could be used to create "Instantly" as many empty shared parts as you need (Instantly!) and then by just getting in one of them all the other would be..... the same!
Am I or ?

<EDIT>
They are Shared! I didn't realized it because each one comes with the Part Start moved one Split at the time... Too bad! It almost worked.
Now I have to move each one!:bang:

Really this is much better than just create a Part and the Ctrl+Shit etc.

If the Part Start wasn't there this would be the fastest Shared copier in the business!

[Trancit]

http://www.mutools.com/mulab/chestnut

If you already have installed MU.LAB 3.1.4 or later, then simply replace the current MU.LAB application file with the new application patch file.

This is MU.LAB 3.1 release candidate 3.

You write always about 3.1.4...on the chestnut is only 3.1.3 and the newer patch available...so, is 3.1.3 enough or where to get 3.1.4????


Trancit

[Trancit]

And a little FR...especially for the compressor, some kind of metering would be very nice...I/O and reduction

For me, it's quite better to adjust, if I see what's going on...


Trancit

[janamdo]

http://www.mutools.com/mulab/chestnut

If you already have installed MU.LAB 3.1.4 or later, then simply replace the current MU.LAB application file with the new application patch file.

This is MU.LAB 3.1 release candidate 3.

You write always about 3.1.4...on the chestnut is only 3.1.3 and the newer patch available...so, is 3.1.3 enough or where to get 3.1.4????


Trancit

as i understand it now use 3.1.3 und update this to the newest testpatch

[robenestobenz]

And a little FR...especially for the compressor, some kind of metering would be very nice...I/O and reduction

For me, it's quite better to adjust, if I see what's going on...


Trancit

The compressor doesn't seem to be working right to me. Or at least not in a similar way to every other compressor I've used.

For example infinite ratio should mean it is effectively acting as a limiter, yet with a knee smoothing over over about 30% it doesn't reduce the signal much at all, even with the threshold set as low as -52db!

In other compressers, the knee softness usual only affects a fairly small area of the amplitude transfer curve (cf le wiki). This is usually without such dramatic db changes as the bottom 0-20% knee smoothness range in MuLab's module either, so what's it doing?


Also, rather than double posting:

Another quick beg for the ability to rename tracks with targets -- I've run into another situation where this is a pain - multi-timbral synths/samplers. I have a sampler with a bunch of different percussion patches on different channels, and of course every track targetting it displays the same title and I can't do anything about it. Another situation where having the target displayed is less clear than user-chosen names, and more maintenance work renaming parts in multiple tracks along the timeline if you want to quickly know what track is what....

In 3.12 the ability to use shortcuts during drag operations seems to have been lost, which slows down moving notes around if you aren't keeping track of the snap toggle and have to deselect>toggle>reselect.

[MuTools]

Hmmm.... Consistency question: should Ctrl-Click on the time bar create locators? Should Ctrl-Click on a locator erase it?

Good questions. I don't have an answer at this point.

When I change the number of beats per bar, say from 4 to 5, if I've got the composition loop start and end positions set to, say 5.1.0000 and 9.1.0000, should MU.LAB keep those settings, rather than "moving" them to 4.2.0000 and 7.3.0000? (That is, I want to loop the second four bars, not a particular range of ticks.)

Keep as is. It's the user's choice to change things or not.