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).

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. 'Selected Driver not found (-10202)'. I am back to 'Selected Driver not found'. So Logic itself appears to be generating a bogus preference. Aug 13, 2009 - I installed MainStage by editing the LogicStudio.dist in the install package. MainStage 2 starts up. When MainStage started up it gave me a 'Selected Driver not found' error. So I looked into the. I have a Line6 Toneport UX1, the same problem (-10202), I will try your solution later. Hope I can use the.

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. Mister Retro Keygen Generator.

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.

I eventually found a workaround for this without having to completely reinstall Logic: delete both com.apple.logic.pro preference files (i.e. Manual Fingerplus Zt 1300. In /Library/Preferences and ~/Library/Preferences), leaving the com.apple.logic.pro.cs file; then start Logic - everything works. 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 Nov 2, 2009 4:49 AM.

One solution: repair permissions! Open Disk Utility, choose your startup voluume and hit repair permissions. Reboot and it should work ok. 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.