Problems starting Logic pro

I have just installed logic pro upgrade software 9.0 then updated to 9.1 logic 7 was installed before this and that fired up fine. on trying to open 9.0 or 9.1 I get the following error
Logic pro quit unexpectedly: opening the report gives the following info:
Process: Logic Pro [268]
Path: /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
Identifier: com.apple.logic.pro
Version: ??? (???)
Build Info: Logic-16972300~1
Code Type: X86 (Native)
Parent Process: launchd [88]
Date/Time: 2010-01-15 23:28:12.988 +0000
OS Version: Mac OS X 10.6.2 (10C540)
Report Version: 6
Interval Since Last Report: 100998 sec
Crashes Since Last Report: 3081
Per-App Crashes Since Last Report: 35
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
Dyld Error Message:
Library not loaded: /Library/Frameworks/XSKey.framework/Versions/A/XSKey
Referenced from: /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
Reason: image not found
Can anyone shed any light on my problem?
Cheers

Have a look through this thread:
http://discussions.apple.com/message.jspa?messageID=9879826#9879826

Similar Messages

What is going on ?!?!? I can't start logic pro in 64-bit mode

I have been struggling with this issue for a while now, but I haven't made any progress. I am unable to start Logic Pro 9 in 64-bit mode. And when I say that, I mean that if I select the Logic Pro app in Finder, and say "Get Info," there is no "Start in 32-bit mode" option like all of the tutorials say to do. It used to show up, and I was able to start in 64-bit mode just fine, but suddenly, the option is not there, and the app is starting in 32-bit mode.
My Mac/OSX have been running so well, that I'm not too knowledgeable about where to even start looking for a solution. I am very comfortable with the Terminal, etc, so I can follow directions well, but I don't know where this problem stems from.
The machine is running in 64-bit mode, ie, if I do uname -a, it does return that the system is running in 64-bit mode. Logic runs just fine outside of not starting in 64-bit mode, but I want/need to be taking advantage of all of the RAM I spent so much money on.
I'm not sure what info would be needed, but here goes:
Mac Pro 3,1 (early 2008), 8-core 2.8Ghz.
10GB RAM
4 SATA HDDs
NVidia Geforce 8800 GT 512MB RAM
OS X Mavericks with all current updates
Logic Pro 9.1.x, again, with all updates available.
Steinberg UR22 audio interface (USB)
Also, I'm not sure if it matters, but I also have Windows 7 installed through Bootcamp, and it is running fine, and recognizes 32-bit/64-bit apps just fine.
I hope that's enough for someone to be able to tell me where to start looking. I really don't get it. This was happening when I first installed Mavericks. I ended up doing a fresh install from USB stick, and everything was going fine. I don't think that an update has changed things, as the last time I opened Logic, it did open in 64-bit mode. Suddenly though, that option is unavailable.
Is there a plist entry I can edit that will force it into 64-bit mode?
What part of the OS is in charge of this type of thing?
Any help is greatly appreciated.

Could be corrupted preferences.
In the Finder, choose Go > Go to Folder from the menu.
Type ~/Library/Preferences in the "Go to the folder" field.
Press the Go button.
Remove the com.apple.logic.pro.plist file from the Preferences folder. Note that if you have programmed any custom key commands, this will reset them to the defaults. You may wish to export your custom key command as a preset before performing this step. See the Logic Pro User Manual for details on how to do this. If you are having trouble with a control surface in Logic Pro.
Be sure and use the ~ character in the path name.

Problem starting logical host on eGate 5.1.0

