MASCHINE 2.11 and KOMPLETE KONTROL 2.4 - Out Now!

Also I have to hit control z a ton of times to get back to where I started something isn’t right. It was fine just the other day before this update

 

And there is many many more.. I have a copy paste bug ... Makes the whole thing unusable...

 

Hey Chad,
can you check your Grid settings ? You might be on 1 Bar setting or something. Try changing it to 1/16 or hold CMD while resizing with the mouse.
Or remove the grid follow # here:

 

Hi Kaldosh, what issue are you experiencing ?

 

Hi Bruno

Hope you're fine.

Same bug I outlined a while ago regarding copy paste...
From M Studio controller, Copy all events from a 4/8/16 bar pattern (whatever) , set the play head on pattern start...the paste.
Destination pattern is enlarged to 49/56/up to more than 100 bars depending on moment (didn't figure a pattern) and events are pasted to bar n° whatever (can be 49/ and on and on up to whatever number) so I have a huge amount of empty bars before my events are pasted, I must then select them all and move then back to position 1.
Think hat was the last but i logged before leaving the beta program

Cheers

 

ok.. sorry my post it may be out of place.. I am one of the many that has to learn to read properly ( I see you out there.. I wasn't the only one that taught that the arranger update was in this one hahaha) anyway my question is more about the friendly Apple, that believes that my laptop is not good enough for their standards anymore.. so in the next OS update I'll be cut off.. so here the question.. the update about the arranger and clips etc.. will be compatible with Catalina? ( if yes also bug fixes etc?) I'm bit worried.. because my wallet doesn't give a damn about my feeling...

 

Might deserve it's own thread.

 

Also, automation curves are registered but not written when performed, the curve remains flat

 

Thank you! Still no VST3 however... its been so long; I have lost hope now...
(no, I dont use MAC so AU is not a solution)

 

I'm not an expert of the forum, can you make it happen? I think a lot of people will experience this..

 

Hi Kaldosh,
what you are experiencing is by design the expected behaviour. When you copy all events from a Pattern onto another one, it will keep the original Events position. What you can do is change the Start Marker to where you want your Pattern to start.
Does this make sense to you ?

 

NI officially support current OS minus 3. It means when Big Sur will be out, Maschine will be officially supported on Mojave, Catalina and Big Sur.

 

Hi Bruno,

No it doesn' as I copy an event with a pattern start 1.1.1 and paste it to a new created empty pattern with same length and it pastes it to bar 49.1.1 or mire setting a pattern lenght of more than a 100 bars with a pattern start position of 1.1.1 leaving my events 48 bars away from start position

How could this be the expected behaviour when 2.10 was not beahaving like that ? I am sceptical ...

Let me know if I can help

Cheers

 

Introducing background scanning for content Products

So how is this working?
I am still getting around a half minute wait for product scan with Maschine and KK at launch. Both standalone and as plugins

Thanks
Oz

 

Ok, so you have a Pattern starting at 1:1:1 with and event placed at 1:1:1 and when you copy that to a new created Pattern it copies it far away.
I still can't reproduce that. And as an old Beta user you might have some extra features on . Maybe we take this private and you can explain me a reproduction scenario.
We haven't touched this part of the code for 2.11 so that's weird that it behaves differently.

 

Ok yes I remain Available... still, since 2,10 I unsinstalled db3 files and plist many times to start fresh because that's what solved my issue when I had that bug.

Let me know

 

When I record a Perform FX automation on a group, the automation is recorded, but the automation curve in the GUI remains flat. I don't know if this is a bug introduced in the latest update.

 

No it's a new ear training program

 

Can confirm, same here. Open a bug report thread about it, if you want.

 

I have started a new thread about the issue. Is it the right way to report a bug?