Sustain bug in Mainstage 2.1.3?

I'd simply compress/archive the current Mainstage version and keep the zip file and buy the new version from the AppStore. This way you could go back to the old version, just in case. Although the evb3 works quite well in that version. AFAIK, the 2.2 is an upgrade thru the AppStore, so the chance of getting an unpaid update is low.

Best,

DaCaptain.

Well, I’m a little sad—just to stay polite as the community terms of use require—about Apple’s bugfixing strategies. I’ve been waiting for this fix quite a long time. And now I just read that it’s fixed since more than a month. But I didn’t receive an update. Because the good guys at Apple decided that it might be a good idea to let all those old customers pay for the next update. For me the point is not that I’m not willing to pay for new features from time to time. Maybe I’ll buy MainStage 2.2 for the direct MIDI mapping thing. The point is, that this fix cannot be such a big thing (the Logic evb3 has been fixed as mentioned earlier), while the bug actually is very disturbing.

Ok, long story short: I kept wondering why there are two different versions in Logic and in MainStage. So I took a closer look and here’s what I found: A little copy and paste would fix it all!

mv /Applications/MainStage.app/Contents/Resources/evb3.res /Applications/MainStage.app/Contents/Resources/evb3.res.old

cp -R /Applications/Logic\ Pro.app/Contents/PlugIns/evb3.res /Applications/MainStage.app/Contents/Resources/evb3.res

The res-files are just the artwork for the plugins, they are not the actual code... Your change either does nothing or break the app.

Yes, it‘s just the artwork AND it’s Info.plist and version.plist that point to evb3 version 9.1.4 resp. 9.1.6 in MainStage.app 2.1.3 and in Logic Pro.app 9.1.6. I think that’s what makes the actual “bugfix“. I have to admit that I didn‘t diff all the files in the res-folders, just made sure they got the same directory structure, and are thus potentially exchangable. So copying the whole res-folder was a quick and easy way to find out if it fixes the bug. And for me it worked—no hanging notes anymore. Now Apple might have had some good reason to let MainStage 2.1.3 still rely on evb3 9.1.4 and of course I‘ll have to test it before the next gig. But if the only reason was, that such a tiny change wasn’t worth a new MainStage version number … well, here is MainStage 2.1.4.DIY.

you might want to post this over in LogicProHelp...

Yeah, if the fix for Apple had been this easy all along - then I'm still disappointed in their non-reaction to solving the bug *after* it had been already corrected in Logic itself. Oh well...

That said...

I really do recommend picking up MainStage v2.2.1, there's more than just parameter mapping - I am definitely getting better performance out of my MBP now - I had to revisit some things, such as telling Kontakt to not do its own multi-processor management, and I stopped using Kontakt's memory server (even had to use this before while running 64-bit). The new settings for buffer sizes also helped quite a bit... My first reaction to v2.2 was... "I need to go back", but once I spent an hour working thru what I had done previously to make it all "fit" and work, and re-tested those options, it's actually more than pretty good right now!

Totally worth the 30 bucks in my opinion. Remember, if there's no revenue stream going to the new, unbundled MainStage - it's not going to get much attention...

Can you summarize the improvements/changes included in 2.2.1, or point me to where omeoe else has already done so? My 2.1.3 is working fine with heavy usage - but I'm always interested in something new, something more.

Thanks!

http://bit.ly/zzgCx9

HAR!