I'm having problem starting logical host for eGate 5.1.0 on Linux platform, and I cant see where is the problem lies. Is there anybody here that can give me some hint or guide?
Below is the error message from the log.
[#|2006-08-22T17:57:28.506+0800|WARNING|IS5.1|javax.enterprise.resource.jms|_ThreadID=11; ThreadName=STCMS process monitoring;|STCMS process ended unexpectedly with exit code 1; initiating application server restart|#]
[#|2006-08-22T17:57:28.567+0800|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=11; ThreadName=STCMS process monitoring;|sending restart notification to server...server|#]
[#|2006-08-22T17:57:28.721+0800|WARNING|IS5.1|javax.enterprise.system.tools.admin|_ThreadID=12; ThreadName=RMI TCP Connection(1)-127.0.0.1;|core.tmp_folder_deletion_failed|#]
[#|2006-08-22T17:57:28.722+0800|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=12; ThreadName=RMI TCP Connection(1)-127.0.0.1;|stcms.alert_shutting_down|#]
[#|2006-08-22T17:57:28.722+0800|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=12; ThreadName=RMI TCP Connection(1)-127.0.0.1;|stcms.broker_shutting_down|#]
[#|2006-08-22T17:57:31.020+0800|INFO|IS5.1|javax.enterprise.system.container.web|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Creating virtual server server|#]
[#|2006-08-22T17:57:31.039+0800|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|IS AVK Instrumentation disabled|#]
[#|2006-08-22T17:57:31.045+0800|INFO|IS5.1|javax.enterprise.system.core.security|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2006-08-22T17:57:31.117+0800|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|[STC JTS Extension] The last agent commit optimization is enabled.|#]
[#|2006-08-22T17:57:32.315+0800|INFO|IS5.1|com.stc.corba.any.UtilDelegate|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|[STC CORBA Extension]EE/SE Corba Util delegate loaded|#]
[#|2006-08-22T17:57:33.730+0800|INFO|IS5.1|com.stc.corba.any.UtilDelegate|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|[STC CORBA Extension]Enabling SE Corba support|#]
[#|2006-08-22T17:57:34.007+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5082: Exception running j2ee services: [java.lang.RuntimeException: java.lang.ExceptionInInitializerError]|#]
[#|2006-08-22T17:57:34.008+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=0;|CORE5091: Error executing J2EE server ...
java.lang.RuntimeException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:351)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:754)
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:233)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:222)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:374)
     at com.sun.enterprise.iiop.ORBMonitoring.<init>(ORBMonitoring.java:48)
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:236)
     ... 9 more
Caused by: java.lang.ExceptionInInitializerError
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:164)
     at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:368)
     ... 11 more
Caused by: java.lang.NullPointerException: No MBeanServer was returned by the MBeanServerFactory
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.getMBeanServer(MonitoringRegistrationHelper.java:83)
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<init>(MonitoringRegistrationHelper.java:60)
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<clinit>(MonitoringRegistrationHelper.java:55)
     ... 14 more
|#]
[#|2006-08-22T17:57:34.012+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5092: J2EE server reported following error: [java.lang.ExceptionInInitializerError] |#]
[#|2006-08-22T17:57:34.012+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5093: Error executing J2EE server |#]
[#|2006-08-22T17:57:34.013+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=1;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: com.sun.appserv.server.ServerLifecycleException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:235)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:222)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.appserv.server.ServerLifecycleException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:763)
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:233)
     ... 7 more
Caused by: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:351)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:754)
     ... 8 more
Caused by: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:374)
     at com.sun.enterprise.iiop.ORBMonitoring.<init>(ORBMonitoring.java:48)
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:236)
     ... 9 more
Caused by: java.lang.ExceptionInInitializerError
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:164)
     at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:368)
     ... 11 more
Caused by: java.lang.NullPointerException: No MBeanServer was returned by the MBeanServerFactory
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.getMBeanServer(MonitoringRegistrationHelper.java:83)
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<init>(MonitoringRegistrationHelper.java:60)
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<clinit>(MonitoringRegistrationHelper.java:55)
     ... 14 more
|#]
[#|2006-08-22T17:57:34.023+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Server Startup failed. Exiting...|#]
[#|2006-08-22T17:57:34.023+0800|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Server shutdown in progress...|#]
[#|2006-08-22T17:57:34.024+0800|INFO|IS5.1|javax.enterprise.system.container.web|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|WEB0303: Stopping Tomcat.|#]
[#|2006-08-22T17:57:34.025+0800|WARNING|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=2;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: WEB0106: An error occurred while stopping the web container
     at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:536)
     at com.sun.enterprise.web.PEWebContainerLifecycle.onShutdown(PEWebContainerLifecycle.java:65)
     at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:400)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:255)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: LifecycleException: WEB0103: This web container has not yet been started
     at com.sun.enterprise.web.WebContainer.stop(WebContainer.java:529)
     at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:528)
     ... 9 more
