Maschine Plus 1.4.4 - Long time when shutting down.

Don't get me wrong - i do not regret the purchase of M+ for one second. Just expecting NI to locate resources for continous further software development and the willingness to Listen to customer's voice.

I.e. - does anyone know a single product in the world with built in bluetooth, but disabled from scratch?

What files?

To clarify I’m talking about m+ in standalone. It’s the new backup feature, the file that is open when you have a crash, it’s kept probably in a cache folder on the hardware internal memory or sd card.

the problem is when you boot up it asks if you want to discard the crashed file or restore it.

That file must be saved somewhere in a folder, that I can maybe reach and delete it, because maschine plus is in a loop if I chose discard, or restore, I get the crashed file back when I choose restore, even if I save it and open a new file and save that one, on the next boot I t’s again the same “do you want to restore (file name with time stamp of crash) with “discard” or “restore”, again and gain and again, if I disable auto backup it stops doing it. So that must be a bug, but maybe there’s a temp workaround by deleting “that” file so we aren’t in the loop and still enable backup feature.

Do you mean automatically loading a template project on boot? Nope, only possible on MAS desktop. It might not be a good idea to auto-load projects on a device not so stable, if the project ever has an issue it might stop you from booting. I'd just make a template project with a name that starts with "AA" or "!" so it shows at the top of the list then use a computer to set it as read-only so I never accidentally save over it, not sure how this would affect auto-save tho.

“It might not be a good idea to auto load projects on a device not so stable” It has happened lots of times on the desktop, you got an error, and could just continue” And about “on a device not so stable”, sorry I can’t believe you wrote that as an admin about one of ni’s main products. It has it’s own Linux os, is the only thing of software that’s running, and as a standalone device should be much more stable than a computer with hundreds of processes ,services and programs. It’s the programming of maschine that’s all. A simple setting in preferences should be possible, to quote your own words in the last paragraph “your M+ is much more like a normal computer than an old-school low res screen standalone.” I know for sure some of those “old school samplers allowed you to set a startup template. And maybe more important, the main competition has had that option since forever...saying such a simple function is impossible is just not believable.

Go to Pad Mode and navigate to the 2nd Page.

Yes, I know I’ve done it a million times lol, and I know lots of people do that, it would be easy to add this setting in prefs, maybe in the tab for velocity (maybe the one with normal,hard,soft velocity settings)set standard full velocity value:127 or other, could be a nice option in the software too, but there you have the luxury of setting a...template where you can set it to default 127. Full velocity is full velocity after all, not 100.

People just repeat that because others said it, it holds a lot of truth for older devices but even those had bugs too.

I’m not talking about older devices,nor repeating anyone, but the flagship of the maschine series. There have been times in standalone that there where almost no bugs and it was a real joy to work with. About the time after the drum synth and bassline was introduced. It was fast, never crashed on me, had almost all the features I wanted, it was better than any hardware sampler I ever used on every aspect and my mpc one was gathering dust because it was inferior compared to m+ in standalone, in terms of workflow, sound and the instruments /fx. It was great

“An M+ is miles apart from standalones from back in the day that had 2mb of firmware, fixing a bug on 600mb of data is not as easy, not an excuse but just saying... your M+ is much more like a normal computer than an old-school low res screen standalone.”

Yes I completely agree, but as you say, it’s not an excuse. It’s about walking the fine line of stability and adding features without adding bugs. Because if you fix one bug, you can get 3 back. For a lot of people this device is a lot of money, so they expect it to work, and work better with each update not worse. I didn’t enjoy my 5 hours troubleshooting instead of making music yesterday. I even did a reset, take out the thumb drive the correct way, ejecting the sd card thinking it would help, the time lost rescanning it, trying to find the culprit but nope. I don’t expect any hardware nor software to be completely bug free, that’s impossible, certainly when you update it. But it should be workable.Better quality control on the release with maybe more beta testers internal or in a group, maybe this update wouldn’t be the train wreck it is now, I can’t imagine this all hasn’t been noticed it’s not like there are dozen of hardware versions, we all have the same device. I just read about someone that feels we are the beta testers instead.

Having to wait more than a minute for it to boot up and 2 to shut down, the bug with the backup function I described, The imo higher cpu usage, also hanging and much longer time when rescanning thumb drives , (wich makes me think the slow file reading could be the reason for the long boot time, and writing is slower so on shutdown it should and does take longer) jerky browser behaviour with larger thumb drives scrolling in the browser (wich happened a few times in the maschine soft since 2.0 and is most always a gpu problem), the update that is in a kind of loop, if you press shift and system update in prefs,it will ask to update again and countdown from 60, and there’s more weird behaviour when you read around.

Sorry if my answers could appear negative, but as a long time (1.0) user this has never happened. Feeling sad and frustrated. We can wait for an update in a few weeks/ months, but the chance to revert to the previous version would be great, hear me out.

I know there was a link for the normal software version posted, but if I could I would instantly return to the previous m+ version for standalone. Of course the system is different than native acces, but maybe a bootable usb drive or an adaption to the update server where we could choose a previous version would be great. Because it could happen one day, one wrong file, programming error that slipped through, a faulty update via WiFi could make all our maschine+ devices unusable.Save previous install file to return to.Food for thought.

Hope you understand my point of view.

1st of all, thx for your input and work around. It could work but there are some possible problems with it, if you don’t pay attention.

“Save a template project, work on your current project, save it”

Here’s the thing, if you save it you have to remember to choose “save as” and choose a different name. If you choose the quick save, your template will be overwritten.

“then load the template when ure finished and THEN turn off the M+.” If you remember to save it under another another name, and have “load last project” enabled in prefs. That could work.

the way I do it now is make template. Make a template_backup, template_backup 2. So when I accidentally write it over with save, I have 2 backups. Then I open the changed template, resave under another name, open the backup, resave as template. Gonna try your way for a while, it’s a good workaround.

Anyway I’m still rooting for an option to have it in prefs. I find that we should get the same user experience, as much as possible, like the software version.

Christmas is near...

I too noticed the slow shutdowns after updating to 1.4.4.. should have stayed on the earlier version I think. My bad.

Man, I didn't even need the 1.4.4. because I haven't updated my Maschine Desktop to 2.16 🤡