MU.LAB 3.1 test

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

mutools wrote:
liquidsound wrote:I suspected this but since I saw the "Send" and "Audio Inputs" in the MUX and since the MUX has not the ability to grow additional Red/Blue triangles connections
Not yet
OK, at least something is coming....(yet)
For example: You can setup a complete mixing environment inside a MUX if you want/need that.
Yes I will have to. Nothing wrong with it at all. I was trying to get this just from the Rack...
liquidsound wrote:"For example: You can setup a complete mixing environment inside a MUX if you want/need that."
Will check
Thank you.
Ah no, it's the same as before: it's not possible to send signals from inside a module directly to a module inside another module; it is possible to get the signal there but you have to route it via output->input. Only the composer (tracks and parts) can target modules directly.
OK this means that if you add the ability to a Send to target "all available (relevant) modules" it is then only to their Inputs but not inside them. That's OK, it adds so much more flexibility at the Rack level. This is great indeed!
Thanks for considering. :)

Hopefully I got the last one... :?
ABEFLGMOPPRRST :phones:

Post

Whee!

Red box serious error.

Start drawing a note.
Hit escape with the mouse button down.
Let go of the button.
Red box.

Hitting escape has always exited the editor rather than just terminating the note paint operation. In this version it causes a crash, though. (Ideally, I'd prefer Escape with mouse down to cancel whatever the mouse is doing.)

Post

Tiny buglet: Composition->Zoom Selection. Correctly resizes window but fails to scroll selection so it's fully visible.

Post

Will check, thanks!

Also a crash bug has been discovered. When using version 3.1.8, please regularly save. Version 3.1.9 coming asap.

Post

pljones wrote:Tiny buglet: Composition->Zoom Selection. Correctly resizes window but fails to scroll selection so it's fully visible.
I can't repeat this one.

Any more details?

Anyone else having this issue?

Post

mutools wrote:I can't repeat this one.
Hm. I can't get it to do it now, either! Maybe I accidentally scrolled as I hit Zoom... :?

Post

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

What's changed:
  • New: Audio Files and Samples: "Add Locators Around Selection" context function
  • New: Double-click in time bar creates a new locator
  • Tuned: When choosing a rack slot send, then you get more target options
  • Tuned: Very new default session uses default i.e. auto rack names
  • Fixed: Event Graph Editor: Issue with selecting parameters from the list
  • Fixed: Crash bug when tool tip hovers automation parts
  • Fixed: Crash bug when hitting Esc while drawing notes
  • Fixed: Issue with auto rack rename feature when renaming modules
  • + some minor tunings
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.

Post

mutools wrote:New: Double-click in time bar creates a new locator
As expected this has a little cost: Setting the playback position e.g. in the composer now has a little delay because the system must check whether the click is a single or double click.

I'm unsure what to think about this.

It's perfectly logical and consistent to create a new locator on double-click.
But the delay time for positioning the play cursor may be a too big disadvantage? What do you think?

Post

mutools wrote: What do you think?
Well.. by keystroke for now than and if paralell processing by multi core processor comes in sight than you can go back to double click

Post

Makes it feel a bit unresponsive when setting the position. Not sure it's worth it for the slight benefit of the markers.

Post

cytone wrote:Makes it feel a bit unresponsive when setting the position. Not sure it's worth it for the slight benefit of the markers.
Yeah, I agree. Thanks for giving the idea a try Jo -- this is probably better left to the Add Locator shortcut, which I've just noticed doesn't even require the cursor to be at the top of the screen. Awesome!

Post

robenestobenz wrote:
cytone wrote:Makes it feel a bit unresponsive when setting the position. Not sure it's worth it for the slight benefit of the markers.
Yeah, I agree. Thanks for giving the idea a try Jo -- this is probably better left to the Add Locator shortcut, which I've just noticed doesn't even require the cursor to be at the top of the screen. Awesome!
+1.
For me, using a shortcut key for Add Locator is fast and efficient.

Presumably the right-click context menu would continue to offer 'Add New Locator' (as this may be where a new user may look to begin with) ?

Les J.

Image

Post

mutools wrote: I'm unsure what to think about this.
I'd never sacrifice instant set of playback possition for that doubleclick locator feature. How many times you need to set a locator on a composition?, as much, much less than 100. How many times you need to move the playback possition in a composition? maybe thousands.

Post

Juan Mendoza wrote:
mutools wrote: I'm unsure what to think about this.
I'd never sacrifice instant set of playback possition for that doubleclick locator feature. How many times you need to set a locator on a composition?, as much, much less than 100. How many times you need to move the playback possition in a composition? maybe thousands.
Well, I suggested it after recording some samples of stuff in my house and trying to set loads of locators to generate a multisample from. As I was in sampling mode I didn't think about it delaying the playback locator...

Post

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
  • Tuned: Finetuned double-click detection algorithm
  • Fixed: When time signature was e.g. 6 beats per bar, dragging locators etc. was still using 4 beats per bar
  • Fixed: OSX: Audio error when using an oscillator's AIPS feature
  • Fixed: OSX: Modular cable colors were not right
  • + some minor tunings
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 2.

Post Reply

Return to “MuTools”