|#]
Hopefully somebody can help me as I'm stuck with it for few days already. Thank you.

This is what I got when I try to start the server from the directory logicalhost/is/domains/domain1/bin/
./startservAug 23, 2006 7:23:55 PM com.stc.is.util.pinger.HttpOKPinger <init>
INFO: Setting URL to http://localhost:18000
Aug 23, 2006 7:23:55 PM com.stc.is.util.pinger.HttpOKPinger isAlive
INFO: Opening connection to http://localhost:18000
Aug 23, 2006 7:23:55 PM com.stc.is.util.pinger.HttpOKPinger isAlive
INFO: Connection to http://localhost:18000 opened successfully.
Aug 23, 2006 7:23:55 PM com.stc.is.util.pinger.HttpOKPinger isAlive
SEVERE: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:365)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:477)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:214)
at sun.net.www.http.HttpClient.New(HttpClient.java:287)
at sun.net.www.http.HttpClient.New(HttpClient.java:299)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:792)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:744)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:669)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:913)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367)
at com.stc.is.util.pinger.HttpOKPinger.isAlive(Unknown Source)
at com.stc.is.util.Ping.main(Unknown Source)
Aug 23, 2006 7:23:55 PM com.stc.is.util.Ping main
INFO: IS is not alive.
Startup failed.
any clue what is it about?

Problem with Logic Pro and Soft eLicenser on Mountain Lion?

Hi!
I have a bunch of Arturia synths, which requires the Soft eLicenser to work. This has always worked great with Lion, never any problems with eLicenser (never had to open it etc.)
Now - I upgraded to Mountain Lion, and tested my synths to make sure everything was OK, experienced a bunch of problems, and did a full recovery to clean Mountain Lion.
After installing the Arturia synths, and adding my licenses, I installed Logic. Everything worked fine!
BUT!
When I closed an Arturia synth within Logic, or closed Logic after running a project with one of these synths, I couldn't reopen any of these synths within Logic afterwards - In fact, I couldn't open the stand-alones either! And when I tried to open the eLicenser Control Center, it would just say "Reading eLicensers" forever. After a reboot, everything is OK.
I can open and close eLicenser Control Center and standalone synths as many times as I want, as long as I don't open Logic, and then Arturia synths as an AU in Logic.
I found a workaround: Open the eLicenser Control Center, and let in run in the background (cmd+H), and then open Logic. Then I could open Arturia synths and close them, close Logic and reopen etc. without any problems at all. NO PROBLEMS.
Until I close the eLicenser Control Center, then I have to reboot to be able to start it again.
I hope you understand what I mean here. It's a bit hard to explain.
In short terms: Logic makes Soft eLicenser crash when a eLicenser synth has been opened as an AU.
The same problem is when scanning the AU with AU manager. eLicenser window should be open before scanning.
Does ANYBODY have the same problems? Can anyone who has these applications test it out?

So it definitely seems to be a issue with Logic.
I can't force this error in 10.7.X no matter how hard I try, but in 10.8.2 it's definitely Logic messing things up.
Could it be auvaltool which has a bug? Or is that only run with AU manager on validation?
Hopefully this discussion can get some attention, and maybe it could be corrected. I guess a lot of Logic Pro users also has eLicenser Control Center for validation of their products.

Problem with Logic Pro 7 Academic Version

I've been using my academic version of logic pro 7 for about a year, and just recently it hasn't been starting up the way it used to. Usually when it launches, it says logic pro 7: academic version. But now it just says logic pro 7 and tries to run it as a one day trial of the retail version. I tried to get help over the phone but they were saying that they can't help me troubleshoot because they can only help out with logic studio. basically, they say to just reinstall it and if still have problems post it on this discussion. so here i am after the reinstall with the problem still occurring. some help please?

i just updated my xskey from the xskey updater in the utilities folder and it works now.

Persisting Cut-off or unplayed notes problem in Logic Pro X

