MU.LAB 2 Test C

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

Post

MU.LAB 2 Test C has been released.

Feedback on MU.LAB 2 Test C can be posted in this topic.

If you're an experienced music software user and want to help with testing MU.LAB 2, feel free to join the test group by sending me an email.

Post

Nice! Giving it a quick test run before bed now.
First impression: the filebrowser when you hit "save" is a real improvement!

:D

Post

Another very quick first impression. I tried opening two sessions (both, I think, created with MuLab 2 Test B). First first failed (it's the Kontakt2 session in the 7-zip file); the second worked (it's from a couple of weeks earlier). I'll investigate further later (i.e. try loading the session back in Test B).

<edit>
OK, couldn't wait...
Panic over. The session won't reload in Test B, either!
</edit>

Post

Yes, it won't load because of a bug in Test B.

When i tried to load your session, i also noticed that problem and reported it here.

Bug is fixed in Test C.

If you need the drum sequence in that musession file, i can recover that.

Regarding the Kontakt2 problem: I don't have K2 here, could download the demo, but i think it won't load the session data as it's a demo. Not sure though.

Anyway, could you make a new (and smaller in size if pos.) musession that demonstrates the mixdown problem?

Post

The MU.LAB 2 Test C package has been updated with some last minute tweaks regarding windowing.

If you did already download the MU.LAB 2 Test C package, then please download and install again. (or at least copy the new application file into your current installation aka patching)

The splash screen should say "Test C2" now.

Post

Ok, lets make it public:

Everyone can download the latest MU.LAB 2.0 Test from:

OSX: http://www.mutools.com/mulab/test20/mul ... -c-osx.zip
WIN: http://www.mutools.com/mulab/test20/mul ... -c-win.zip

(not yet including the final graphics nor the final docs)

Feel free to give it a test, then please feedback here if you notice any bugs or workflow bottlenecks.

Cheers!

Post

Someone emailed:
The new mouse tool system is a solution, but not for me. The best way to work quickly with MULAB, and this is the best for me in your software, the fastest workflow.

Press the roll button of the mouse and choose fast what I need (and other users, sure), arrow, pencil, gum and split like Cubase, it's very good.

Work whit press combinations like Logic, Reason and others don't like me.

I love your MULAB, the sound it's very good and now your latest updates makes the software best. Don't break this good job.
The middle mouse button still works, it quickly switches between arrow and pencil.

In fact this is faster as before because you have to click 1 time less to switch tools!

(note for other users: the arrow and pencil mimic eachothers functionality by holding control (win) / command (osx), so you don't have to switch tools)

So it's only about the gum and splitter, agreed?

About the gum:

Well, to delete objects, just select them and press delete (or backspace).

This doesn't need a modifier key combination. And since you don't have to switch tools anymore, i think it's faster. Agreed?

Alternatively, you can also delete a part / note by holding [alt] while hovering over the start or end of the part / note.

And about splitting:

Now it's 1 click on the part at the relevant position, second click = "Split".

Previously it was 1 click to call toolbox, 2nd click to select splitter, third click to split, fourth + fifth click to select original tool back.

So now it's much faster i think.

And you can still work without modifier keys if you want.

Curious for your reply.

Post

I'd say that after some initial confusion/getting-used-to-it I'm all for the menu-driven system we have now. Just look at all the options you get with one right mouse click! It works very well once you get the hang of it.

What I still do't get - What is "unroll Loop"?

:D

Post

If makes real copies of the sequence loop, so all events are editable individually.

Post

Hi !

For me is best the older system on Luna or MULAB 1, choosing the tools whit the middle mouse button. It's more visual and faster, isn't necesary read something more.

TONi

Post

Toni,

But what about my arguments, aren't they not true for you?

For example about the splitting, previously you had to click a lot more to split a single part, no?

Post

I understand your arguments, but it's best for me the old system. Splitting is not utilized very often, but erase if.
Lastest you are the boss, can make what do you want. :wink:

TONi

Post

In fact, you're the boss, Toni, i mean: You, the users! (of who i am one of too ;))

Post

mutools wrote:When i tried to load your session, i also noticed that problem and reported it here.
Ah, so you did... Missed that bit, sorry! :oops:

I'll try to create a very simple Session with K2. I think it's more to do with the sample set size and/or complexity, so I may have to do some experimenting. (I should be able to generate a sufficiently large number of highly compressible samples for testing purposes fairly easily.)

Post

mutools wrote:The MU.LAB 2 Test C package has been updated with some last minute tweaks regarding windowing.

If you did already download the MU.LAB 2 Test C package, then please download and install again. (or at least copy the new application file into your current installation aka patching)

The splash screen should say "Test C2" now.
Just noticed that the splash screen only appears the first time you open this new version.

Post Reply

Return to “MuTools”