MachFive 3.2.1 update available

[mikehalloran]

(although, ironically, not MF 3.2.1), usually a week or so, after they are noted here.

Of course, MOTUNation is not affiliated with MOTU. If I don't hear about it here, I normally don't know. There are quite a few users (the vast majority?) who don't frequent these boards, unlike you and me.

If MOTU is worried about a massive hit on their servers (justifiable), they can do what everybody else does: roll out the announcements over time. I notice that even Apple does that. App Store and Software Updates are never rolled out at once. Taking care of as many Macs as I do, I observe that every time Apple rolls out an update. Often I'll know about it one to three days before I see the announcement from Apple and different users get notified on different days. I often read about them here first as it turns out.

[bayswater]

... roll out the announcements over time. I notice that even Apple does that. App Store and Software Updates are never rolled out at once.

Seems to be not working out that well with the 10.9.2 update.

[mhschmieder]

As I had to register and authorize TrueKeys Ravenscroft tonight, I noticed finally the reason behind my error messages in MachFive: I had moved my MachFive V2 license to an extra iLok that I use for dead products and products that have been updated with new licenses or have shifted away from iLok licensing.

As soon as I dragged my MachFive V2 license back to my main iLok (the only one I keep plugged in), I stopped getting startup errors for the four MachFive V2 component libraries.

[MIDI Life Crisis]

That should be a sticky and added to every upgrade box on a hot pink slip of paper! I'll have to check to see if old M5 authorizations are on my ilok.

[bkshepard]

I had the same thing. My MF v2 authorization was on a different iLok for apps I no longer use. As soon as I put it on the iLok that had v3 all was good.