MU.LAB 3.1 test

[MuTools]

What to do about that?

[robenestobenz]

I tried the multi-track implementation. It's extremely flexible, and I'm liking the integration with the MPA, but I found it quite confusing to begin with, and a bit clunky after that.

The advantage of the track based approach is that toggling recording and monitoring is much faster than this multiple-menu approach, it usually just being a case of clicking some icons on the track headers.

Here for example, if I want to stop recording and monitoring to one track and turn off monitoring to another, I have to go through a lot of steps and menus compared to just clicking three icons in the track panel. Another downside of the current system is that there is no fast and easy way to see what's active.

[Jake Jackson]

Ah!!!!! Now I see. Works. I must say that I'm not surprised that earlier I didn't find that "Record from" by right-clicking on the Record Audio button. That command is, well, hidden. A vote, here, for putting it on the Transport bar in plain view.

Then what if there are 2 or more recorders i.e. multi-track recording?

Well, I run into problems there, too. I created a subtrack and put a synth on the main track and the subtrack, but only one plays. But if I put each on a separate track, right-clicking Record Audio only lets me select one track to record from. Slow learner, I am. What I keep wanting is just an "Arm track" button on each pane to the left of each track.

[Jake Jackson]

What to do about that?

Maybe just have the audio track pasted into the fourth track instead of the dead fifth track?

[MuTools]

The advantage of the track based approach is that toggling recording and monitoring is much faster than this multiple-menu approach, it usually just being a case of clicking some icons on the track headers.

Here for example, if I want to stop recording and monitoring to one track and turn off monitoring to another, I have to go through a lot of steps and menus compared to just clicking three icons in the track panel. Another downside of the current system is that there is no fast and easy way to see what's active.

Note that if you have multiple recorders, you can access them more quickly via right-click on the record audio button, there you have them all together.

But at the same time i know what you mean, i'm aware of that, but i decided to go in steps, and this step is about adding the multi-track recording capabilities.

A possible next step (in M4) is about further optimizing the workflow. But things are all very related and i didn't want to make rushy changes. Lets discuss the deeper workflow/concept optimizations in a M4 chat, lateron.

Anyway, besides some true critical notes, i think the MT recording already is very usable.

[MuTools]

But if I put each on a separate track, right-clicking Record Audio only lets me select one track to record from.

FYI: You cannot record from Tracks, only from modules (i.e. audio inputs, racks, plugins, ...)

[pljones]

What to do about that?

Maybe in "Free" only create two blank tracks? (Maybe only create two anyway?)

[MuTools]

Hey guys, what do you think about removing the Level Threshold from the recorder setup? cfr http://www.kvraudio.com/forum/viewtopic ... 73#4081873

I tend to remove it, to simplify things. A fixed (eventually preferencable) value of -48 dB is a good value i think.

What do you think?

[Jake Jackson]

But if I put each on a separate track, right-clicking Record Audio only lets me select one track to record from.

FYI: You cannot record from Tracks, only from modules (i.e. audio inputs, racks, plugins, ...)

Well, yes, one is recording to tracks. But I still don't see how to record two tracks at once...

[MuTools]

First time in session:

* Open the Modular Area
* Create as manu audio recorders as you need
* Set them up as you want
* Make sure the Record Audio button is enabled
* Click record

Note that once you have setup things, you can record new takes by simply clicking Record.

[robenestobenz]

Does anyone else get a lot of lag (between for example, clicking on a module and it being selected) in the modular areas in M3, if there's a lot of modules?

It gets faster if I downsize the window, but I checked the same project in M2.7 and module selection and dragging and so on was extremely responsive and smooth.

[liquidsound]

Also opening a file or saving it's slower than 2.7

[MuTools]

Does anyone else get a lot of lag (between for example, clicking on a module and it being selected) in the modular areas in M3, if there's a lot of modules?

Let me try to repeat this situation here.

So around how many modules? Approx what modular area size?

[robenestobenz]

Does anyone else get a lot of lag (between for example, clicking on a module and it being selected) in the modular areas in M3, if there's a lot of modules?

Let me try to repeat this situation here.

So around how many modules? Approx what modular area size?

About 25 modules in this project. After more testing, it corresponds directly to the amount visible-- the size of the MPA window doesn't really matter.

Also, a little FR. I've just started using the extremely handy hide window feature. Could we have the hide window bar status saved with the project?

[MuTools]

Does anyone else get a lot of lag (between for example, clicking on a module and it being selected) in the modular areas in M3, if there's a lot of modules?

Let me try to repeat this situation here.

So around how many modules? Approx what modular area size?

About 25 modules in this project. After more testing, it corresponds directly to the amount visible-- the size of the MPA window doesn't really matter.

Ok, i see. It's especially the number of connections.

M3 draws thicker connections than M27 and it takes more time to draw each connection, that's the reason for sure. Added a note on the WL about optimizing that line drawing function.

Also, a little FR. I've just started using the extremely handy hide window feature. Could we have the hide window bar status saved with the project?

Saving the state of the editors is on the WL, but i doubt it will be for M4, sorry.