Currently Being ModeratedDec 9, 2011 8:12 AM (in response to Blueberry)
yeah... was following that one myself... down to a Yamaha Motif ES8, over USB (found a 64-bit driver so just updated that - saw that the MIDI Server process was restarting in 32 bit mode - that's resolved, was never a problem by the way, but no change).
I have a Focusrite LiquidMix 56, it "adds" a MIDI in/out, that it runs over the FireWire connect. gotta have my audio interface... so can't let go of that...
There's a MOTU ATP AV - whether it's on or off doesn't make a difference.
There's a Behringer BCF2000, which is supported, doesn't make a diff if it's on or off (I reboot in between)
and then... there's a Novation ZeRO SL Mk II... this thing was my 1st most likely choice, but it doesn't seem to be the prob either... so... but whether it is on or off, or that really messy AutoMap is running or not... no change.
MS v2.2 MIDI architecture is likely changed, as you can now assign directly from hw to some-mapping w/o having to go through screen objects first (from the release notes - I never got that far). But *what* did they change??? Really hard to nail this down, if the previous version still works, the *new* version of Logic works, Live works, anything that reads MIDI works (NI apps vs. plugs, Ivory Standalone, you name it).
Currently Being ModeratedDec 9, 2011 8:18 AM (in response to michaelhuisman)
Did you figure out which device/driver triggered that issue?
Regarding MS 2.2: The table view for all active mappings (concert/set/patch level) is brand new. It also allows you to create a mapping/assignment without a screel control, which is what you ask for: control a plugin parameter without going through screen objects first.
Currently Being ModeratedDec 9, 2011 9:20 AM (in response to Blueberry)
not yet... haven't figured out which input is causing this.
as for that table view... it's not that I asked for this... I think it's *interesting* and likely better in terms of resources... it seems like a good idea.... I'm actually still trying to get that far :-)
my issues have been manifesting itself on my main studio machine (not the live rig). that's an 8 core MacPro. I could see (briefly) the two times that MS actually ran (which makes me wonder why it otherwise won't...) that multiple cores were in use, but I really want to see if my live rig, which is a 17" MBP from the summer of 2009, if two cores can/will be used better than they have been to date. Have held off on updating this machine because the usage of cores wasn't great anyway... perhaps now I'll make the jump.
at any rate... installed version 2.2 on the laptop (no midi devices, no audio interface) and here MS v2.2 starts up fine.
back to the mac pro, and I guess I'll start with nothing, add devices one by one and see what happens.
again, I just wish I knew what has changed whereby the situation no longer matches up with what v2.2 is expecting.... because *everything* else works just fine...
Currently Being ModeratedDec 9, 2011 10:15 AM (in response to michaelhuisman)
When you say you 'saved version 2.1.3' what do you mean.. or maybe, how did you save it? Reason I ask this is that it seems that the App Store install will seek and update the app not by using the app name (as in the past when if you renamed the app it couldn't be found by the updater). So I'm just wondering if something happened during the upgrade process on the Mac Pro.
Currently Being ModeratedDec 10, 2011 8:48 AM (in response to michaelhuisman)
been on this ALL day. no repeatable success unless there are NO MIDI devices at all.
Monitoring the console indicated that the USB MIDI driver for my Yamaha ES8 wasn't 64-bit, so I updated that.
There are no differences in console messages during startup of MainStage with the following exception:
during v2.2 startup it immediately posts two messages
16:26:08 [0x0-0x80080].com.apple.mainstage: MTEngine
16:26:08 [0x0-0x80080].com.apple.mainstage: MTEngine>
I don't know what this is, but v2.1.3 doesn't post these messages on the console.
OS X seems to recognize that the process has hung as it posts this message on the console and creates a logfile
Saved hang report for MainStage version 2.2. (419.23) to /Library/Logs/DiagnosticReports/MainStage followed by a timestamp, then the name of this machine ".hang"
To say that I'm flabbergasted by this is an understatement.
I thought to give reinstallation a thought, so I deleted v2.2 of the app, also removed it from the Launchpad (I never use this, it's just that the App Store installs here).
Then it got even weirder... unlike the iOS app store, the Mac app store app insisted that MainStage was already installed on this machine, and offered no way of reinstalling...
I restored v2.2 then from my nightly clone of the startup disk.
Should there be someone who can read the "spindump" I'd be happy to post... but I'm truly not a happy camper at the moment.
Currently Being ModeratedDec 10, 2011 9:45 AM (in response to Blueberry)
Thanks Blueberry..., really...
no way to attach a dumpfile to on that site... if I throw the contents of the dump into the text, the website kicks my feedback response out with an error.
I'm a little tweaked at the MainStage team today.
All I really wanted was the EVB3 sustain pedal fix that they released in Logic months ago... that I had to *pay* for that... okay... not chique, but whatever.
that I paid for this and it won't even start up???
that's just plain bad...
I've lead technology projects of all kinds for a long time... my question is simply "Who tested this?"
Currently Being ModeratedDec 10, 2011 10:13 AM (in response to michaelhuisman)
I totally get your frustration, but you seem to be the only one with a hang at launch while initializing MIDI, so there must be something special to your setup. The trick is to find out what! Can you post the spindump here and reference to it in the feedback - I am sure the Apple guys will find it that way, too.
Currently Being ModeratedDec 10, 2011 5:19 PM (in response to Blueberry)
I'm having the same problem. if my midi interface is turned off, Mainstage comes up ok. With the midi interface turned on the initialization hangs. Everything worked fine before the "update."