I'm having sever latency issues on Logic 9 through the built-in input (despite having no plugins active and 32 bit buffer size selected)

I'm literally running a guitar straight into my computer (no plugins, no interface, just the "built-in input" on my macbook) and there's a LOT of latency. I'm very experienced with Logic and pro-audio (I have logic on my other computer and it works fine) but for some reason there's a ton of delay on my signal. NO idea where to start with this one. I've examined every option within Logic and nothing seems to be helping. I've changed every parameter, including buffer size, disabling and reenabling core audio, and low-latency mode, but nothing has worked.
Any advice would be appreciated, thanks.
Also, I'm using a late 2011 15" Macbook (Quad core, 4 GB ram)

Never heard of this before... what are you using for output in Logic's Audio Prefs?
Are you on 10.7.5 as you signature says?  There is a supplemental update for early builds of 10.7.5 that were released.
Take a look at the Audio portion the "Audio-MIDI Setup" in Utilities.
Bit-depth, sample frequency?  Try it at 16-bit 44.1kHz.  Is Logic set to the same?
What kind of cable are you using to get the guitar into Logic, the Mac audio input jack is multifunction, could you be partially enabling the digital I/O.
just tossing some ideas..

Similar Messages

  • Can't record into Logic through the built-in mike

    Hi guys, just faced a strange thing in Logic 8, want to record my voice through my MacbookPro's internal mike, so in Audio preferences I've put an in-built input, in System preferences put input and output to in-built speakers and mike, but I can't move the track level meter in Logic with my voice at all, and there's no waveform, no sound is going inside, i got just an empty audio region, while in the System's preferences window the level meter moves when I'm saying sth...What can it be?Anyone faced the same?
    Thank you

    you need to select the build in microphone as the input in Logic Audio preferences as well.
    it's the 1st on the drop down menu in Input Device Logic's Audio prefs.
    And mute the output of the build in speakers or wear headphones
    A
    Message was edited by: immo

  • Digi002R latency issue with Logic

    I am having latency issues with my Digi002R and Logic Express. I read up here somewhere on the forum that if you initiate the Digi Core Audio manager first, set the buffer size to say 128, and then launch Logic it should sort out the latency issue. But I am still having problems. When I open Logic and set the buffer to 128, there seems to be the same latency as there is at 512. I have the lastest audio drivers. Is there something else I am not doing that can correct the latency issue. I hope the answer isn't get another audio interface. I see that there are other users on this forum that have had no issues with there Digi002R. I know that it isnt very compatible with CoreAudio, but there must be some way to resolve this issue.

    Hi,
    I have the same unit as you, and did extensive latency tests.
    I know that it isnt very compatible with CoreAudio, but there must be some way to resolve this issue.
    This is false. Digidesign makes both the software and the hardware. It is completely compatible. You might have to get a different version CS update from Digidesign, but since you are not giving me the Core Audio software version, I can't tell you if you do need an update, or not. So far Digidesign has gone to version 7.3.1cs4, which is a recommended update for ALL users. Is this what you are running?
    Here's the link to an excel spreadsheet and a PDF version as well:
    http://nicksevilla.com/audioworld/LogicTests.html
    Check my spreadsheeet to see what I got as far as latency, and see if you can also do the latency test. I really want to see what numbers you are actually getting on your system, so I can update my spreadsheet as well.
    Cheers

  • I am running on OSX 10.10.1 and have a 2009 imac intel and I am having severe latency issues.  I am not familiar with macs as this is my home computer used by other family members.  Any help on how to troubleshoot why such latency issues?

    I am running on OSX 10.10.1 and have a 2009 imac intel and I am having severe latency issues.  I am not familiar with macs as this is my home computer used by other family members.  Any help on how to troubleshoot why such latency issues?

    When you see a beachball cursor or the slowness is especially bad, note the exact time: hour, minute, second.  
    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad and start typing the name.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen.
    Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
    Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
    Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    Some private information, such as your name, may appear in the log. Anonymize before posting.

  • I have published my Ni logic through the internet ..

    I have published my Ni logic through the internet ..AS far I know that any device whithin the same connection area can access my logic But that when using any windows system(Xp or either winows7) ....How about trying to access the logic from my mobile??? ..for example i have an androide system mobile !!! I noticed that I can access the page but without having the control panel of the labview !!
    What shall I do ..Does the androide system needs such as an Engine to be able to activate that front panel ..Or What !
    waiting yr quik response..
    thanx

    Hi Eman sa3d;
    I am not quite sure what you are asking. When you say “publish my NI logic,” what do you mean by that? Are you creating a web service and trying to control it via your phone’s web browser? We have the Data Dashboard app for Android that might be what you want.
    Also, here are some links that might prove useful:
    1) Building Android Applications for Simple Data Monitoring.
    2) Data Dashboard for LabVIEW (iPhone, iPad, and Android App).
    Bill E. | Applications Engineer | National Instruments

  • I want to hook up a mac mini and us my tv as a monitor. how can I use airplay from my phone on the mac mini like i can with an apple tv (without having to buy an apple tv!). the airplay capabilities i want to use are mirroring and streaming from my iphone

    i want to hook up a mac mini and us my tv as a monitor. how can I use airplay from my phone on the mac mini like i can with an apple tv (without having to buy an apple tv!). the airplay capabilities i want to use are mirroring and streaming from my iphone!

    Download AirPlayer for Mac - Transforms your Mac into an AirPlay-compatible display. MacUpdate.com

  • I teach Continuing education classes to Real Estate agents and I need to issue them certificates at the class, whihc need to be signed by me and it needs to contain their info on the certificate. The certificate is currently saved in a word format.What i'

    I teach Continuing education classes to Real Estate agents and I need to issue them certificates at the class, whihc need to be signed by me and it needs to contain their info on the certificate. The certificate is currently saved in a word format.What i'm trying to accomplish is to do a "mail merge " ( as some classes i have as many as 150 attendees) for the document, digitally sign each one with my signature on the certificate and then e-mail it out to the respective attendees. can this be done? if so How?

    This is the step that I took after inputting my signature.
    On the right, after saving my document, I click "Get Others to Sign."  I was confused because it says that it's powered by EchoSign.  Like I stated before, my clients are able to sign this document when I send it to them, but it is returned to me with their signature (not in the signature field, but at the end of the document), and my signature is missing.  I tested this on myself - my signature is missing when they receive it. 

  • HT203167 Cloud has appeared on my laptop although I am not aware of having downloaded it; as a result only the items I have purchased appear in my library and I cannot access the hundreds of songs I have imported from my own CDs. How can I find them?

    cloud has appeared on my laptop although  Iam not aware of having downloaded it: as a result only the items I have purchased appear in my library and i cannot access all the songs I have imported from my own CDs. How can I find them?

    If the music is purchased through iTunes:
    iTunes Store: Transferring purchases from your iOS device or iPod to a computer
    If the music is not purchased through iTunes:
    Senuti — Recover music from your iPod, iPhone or iPad to your Mac

  • Latency Issue with Logic 8 and Reason

    Hello evryone,
    I am using Logic 8 with Reason 3.0 and have a Digi 002 as my audio interface. I have set up an aux track in Logic with inputs being RW:L/R and outputs 1&2. When I open Reason after I have opened Logic and go to play an instrument in reason there is massive latency. I've tried messing with the plu-in delay compensation in Logic's prefs. and it didn't have any effect. When I use this set-up with Protools it works beautifully and I don't have any issues like this. Does anyone have any answers or suggestions. Thanks, E.M

    Hi and thanks for the response. I forgot to mention in my previous post that I have indeed changed the buffer size time and time again and it has not helped. What is going on forum? This seems to be a common problem I am having with Logic. Why is it so easy to have a set up like this in PT but not in Logic. Ever since I bought this program I have had nothing but stupid little problems like this. Apple, what's going on with the design of this program. How can you have so many cool features and yet not have the most basic things work properly? I am at my wits end as I am wasting time with this product and am about to throw it out the window, trash it to other musicians/composers and go back to PT. Really, where is the Apple support team on this?

  • Having a strange issue with Logic, don't know what to do.

    Aright, so I'm having a really weird problem with Logic. It all started about 20 minutes ago. I'm working with 12 midi tracks; all logic instruments. Every first Snare midi note plays extra soft and then every midi note after that plays at its correct velocity. Don't know why. I tried deleting the note and pasting a new and that didn't work so I saved and quit. I then took a look in my console and this is what came up:
    11/7/11 12:21:53 AM
    bootlog[43]
    BOOT_TIME: 1320650503 0
    11/7/11 12:22:12 AM
    loginwindow[31]
    USER_PROCESS: 31 console
    11/7/11 12:29:13 AM
    loginwindow[31]
    DEAD_PROCESS: 31 console
    11/7/11 12:29:15 AM
    loginwindow[202]
    USER_PROCESS: 202 console
    11/7/11 1:32:51 AM
    loginwindow[202]
    DEAD_PROCESS: 202 console
    11/7/11 1:32:52 AM
    shutdown[2714]
    SHUTDOWN_TIME: 1320654772 505951
    11/7/11 1:33:14 AM
    bootlog[46]
    BOOT_TIME: 1320654783 0
    11/7/11 1:33:17 AM
    loginwindow[35]
    USER_PROCESS: 35 console
    11/7/11 8:18:59 AM
    loginwindow[35]
    DEAD_PROCESS: 35 console
    11/7/11 8:19:06 AM
    loginwindow[349]
    USER_PROCESS: 349 console
    11/7/11 8:28:02 AM
    reboot[1018]
    BOOT_TIME: 1320679682 95944
    11/7/11 8:28:45 AM
    bootlog[51]
    BOOT_TIME: 1320679715 0
    11/7/11 9:15:22 AM
    loginwindow[40]
    USER_PROCESS: 40 console
    11/7/11 9:56:40 AM
    loginwindow[40]
    DEAD_PROCESS: 40 console
    11/7/11 9:56:48 AM
    loginwindow[242]
    USER_PROCESS: 242 console
    11/7/11 9:59:01 AM
    reboot[835]
    BOOT_TIME: 1320685141 69936
    11/7/11 9:59:29 AM
    bootlog[48]
    BOOT_TIME: 1320685155 0
    11/7/11 10:08:33 AM
    loginwindow[37]
    USER_PROCESS: 37 console
    11/7/11 1:20:53 PM
    loginwindow[37]
    DEAD_PROCESS: 37 console
    11/7/11 1:20:57 PM
    shutdown[7541]
    SHUTDOWN_TIME: 1320697257 332087
    11/7/11 1:21:22 PM
    bootlog[50]
    BOOT_TIME: 1320697269 0
    11/7/11 1:21:50 PM
    loginwindow[39]
    USER_PROCESS: 39 console
    11/7/11 2:30:13 PM
    loginwindow[39]
    DEAD_PROCESS: 39 console
    11/7/11 2:30:31 PM
    shutdown[1377]
    SHUTDOWN_TIME: 1320701431 300114
    11/7/11 2:31:00 PM
    bootlog[48]
    BOOT_TIME: 1320701445 0
    11/7/11 2:58:14 PM
    loginwindow[37]
    USER_PROCESS: 37 console
    11/7/11 3:02:19 PM
    loginwindow[37]
    DEAD_PROCESS: 37 console
    11/7/11 3:02:20 PM
    shutdown[206]
    SHUTDOWN_TIME: 1320703340 498493
    11/7/11 3:02:42 PM
    bootlog[48]
    BOOT_TIME: 1320703352 0
    11/7/11 4:33:21 PM
    loginwindow[37]
    USER_PROCESS: 37 console
    11/7/11 5:57:24 PM
    loginwindow[37]
    DEAD_PROCESS: 37 console
    11/7/11 5:57:24 PM
    shutdown[404]
    SHUTDOWN_TIME: 1320713844 888171
    11/7/11 5:57:58 PM
    bootlog[48]
    BOOT_TIME: 1320713868 0
    11/7/11 5:58:21 PM
    loginwindow[37]
    USER_PROCESS: 37 console
    11/7/11 6:01:48 PM
    loginwindow[37]
    DEAD_PROCESS: 37 console
    11/7/11 6:01:48 PM
    shutdown[169]
    SHUTDOWN_TIME: 1320714108 381468
    11/7/11 11:48:22 PM
    bootlog[48]
    BOOT_TIME: 1320734891 0
    11/7/11 11:48:45 PM
    loginwindow[37]
    USER_PROCESS: 37 console
    11/8/11 4:19:03 AM
    loginwindow[37]
    DEAD_PROCESS: 37 console
    11/8/11 4:19:03 AM
    shutdown[641]
    SHUTDOWN_TIME: 1320751143 318155
    11/8/11 8:36:13 AM
    bootlog[45]
    BOOT_TIME: 1320766559 0
    11/8/11 8:36:30 AM
    loginwindow[34]
    USER_PROCESS: 34 console
    11/8/11 8:10:50 PM
    loginwindow[34]
    DEAD_PROCESS: 34 console
    11/8/11 8:10:50 PM
    shutdown[183]
    SHUTDOWN_TIME: 1320808250 610564
    11/8/11 8:12:08 PM
    bootlog[48]
    BOOT_TIME: 1320808315 0
    11/8/11 8:12:22 PM
    loginwindow[37]
    USER_PROCESS: 37 console
    11/8/11 9:44:19 PM
    loginwindow[37]
    DEAD_PROCESS: 37 console
    11/8/11 9:44:20 PM
    shutdown[385]
    SHUTDOWN_TIME: 1320813860 87755
    11/9/11 10:30:35 AM
    bootlog[48]
    BOOT_TIME: 1320859824 0
    11/9/11 10:31:05 AM
    loginwindow[37]
    USER_PROCESS: 37 console
    11/9/11 1:01:13 PM
    loginwindow[37]
    DEAD_PROCESS: 37 console
    11/9/11 1:01:13 PM
    shutdown[292]
    SHUTDOWN_TIME: 1320868873 995966
    11/9/11 1:02:02 PM
    bootlog[48]
    BOOT_TIME: 1320868909 0
    11/9/11 1:02:15 PM
    loginwindow[37]
    USER_PROCESS: 37 console
    11/9/11 3:13:01 PM
    login[5975]
    USER_PROCESS: 5975 ttys000
    11/9/11 3:13:01 PM
    login[5975]
    DEAD_PROCESS: 5975 ttys000
    11/10/11 5:32:55 AM
    loginwindow[37]
    DEAD_PROCESS: 37 console
    11/10/11 5:32:55 AM
    shutdown[6997]
    SHUTDOWN_TIME: 1320928375 628779
    11/10/11 8:41:31 PM
    bootlog[45]
    BOOT_TIME: 1320982876 0
    11/10/11 8:42:42 PM
    loginwindow[34]
    USER_PROCESS: 34 console
    11/10/11 9:29:47 PM
    loginwindow[34]
    DEAD_PROCESS: 34 console
    11/10/11 9:29:48 PM
    loginwindow[180]
    USER_PROCESS: 180 console
    11/10/11 9:30:20 PM
    reboot[283]
    BOOT_TIME: 1320985820 923753
    11/10/11 9:31:10 PM
    bootlog[45]
    BOOT_TIME: 1320985858 0
    11/10/11 9:31:43 PM
    shutdown[98]
    SHUTDOWN_TIME: 1320985903 450229
    11/11/11 12:05:40 PM
    bootlog[45]
    BOOT_TIME: 1321038331 0
    11/11/11 12:06:10 PM
    loginwindow[34]
    USER_PROCESS: 34 console
    11/12/11 5:08:26 PM
    kernel
    11/12/11 5:08:26 PM
    kernel
    11/12/11 5:08:26 PM
    kernel
    11/12/11 5:08:26 PM
    kernel
    11/12/11 5:08:26 PM
    kernel
    11/12/11 5:08:26 PM
    kernel
    11/12/11 5:08:26 PM
    kernel
    11/12/11 5:08:26 PM
    kernel
    11/12/11 5:08:26 PM
    kernel
    11/12/11 5:08:26 PM
    kernel
    11/12/11 5:08:26 PM
    kernel
    11/12/11 5:08:26 PM
    kernel
    11/12/11 5:08:26 PM
    kernel
    11/12/11 5:08:26 PM
    kernel
    11/12/11 6:01:11 PM
    loginwindow[34]
    DEAD_PROCESS: 34 console
    11/12/11 6:01:11 PM
    shutdown[459]
    SHUTDOWN_TIME: 1321146071 420746
    11/12/11 9:39:44 PM
    bootlog[45]
    BOOT_TIME: 1321159171 0
    11/12/11 9:40:04 PM
    loginwindow[34]
    USER_PROCESS: 34 console
    11/12/11 10:59:25 PM
    loginwindow[34]
    DEAD_PROCESS: 34 console
    11/12/11 10:59:25 PM
    shutdown[190]
    SHUTDOWN_TIME: 1321163965 560483
    11/13/11 12:15:33 AM
    bootlog[45]
    BOOT_TIME: 1321168520 0
    11/13/11 12:15:55 AM
    loginwindow[34]
    USER_PROCESS: 34 console
    11/13/11 2:02:40 AM
    loginwindow[34]
    DEAD_PROCESS: 34 console
    11/13/11 2:02:40 AM
    shutdown[324]
    SHUTDOWN_TIME: 1321174960 535970
    11/13/11 10:54:04 AM
    bootlog[45]
    BOOT_TIME: 1321206832 0
    11/13/11 10:54:19 AM
    loginwindow[34]
    USER_PROCESS: 34 console
    11/13/11 11:02:13 AM
    loginwindow[34]
    DEAD_PROCESS: 34 console
    11/13/11 11:02:13 AM
    shutdown[154]
    SHUTDOWN_TIME: 1321207333 741020
    11/13/11 4:11:30 PM
    bootlog[45]
    BOOT_TIME: 1321225878 0
    11/13/11 4:12:00 PM
    loginwindow[34]
    USER_PROCESS: 34 console
    11/13/11 4:14:40 PM
    loginwindow[34]
    DEAD_PROCESS: 34 console
    11/13/11 4:14:41 PM
    shutdown[152]
    SHUTDOWN_TIME: 1321226081 279428
    11/13/11 4:15:01 PM
    bootlog[45]
    BOOT_TIME: 1321226090 0
    11/13/11 4:15:18 PM
    loginwindow[34]
    USER_PROCESS: 34 console
    11/13/11 4:54:48 PM
    loginwindow[34]
    DEAD_PROCESS: 34 console
    11/13/11 4:54:48 PM
    shutdown[178]
    SHUTDOWN_TIME: 1321228488 443594
    11/13/11 10:11:05 PM
    bootlog[45]
    BOOT_TIME: 1321247453 0
    11/13/11 10:11:39 PM
    loginwindow[34]
    USER_PROCESS: 34 console
    11/14/11 2:34:46 AM
    loginwindow[34]
    DEAD_PROCESS: 34 console
    11/14/11 2:34:47 AM
    shutdown[283]
    SHUTDOWN_TIME: 1321263287 223296
    11/14/11 11:02:03 AM
    bootlog[45]
    BOOT_TIME: 1321293712 0
    11/14/11 11:03:19 AM
    loginwindow[34]
    USER_PROCESS: 34 console
    11/14/11 5:14:25 PM
    loginwindow[34]
    DEAD_PROCESS: 34 console
    11/14/11 5:14:25 PM
    shutdown[345]
    SHUTDOWN_TIME: 1321316065 545760
    11/14/11 5:16:14 PM
    bootlog[45]
    BOOT_TIME: 1321316165 0
    11/14/11 5:16:33 PM
    loginwindow[34]
    USER_PROCESS: 34 console
    11/14/11 5:44:15 PM
    loginwindow[34]
    DEAD_PROCESS: 34 console
    11/14/11 5:44:16 PM
    shutdown[187]
    SHUTDOWN_TIME: 1321317856 83312
    11/15/11 12:48:10 AM
    bootlog[45]
    BOOT_TIME: 1321343279 0
    11/15/11 12:48:38 AM
    loginwindow[34]
    USER_PROCESS: 34 console
    11/15/11 3:26:19 AM
    loginwindow[34]
    DEAD_PROCESS: 34 console
    11/15/11 3:26:19 AM
    shutdown[365]
    SHUTDOWN_TIME: 1321352779 718218
    11/15/11 11:32:51 AM
    bootlog[45]
    BOOT_TIME: 1321381958 0
    11/15/11 11:33:07 AM
    loginwindow[34]
    USER_PROCESS: 34 console
    11/15/11 11:50:40 AM
    loginwindow[34]
    DEAD_PROCESS: 34 console
    11/15/11 11:50:40 AM
    shutdown[173]
    SHUTDOWN_TIME: 1321383040 949601
    11/15/11 3:13:03 PM
    bootlog[48]
    BOOT_TIME: 1321395171 0
    11/15/11 3:13:16 PM
    loginwindow[37]
    USER_PROCESS: 37 console
    11/15/11 3:28:56 PM
    loginwindow[37]
    DEAD_PROCESS: 37 console
    11/15/11 3:28:56 PM
    shutdown[169]
    SHUTDOWN_TIME: 1321396136 717878
    11/15/11 3:31:06 PM
    bootlog[48]
    BOOT_TIME: 1321396254 0
    11/15/11 3:31:21 PM
    loginwindow[37]
    USER_PROCESS: 37 console
    11/16/11 2:38:00 AM
    loginwindow[37]
    DEAD_PROCESS: 37 console
    11/16/11 2:38:00 AM
    shutdown[1961]
    SHUTDOWN_TIME: 1321436280 560702
    11/16/11 11:30:09 AM
    bootlog[47]
    BOOT_TIME: 1321468198 0
    11/16/11 11:30:48 AM
    loginwindow[36]
    USER_PROCESS: 36 console
    11/16/11 4:34:51 PM
    loginwindow[36]
    DEAD_PROCESS: 36 console
    11/16/11 4:34:51 PM
    shutdown[341]
    SHUTDOWN_TIME: 1321486491 583341
    11/16/11 4:36:11 PM
    bootlog[48]
    BOOT_TIME: 1321486559 0
    11/16/11 4:36:34 PM
    loginwindow[37]
    USER_PROCESS: 37 console
    11/16/11 9:59:04 PM
    loginwindow[37]
    DEAD_PROCESS: 37 console
    11/16/11 9:59:05 PM
    shutdown[371]
    SHUTDOWN_TIME: 1321505945 161871
    11/17/11 12:20:08 AM
    bootlog[48]
    BOOT_TIME: 1321514397 0
    11/17/11 12:20:32 AM
    shutdown[106]
    SHUTDOWN_TIME: 1321514432 588785
    11/17/11 12:21:30 AM
    bootlog[48]
    BOOT_TIME: 1321514481 0
    11/17/11 12:21:45 AM
    loginwindow[37]
    USER_PROCESS: 37 console
    11/17/11 12:39:52 AM
    login[174]
    USER_PROCESS: 174 ttys000
    11/17/11 12:40:12 AM
    login[174]
    DEAD_PROCESS: 174 ttys000
    11/17/11 12:40:15 AM
    login[180]
    USER_PROCESS: 180 ttys000
    11/17/11 12:54:34 AM
    login[180]
    DEAD_PROCESS: 180 ttys000
    11/17/11 2:28:30 AM
    loginwindow[37]
    DEAD_PROCESS: 37 console
    11/17/11 2:28:30 AM
    shutdown[331]
    SHUTDOWN_TIME: 1321522110 593580
    11/17/11 4:37:08 PM
    bootlog[48]
    BOOT_TIME: 1321573005 0
    11/17/11 4:38:49 PM
    loginwindow[37]
    USER_PROCESS: 37 console
    11/17/11 7:39:32 PM
    loginwindow[37]
    DEAD_PROCESS: 37 console
    11/17/11 7:39:32 PM
    shutdown[386]
    SHUTDOWN_TIME: 1321583972 773529
    11/18/11 1:41:17 AM
    bootlog[48]
    BOOT_TIME: 1321605668 0
    11/18/11 1:41:40 AM
    loginwindow[37]
    USER_PROCESS: 37 console
    11/18/11 3:48:55 AM
    loginwindow[37]
    DEAD_PROCESS: 37 console
    11/18/11 3:48:55 AM
    shutdown[355]
    SHUTDOWN_TIME: 1321613335 819965
    11/18/11 10:23:51 AM
    bootlog[48]
    BOOT_TIME: 1321637021 0
    11/18/11 10:24:13 AM
    loginwindow[37]
    USER_PROCESS: 37 console
    11/18/11 10:28:27 AM
    kernel
    11/18/11 10:28:27 AM
    kernel
    11/18/11 10:28:27 AM
    kernel
    11/18/11 10:28:27 AM
    kernel
    11/18/11 10:28:27 AM
    kernel
    11/18/11 10:28:27 AM
    kernel
    11/18/11 10:28:27 AM
    kernel
    11/18/11 10:28:27 AM
    kernel
    11/18/11 10:28:27 AM
    kernel
    11/18/11 10:28:27 AM
    kernel
    11/18/11 2:15:52 PM
    loginwindow[37]
    DEAD_PROCESS: 37 console
    11/18/11 2:15:59 PM
    shutdown[770]
    SHUTDOWN_TIME: 1321650959 323280
    11/18/11 2:16:33 PM
    bootlog[48]
    BOOT_TIME: 1321650971 0
    11/18/11 2:16:52 PM
    loginwindow[37]
    USER_PROCESS: 37 console
    11/18/11 6:30:25 PM
    loginwindow[37]
    DEAD_PROCESS: 37 console
    11/18/11 6:30:27 PM
    shutdown[1470]
    SHUTDOWN_TIME: 1321666227 362936
    11/18/11 6:31:47 PM
    bootlog[38]
    BOOT_TIME: 1321666248 0
    11/18/11 6:32:34 PM
    loginwindow[26]
    USER_PROCESS: 26 console
    11/18/11 8:24:46 PM
    loginwindow[26]
    DEAD_PROCESS: 26 console
    11/18/11 8:24:56 PM
    shutdown[205]
    SHUTDOWN_TIME: 1321673096 424661
    11/18/11 8:25:23 PM
    bootlog[40]
    BOOT_TIME: 1321673108 0
    11/18/11 8:26:03 PM
    loginwindow[26]
    USER_PROCESS: 26 console
    11/18/11 8:37:36 PM
    loginwindow[26]
    DEAD_PROCESS: 26 console
    11/18/11 8:37:37 PM
    loginwindow[210]
    USER_PROCESS: 210 console
    11/18/11 8:38:12 PM
    reboot[264]
    BOOT_TIME: 1321673892 663474
    11/18/11 8:38:43 PM
    bootlog[40]
    BOOT_TIME: 1321673906 0
    11/18/11 8:39:06 PM
    loginwindow[27]
    USER_PROCESS: 27 console
    11/18/11 9:45:07 PM
    loginwindow[27]
    DEAD_PROCESS: 27 console
    11/18/11 9:45:08 PM
    shutdown[387]
    SHUTDOWN_TIME: 1321677908 37081
    11/18/11 10:20:09 PM
    bootlog[40]
    BOOT_TIME: 1321680000 0
    11/18/11 10:20:44 PM
    loginwindow[28]
    USER_PROCESS: 28 console
    11/18/11 11:56:22 PM
    loginwindow[28]
    DEAD_PROCESS: 28 console
    11/18/11 11:56:22 PM
    shutdown[328]
    SHUTDOWN_TIME: 1321685782 469361
    11/19/11 5:41:15 AM
    bootlog[40]
    BOOT_TIME: 1321706467 0
    11/19/11 5:42:10 AM
    shutdown[99]
    SHUTDOWN_TIME: 1321706530 778985
    11/19/11 5:49:24 AM
    bootlog[40]
    BOOT_TIME: 1321706956 0
    11/19/11 5:49:52 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/19/11 12:35:11 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/19/11 12:35:11 PM
    shutdown[658]
    SHUTDOWN_TIME: 1321731311 570256
    11/19/11 4:26:55 PM
    bootlog[40]
    BOOT_TIME: 1321745206 0
    11/19/11 4:27:31 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/19/11 4:49:55 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/19/11 4:49:55 PM
    shutdown[214]
    SHUTDOWN_TIME: 1321746595 832157
    11/19/11 4:50:36 PM
    bootlog[40]
    BOOT_TIME: 1321746619 0
    11/19/11 4:51:00 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/19/11 6:34:58 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/19/11 6:34:58 PM
    shutdown[266]
    SHUTDOWN_TIME: 1321752898 862103
    11/20/11 12:48:24 AM
    bootlog[40]
    BOOT_TIME: 1321775295 0
    11/20/11 12:48:50 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/20/11 12:50:56 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/20/11 12:50:56 AM
    shutdown[190]
    SHUTDOWN_TIME: 1321775456 727774
    11/20/11 12:51:57 AM
    bootlog[40]
    BOOT_TIME: 1321775508 0
    11/20/11 12:52:15 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/20/11 2:44:47 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/20/11 2:44:48 AM
    shutdown[287]
    SHUTDOWN_TIME: 1321782288 27378
    11/20/11 9:40:35 AM
    bootlog[40]
    BOOT_TIME: 1321807226 0
    11/20/11 9:45:38 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/20/11 1:10:45 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/20/11 1:10:45 PM
    shutdown[376]
    SHUTDOWN_TIME: 1321819845 699702
    11/20/11 2:47:41 PM
    bootlog[40]
    BOOT_TIME: 1321825653 0
    11/20/11 2:48:05 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/21/11 3:18:25 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/21/11 3:18:25 AM
    shutdown[738]
    SHUTDOWN_TIME: 1321870705 862572
    11/21/11 1:41:49 PM
    bootlog[40]
    BOOT_TIME: 1321908100 0
    11/21/11 1:42:31 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/21/11 1:45:37 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/21/11 1:45:37 PM
    shutdown[199]
    SHUTDOWN_TIME: 1321908337 723401
    11/21/11 1:46:42 PM
    bootlog[40]
    BOOT_TIME: 1321908393 0
    11/21/11 1:47:01 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/21/11 2:47:30 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/21/11 2:47:31 PM
    shutdown[221]
    SHUTDOWN_TIME: 1321912051 100508
    11/21/11 9:57:25 PM
    bootlog[40]
    BOOT_TIME: 1321937836 0
    11/21/11 10:00:25 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/21/11 10:05:34 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/21/11 10:05:34 PM
    shutdown[197]
    SHUTDOWN_TIME: 1321938334 457516
    11/21/11 10:05:55 PM
    bootlog[40]
    BOOT_TIME: 1321938345 0
    11/21/11 10:06:14 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/21/11 10:36:32 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/21/11 10:36:32 PM
    shutdown[249]
    SHUTDOWN_TIME: 1321940192 772946
    11/22/11 5:47:52 PM
    bootlog[40]
    BOOT_TIME: 1322009263 0
    11/22/11 5:48:18 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/22/11 5:57:09 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/22/11 5:57:10 PM
    shutdown[180]
    SHUTDOWN_TIME: 1322009830 100353
    11/22/11 5:57:52 PM
    bootlog[40]
    BOOT_TIME: 1322009862 0
    11/22/11 6:03:27 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/22/11 8:17:23 PM
    login[262]
    USER_PROCESS: 262 ttys000
    11/22/11 8:25:20 PM
    login[262]
    DEAD_PROCESS: 262 ttys000
    11/22/11 10:02:20 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/22/11 10:02:20 PM
    shutdown[501]
    SHUTDOWN_TIME: 1322024540 841538
    11/23/11 11:09:36 AM
    bootlog[40]
    BOOT_TIME: 1322071768 0
    11/23/11 11:12:10 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/23/11 11:16:40 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/23/11 11:16:40 AM
    shutdown[201]
    SHUTDOWN_TIME: 1322072200 484093
    11/23/11 11:17:01 AM
    bootlog[40]
    BOOT_TIME: 1322072211 0
    11/23/11 11:17:22 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/23/11 11:57:01 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/23/11 11:57:01 AM
    shutdown[219]
    SHUTDOWN_TIME: 1322074621 710897
    11/23/11 6:10:29 PM
    bootlog[40]
    BOOT_TIME: 1322097020 0
    11/23/11 6:11:30 PM
    shutdown[107]
    SHUTDOWN_TIME: 1322097090 157202
    11/23/11 6:11:48 PM
    bootlog[40]
    BOOT_TIME: 1322097100 0
    11/23/11 6:12:07 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/23/11 6:43:45 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/23/11 6:43:45 PM
    shutdown[212]
    SHUTDOWN_TIME: 1322099025 671753
    11/24/11 3:06:36 AM
    bootlog[40]
    BOOT_TIME: 1322129187 0
    11/24/11 3:07:23 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/24/11 3:25:50 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/24/11 3:26:16 AM
    shutdown[263]
    SHUTDOWN_TIME: 1322130376 181854
    11/24/11 3:41:59 PM
    bootlog[40]
    BOOT_TIME: 1322174510 0
    11/24/11 3:42:29 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/24/11 5:41:41 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/24/11 5:41:44 PM
    shutdown[182]
    SHUTDOWN_TIME: 1322181704 304082
    11/24/11 5:42:27 PM
    bootlog[40]
    BOOT_TIME: 1322181730 0
    11/24/11 5:42:44 PM
    shutdown[107]
    SHUTDOWN_TIME: 1322181764 200841
    11/25/11 1:06:30 AM
    bootlog[40]
    BOOT_TIME: 1322208382 0
    11/25/11 1:07:20 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/25/11 2:02:05 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/25/11 2:02:05 AM
    shutdown[243]
    SHUTDOWN_TIME: 1322211725 412106
    11/25/11 12:19:23 PM
    bootlog[40]
    BOOT_TIME: 1322248755 0
    11/25/11 12:19:50 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/25/11 12:21:18 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/25/11 12:21:19 PM
    shutdown[185]
    SHUTDOWN_TIME: 1322248879 181508
    11/25/11 12:21:40 PM
    bootlog[40]
    BOOT_TIME: 1322248891 0
    11/25/11 12:21:58 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/25/11 2:31:25 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/25/11 2:31:25 PM
    shutdown[388]
    SHUTDOWN_TIME: 1322256685 817758
    11/25/11 3:55:28 PM
    bootlog[40]
    BOOT_TIME: 1322261718 0
    11/25/11 3:55:55 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/25/11 3:57:10 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/25/11 3:57:11 PM
    shutdown[159]
    SHUTDOWN_TIME: 1322261831 182162
    11/25/11 5:12:01 PM
    bootlog[40]
    BOOT_TIME: 1322266311 0
    11/25/11 5:12:20 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/25/11 5:22:48 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/25/11 5:22:48 PM
    shutdown[196]
    SHUTDOWN_TIME: 1322266968 596246
    11/25/11 5:50:55 PM
    bootlog[40]
    BOOT_TIME: 1322268646 0
    11/25/11 6:04:42 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/26/11 12:28:03 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/26/11 12:28:03 AM
    shutdown[527]
    SHUTDOWN_TIME: 1322292483 989128
    11/26/11 9:56:40 AM
    bootlog[40]
    BOOT_TIME: 1322326592 0
    11/26/11 10:16:17 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/26/11 10:18:14 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/26/11 10:18:14 AM
    shutdown[203]
    SHUTDOWN_TIME: 1322327894 987763
    11/26/11 10:18:35 AM
    bootlog[40]
    BOOT_TIME: 1322327907 0
    11/26/11 10:18:54 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/27/11 12:51:27 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/27/11 12:51:28 AM
    shutdown[592]
    SHUTDOWN_TIME: 1322380288 289445
    11/27/11 8:33:25 PM
    bootlog[40]
    BOOT_TIME: 1322451196 0
    11/27/11 8:34:08 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/27/11 8:35:39 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/27/11 8:35:39 PM
    shutdown[158]
    SHUTDOWN_TIME: 1322451339 576729
    11/27/11 8:35:59 PM
    bootlog[40]
    BOOT_TIME: 1322451350 0
    11/27/11 8:36:16 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/28/11 2:20:14 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/28/11 2:20:17 AM
    shutdown[330]
    SHUTDOWN_TIME: 1322472017 680079
    11/28/11 11:32:31 AM
    bootlog[40]
    BOOT_TIME: 1322505141 0
    11/28/11 11:33:01 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/28/11 6:34:50 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/28/11 6:34:50 PM
    shutdown[473]
    SHUTDOWN_TIME: 1322530490 514177
    11/29/11 12:49:32 AM
    bootlog[40]
    BOOT_TIME: 1322552963 0
    11/29/11 12:51:15 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/29/11 4:40:24 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/29/11 4:40:24 AM
    shutdown[609]
    SHUTDOWN_TIME: 1322566824 951691
    11/29/11 9:00:52 AM
    bootlog[40]
    BOOT_TIME: 1322582442 0
    11/29/11 9:01:10 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/29/11 9:44:53 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/29/11 9:44:53 AM
    shutdown[176]
    SHUTDOWN_TIME: 1322585093 264673
    11/29/11 10:54:01 AM
    bootlog[40]
    BOOT_TIME: 1322589232 0
    11/29/11 10:54:17 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/29/11 11:12:07 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/29/11 11:12:07 AM
    shutdown[162]
    SHUTDOWN_TIME: 1322590327 902267
    11/29/11 8:32:30 PM
    bootlog[40]
    BOOT_TIME: 1322623940 0
    11/29/11 8:32:50 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/29/11 9:35:59 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/29/11 9:35:59 PM
    shutdown[188]
    SHUTDOWN_TIME: 1322627759 382014
    11/29/11 9:36:59 PM
    bootlog[40]
    BOOT_TIME: 1322627810 0
    11/29/11 9:39:05 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/29/11 9:39:35 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/29/11 9:39:35 PM
    shutdown[158]
    SHUTDOWN_TIME: 1322627975 625235
    11/29/11 9:42:45 PM
    bootlog[40]
    BOOT_TIME: 1322628157 0
    11/29/11 9:43:17 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/30/11 2:15:04 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/30/11 2:15:04 AM
    shutdown[440]
    SHUTDOWN_TIME: 1322644504 701322
    11/30/11 3:26:41 PM
    bootlog[40]
    BOOT_TIME: 1322691992 0
    11/30/11 3:27:50 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/30/11 3:29:39 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/30/11 3:29:40 PM
    shutdown[188]
    SHUTDOWN_TIME: 1322692180 264860
    11/30/11 3:30:15 PM
    bootlog[40]
    BOOT_TIME: 1322692207 0
    11/30/11 3:30:41 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    11/30/11 3:52:12 PM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    11/30/11 3:52:12 PM
    shutdown[194]
    SHUTDOWN_TIME: 1322693532 474756
    11/30/11 9:18:14 PM
    bootlog[40]
    BOOT_TIME: 1322713080 0
    11/30/11 9:18:46 PM
    loginwindow[29]
    USER_PROCESS: 29 console
    12/1/11 5:57:47 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    12/1/11 5:57:47 AM
    shutdown[869]
    SHUTDOWN_TIME: 1322744267 855950
    12/1/11 9:52:39 AM
    bootlog[40]
    BOOT_TIME: 1322758350 0
    12/1/11 9:53:01 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    12/1/11 10:24:02 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    12/1/11 10:24:03 AM
    shutdown[234]
    SHUTDOWN_TIME: 1322760243 279103
    12/1/11 10:24:22 AM
    bootlog[40]
    BOOT_TIME: 1322760253 0
    12/1/11 10:24:41 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    12/1/11 10:41:30 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    12/1/11 10:41:31 AM
    shutdown[240]
    SHUTDOWN_TIME: 1322761291 172303
    12/1/11 10:48:01 AM
    bootlog[40]
    BOOT_TIME: 1322761671 0
    12/1/11 10:50:46 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    12/1/11 11:44:03 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    12/1/11 11:44:03 AM
    shutdown[244]
    SHUTDOWN_TIME: 1322765043 549953
    12/2/11 12:51:18 AM
    bootlog[40]
    BOOT_TIME: 1322812270 0
    12/2/11 12:51:49 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    12/2/11 2:06:17 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    12/2/11 2:06:17 AM
    shutdown[245]
    SHUTDOWN_TIME: 1322816777 845146
    12/2/11 10:48:28 AM
    bootlog[40]
    BOOT_TIME: 1322848098 0
    12/2/11 10:48:50 AM
    loginwindow[29]
    USER_PROCESS: 29 console
    12/3/11 1:49:58 AM
    loginwindow[29]
    DEAD_PROCESS: 29 console
    12/3/11 1:49:59 AM
    shut

    Why did you put up with all those issues for a year? 

  • Yet Another Latency Issue Involving Audio through a 1620 into Logic 9

    Hi. Let me apologize in advance for my ignorance, and let me acknowledge that there are lots of tips on latency all over this and other sites.
    I haven't found the answer despite some extensive looking.
    I'm running Logic Studio / Logic 9 on a 32-bit only 2008 iMac.  I am using a Mackie Onyx 1620 [not 1620i] with Firewire InterfaceLogic as my audio interface.
    I am tracking audio into a project with both MIDI tracks and Audio tracks.  I have established an audio loop as an augmented click track.
    I have set latency to a low setting / buffer size in general preferences, and I have engaged "low latency" mode during audio recording.
    I have no problem monitoring through my Mackie Onyx 1620 [not 1620i], with no audible latency or delay problem at all whilst tracking.
    When I then play back the audio tracking, it is about 240 ticks off -- a dramatic latency problem.
    The problem exists even where I have no other tracks beyond my audio loop, and where there are no effects on the audio loop/click track.
    In other DAW setups, I've experienced latency in hearing my backing tracks and having an audible delay from latency in monitoring my input track.  This is effectively the reverse.
    Any ideas?  And again, I am woefully under-educated in the area.  With your kind help, I intend to remedy that . . . .
    Thanks very much.

    Pancenter, thanks for responding and trying to help.
    if so, you have a misunderstanding regarding latency.
    I can promise you that you're right!
    My understanding of latency in a nutshell: it is the small but perceptable delay [from "withholding" of signal] caused as a signal travels from point to point -- both (1) physical point-to-point (for example, from Mac processor to FW jack out on Mac through FW cable to FW jack in on interface, through cable out to monitor speakers or headphones); and
    (2) processing point to point (from recorded audio track through multiple plug-ins on channels strip to bus or master out, through plug-ins on each of those).
    I already know that I likely am wrong about this, or am at least incomplete.
    Based on that understanding, the problem I'm experiencing defies latency as I understand it, and defies logic (no pun intended; I just mean it makes no sense, as I'll explain below).
    What effects do you have on the master bus?
    None.  I had none in the original project I described in my first query, and have none on a simplified experiment project I've conducted since (after reading your response).
    If you are monitoring through the Mackie and NOT using Logic's software monitoring there is no need to set the Preferences/Audio/ I/O Buffer to a low value, set it to 256.  You also don't need to use Low Latency mode if you're monitoring through the Mackie.
    Here, I think I understand, but am not sure. 
    I am definitely monitoring through the Mackie in an absolute sense -- the returning signals from my DAW are coming in to the Mackie and (a) going out the 1620's headphone jack; (b) going out the 1620's master out to a Mackie Big Knob; and (c) going out the Big Knob's headphone jack, or to powered Mackie 824s.
    [No, I'm not a Mackie devotee; I just happened across the gear at great prices, and thought I understood it.]
    I don't think, though, that I'm "monitoring through the Mackie" as you intend it.  For my simple experiment, I established an audio drum track as a click track.  Each of the transients falls right on the metronome click/ beat location, so I know that it's "good."  I then plugged a Precision bass into the Mackie (channel one), with an audio track in Logic with "Input 1" as the input source. There are no plugins on the Precision track's channel strip.
    Because the Mackie FW interface  on the 1620 sends post-gain but pre-fader, I was able to turn down all faders on the Mackie except the master out.  When muting the Precision channel strip in Logic, I hear NO Precision.  *Nothing from the Precision gets to the monitors if the faders are down and Logic is not sending signal.*  If I then "de-mute" the Precision in Logic, I hear signal through the master line in the Mackie 1620. 
    In this setup, I assume I am not "monitoring through the Mackie," but I'm not sure.  I think that I'm "monitoring through Logic," and that's why I've engaged low-latency and set the preferences to minimize latency.
    we need to establish your setup, how you're monitoring, and what effects are on the master bus. (if any)
    In my simple experiment, with Logic set up to minimize latency, and with no plugins on the Logic master, I engaged "record" in Logic (only on the Precision track with no plugins), and I then played simple quarter notes on the Precision in time with the drumbeats in my Logic "clicktrack."  By playing simply like that, I confirmed that I am "in time" as far as my ears can perceive.  I then hit "Stop" in Logic.
    Upon playback, my Precision is perceptably (about 240) ahead of the click track !
    In my understanding of latency, at the worst the Precision should have been late because the Clicktrack would have been traveling through Logic's processing and down the lines to my monitors.
    Again, thanks a ton for trying to help me out here.  I hope that this description makes it easier.

  • Latency issue between Logic & MainStage with guitars

    Any reasons why the latency is different between the 2 apps, even with the same setting?
    I can use Logic with little problems but Mainstage is unusable with my guitar rig because latency. Even with no plug ins it's huge. Keyboards run perfectly though.
    I'm using a 24" silver iMac, 4 Gigs of RAM, 10.5.1, apps on the main drive, recording to an external. The guitar is a Line 6 Variax is going through a POD XT Live (I realize I'll have some latency issues with this but it's not bad at all).
    And this might be the problem right here: I'm a ProTools convert so I'm running an 1st generation MBox (USB 1) for the interface (surprisingly without any problems whatsoever).... I'm VERY curious to know if switching to a firewire interface would help the latency issues (looking at the Apogee Duet).

    Have you tried this button?

  • High latency issue When connected through Wifi

    Hi
    I have configured wlc 2504 with cisco 3600 ap .when i connected my laptop wlan on n range,i tried to ping with my network devices am getting high latency 130ms,150ms
    Can anybody provide solution for this
    by
    Veeramani.G

    Hi Veeramani,
    There are actually a lot of different factors that can go into high latency type problems on your wireless deployment such as co-channel interference, interference from other wireless devices, and overall utilization on the AP/Channel.  With that said, there are a number of questions that need to be answered:
    1. Is this issue isolated to either the 802.11b/g 2.4Ghz, the 802.11a 5Ghz, or both bands?
    2.  While associated to the Access Point, in the Controller Web interface, navigate to Monitor > Access Points > 802.11a/n or 802.11b/g/n(pick the band your client is associated on) > Find the Access Point and scroll to the far right.  Hover over the small blue box and select 'Detail'.  Find the section labeled 'Load Statistics' and let me know what you see as the Channel Utilization percentage as well as the 'Attached Client Count'
    3. Since you have a 3600, I am assuming you have CleanAir enabled on them.  Navigate to Monitor > Cisco CleanAir, and see if you can pinpoint any noticeable interfering devices with high % Duty Cycle

  • How to view the code/logic for the built-in oracle functions

    Hi,
    How can we view the logic behind the oracle supplied built-in functions like LAST_DAY , MONTHS_BETWEEN etc.,
    I tried to view the same using the sys.STANDARD package , the observations are given below
    function LAST_DAY(RIGHT DATE) return DATE;
    pragma BUILTIN('LAST_DAY',38, 12, 12); -- PEMS_DATE, DATE_LAST_DAY
    pragma FIPSFLAG('LAST_DAY', 1450);
    Regards
    Lok

    How can we view the logic behind the oracle supplied built-in functions like LAST_DAY , MONTHS_BETWEEN etc., You cannot. These built-ins, are 'built-in'.... As far as I know they are implemented in Oracle's kernel, as C code.

  • Does anyone have an issue when listening through the earpiece you get a vibration?

    Experiencing a small issue with the iPhone 4s, when making a phone call and listening through the phones earpiece I get a vibration like something is loose through the earpiece, I've had iPhone 3G, iPhone 4 but never experienced this before.

    I think it depends on how you share it.  Sometimes when I email it to myself it retains the edits, but I read that when people sync their phone it sometimes does not.

Maybe you are looking for