Why is Logic so Unstable?

After working on a track for the best part of the morning, Logic decided to crash on me again...
I had saved my work, but there are a few things I have lost.
My question is this.. Why is logic so unstable? I have used logic since 1999 and never have I experienced it to be this bad.
I get random crashes with Logic Pro but with no other Apple app.. Final Cut and others work like a dream on my machines.
Logic can crash at any point it wants and I can never replicate the crash or figure out why.. I always keep my system tidy, repairing permissions on installs, Onyx, Disk warrior all the time. I have completely erased and installed my Mac HD writing Zeros to it and still get these problems.
I have third party plugs like RMX, Ivory, IK Philharmonik, and others, but all with reputable companys who have all released regular updates that work with all versions of the present Tiger OS. I have also tried running Logic with no third Party plugs, and still get random crashes.. but who would want to as the factory sounds are not as good as my third part plugs.
Many people say it is third party plugs that cause instabillity, which if it is the case, is even worse on Apple's part as no other DAW I use (with all same plugs) crashes like this....period.
DP, Pro tools, they all work great.. Trouble is I know logic to well to switch to another DAW mid project.. Besides, why shouldnt we be able to use third party software with Logic if other apps handle them perfectly??
Does anbody else have similar experiences or find that Logic Pro seems to be overlooked and way under-developed in terms of its basic stability?
I know that WWDC is coming up, but to me, even if they do release something that will be the killer app, I feel that the way they have treated their Pro customers in not developing Logic Pro sooner and quicker is a swift reminder that Apple is far more concerned with other things and not its professional and loyal music making customers? (Garage band users not included!!haha)
I had to vent this somewhere..hope you all understand where I am coming from!
thanks..
Two G5 Dual 2.5Ghz, 2.5GB Ram, Logic Pro 7.2.3   Mac OS X (10.4.8)  

Just to stay with the subject for a second (myself included...)
I always keep my system tidy, repairing permissions on installs,
Onyx, Disk warrior all the time. I have completely
erased and installed my Mac HD writing Zeros to it
and still get these problems.
OK, I see you've given her the ol' "this is going to feel cold and intrusive". Do I take it to mean that you re-installed the OS from the factory disks as well?
Also, might be time for a firmware refresh.
Regarding doing Onyx/Disk Warrior "all the time"? I'd suggest that you don't make this a regular practice (I know some people will have my head for saying that). But the reason I say this is that I actually find that Logic feels particularly unwieldy after doing a full Onyx run-through. It takes a couple of Logic crashes before it all sorts itself back out.

