Logic 9.0.2: "Selected Driver not found (-10202)"

Question

Level 1

0 points

Logic 9.0.2: "Selected Driver not found (-10202)"

I am running Logic Pro 9.0.2 on a Macbook Pro (10.5.8), using a Steinberg MI4 audio/MIDI interface (whose drivers & firmware are up to date). This setup works fine with all my other apps (Ableton, Reaktor, Guitar Rig, etc), but when I fire up Logic, I get the error message in the subject line. The CoreAudio preferences in Logic show 'none' for input device and nothing at all for output device. I reset the MIDI devices, just for grins, to no avail. All the plugins in my project have a line through them, even the Logic stuff like EXS24. The "Logic Pro" menu on the apple toolbar contains items like "About NewApplication" and "Quit NewApplication" (!?), although the 'About' item correctly shows Logic Version 9.0.2 (1664.16). The usual 'File', 'Edit', etc. menus are missing. Although the loops browser works, the Library shows up as empty (hence all the missing plugins), even after I refresh the library.

Thinking that the preferences might be screwed up somehow, I removed Library/Preferences/com.apple.logic.pro.plist, which fixed everything... at least until I had to reboot for another reason. Now it gives me the same -10202 error whether or not there is a preferences file. Oddly, if I then pull the plug on the MI4, Logic tells me: "Instrument “Steinberg MI4 MIDI” sends to a MIDI port named “Steinberg MI4 MIDI” of MIDI interface “Steinberg MI4 MIDI” which no longer exists." So it is somehow cognizant of the device, even though no devices appear in the CoreAudio prefs.

The Mac system settings default to the MI4 for input/output, and the Audio MIDI setup tool sees the MI4 w/o problem, as do all my other music apps except Logic...

Unfortunately, reinstalling Logic is not an option, as I am 3000 miles from the install discs. And I cannot reinstall the 9.0.2 upgrade, as the installer in its wisdom will not let me force an install over an existing 9.0.2 version, and tells me I don't need the upgrade if I first move the Logic app out of the applications folder.

Any ideas about what might so totally screw up the program's initialization? E.g., other config or cache files?

- John

MacBook Pro

Posted on Oct 28, 2009 5:16 PM

Reply

Answer 1

Oct 29, 2009 8:03 PM in response to John Pope

I have this same problem ...

but im install 9.0 again and the core audio work ...

i have a m-audio audiophile firewire

Reply

Answer 2

John Pope Author

Level 1

0 points

Oct 30, 2009 1:28 AM in response to DJ Caverna

Thanks, DJC - at least I know there is a solution once I'm not on the road anymore...

In the meantime, does anyone know a way around this problem, or if there is a way to trick the installer into letting me re-install 9.0.2 (or 9.0.1 for that matter, which worked without any problems)? I still find it amazing that there is no obvious way to force a reinstall.

- John

Reply

Answer 3

John Pope Author

Level 1

0 points

Nov 2, 2009 4:49 AM in response to John Pope

I eventually found a workaround for this without having to completely reinstall Logic: delete both com.apple.logic.pro preference files (i.e. in /Library/Preferences and ~/Library/Preferences), leaving the com.apple.logic.pro.cs file; then start Logic - everything works. BUT... if I then stop Logic and restart it, leaving the preferences file Logic created when it was just running, I am back to "Selected Driver not found". So Logic itself appears to be generating a bogus preference, which future runs of Logic choke on. If anybody from Apple is reading this, I can forward you the .plist file.

Also: when the error occurs, the telltale line from the console output is:

11/1/09 6:04:17 PM Logic Pro[5492] * -[NSCFDictionary setObject:forKey:]: attempt to insert nil key

- John

Reply

Answer 4

samplaire

Level 2

184 points

Nov 2, 2009 5:25 AM in response to John Pope

One solution: repair permissions! Open Disk Utility, choose your startup voluume and hit repair permissions. Reboot and it should work ok. Why? I suspect a folder has a corupted permissions not allowing you and any application to alter its content. I faced similar thing when playing Unreal tournament (hehe, reset is essential in my work, sometimes) and once I noticed my saves don't save anymore! Then I've noticed the saves folder is locked for any changes made by me...