Hi Guys,
I've been having this persisting problem in LogicPro X. Let me just explain it here, I have a MIDI file which i got from the net, i played it in my piano role software and it was fine, but one i just imported the midi into Logic and just exported it straight away( just for experiment purposes), the notes became cut-off( example of cut-off? Ill send you the MIDI which i got on export from LOGIC aswell) when i played them in the piano roll software, and if i import and export the same MIDI in another software its fine, its just trhat ive grown accustomed to Logic Pro and i really enjoy it! I find FL studio and all those things annoying, so thats why i wondered if you guys could help me get a fix. And if something is wrong with my Logic just incase - if you guys give me your email address i will send the midi to you and can you just export it from your software and send it back to me? If the MIDI plays fine could you tell me your Logic Pro settings and such and such thanks! -And FYI if i re-open the exported MIDI in Logic its plays back fine! Im getting really annoyed and confused
PS: My piano roll software is Synthesia

You might want set up a key command for "paste at original position". My key command is command/option/shift/p. This seems to work flawlessly. Unfortunately I have run across the bug you're refering to.
Jim

Evolution MK449C Mod Wheel problem with Logic Pro/VSL Performance Tool

I'm using the latest version of Logic Pro on a new Intel Mac Pro. My controller keyboard is the Evolution MK449C, connected via a USB cable.
When using a Logic Audio Instrument assigned to the ESX Sampler Plug-in (running various samples, mostly from the Vienna Symphonic Library,) Logic's Transport Window doesn't register any modulation information generated from my keyboard.
As the VSL Performance Tool relies heavily on the Mod Wheel info to effect the sounds, I'm at a bit of a loss to spot the solution. When I assign a different conroller to the Mod Wheel, i.e. volume, pan, pitch bend, etc., I can see the info in the Transport Window with no problem, so I know the wheel itself is working okay.
Has either Logic or the ESX got some kind of controller filter, - maybe I've accidently turned something on that cuts out any incoming modulation. Can anyone help?
Thanks
Mac Pro Mac OS X (10.4.8)

It's good to know someone else is having a similar problem (if one can call that good!)
I've been poking around and I've also noticed this: If I create a cello part in Garageband, articulation works everytime I open it. If I take that Garageband song and open it in Logic, articulation still works everytime I open it. The Logic file in this instance is saved as a "Logic Song." I don't know how to tell, but I'm assuming the Logic song is drawing it's sound files from the Garageband song (I don't know how to check that).
However, if I save the newly created Logic song as a project - with all sound files being copied to folders within a master project folder - articulation does not work when I reopen the file.
Strange. And frustrating.
MacPro 2.66 2GB RAM & Powerbook 400mhz "Pismo" Mac OS X (10.4.7)

Problem open logic pro 7 songs made on other computer

i cant seem to load my iso that i have made on another logic - same spec logic etc..
this comes up - Damaged Song or not a Logic Pro Song! Search for fragments?
then when i click search, its aborts.
Anyone know why this problem is occuring?

thanks very much for helping me. the other computer is a new g5 desktop, with logic pro7 also installed on it.
i have made a track on the desktop in our studio, it includes samples that we have cut up, and plenty of midi controlling our outboard keyboard set up.
I just bought a new macbook the other day, installed logic. I then tried opening the logic file that i had made on the desktop. it comes up saying that the song is damaged etc. I then tried to put my autoload file that i have always used on logic, and it had the same problem, HOWEVER,for some reason this now works when i tried again.
So i am a little confused as to why i cant open the new tune. Other tunes seem to be opening, but they are from a long time ago. I need to work out why recent songs arent opening.
i will try re-saving the original song.. is there anything else that springs to mind that could be causing this?
cheers,

A Problem with Logic Pro 7 Crashing

Appreciate any help.
I'm running Logic Pro 7.2.0 (academic - no upgrades) on a Mac Pro w/3GB. I use an M-Audio Firewire 410.
Logic runs perfectly...AFTER the audio has been played successfully once. Before that, when I open a song and press Play, it's about 50% likely I'll get, "The program Logic has quit unexpectedly" - occasionally, this is preceeded by "Core Audio too slow" or "1 or more Files in Use."
I'll tried deleting preferences, etc. Should I re-install the program? Can this really be the solution, considering it works perfectly once the song has successfully started playing? (If I open a new song and close the 1st, I'm back to 50% likelihood of a crash.
It very seldom crashes under any conditions other than immediately trying to play a song that has just been opened. (Is this the crucial clue?)
Oh, and I'm running 10.4.10. Everything is brand new. Arghhh!
Thanks for any help you can give.

