Page 1 of 1

MachFive ver 3.0 / 3.01 Unsaved Changes Bug

Posted: Fri Sep 23, 2011 7:28 am
by MIDI Life Crisis
I'm excerpting this from my mini review since it is important ...critical even... and it hasn't been fixed in the .01 update released 9/22/11. This must be addressed and soon.

MOTU must face! [inside joke]
With DP hosting it, DP will remember the last loaded M5 patch (as long as you save the project but there is no warning that you changed a patch so if you don't save and change a patch the last saved project patch will appear). If you change or tweak the M5 patch and quit or close the project, there is no warning that the changes will be lost - and they will be lost. Perhaps there is a preference for that - I couldn't find it. Even something as simple as changing the overall volume or pan setting from within M5-3 will be forgotten, at least by the M5 plug-in.

In stand alone that is not the case. Make a change and the standalone version will warn you to save or discard the changes. I can't imagine that is a useful nor intended implementation. You do have the option to save changes to a new user preset, but not everyone remembers to do that and if you're like me, you instinctively hit CMD-s, CMD-q, grab your coffee and rush out the door. It would be nice if M5-3 would at least warn you that you have unsaved changes.

Interestingly, in Plogue Bidule, that app does remember changes to M5-3. It doesn't ask you to save them, but PB saves them. You'd think DP would as well, but no!
Image

Re: MachFive ver 3.0 / 3.01 Unsaved Changes Bug

Posted: Sat Sep 24, 2011 11:57 pm
by twistedtom
So we have to save the song in DP before we close it to get the changes in M5-3? You’re saying there is no auto saves for M5-3 changes?

Face they must!

Re: MachFive ver 3.0 / 3.01 Unsaved Changes Bug

Posted: Sun Sep 25, 2011 12:13 am
by MIDI Life Crisis
Frankly, I haven't even gotten as far as to check if it saves parameter changes in the plugin.The standalone and when hosted in Plogue Bidule does save changes, but the DP plugin only seems to save whatever the user saves, but doesn't warn of ANY M5 changes at quitting. It would appear that PB is either using a different plugin or DP is not MachFive aware.

Re: MachFive ver 3.0 / 3.01 Unsaved Changes Bug

Posted: Sun Sep 25, 2011 12:20 am
by stephentayler
What I have found is that DP's Save is not available after making a change in M5.... some other parameter has to be changed in DP, then Save becomes available and therefore M5's last change will be kept.

to be clear...... Save, then make a change in M5...... now Save is not available.....

Stephen

Re: MachFive ver 3.0 / 3.01 Unsaved Changes Bug

Posted: Sun Sep 25, 2011 12:23 am
by MIDI Life Crisis
Put another way... What's that about? And nobody at MOTU or the beta-teasers saw that?

Re: MachFive ver 3.0 / 3.01 Unsaved Changes Bug

Posted: Sun Sep 25, 2011 12:42 am
by stephentayler
I have submitted a Tech Link for this....

Unfortunately I had to file it under a MachFive 2 problem..... This is an ongoing issue with MOTU.com for UK users who upgrade through the UK dealer.... one has to wait for the registration to be filed by the dealer, it cannot be changed by the user........ not a smart system.

Stephen

Re: MachFive ver 3.0 / 3.01 Unsaved Changes Bug

Posted: Sun Sep 25, 2011 8:59 am
by twistedtom
This needs to be fixed, at least there is a work around; thanks for the heads up guys.