Maschine+ / Plus update 1.6.1 has screwed my standalone startup AGAIN.

NI replaced an original unit with a new one 2 or 3 years back, but it's the SAME issue on multiple threads - it hangs on the start-up screen. So they replaced faulty hardware with faulty hardware (and there are many users reporting the same).
It was KIND OF stable on the last update - it would hang every 3 or 4 startups… now i've tried upwards of 40 times.
The thread about the .nut file didn't help before - weirdly it just kind of 'stopped being so buggy' over time.
I have no idea how NI even deliver support anymore. This update has bricked my hardware in stand-alone - it's useless. A thousand dollars… come on Native - offer clear and proper support and sort out this 5 year old issue which has affected hundreds of users?!
NO idea what to try now.
Answers
-
Wow. Sorry I heard that and I hope it's…something that can be solved.
Immediately after the update my new projects started to Crash and Restore from the last time it was saved automatically.
This is what is happening and it's not about Genre. I did what I do from the MK3 and now M+ Standalone mode but the only change I did was Massive NKS int- preset I used.
Is it something that is happening to you? Is it how it started, I would appreciate any answer but again I really hope you can get software fix and if it's something that is happening to many of us than maybe we should notify Team to get the patch for the problem.
0 -
Mine will not get past the start-up screen. So it's a completely different issue.
-1 -
I wonder if there are any issues with the manufacturing of these things? Like maybe some batches are worse than others? I got mine in like 2021 or 2022, I think? I wanna say that after one of the 2.x updates, I stopped having regular glitches. On launch, yeah it froze every other session for me…more recently, I've left it on for several hours while working on a track and had no issues. Although after turning it on to update the other day, after leaving it on the shelf (unpowered, in a soft case.), I found I had to reinsert my SD card to get it to read again. Given the fact that all Maschine+ are using the same components, there must be some other variable that is making some user's experience more bug-prone than others.
1 -
In my experience, the reliability of the SD card has more impact than expected. I exchanged the stock SD card with a high quality 256GB micro SD right after purchase of the M+ and was experiencing odd behavior and once lost a project I was working on for two days. Then, about a year ago while trying to track down an odd bug and to just rule out a faulty card, I exchanged the microSD card with a full sized SD card (SanDisk Extreme PRO 256GB SDXC). From then on, my M+ felt faster, more solid and ran smoothly like never before.
2 -
im going to try this - I’ve got a micro SD (tho a good one - fast sandisk) but still - it’s the only thing I can try really! Thanks for this - I’ll report back
0
Categories
- All Categories
- 18 Welcome
- 1.6K Hangout
- 66 NI News
- 858 Tech Talks
- 4.4K Native Access
- 17.6K Komplete
- 2.1K Komplete General
- 4.6K Komplete Kontrol
- 6.1K Kontakt
- 1.6K Reaktor
- 398 Battery 4
- 888 Guitar Rig & FX
- 453 Massive X & Synths
- 1.4K Other Software & Hardware
- 6.2K Maschine
- 7.8K Traktor
- 7.8K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators