Logic Pro 8 graphic bug inOS X 10.9

Logic Pro 8 has a graphic bug since update to OS X 10.9. The the position tracker turns everything behind it into black in the the arrangement window while playing or recording - Is there a possibility to fix this bug?

Blueberry wrote:
Well, Logic Pro 8 was shipped 2 OS versions before Mavericks and is many years old. I don't think this is a push to force you to spend money, otherwise they would have done the same for Logic Pro 9 (which does work on Mavericks just fine)
That is, the very last update of Logic Pro-9,  9.1.8.

Similar Messages

  • Logic Pro graphic feedback problems

    hello I have a macbook pro 13  inch i5 thunderbolt and updated to the latest version of snow leopard quite a while ago but since i got logic pro 9.1.8 i have noticed my graphics on the multipressor and adaptive limiter are moving alot slower please help as i cannot mix my trackswithout these plugins i've tried to reinstall the update and it still didnt work anyone have any advice on this problem?

    Please see my response in this thread.....
    https://discussions.apple.com/thread/4787769?tstart=0
    ...as it appears you are having the same basic issue and my suggestion in regards to using 9.1.5 in that thread will apply to you too.

  • Is this a Logic Pro 9 bug: when I do a "Save as..." my mono tracks are converted to stereo.

    I have six mics on my drum kit, each running into a single channel input on my Mackie.
    I noticed that, after I got the sound dialed in for each of the six tracks, and finishing up one drum project, and after performing a "Save as..." to save the project settings for my next drum project, then opening the newly saved project to start recording, I was unable to "record enable" all six tracks, because they had been changed from mono to stereo tracks, and instead of using "Input 1" for track 1, "Input 2" for track 2, etc... track 1 and track 2 had both switched to "Input 1-2", tracks 3 and 4 had switched to "Input 3-4" etc... It took me forever to figure out why I couldn't find the mono inputs from my Mackie in my available options for each track.
    So now I have to go through and specify "mono" for each track and then re-select "Input 1", "Input 2", "Input 3", etc... for each corresponding track. Please let me know if this is something I can fix in the preferences. Thanks!

    I can't reproduce the problem with "Save as..." again, so the tracks switched from mono to stereo somewhere between the time I recorded them and by the time I was done tweaking their EQ and compression settings. I don't know how to delete or edit my discussion question above, sorry!

  • Macbook Pro or Mac Mini for Logic Pro X

    Hi I currently have a Mid 2011 Macbook Pro 13' with 16GB 1600Mhz RAM and a 500GB Hybrid Solid State Drive. I use Logic Pro X heavily to the point where I get crazy CPU spikes and cant work with Logic Pro smoothly anymore. (Note: I only have around almost 20 tracks and I get these spikes, I've been doing much research to reduce this but still no luck.) I can't work with freezing tracks as well due to the Logic Pro X bug that unfreezes all the frozen tracks when pressing CMD+Z. Now I really think I need to upgrade my mac. I'd want to save as much money as I can so I was thinking of the 2.3Ghz quad core i7 Mac Mini?
    What difference does the regular Mac mini make with the mac mini with the OSX Server? Do you think the $799 mac mini, when paired with a 16GB 1600Mhz ram and a 7200rpm HD work wonders for me in my music dream? Should I still go for the macbook pros. As far as portability, I think both are portable and I won't have any problem with both. When it comes to the screen, and keyboard and mouse, I have no problem in buying them individually. All I really care about is if it could handle what I want it to do at the cheapest price possible. I can't move away from the mac beacause Logic Pro X is pulling my leg.
    If you guys have any recommendations please feel free to comment.
    Thank you very much

    Ok.. a few points..
    A Mac Mini is really much the same as a Macbook Pro without the screen and keyboard..  but for a lot less money...
    The Mac Mini Server version is identical to the standard Mac Mini with OS X but on the system disk is the Server App which you must run to activate the server functionality. Dont run the server app and the Mac Mini Server is just a mac Mini running normal OS X
    Instead of freezing tracks.. have you tried Bounce in place... ?
    Overloads can often occur due to using internal audio or... the Audio interface you are using and its (poor quality) drivers.. Are you using one? if so, which>
    If you are getting overloads with that Macbook Pro then a recent Mac Mini will probably not improve the situation for you... The fact you are getting overloads could be how you are using Logic.. what plugins you are using.. what else is running ion the Mac and so on.. What processor does your MBP have. The newer Mac Minis can have faster more powerful  i7 quad cores which effectivelky gives you 8 cores to work with and that can help reduce loads...
    Note: Often starting from scratch with a clean Mac and just installing LogicPpro plus plugins (and not using it for anything else..) can speed things up anyhow...

  • In logic Pro, when I open up an audio track and load an audio file, there is no sound. I will finally get a sound out of one of the audio tracks after opening at least 5 of them alternately. Is anyone familiar with this kind of bug? It's really frustratin

    In logic Pro, when I open up an audio track or software track and load an audio file/loop or software file loop, there is no sound. I will finally get a sound out of one of the audio or software tracks after opening at least 5 of them alternately. Is anyone familiar with this kind of bug? It's really frustrating as this takes much time to complete work.
    os x, Mac OS X (10.6)

    I'm not sure I follow your words Fuzzynormal. You've helped by offering the insight that my issue in Logic Pro 9 is not a bug but a feature. But fell short of enlightenment by being a judge of character and of how one should interact in this forum. You insinuate that I haven't tried to solve the issue on my own when in fact I have. These forums are always my last resort. You further suggest that I am complaining. This is not a complaint. It is a genuine issue that I cannot figure out. Then you think that Brazeca is holding my hand and being a nice guy. Brazeca is helping people like me who might not be as adept at using Logic Pro as probably you are.This community forum was established to raise questions, answers and dicussion to help Apple's customers better undertand their operating systems and related issues. You are doing a disservice by not contributing positively and by trying to make this forum what you want it to be. You may have all the time in the world to try figuring out stuff but we are not all like you. We all have different schedules and different levels of understanding. And that is what this forum is for - to help people move forward. If you can't contribute positively then keep silent. And by the way, you say to "read the words that are printed down to explain to you how that works" what words are you talking about? Why don't you be of some help instead of trying to own this forum. 

  • When i editing in the piano roll windows, after 10 at 20 editing steps my logic pro 9 crashed down. Every time. Is this a bug?

    When i editing in the piano roll windows, after 10 at 20 editing steps my logic pro 9 crashed down. Every time. Is this a bug?

    Maybe find a local who can translate for you. I don't know what to tell you for dealing in another country for service on your computer.
    I can offer you something you can do if you want to give it a try. You'll need a backup of your data in your Home folder because you need to erase the drive. You'll also need a solid, preferably fast, internet connection.
    Install or Reinstall Lion/Mountain Lion from Scratch
    Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
    Boot to the Recovery HD:
    Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Erase the hard drive:
      1. Select Disk Utility from the main menu and click on the Continue button.
      2. After DU loads select your startup volume (usually Macintosh HD) from the
          left side list. Click on the Erase tab in the DU main window.
      3. Set the format type to Mac OS Extended (Journaled.) Optionally, click on
            the Security button and set the Zero Data option to one-pass. Click on
          the Erase button and wait until the process has completed.
      4. Quit DU and return to the main menu.
    Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion and click on the Install button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible
                because it is three times faster than wireless.

  • Logic Pro 5.1 ch plugin subwoofer channel bug report

    hello,
    I had found out that Native Instruments absynth 5.1 ch synthesize sofware , which in stand alone mode
    outputs the subwoofer channel audio properly, does not output subwoofer channel audio in Logig Pro surround
    plugin in 64 bit mode.
    I contacted  Native Instruments about this and after a certain time, they say that they did deeper invstigation
    and found out that it is the Logic bug.
    I just don't know how to bug report to the apple, so I put this here.
    Please confirm and fix it.

    The crashed thread (7) mentions logic's preferences file. (com.apple.logic.pro). Drag it to the desktop (so you can reclaim you key commands if it works) and restart logic. Logic will create a new preferences file. Worth a try..

  • Logic Pro (and Garage Band) guitar bug.

    This is a rather irritating bug that happens constantly on my set up. I can play guitar for a couple of minutes then the sound cuts out but then plays after about a three second delay. This happens in both Logic Pro 9 and Garage band but not in Ableton Live or other apps.
    At first I thought it was an interface problem (UA-101) till everything worked without a hitch in Ableton Live. The interface lights also show no delay. I've got a new MacBook pro with Leopard on it with latest versions of Logic and Garage band.
    Anyone else seen this before or know of others that have had this problem. Any suggestions of what I could do to fix it?

    Well I dont get this but I use Apogee Duet, so there could be the difference. Process buffer range could make some difference, set it to low in Preferences/Audio. The other obvious thing is to check the buffer size in preferences is set as low as possible.

  • Logic Pro X - workaround bugs

    Hi!
    Logic Pro X is still a new release (10.0.3 when writing this) and there will of cource be updates to fix bugs. But meanwhile, why don´t share some workarounds for bugs that occur?
    My first tip which for problems with recording audio is to bounce what you have and go back into Logic Pro 9 and do the recording and then cut/edit all the takes before taking it back to Logic Pro X and continue to work.
    Does anyone else having problems with recording? My LPX just quits after some time of recording when I hit the rec-button.
    My first workaround for this was to use the command "Save a copy as..." since it seems to work some more minutes before crashing.
    It clears unused memory in the file in some way I think.
    Before saving as a copy the file is always about 100Mb bigger.
    Any more workarounds?

    Does anyone else having problems with recording? My LPX just quits after some time of recording when I hit the rec-button.
    No, not here.. I finished a 10 track  1 hour live recording this weekend without issue..
    If Logic just quits, do you get an error msg, a crash log or failing that look in your console logs to see what is causing the problem.. and post up what you find/see

  • Is a dedicated graphics card better than an integrated graphics card for running Logic Pro?

    I am trying to figure out if a dedicated graphics card is better than an integrated graphics card for using Logic Pro. I have heard opinions supporting both. From what I have been told a Mac mini with an integrated graphics card would work just fine. I have also heard that a modest dedicated graphics card could also benefit Logic Pro. Honestly, I have heard more people saying that the integrated graphics card on the Mac mini would do the job. But still, I have heard a couple people (even 2 senior Mac experts) state that a dedicated graphics card (iMac) is the way to go. Maybe a Mac mini with integrated graphics card will do the job, but an iMac would do the job better, I don't know, if anyone could help me I would greatly appreciate it. Thank you.

    One thing is Logic Pro and another thing is Final Cut Pro. Logic Pro is a music production app, so it doesn't use the GPU heavily and you can use it with an integrated GPU without any problem. However, video editing apps like Final Cut Pro or iMovie will note the difference

  • Could not load Module... A known bug in Logic Pro 7.3 with Snow Leopard?

    I know this issue has been discussed before, but on my brand new MacBook Pro it's still an issue, so can someone please help me out with this?
    Here goes:
    Loading Logic 7.2.3 in Snow Leopard:
    The previously selected audio interface is not available
    The built-in audio inputs and outputs of the computer will be used instead for this session.
    <ok>
    Could not load Module "FW-1884" (-43)
    <cancel>
    Could not load Module "HUI" (-43)
    <cancel>
    Could not load Module "Logic Control" (-43)
    <cancel>
    Could not load Module "TranzPort" (-43)
    <cancel>
    Logic loads, and everything seems to work just fine.
    <selecting a plugin ---> Bass Amp>
    CoreAudio:
    Resource not found. (-10109)
    This happens no matter which plugin I choose - Bass Amp, EXS 24, ES1 etc…
    <Continue>
    The plugin loads, and works, but the display is in "Controls" Mode. Trying to switch to "Editor" Mode resulsts in the same error as above.
    Is there anyone out there who knows why this happens?
    Thanks
    Warbler

    Given that so many things are funky, I'd suspect that one or both of the following is occurring:
    1) Your Logic Pro application/installation is corrupt. Logic is failing loading control surface modules which should be in the application bundle. Reinstall.
    2) You have an incompatibility between Logic and the necessary system frameworks because Logic is too old/your system/OS is too new. You can't expect to hold back on an old version of an application and press forward with the OS (or vice versa) forever - eventually, something will break, and you'll have a large leap to get things working again.
    It's probably better to stay on the update train unless there is a specific reason to get off, or at least, freeze your computer/OS version at the same tim as you freeze your application.

  • Is this a bug in Logic Pro?

    I use a MAC G5 with Logic Pro 7.2.1 - I play a Korg Triton through a Motu Micro Express Midi interface to access the sounds in Logic as well as my Ivory Grand Piano Plug In. A Mackie Control Universal is my interface.
    Ever since I got geared up last March I noticed that when I changed files (song projects) from client to client during the course of the day that my Ivory track would show up transposed a step down. Not limited to the Ivory track sometimes a Bass track, maybe a Bass from Apples Jam Packs, would be transposed.
    I never have messed with the transposition of any Logic track, I don't even know how to do that, but I have transposed a song or two in the Ivory Grand Piano Plug In Window.
    It was my understanding that once you close the Logic file that it would remember the parameters of that file the next time you opened it.
    Well something very telling happened yesterday. In the morning I worked on a clients song. It was a song that early on I may have transposed the Ivory track to help the singer. I closed out of that file and when I brought up a file of another client's work their Ivory track and their Bass track were transposed down a step. Keep in mind that the day before that client's track played down perfectly in the right key and I'm sure I closed the file with it in the right key. And obviously all the audio tracks remained in the original correct key.
    Here's the kicker. Fearing that I would mess up my client's song I quickly closed the file without saving any changes and completely closed Logic. When I rebooted Logic Pro and reopened their file the Ivory Grand piano track and the Logic Bass track were in key again!
    This has happened quite a few times to me but only now have I realized that completely closing down Logic fixes the problem. ie - If I just ping pong from one file to the next without closing Logic down I have this transposing problem on the Midi instrument tracks.
    I'd like to remedy this because it's time consuming to close down Logic between every client. Any ideas? Thanks

    InnoMan, I experience frequent problems with Logic Pro that require quitting and relaunching the application. I'd say in a typical 3-hour session working with Logic, I end up doing this about 4 or 5 times. The glitches I experience sometimes involve transposition of notes.
    Tell me, when your track gets transposed, does it actually appear transposed, or does it just sound that way? In other words, does the region become magically set to transpose (say, set to +4 or something)? Or, when you go into the region, have the notes been moved?
    If neither of these things is happening, but the track just sounds wrong, then that's a problem I've been having. I have a bass line that repeats throughout a track, and it's all in key (A). Recently, I moved that baseline further along in the track. I changed nothing. The first time I listened to it, it all sounded fine. Every subsequent listening, however, sounded like the notes had been transposed to a completely different key. The region had not been transposed, and the notes in the region are still in A. However, it sounds completely off.
    I tried completely recreating the region, instead of using a copy from earlier in the track. That worked on the first listen, however again, subsequent listenings and the notes are off.
    I'm guessing that upgrading to Logic 7.2.1 might make a difference (I'm using 7.1.1). However, Apple wants me to give them $50 for this experiment, and given Logic's reliability so far (pretty bad), I'm loathe to give Apple more money for this thing.
    Anyhow, let me know your experience. Thanks.

  • I have found a bug in Logic Pro 10.0.3.

    In the Environment Window, go to "Clicks & Ports" & create a new object.
    Go to Fader/Specials/Cable Switcher.
    In the parameter window- Set the Style to "As Text", then change the Range to anything other then 0-127.
    Instant crash every time.
    Also, if you can double click on the cable switcher to edit it, it is full of random symbols and text.
    Any help?
    Thanks,
    Rychard

    You can do that from within the app, under menu Logic Pro X;
    Regards

  • Yosemite 10.10.1 with Logic pro X 10.0.7

    Hello guys. i just wanted to start a small conversation according to the performance of logic pro x on the latest macbook pro's (mid-2014)
    i am on a 13macbook pro running yosemite 10.10.1 and logic pro x 10.0.7...
    Everything works fine and smoothly but the there is just one thing that freaks me out. the level meters gets very laggy sometimes. for no reason.(mostly when i add new audio files but many times for no reason) . all i have to do is to make any activity in the logic's environment to "wake them up" (like opening the mixer or changing the selected channel)and then it may appear again.
    i have tried everything from clean installing to various turnarounds i found on the web . but nothing.
    i think that it might be a bug or method that logic use to spend less graphics. i don't know. i wondered if anyone else has that issue. its has nothing to do with cpu,heavy projects,etc. i have tested it in all the cases.
    so what do you think? have experienced this issue before?

    Logic Pro X + Yosemite  (and even more so + Retina) is a recipe for less performance...... at this current time...
    The graphical 'lagging' you notice is an example of this reduction in performance and has been well reported here and elsewhere.
    It's not the only affect in this drop in performance however as overall Logic performs less well with Yosemite especially with Retina Macs...
    A quick test using the Logic Benchmark test shows that particular combination of OS X and Logic Pro X indicates a reduction of at least 15% in general performance at this time... and in many cases it rises to about 30% ... with projects that ran without issue under 10.9.4 having sporadic 'Overload' issues under 10.10.1
    Currently I don't recommend installing Yosemite on any system where the use of Logic is important..... but instead, to stick with 10.9.4/5 for the time being until such issues are resolved.
    Cheers..
    Nigel

  • Logic Pro 9.6.1 - the screen turns black?

    Hi everyone
    The screen turns black where the curser has been, when I record or playback in Logic pro 9.6.1.
    My system on my Mac book pro 13' is OS X 10.9.6 - and it accour in all my session. Does anyone have a clue?
    Best Nanna

    For Logic 9 to work in Mavericks (OS 10.9.x) Your Logic app needs to be updated to the latest which is 9.1.8 (I think you have a typo in your original post and your current version is 9.1.6).
    You can do this update through Software Update, or the App Store under Purchases or Updates and is free.
    Your Logic will the not have this graphical Bug.

Maybe you are looking for