Live on Mac OS X - fine tuning the start-up

[8O]

Hi,

Was just taking a look at the OS X console today fixing some other stuff and saw that Live's start-up doesn't look 100% happy.

Here's my console output:

Code: Select all

10/11/2009 12:51:00	[0x0-0x17017].com.ableton.live[152]	: No custom exception handler installed.

10/11/2009 12:51:03	MIDIServer[157]	MIDIServer [157] starting; arch=x86_64
10/11/2009 12:51:03	MIDIServer[157]	PlugIn EmagicUSBMIDIDriver.plugin -- /Library/Audio/MIDI Drivers/ does not contain a supported architecture.
10/11/2009 12:51:03	MIDIServer[157]	MIDIServer relaunching because a 32-bit driver was found
10/11/2009 12:51:03	MIDIServer[157]	MIDIServer [157] starting; arch=i386
10/11/2009 12:51:03	MIDIServer[157]	PlugIn RDUSB0065Midi.plugin -- /Library/Audio/MIDI Drivers/ does not contain a supported architecture.
10/11/2009 12:51:03	MIDIServer[157]	PlugIn MIDI Monitor.plugin -- /Users/User//Library/Audio/MIDI Drivers/ does not contain a supported architecture.
10/11/2009 12:51:05	com.apple.midiserver[157]	Debugger() was called!

10/11/2009 12:51:08	[0x0-0x17017].com.ableton.live[152]	objc[152]: Class OAuCocoaWindowResponder is implemented in both /Applications/Live 8.0.9 OS X/Live.app/Contents/MacOS/Live and /Applications/Live 8.0.9 OS X/Live.app/Contents/Resources/Ableton Live Engine.bundle/Contents/MacOS/Ableton Live Engine. One of the two will be used. Which one is undefined.
10/11/2009 12:51:08	[0x0-0x17017].com.ableton.live[152]	objc[152]: Class OAuCocoaWindowDelegate is implemented in both /Applications/Live 8.0.9 OS X/Live.app/Contents/MacOS/Live and /Applications/Live 8.0.9 OS X/Live.app/Contents/Resources/Ableton Live Engine.bundle/Contents/MacOS/Ableton Live Engine. One of the two will be used. Which one is undefined.

Ok, so the top ones are OS X and Midiserver related, but the lower two are Live-related. I also someone else on the forum post the same console notification recently (can't find the thread again though). But the fact that it reports a duplicate delegate and responder class can't be good, right?

Thanks for any tips here...

Edit: this is all on OS X 10.6.2

[TobiasHahn]

Hi 8O,

thanks for the report. We are aware of the issue about the duplicate implementation. So far, it does not seem to cause any problems (since the two implementations are in fact identical), but we will fix it in an upcoming release in any case.

Best wishes,
Tobias

[8O]

Good to know - thanks for the fast answer.

[Gerald]

It is not a minor issue and it does cause Live to hang at launch in Snow Leopard. It is very annoying. Is there a way to edit the Ableton Live Engine.bundle file so it is defined as not to be used at launch? The console shows two separate paths to different engines at launch and it takes a long time for the system to time out and default to the first one.
Thanks!

[8O]

Thanks for the bump, Gerald, prompted me to check the console again with the latest version of Live.

Looks like this issue (the duplicate delegate and responder class definitions) is fixed in L8.1.1...

[TobiasHahn]

Yes, this was fixed for 8.1.1 but somehow slipped through the changelog.

Best, Tobias

PS: Happy new year!

[bodhi71]

That's weird. Didn't have any hang ups until 8.1.1

Must be a johnny come lately or something.

[Gerald]

Bump please. Old problem new plugin. Maybe the solution is to release a 64 bit version of Live?



1/31/10 11:41:59 AM [0x0-0x2c02c].com.ableton.live[390] : No custom exception handler installed.
1/31/10 11:42:01 AM MIDIServer[395] MIDIServer [395] starting; arch=x86_64
1/31/10 11:42:01 AM MIDIServer[395] PlugIn NIUSBMIDIDriver.plugin -- /Library/Audio/MIDI Drivers/ does not contain a supported architecture.
1/31/10 11:42:01 AM MIDIServer[395] MIDIServer relaunching because a 32-bit driver was found
1/31/10 11:42:01 AM MIDIServer[395] MIDIServer [395] starting; arch=i386

[8O]

Bump please. Old problem new plugin. Maybe the solution is to release a 64 bit version of Live?



1/31/10 11:41:59 AM [0x0-0x2c02c].com.ableton.live[390] : No custom exception handler installed.
1/31/10 11:42:01 AM MIDIServer[395] MIDIServer [395] starting; arch=x86_64
1/31/10 11:42:01 AM MIDIServer[395] PlugIn NIUSBMIDIDriver.plugin -- /Library/Audio/MIDI Drivers/ does not contain a supported architecture.
1/31/10 11:42:01 AM MIDIServer[395] MIDIServer relaunching because a 32-bit driver was found
1/31/10 11:42:01 AM MIDIServer[395] MIDIServer [395] starting; arch=i386

This is just the 2 seconds OS X needs to switch from 64-bit to 32-bit handling, right? No big problem.

[Gerald]

Bump please. Old problem new plugin. Maybe the solution is to release a 64 bit version of Live?



1/31/10 11:41:59 AM [0x0-0x2c02c].com.ableton.live[390] : No custom exception handler installed.
1/31/10 11:42:01 AM MIDIServer[395] MIDIServer [395] starting; arch=x86_64
1/31/10 11:42:01 AM MIDIServer[395] PlugIn NIUSBMIDIDriver.plugin -- /Library/Audio/MIDI Drivers/ does not contain a supported architecture.
1/31/10 11:42:01 AM MIDIServer[395] MIDIServer relaunching because a 32-bit driver was found
1/31/10 11:42:01 AM MIDIServer[395] MIDIServer [395] starting; arch=i386

This is just the 2 seconds OS X needs to switch from 64-bit to 32-bit handling, right? No big problem.

If it were 2 seconds I would not be bothering to mention it. It hangs with a beach ball for several minutes which although not life threatening is very annoying and impacts my workflow.

[8O]

The console log you posted is over a 2 second period. Sounds like there's something else going on with your set-up. I'd get in touch with Ableton support directly with details of your set-up and your log file. I had another similar start-up issue recently (unrelated to the issue in this thread) and thanks to some emails with support, the cause was very quickly identified.

[Gerald]

The console log you posted is over a 2 second period. Sounds like there's something else going on with your set-up. I'd get in touch with Ableton support directly with details of your set-up and your log file. I had another similar start-up issue recently (unrelated to the issue in this thread) and thanks to some emails with support, the cause was very quickly identified.

Thank you. I have already emailed Ableton about this. I thought it might be related to your original issue because it appeared to me to be a failure to properly implement -arch which is going to load 64 bit executables by default if you make the value =x86_64. Googling the issue reveals different opinions as to where the branching should take place in order to accommodate different platforms like PPC or Intel. It worked before but now Snow Leopard seems to take longer to timeout while it first loads 64 bit and then 32 bit drivers. I guess the problem is if you impliment -arch=i386 higher up you leave out PPC Users which would limit your revenue. I am just tired of all the 32bit/64bit crap and felt like complaining. Problem is I am not a programmer (but I took a class in college that makes me dangerous) so I am left with trying to answer the question myself which I am finding is not good for my mental health.