As already pointed out, 10.4.10 is not great on intel machines for audio. The latest driver for the M-Audio Firewire 410 is better than most USB ones on 10.4.10, but the lack of Logic upgrades does mean it is of an earlier time than 10.4.10 and I would try to do something about that first.
It may well be to do with the core audio system, and you may get different results if you create an aggregate device in Audio Midi Setup, including both built in devices and the Firewire 410 and see if that helps!
Karn.

Problems w/ Logic Pro 8 plugins GUI

hello all,
I am setting up a small pre-production studio at home....I have installed Logic Pro 8 and all of the updates on my Mac Mini 2.0GHz proscessor w/ 2Gb of RAM. Logic Pro 8 is working just fine. I haven't yet installed any third party plug-ins at all. But the GUI to ALL of the plugins that come standard with Logic Pro 8 does not appear. The plugins is recognized and i can playback sound and eveything, but the GUI to "all" of the plug-ins will not display.....I have tried removing the preferences and I checked to make sure that my displays meet the required settings for Logic.....Can someone please help me with this? Has anyone had this problem? I would really appreciate some feedback asap.....
system: mac mini (os x 10.5.3)
software: logic pro 8 w/ current updates

Yes, everybody who tries to run Logic Pro 8 on Mavericks. It does not work!
Either do not use Mavericks, or upgrade Logic Pro to a newer version - I think everything after 9.1.5 seems to work. Logic Pro X - of course - also works on Mavericks.

Crash report everytime i start Logic Pro X

During my installation of Logic Pro X it got cancelled, now i cant even start it and i've tried to download it again. Still only gets crash reports!

Have either of you actually tried calling/contacting Apple directly and asking them for assistance?
http://www.apple.com/contact/
Note: You have 90 days of free support when you purchase Logic Pro X so...
I always find myself wondering why people just don't contact Apple in the first place..
Answers on a postcard please.. (and Pancenter, you are disqualified from answering because I know you probably know the answer already!

Presonus Faderport problem with Logic Pro 7 running Snow Leopard

I've been been using Tiger to run Logic Pro 7 without any problems for the past few years. I've held out on upgrading to Snow Leopard since everything worked so nicely, but I finally gave in and loaded 10.6.6. Logic Pro 7 seems to be okay except for my Faderport control surface functionality. I upgraded to the newest FP firmware, and Logic 7 recognizes the FP, but it doesn't work. When I open a Logic project I get a pop up dialog box that says:
Module file "Faderport" is too new and cannot be used with this version of Logic control surfaces. Please get an update of the Logic control surface application file. I also get another dialog box that says: "Loading Module Faderport..." But nothing happens.
I'd appreciate any and all ideas on how I might deal with this. Thanks!

Hi,
I'm getting this message since updating the Faderport Firmware. I'm using Logic 7 in Tiger still.
How did you fix the install pref?

Mac Mini(2011). Problems running Logic Pro 9

I have a 2011 Mac Mini 2.3Ghz i5. I have upped the ram to 8gb. Whilst using Logic Pro 9 after laying down 5 MIDI tracks it crashes and I have to hard reset. It instantly crashes when recording audio. Any ideas?

If nobody answers here, you may want to post in the Logic Pro discussion here.

Connection problems between logic Pro X and Mackie MCU PRO

Hello, I need help.
I bought a mackie MCU control PRO and don´t work on my Logic Pro x. Does anyone know if I have to do something in the logic to configure? or should it automatically go?
Thanks for your help
This is my equipment list if you have any questions;
MAc Book Pro, Maverik IOX
Motu Ultralite
Mackie MCU PRO
Logic Pro X

Not enough information to help you.

Problem opening Logic Pro

So I had been running Logic Pro completely fine for a few weeks but then I had my computer do a software update. After it had updated I tried opening Logic Pro and it asked for the serial number again. I entered it and it said it is invalid. Any help?

If it's a legit copy, I would contact Apple and find a solution that way.

Problems starting Logic pro

Similar Messages

Maybe you are looking for