Manual Slicing Samples on Maschine Mikro MK3

nickstomp

Hi!

it is possible to slice samples in manual mode on the maschine mikro?

I want to slice the samples manually pressing the pads on the cut point

it is possible?

Thanks,

Nick

Olihop

Not feasible with the mikro controller. You have to use the software to do this.

Paule

Please start your manual page 890 ff

Olihop

Not feasible with the mikro controller. You have to use the software to do this.

nickstomp

Hi I tried to go to the slice page but I cannot find a way to play the sample and slice it with the pads like on machine mk3

Murat Kayi

Because you can't, like Olihop told you.

But that's not bad, I rarely use the live slicing feature. Just duplicate the Sound to the next pad, set the start and end point, duplicate, set points a.s.o. - It's blazingly fast and offers much more control.

Olihop

Manually ok, but it's still tedious compared to automatic slicing. They could give us this possibility for the mikro maschine. There are far too many basic functions removed from this mikro mk3.

The mpc studio 2 has this function from the controller.

Jeremy_NI

@Paule As mentioned by others here, this is not possible with the Mikro MK3, please avoid posting answers when not sure.

ALLAHJOSEPH

Wow. This is actually a crazy backstep NI. I JUST upgraded to the Mikro Mk3. The Mikro Mk2 has been wonderful up until pads stopped working… regardless, manual live slicing was a feature that was ALWAYS available on either piece of hardware. That feature has now been put behind a paywall. Yeah, having a flagship machine mk3 or larger is ideal, but sometimes you dont want all of that space taken up in your workspace. NI needs to bring the feature back ad standard for ALL drumpad hardware. Its a bit counterintuitive that the “fast” and “on-the-go” model has the slowest sampling process. It really ruins the workflow I’ve been used to for over a decade now. I will be contacting support to see if they can revert the settings.

ALLAHJOSEPH

@Paule @Jeremy_NI @Olihop @Murat Kayi @nickstomp This was always possible on mikro platform, why did they change it? we gotta get NI to change that back because it ruins work flow. Kind of ironic and counterintuitive that the “fast” and “on-the-go” model has the slowest sampling process. It REALLY ruins the workflow I’ve been used to for over a decade now. This was a feature that made me like the maschine in the first place. I will be contacting support to see if they can revert the settings. We all should.

• context: started on the OG big block maschine. Ive been using the Mirko since it came out because i like the smaller footprint. Got the Mk.2 in 2017 and JUST upgraded to the mk.3 in 2024, my maschine logo was still orange. After all the updates from OS to VST i go to make beats on this awesome looking hardware and the workflow is a step below what it was and should be. Very disappointed with the sampling on this model. Again, it wasnt always like this, and it’s definitely a software thing because other models can do it and the mikro before this could.

darkwaves

https://community.native-instruments.com/discussion/comment/163141#Comment_163141

Back on the old forum; one of the devs stated they couldn't find a way to implement the workflow on the mk3 mikro. They didn't like the user experience so the function was dropped. It was quite literally years ago (i.e. good luck trying to get it changed now).

ALLAHJOSEPH

https://community.native-instruments.com/discussion/comment/163155#Comment_163155

I’m curious what's different between how it worked on the Mk.2 and the Mk.3. Minus having a larger screen, it should theoretically work the same. Also, research shows the feature was dropped across all devices until update 2.4.5 re-enabled it for flagship models. This suggests it’s a software issue. Five years ago, the Mk.3 couldn’t even set start and end times for samples, only record them—also a software limitation that was eventually resolved.

Given it’s now 2024, with advanced capabilities and ample development time, the devs should be able to reintegrate this feature, especially considering AI advancements. As a programmer, I find it surprising this hasn’t been addressed, particularly since older Mikro models supported it. The more we voice our concerns, the faster we can push for this update.

It would be more practical for NI to release a software update rather than developing a new Mikro Mk.4 or issuing refunds for the Mk.3. Let’s highlight the importance of this feature to ensure it returns promptly.