M+ Crackling noise, bpm decrease and sound loss when switching scenes

System: 1.4.0.3 - same crackling, and playback also slows down. Faster encoder rotation - more it slows down.

@benMaj7 can you plase check how it plays Motherboard: Boombleduple right after turning on or rebooting M+. With versions 1.4.3 and 1.4.4 my unit was stumbling at the beginning of bar 9 for a fraction of second, very annoying. But it was only during first play attempt after boot. All consecutive playbacks were fine until reboot/power off.

I had had same and also ton of other weird issues until i did a factory reset by tech support advice. Now my unit works mostly fine except these annoying stumblings on the first project playback. Actually it happens not only in expansion demos but in my own projects too. In my case number of affected projects depends on system version. With 1.4.3 and 1.4.4 it stumbles in perhaps 5-6 projects, with 1.4.0.3 only in 3 approximately and also its is kind of less pronounced i would say. Unfortunately tech support guys told me they cant reproduce this issue.

But i suspect this issue is not specifically connected with faulty M+ unit but its a system bug and so it should be much more widespread, can anybody else confirm having similar playback stumbling?

Same here, first pressing of 'Stop' produces very annoying click. But only first, no clicks on stop after that in same project. So in general issue looks like something in M+ system isn`t properly inititalized (precalculated, cached) during project loading phase and during system booting up.

Hello DJ Breeze here again Don't want to have a book long post so make a few short ones...

So what made me say ill keep it a bit longer is ...I have a very good ear for mi-nute sound..like a hearing test..

so when I am in the pc in controller mode. the only thing you can do is switch back to standalone mode. I close out the software then listen very closely thru the headphones as the switch is made is made and you will hear the static start and then go away...if you have preety good hearing you will hear a light white noise fade into pure silence...espesially if you use isolation headphones like do... that's how I discovered this...I was frustrated had my headphones one listening to static track stopped it just sat ther and noticed the complete silence come into my headphones.....I pressed play again and it was bumpin that $1,300 sound again.. Crazy....raise your right hand when you hear a beep...remember that a

in grammar school...LMAO

Regarding the crackling noises: This is happens in a lot of situations. To my use the most debilitating example of this is when using the "Audio" plugin. We use this plugin whenever you want to have a audio track locked in tempo and optionally, pitch. If you want to make some use of the audio plugin - say making the tracks in some other daw and use them in Maschine standalone - you are very, very limited IF you don\t want to hear those annoying crackling when restarting play back or changing scenes. WHen i say very, very limited i mean it. For you maschine plus users try the following:

1 - Start a blank project;

2- Add a audio plugin to one "Sound" of the first "Group", change the the stretch algorithm to stretch - this one is the one that mantains the pitch when you timestretch, but its not the heaviest on your cpu;

3 - load a one or two bar loop on that sound.

3 - Press restart play. When you do that you hear the looped sampled playing normally, as it should, no wanted artifacts. Press a few more times to recheck.

4 - Duplicate the sound one more time and press restart again, After a few times you will hear that crackling noise. Annoying.

You might think that this is me being picky (why the hell do you want to press restart when i track is playing), but very often if i am jamming, i might want to change a scene before time and i use restart for that. Also, if the project gets heavier this audio files will contribute heavily to referred glitches when changing scenes, tweaking knobs, reading automation, etc.

So with a problem it can also comes a solution. If you can avoid using timestretched samples , specially with a locked pitched algorithm, you might be able to eliminate those glitches in a somewhat glitchy project- use the ptich algorithm (but be aware that if you change the speed of the project you will change the pitch, which is really bad if you want to beat match 2 projects/ groups from different projects with diferent tempos), or even better, the "sample" machine, if you dont want to time stretch.

I have very cpu efective projects and i only use 1, max two stretched samples.

But this severely limits the potential of the M+ as a potential live machine. Im sure there will be a ton of users that would love to use the M+ as a live machine and live remixer. This users will have trouble doing this if they use just a few stems.

Solution/whish:

What about the Team in Native instruments design a specific M+ timestretching algorithm, where you can lock the pitch, and its optimized for the M+ weaker cpu?

Then, millions of us might see "Fred again" using the M+ live on the boiler room without being connected to a computer. ;)

Im writing this here because i think is relevant, but i will also create a new post for this specific issue and feature wish.

Just one more case of clicks on play/stop:

https://www.youtube.com/watch?v=KjC6J1oGUng&t=1277s