Similar Messages

  • 2 Projects open at once... WHY IS LOGIC 8 SO UNSTABLE?!!

    Why is Logic 8 sooooo... slow & unstable with two projects opened at the same time? I know Core Audio can be disabled to speed things up & improve stability, but often the things you want to copy from one project to another involve Core Audio (EXS, Channel Strip settings etc). (I also know that you can save & re-load settings, but often you need both projects open to visually identify what needs saving or copying)...
    The problem it seems, is every time you switch between a project, it insists on re-loading audio files & samples - surely with the amount of Ram most modern computers have Logic 8 should be able to handle both project's assets at the same time? Alternatively can't programmers come up with a "Disable Audio File Load" command instead disabling Core Audio?
    This really is an essential part of modern production - something Logic 7 used to handle without breaking into a sweat - what's your problem Logic 8?

    Yes, when you move between the two songs, Logic will insist on reloading all it's samples, plug-ins etc. That is why you want dis-able the audio core. I've also found dragging a track between two songs, will sometimes cause Logic to crash.
    My work-a-round is this. I make extensive use of Apple's 'Grab' application. Open the song you want to copy from. I take pictures of arrangements, close up, zoom outs, etc. to get overall view of song and detail. You might take pics of the virtual instruments faceplate (so I can see patch). Use 'save performance' for each track you want to copy from. Give names like 'song21-bass' etc. You can also use 'save channel strip setting as' - but 'performance' is more complete. Now also export the midi for that track, and possibly audio, if you're going to use same patch in new song.
    When you've done that. Close song completely and open new song. Use the pictures you took for reference. To create your virtual instrument tracks, create an instrument track and look under setting. all your new 'performance' instruments will be there. Click on one to open it. Now import the corresponding MIDI track that you exported for this earlier.
    Once you've done this a few times, it's a lot faster than dragging tracks between two songs, waiting for core audio reload, and hoping it doesn't crash.

  • Why is Logic Express 8 keep stopping after 2 sec, every time I press play? Help!!!

    Why is Logic Express 8 keep stopping after 2 sec, every time I press play? Help!!!

    Its likely to be caused by Ozone5.. many people have reported that plugin is currently quite unstable and are awaiting updates from izotope to fix the problem... No ETA has been given by izotope for the fix however...
    Also several of your plugins are out of date (Zebra2, Clariphonic, Ozone itself.. to name but a few,)
    Finally, you are running an older version of Logic Pro X (10.0.3)...and  I would normally suggest you update to the latest version  but... if you have a USB2 audio interface do not update to 10.0.5 at this time.... unless you know it will work correctly with the new version of LPX.

  • Can anyone answer why in logic pro X I keep getting a window popping up that says Directory not found, result code= -120, followed by another window saying, Fade update failed, (error -120)?

    Can anyone answer, why in Logic Pro X I keep on getting a window popping up saying, Directory not found, result code = -120. Followed by another window saying, Fade update failed, (error -120)?
    I am running the latest version 10.0.5 through a Macbook Pro that has just been upgraded to 16GB Ram and a 960GB SSD which has made it as fast as ****. I upgraded because I was experiencing problems before and it was suggested that I didn't have enough Ram?
    I am using a Focusrite scarlett 2i4 and an Alesis Q61 midi controller. Weirdly, just trying to put a bass line down on a track using the Alesis, the bass sound goes out of tune with the track during recording only. This is very frustrating! I surely can't be the only one experiencing this?
    Many thanks
    Rob.

    Hi
    Time lost could be a problem, but.....
    Sadly, I don't think that there are any Apple docs relating to networked storgae issues with Logic. Other than a 'school' or 'business' setup, NAS/OD/AD setups are not usual circumstances for audio.
    If the issue is one of data backup & security, it may be enough to automatically backup the students local work folders to the NAS.
    If the issue is one of the Users being able to work from any Mac and pick up their files from the server, you are not likely to resolve this problem, without copying the files to the Local Mac.
    CCT

  • Why is logic asking for a Serial number

    Why is logic asking for a Serial number.

    It means you've had another "Version" on your drive before.
    The App store version does not require a serial number unless it sees certain files that indicates a previous installation of Logic.

  • Why is Logic 10.0.5 crashing every time I try to load the "Sausage Fattner" plugin

    Why is Logic 10.0.5 crashing every time I try to load the Sausage Fattner plugin by Dada Life?  It was working perfectly before the 10.0.5 update.  Is anyone else having these problems??  Plugins don't get anymore basic (and useful) than the Sausage Fattner....

    If you own "Sausage Fattner" you'll find a update in your email that solves this problem.

  • Why does Logic keep showing me black every time I hit spacebar?

    Why is Logic doing this?

    BBecause you upgraded to Mavericks and have a Logic version before 9.1.8. Earlier versions are not compatible.

  • Why is Logic 9 on mac book pro 13 inch so unstable?

    I have a 2.4 Ghz i5 4GB macbook pro and experience lots of glitches and freezes using Logic Pro 9.
    Never happened before on any previous mac books I owned. Makes me worried because I also use it on stage and Apple never, ever updates Logic 9!
    thx!
    Nutville

    By the model with the fastest cpu you can afford with the standard ram and hard drive because those 2 things can be upgraded by the user. That is if you are looking at the standard mac notebooks and not the retina models.
    I agree with the above post that a 15" with discrete graphics would be a better choice for your needs.
    With whichever model you choose factor in the cost of the extended applecare warranty because to fix any mac computer once the warranty is over is very expensive. So much so that in some cases it would be more cost effective to just buy a new computer with newer technology then to fix one that is 1+ to 3 years old. With the applecare extended warranty you will get at least 3 years use out of it with no worries of a repair bill should anything go wrong.
    Note that no apple warranty covers any accidental damages. From dropping it to spilling water on it or general misuse or abusive treatment of the system.

  • Why does Logic 9 not work with Snow Leopard?

    I have the basic system and it fails to load everytime.  Had to reinstall Leopard and lost all my prefs... very much a pain.  I don't understand why Apple makes updated operating systems and doesn't ensure that their own products are compatible.  Apple was my favorite but after this, it was way to much drama.  Had a client from out of town watching me reinstall everything because of this issue.

    Hey, Listen I feel your pain Ive gone through **** the past month with the exact same problem!
    I upgraded my system with bigger hard drive and mem, and Snow Lepoard!
    Got my Logic Studio and after a month of trouble shooting on here and with Tech Support it did
    turn out to be because of Snow Lep! I tried all the updates, un install Logic Studio.
    But the guys who put Snow Lep on my system did it in the shop and didnt charge me. I didnt think
    too much into it really. So basically it was an illegal copy of Snow Lep. I went and bought a copy. Un installed
    Snow Lep and put the legal one on. Its been working fine since!

  • URGENT! Why doesnt logic ProX, profx8, and mbox mini 2 record?

    I have all my equipment set up and all working as in i can hear my Mackie mixer on and i see that my mbox mini is connected on Logic but when i record nothing gets recorded! Yet everything is working fine i can hear the Fx from my mixer and logic recognizes my mbox so why cant i record? please help ive been at this for weeks! Thank you for your time.

    Yes, my Logic Pro X is at version 10.0.6. Any other suggestions? They are highly appreciative.

  • Why Does Logic Pro Repeatedly Asks for Serial # and XSKey When Started?

    I've purchased and installed an upgrade to Logic Studio 9. I previously used Logic Pro 7 but did not have it installed on my MacBook Pro when I installed Logic Studio 9.
    The installer asked for the Logic Studio 9 serial number which I entered and then prompted for the original serial or XSKey. I dug out the Logic 7 XSKey, plugged it in and it was accepted so I could continue with the installation which completed successfully.
    So far so good.
    But now Logic Pro 9 asks for the serial number and XSKey every time I run Logic which isn't what I expect. I re-enter the new serial number and then plug in the XSKey which is accepted and the software runs as expected, but I would prefer not to have to do this every time I start the application, in particular because I don't want to carry the XSKey around with me at all times.
    Why isn't Logic 9 storing my serial number? Why does it ask for the serial # and XSKey every time I start the application?
    I'm not running Logic as an admin user. Could this be preventing Logic from storing the serial information?
    Any help would be greatly appreciated.

    I had this when upgrading from 7 to 8. What I did was plugin the xskey BEFORE I started the upgrade and it never asked for a key or serial again after that.

  • Why does Logic Pro 9 add 0.3s silence at start of all my tracks when I "export all tracks as audio files"?

    OK - when I "export all tracks as audio files" it works fine - I get a load of exported tracks (annoyingly with the stupid "_bip" prefix at the end).
    But I find that they all have about 0.3s silence inserted at the start. WHY??!!!
    I checked, and on the timeline all the tracks start with their first note at the beginning of the track so there is no silence in the arrangement. But still this silence on export.
    This Logic feature is so badly designed - why can't it do the simplest things as expected.

    rbdavis wrote:
    Thank you I will look into plug-in latency compensation. However, there is no latency or need for latency compensation when outputting offline files in this way. Latency compensation is for live playback where real-time processing matters. So this is flawed software design, hence my comments about it being illogical.
    "there is no latency or need for latency compensation when outputting offline files.....etc"
    You don't fully understand how Logic's audio engine and buffering scheme works... not that anyone fully does except the programmers. Basically your above statement is incorrect, as some plugins have built-in-latency and others don't, but that's not the complete picture. The problem is a combination of a plugin's built-in-latency and how Logic buffers data. Logic deactivates the audio engine when stopped, all plugins and software instruments become deactivated including the ability to load or purge data buffers with the exception of a software instrument or audio track that is selected for "live" input.
    (Look up Plug-in-Latency Compensation in the manual for a full explation of the choices available)
    I won't disagree with you about the software design, however, rather than flawed I tend to think of it as antiquated. The positive side of this is extremely low processor use and the ability to design templates with all plugins and software instruments loaded and ready to start a new project. The downside most Logic users are familiar with...  unexpected overloads in the middle of a project when a approaching a region that makes use of processor intensive plugins, Loops that don't match up perfectly when starting a project from bar 1 and/or missing notes at the beginning of MIDI loop if starting at bar 1.... plus a half dozen other anomalies related to Logic's "efficient" audio engine. The efficiency concept made sense back when computers didn't have enough power to handle active or semi-active plugins, seems it causes more problems than not these days.

  • Why Is Logic Express 9 Afraid Of 2 GB Files?

    I use GarageBand to record my podcasts. Sometimes - when the duration of the mono recording is approximately 1 hr - GB (32-bit) will crash when I try to export to MP3, because it's running out of available memory. I'll leave aside what I know about programming in 32-bit, and how UNIX-based OSes shouldn't have too much difficulty turning a 1 gigabyte GB proprietary data file into a 30 megabyte MP3.
    I purchased Logic Express 9 because it could operate in 64-bit mode, and be able to get to the remaining 4 Gb of RAM on my iMac that GB couldn't see. For podcasts around 1 hr, this worked. However, now I've got a 2-hr podcast from GB, and LE9 is complaining that "the maximum file size of 2 GB has been exceeded." There's a post at:
    http://discussions.apple.com/message.jspa?messageID=6149049
    but back in 2008 the posters expected Apple to fix this. The last post was three years ago.
    Back in the days when Macs came equipped with drives that had 10's of gigabytes of disk space, I could see where putting 2 Gb out into the file system might be dicey. But my new iMac has over 1,000 Gb of space. Apple, are you kidding me? This is an arbitrary limitation for a machine that is both 64-bit and has 8 Gb of RAM not to mention 500 Gb of free disk space. ***?
    The previous article had some suggestions that I'm about to try. But this is just stupid.
    So, just to ask: is Logic Studio better? Did Apple hamstring Express? What about Logic Pro?
    Cheers,
    karl

    Fox:
    My apologies for taking so long to  get back to you. I need to pay more attention!
    So, GB really does crash when trying to export to MP3 of anything longer than about 1 hour 15 minutes or so. I did find a fix for this - there's an option in Preferences that if turned off GB will stop trying to do some kind of whole-track normalization while it does the MP3-compression. I haven't tried this on the 2-hour recording, but it works for the 1:15 recording. While in its failure behavior (i.e., before I turned off the option), I watched the memory usage of the entire machine while GB attempted to compress the MP3 and it crashed ("The application GarageBand has unexpectedly quit") as soon as it ran out of memory (i.e., its memory demands were 4+ Gb, which is the max for all 32-bit apps).
    LE spins the beachball and then displays the aforementioned message about a max file size of 2 Gb. LE is running in 64-bit mode, but I have no idea why a file size of 2 Gb is a problem for it. Especially when the resulting MP3 file is smaller than 100 Mb.
    My guess: Apple didn't stress-test either of these products with Really Large Files.
    Good luck with your endeavor!
    Cheers,
    karl

  • Why is Logic so stable?

    My Logic setup only ever crashes when I load too many K2 instruments for its RAM. I am a pro, it's my job. Big arrangements/dialogue mixes.
    Why doesn't it crash as often as for the people for whom it crashes a lot? I feel left out.
    Back to work.
    Paul.

    hi, all.
    yep, my old thing just keeps on keepin' on, atm.
    i think a lot of users that do have problems post here in the hope apple notices their problems, plus the usual ranters, trolls, and misfits.
    i do know a number of users, and out of those pilot error (both osx and LP7) is the main cause of grief .
    next is 3rd party software, and then hardware/driver conflicts.
    my system is used 24/7 and i know it so well now that even the slightest deviation from the norm i notice.
    i have a strict routine of maintenance and back-up - i have DVDs that strech back to projects over 6years ago.
    i'm basically happy with my set-up, but, like many others, i'm not so trilled by apple.
    best, david r.

  • HT4229 Why dosent Logic Express 9 work with OSX Lion on the iMac?

    Why dosent my Logic Express 9 work on the OSX Lion on my iMac desktop computer?

    You're no tard - had exactly the same issue myself. You'd think logic would have some built in message that suggests you run a software update before opening...

Maybe you are looking for