Quantization-related

[Psy-T]

Hello, I just tried out MU.LAB for the first time today, and it's fast becoming my sequencer of choice (except for Reason).

I'm having trouble figuring out how to move items freely:
When I try to move a sequence, I find I can only move it in bar increments.
When I try to move a note in a sequence, I find I can only move it in 1/16th increments.

I'm just getting into involving audio recording into my music recently, and as a result, my system isn't optimized for avoiding latency, so I need the ability to correct the recording delays in the sequencer, just nudging them a bit to the right, basically.

Can anyone give me a hand please?

Cheers

[Psy-T]

Hmm, on a different topic, I just noticed that MU.LAB's memory usage jumps to 300MB when I use my current project (for reference, a blank project takes up less than 20MB).

The project in question contains one instance of each of the following: SuperRiffGuitar, Ugo Metallurgy 1.5, MUSynth, Kjaerhus Classic Compressor, H.G.Fortune STS-33free, Lost Technology, Kjaerhus Classic Chorus, and one 12-bar-long audio recording.

1. Is this amount of memory usage normal for such a project?
2. For about 10 minutes since I loaded the project, MU.LAB's CPU usage display showed "overload". I have 600MB more of available RAM, so why would it tell me it's overloaded?

Thanks.

[pljones]

Right-click the background and do "Edit->Select Grid" to set the editing grid.

[Psy-T]

Thanks

[pljones]

I've had a think about the other but I've no idea... I tend not to worry about RAM or CPU but I don't do much at any one time.

[MuTools]

I'm just getting into involving audio recording into my music recently, and as a result, my system isn't optimized for avoiding latency, so I need the ability to correct the recording delays in the sequencer, just nudging them a bit to the right, basically.

Can anyone give me a hand please?

There's a little bug in 1.1 that causes the audio recordings to be not-latency compensated.

This will be fixed in 2.0.

[MuTools]

Hmm, on a different topic, I just noticed that MU.LAB's memory usage jumps to 300MB when I use my current project (for reference, a blank project takes up less than 20MB).

The project in question contains one instance of each of the following: SuperRiffGuitar, Ugo Metallurgy 1.5, MUSynth, Kjaerhus Classic Compressor, H.G.Fortune STS-33free, Lost Technology, Kjaerhus Classic Chorus, and one 12-bar-long audio recording.

I you use a lot of MuSynths in a session, than mulab 1.1 indeed needs quite some more memory.

Using VSTs in mulab does not take more memory than in other hosts. Of course it also depends on the vst itself, e.g. a sampler vst with a lot of samples loaded could take a lot of RAM.

1. Is this amount of memory usage normal for such a project?

It depends on what you do with the plugs...

2. For about 10 minutes since I loaded the project, MU.LAB's CPU usage display showed "overload". I have 600MB more of available RAM, so why would it tell me it's overloaded?

The CPU meter does not measure the amount of used RAM. CPU and RAM are 2 different things.

When the CPU meter shows an overload, it basically means that there are too many plugs to be processed at the same time.

If you want, you can disable that overload protection via Edit menu -> Audio Setup -> Max CPU Weight = 0 meaning 'Off'.

[MuTools]

There's a little bug in 1.1 that causes the audio recordings to be not-latency compensated.

This will be fixed in 2.0.

You could manually finetune this by tweaking the start locator in the audio lab (double-click the audio recording)

[Psy-T]

thanks jo