Project always (*) [not saved]

Hi to all of you, machinists

Been working on a project on Maschine, the project name always shows the asterisk at the end of file name, even if cmd + s or saving through main menu

I checked if the file was actually saving and for now, it is. I also created a backup file under another file name, but it has the same glitch.

Should I get worried, meaning I risk the file stops saving as I keep working on it (it happened once, time ago on Maschine 2)?

Restart the project now it s kind of tricky as I laid down many patterns and song elements.

Maschine has full disk access.

Any advice?

Cheers

Find more posts tagged with

Maschine 3 SW

Accepted answers

Sunborn

https://community.native-instruments.com/discussion/50549/project-always-not-saved

Your file is saved every time you click the "save" button. There is nothing to worry. It is unusual but it is not an error.

The main reason for this to happen is that you do have some FX in constant flux mode. Meaning, it is always running or making some loop, even if your project is stopped! An automation can do that too.

So, you clicked "save" (and your project was indeed saved, every time) but on the next millisecond your project gets new data (from that FX/loop/automation) so it is "unsaved" again. ;-)

All comments

Sunborn

https://community.native-instruments.com/discussion/50549/project-always-not-saved

Your file is saved every time you click the "save" button. There is nothing to worry. It is unusual but it is not an error.

So, you clicked "save" (and your project was indeed saved, every time) but on the next millisecond your project gets new data (from that FX/loop/automation) so it is "unsaved" again. ;-)

Sunborn

…to say it more "professionally" in case you didn't understood:

Maschine tracks a massive amount of metadata. Sometimes, just having the transport running or a specific plugin open can trigger a "change" state.

The cause: Modulations or "Perform FX." If you have a Touch Strip or a knob assigned to a parameter that is constantly moving or being modulated by an LFO, Maschine views every millisecond of that movement as a state change.

Do this : Stop the transport, wait a second, and hit Cmd + S again. If the asterisk disappears for a split second and then comes back, an active modulation is the likely cause.

Maxray

Yes, shutdown via Task Manager, reopen, click the "Restore Project" prompt, and attempt a resave from there.

Also, it's a good idea to create separate folders within the "Projects" folder that correspond to the DAW you're building within, such as "Cubase Projects", "Ableton Projects", "Bitwig Projects", "Reason Projects", "Stand Alone Projects", etc. Save the projects in the Native Instruments\Maschine 3\Projects folder (Which can be placed where you want through NI Access preferences) that you build in other DAWs so that you have them in case of any computer issues. I keep them on a separate drive, and they tend to not have saving issues when I do it that way. It seems to break that saving issue glitch when you go to save in separate folder than in Documents. It probably works the same way in Mac?!

Quick links

Unanswered questions