Also, don't attempt to alter the folder permission settings by hand without the Disk Utility (there is a possibility to do that not using the Disk Utility) by yourself unless you are an experienced user. Before you do all that stuff, please, make a backup of your entire system volume with the Time Machine. This is essential. Lately I was playing with my 10.6.1 partition (I had problems with the trash folder not allowing me to put things into it) (my main one is 10.5.8) and I f *ed up everything and restoring the WHOLE volume from the backup helped.

Message was edited by: samplaire

Reply

Answer 5

John Pope Author

Level 1

0 points

Nov 2, 2009 2:29 PM in response to samplaire

Thanks for the suggestion - I repaired the permissions, but unfortunately still have the same symptoms. And I poked through the .plist file, without seeing anything obviously wrong.

The only thing I can think of is that I moved the Jam Packs, etc. off the system disk when I first installed 9.0 (like most laptop users do, I suspect). Though that worked fine under 9.0.1, maybe that somehow tripped up the 9.0.2 installer (a less mature and well-thought out piece of work than the main product, IMHO).
- John

Reply

Answer 6

samplaire

Level 2

184 points

Nov 2, 2009 5:14 PM in response to John Pope

Jampacks have nothing to this... Just to ensure everything: can you please check something? Please, go to your user/library and 'get info' of the preferences folder: on the bottom you should see 'sharing and permissions, they should be 'user(me)': read & write; 'everyone': No Access, where 'user' is your user account name. The same should be with the plist file inside the folder. If the settings are different than in my case then it's this problem. I don't recommend changing those settings by hand because (as I said before) I distroyed my whole system this way. But at least you would know the reason. Then you could ask in the other forum as it's the system matter, not Logic.

Message was edited by: samplaire

Reply

Answer 7

John Pope Author

Level 1

0 points

Nov 3, 2009 4:05 AM in response to samplaire

The permissions on the prefs directory and the .plist file itself are okay.

I agree that the location of the library shouldn't matter - it's just the only remotely non-standard thing about my setup, as far as I can tell.

It's too bad that the error message: "-NSCFDictionary setObject:forKey:: attempt to insert nil key" doesn't tell which dictionary it's dealing with - that would help a lot in narrowing things down...

- John

Reply

Answer 8

Nov 6, 2009 8:00 PM in response to John Pope

YES!!! YES!!! YES!!!
I got it!!! Yes!!!

Guys, I've solved my problem about that error -10202 (Selected driver not found).

I have installed in my Mac Pro (OS X 10.5.8) a document with an extension ".rsrc" to correct the position of the accents in my keyboard, like acute accent, tilde and circumflex.
That file is called "U.S. - International.rsrc" and it's stored in the following path:
"Macintosh HD/Library/Keyboard Layouts"

So, when it's properly installed, I can choose 2 country flags on the right side of the menu bar (U.S. - International and Brazilian).
That's the clue!
When I pick up "U.S. - International", my keyboard works fine with the accents, >>>BUT<<< Logic Pro 9 doesn't recognize my audio driver; and when I pick up "Brazilian", my keyboard doesn't work with the accents exactly as it shows me on each key, BUT Logic Pro 9 DOES recognize my audio driver.
So, when I want to write anything out, I will pick up the "US - International" and when I want to work on the Logic Pro 9, I will pick up "Brazilian".

I hope I can help all of you.

Regards,

Renato Veiga.

Reply

Answer 9

John Pope Author

Level 1

0 points

Nov 7, 2009 12:40 AM in response to renatovms

Bingo! Great catch! I am using the US-International keyboard layout as well, and switching to another layout during Logic startup (afterwards I can switch back) solved it. That is a cleaner workaround than having to delete the preferences file every time, and should make finding and fixing the bug trivial for Apple.

I hope while they are fixing it, they take the opportunity to improve that error message and others like it - simply printing the name of the 'selected driver' that wasn't found (instead of, er, -10202) would have made diagnosing the problem much easier and saved a lot of people a lot of time.

Obrigado Renato!

- John

Reply