Two issues

Maybe these have been discussed here before.

  1. Everytine I change the recording buffers on my MK2 the tracks (all incl. static ones) won‘t make any sound anymore. This is resolved by restarting the device. Is this a common problem? Is there a way of fixing this?

  2. I get some noticable latency when using thru machines even when not using any effects. I run keyboards, guitars and vocals through them. Usually one at a time. The latency is enough to be bothersome. Is this a common issue? Can this be fixed?

You mean Memory Config ? Known bug.

Do you listen Thru and Inputs with DIR ?
There is a delay compensation setting in Project > Control > Inputs

The delay is around 1.5ms.

1 Like

1.5 ms isn’t really perceivable though?

1 Like

Thank you for the replies!

Yes, i mean memory config. Is this a bug common to all MK2‘s or just some machines? I‘m asking bc i can stilm exchange it for a new one within a 20 day period.

I turned on the delay/latency compensation while using thru machines and particularly when playing keyboards there is a proper delay as compared to playing through my audio interface with direct monitoring which I find bothersome.
I believe this isn‘t the case when I just use the direct setting. But I have to check when I get home.

That all recording buffers gets cleared when you change the memory config isn’t a bug, but is well documented in the manual. There is even a prompt showing up before it happens.

What I am missing here? Why should it be necessary to restart the device, @sezare56?

1 Like

I am not talking about recording buffers being cleared.

For example: T1 is a static track playing some samples.
When I change the memory settings this track will no more produce any sounds until I restart the device.

Is there any reason why you’re changing the buffer settings? I figured it’s a set and forget kind of thing.

Yes, when I realize I wanna record smth during the process of creating music.

By static track you mean a track with a static machine, right? Doesn’t “reload project” resolve the issue?

Don’t get me wrong: I’m just curious here. It looks like it clears more of the RAM as it should, but a “reload project” should fix this without a reboot required.

2 Likes

Yes a track with a static machine, I‘m not fluent in the terminology yet, sorry!

I haven‘t tried saving and reloading the project yet, but will when I get home

I am wondering if there might be some hardware issue given the combination of this and the latency issues. But this might just be me worrying due to the high price of the OT.

1 Like

Save, then reload, will work.
The silent slot bug was introduced after OS 1.25E and still hasn’t been addressed.
And it happens on Mk1 too - it’s clearly an OS problem.

6 Likes

I am glad to hear that, thanks!

Doesn‘t using the DIR setting sort of defeat point of using a thru machine though?

It may be useful, because you can use this as kind of dry (DIR) and wet (THRU machine) signals. But it needs some delay compensation to prevent phasing effects.

3 Likes

soooo everything you guys wrote was correct. Saving and reloading works. And the latency came from my use of the spacializer effect. Pretty stupid, but it happens :smiley: Thank you for the help!

6 Likes