Metronome click issue with Logic 8

Hello.
I'm having a strange issue with Logic 8 where the first click after hitting play or record is lower in volume than the rest of the clicks and sometimes isn't there at all - every subsequent click sounds fine. I have checked the metronome preferences and made sure the bar click is the same velocity as the beat click. I've double checked my entire configuration to see if there is a problem somewhere and everything seems to be right. I figured this might be just a bug but I wanted to post this to make sure.
Any ideas on how to fix this?
Here is the configuration I'm working with which has all the latest drivers and updates:
Mac Pro 3.2 GHz 8-core Intel
Mac OS 10.5.2
14 GB RAM
Logic Pro 8
Apogee Ensemble
Trilogy with the Intel wrapper (this might be pertinent)

You need to add more RAM.

Similar Messages

Performance issues with Logic Pro 9

Hi,
I'm experiencing quite big performance issues with Logic Pro 9:
bad midi timing and sync, user interface is kinda slowing and less reactive, ...
Mac Pro 2x2.26 Ghz Quad, 4Gb ram, early 2009, shipped with 10.5.6 now upgraded to 10.5.8
Should I upgrade to 10.6.2?
Thanx

Hi,
I'm using the same machine ...
I never get any performance issues
I bought my mac in March 2009 and I was ben ready to work in less that 3 days without issue...
so more details about your setup are required to answare!
4GB ram???
I suggest to check your ram!!!
Ram must be compatible with Xeon Nehalem Try specification!
if you add 1GB of ram from nor clear manufactor.. i suggest to disconnect the addition 1GB RAM
G

I am having major issues with Logic 8 and want to reinstall.

I am having a lot of issues with Logic 8 and want to do a re-install. What is the procedure and what do I need to uninstall first. I need to be careful, because I don't want to affect my Logic 7.
Any suggestions?

What problems?
The first thing to do is trash the preferences. As far as affecting Logic 7, once you install 8, 7 is "forgotten" about. I'm assuming your L8 is a real version, not a "borrowed from the interweb" one.

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?

Click issue with s:Datagrid on mobile for iPads with retina displays (only left half is clickable)

I'm currently testing a Flex mobile application (that was originally made for iPad 2) on high rest iPad fourth generation and iPad Air devices.
I'm having this strange issue where the s:DataGrid, no matter where I use it in the application, will display correctly, but only the left half is clickable to select rows. The number of columns in the DataGrid is not important, nor is the width of the DataGrid, the problem is always present. As soon as you try to click in the right half, it doesn't work.
The application uses an applicationDPI of 160, and scales properly on the higher resolution devices.
So this feels like a bug to me, as if the DataGrid scales properly, but not it's clickable area?
I have tried a bunch of stuff to see if I could work around this issue, like calling invalidate functions and setting the DataGrid's width dynamically, but no change so far.
At this point I'm open for any suggestions or ideas...
Edit: After further testing it seems the same is true for the height. I noticed when I added more rows in the grid. Only the top half of the DataGrid can be clicked. So it really looks like a dimension issue with the clickable area?
Thanks

I ended up not using the DataGrid, and decided to use the experimental MobileGrid instead, which is not afflicted with this issue.
So this issue no longer concerns me.
BTW the default theme of MobileGrid is dark, but can be lightened up with CSS and by extending the MobileGrid skins, up to a point where I almost can't tell the difference v.s. the DataGrid.
It also performs better then the DataGrid. since it's based on List. With 300 elements, it scrolled noticeably faster.

Oxygen25 midi issue with Logic 9.1.8

Just recently bought a Oxygen25 midi keyboard controller and I'm running it on the latest macbook pro (10.8.2), with logic pro 9.1.8 - 32 bit. Everything functions on the midi keyboard expect the 8 controller Knobs, no matter what I do I can't get the knobs to recorded functions into Logic. I've download the latest directlink mode drivers and installed them correctly, I've gone into controller assignment window using learn mode button and assigned each knob to certain functions, cutoff, speed on ES2 synth. When you play the keyboard and turn the knobs the sounds work fine (no problem) but when I hit recorded the sounds play but will not record into logic. The pitch bend shows and works in the hyper editor and the All velocities but there's nothing coming through on the rest (Volume, Pan, Modulation, Ch. Pressure, Poly Program and Program.
I'm I missing something really simple here or does this keyboard just not work with logic ? I've been on M-audio website and there's no solutions, I've also looked on discussion board but had no luck. Any advice or help would be welcome, please help me get back into making some music.
Found this article on M-audio but not sure what it relates to - (These knobs map to control the track volume for the currently active bank of eight tracks)
Thank-you
Andrew

I'm having the exact same issue with the Multipressor in Logic (but not in Waveburner). What gives?

Mavricks issues with Logic 9.1.8 and multiple dislays

I have graphical glitches every time i move my mouse from one monitor to the other. It seems to be an issue with the new way Mavricks works for adding wireless monitors and I can't turn its smart displays option off to rectify and revert to the way things were in previois versions od the O.S
A good example of this would be when i select my mixer on the right monitor then move to the left to adjust an EQ or filter.
Once i have adjusted the EQ/ filter it takes up to 5 seconds to respond graphically and audibly. somtimes it even locks play and pressing space bar has no effect at all. I never had this issue with Mountain lion and my machine is more than cpable of runningthe software as the CPU is not even over 1/5 cpacity. I also have 8GB ram so thats not the issue either.
Can anyone help am i doing somthing extrelemy stupid or just have bad luck? I'm really trying to avoid the "just get Logic X" option as many of my plugins wont work in 64 bit!
responses welcome
Mac pro 2x 3ghz quad core 8 gb ram
max

I'm having the exact same issue with the Multipressor in Logic (but not in Waveburner). What gives?

Having some weird issues with logic 8

i am almost Positive! that i pushed some buttons or selected something to mess it up, i would be indebted to anyone who can help me with like three issues i'm having
I run my M-audio mobile pre into logic and am having these issues:
#1. track 1 and two seem to be tied together even though i select mono tracks... so i need to leave track two blank otherwise it interferes with whatever is on track one. and on the bar where i drag the loop i was using it has two O's that make like a vinn diagram symbol.
#2. the volume controll (the bottom left fader one) can increase the Db but not decrease...
#3 through my headphones the signal only comes out the right side. i am inputting my guitar/vox into the right input on the mobile pre, but i thought if the tracks were mono, it wouldn't matter.
please please please help, i need to get recording soon!
thanks.

i figured out the volume issue, with the weird stereo track, i needed to adjust it on both tracks (even though one was empty haha duh)

ProTool Digi 003 new driver issues with Logic

I just purchased Logic Pro and have OS 10.9.5 running on a new 2.2 Ghz Inter Core i7 16 GB memory laptop.
I was told that the new driver for the Digi 003 would work with Logic and yet I have all kinds of crazy issues whenever I connect Logic to it.
The issues shift all around including midi issues, but the main problem is that no audio can be heard through the Digi 003.
There is a very faint (VERY FAINT) ghost of sound coming through but I can barely hear it.
I tried setting the output to the computer headphone jack but then none of the effects I have are audible.
When I try and record sometimes it works and sometimes it doesn't. All inputs are correct and I have tried changing them.
This has been hours on the phone with Apple who keep telling me that it's all AVID's fault. AVID has no tech support and doesn't care which is why I'm switching from Pro Tools to Logic after 15 years.
Buying a new interface would defeat the money savings that I thought switching to Logic would bring as well as sending a perfectly good piece of equipment to the landfill.
Any help appreciated but please keep the comments to civil and nice. Thank you.

I just purchased Logic Pro and have OS 10.9.5 running on a new 2.2 Ghz Inter Core i7 16 GB memory laptop.
I was told that the new driver for the Digi 003 would work with Logic and yet I have all kinds of crazy issues whenever I connect Logic to it.
The issues shift all around including midi issues, but the main problem is that no audio can be heard through the Digi 003.
There is a very faint (VERY FAINT) ghost of sound coming through but I can barely hear it.
I tried setting the output to the computer headphone jack but then none of the effects I have are audible.
When I try and record sometimes it works and sometimes it doesn't. All inputs are correct and I have tried changing them.
This has been hours on the phone with Apple who keep telling me that it's all AVID's fault. AVID has no tech support and doesn't care which is why I'm switching from Pro Tools to Logic after 15 years.
Buying a new interface would defeat the money savings that I thought switching to Logic would bring as well as sending a perfectly good piece of equipment to the landfill.
Any help appreciated but please keep the comments to civil and nice. Thank you.

Presonus Faderport - issues with Logic?

Hi - I've just gotten the Presonus single-channel faderport - great and affordable little product; however, it's causing a strange issue in Logic despite their claim that it's compatible, and their tech support has led me to one possible issue I wanted to ask about...the faderport sends data exclusively on MIDI channel 1 apparently, which makes sense because when it's hooked up, any external sampler I have will not play out of channel 1. This seems like a fatal flaw - they said it could have to do with my environment setup, ie if any instrument has its MIDI port set to all...why would that be? I have multi-instruments that have each channel going to 1 of 16, and there are some old icons in the environment of instruments no longer attached that say "All". Otherwise, seems fine.
Any ideas of whether this is my Logic environment setup or the faderport? The faderport by the way is set up and installed correctly.
thanks!

update on this issue - I've found that the faderport can be installed and work without bottle-necking MIDI channel 1 and anything external that transmits on it only if it is installed while any external samplers are shut down and booted up after faderport installation.
however, the issue with it losing its connection to Logic quite frequently still occurs way too often making it too frustrating to use thus far- would love to know if anyone's figured out how to eliminate this problem and use the unit productively, because it has potential to be a great studio addition.
thanks, look forward to any feedback-

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

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?

Windows 8, Y55 ideapad continual clicking issue with touchpad. Help please

For some reason, when I tap to click the item I clicked remains actively clicked when I move my hand away from the touchpad. In order to process any action, I need to move my cursor away from the button I'm trying to click.
Interestingly enough I tried to disable tapping to see if it would solve the issue, and tapping continued to work...which is odd. It doesn't have this issue when I click objects with a mouse, only when I use the trackpad. Please help me, I'm confused.

hi BFG9000,
Welcome to Lenovo Community Forums!
You can try Uninstalling the driver of your touchpad from Device Manager, under Mice and other pointing device and make sure to put a check on Delete Driver/software prompt.
Then try Checking the touchpad if it works ok without a driver, If it does then try downloading a driver from synaptics website.
If not then Most likely this is a Hardware concern and you need to contact Lenovo Technical Support for assistance.
Best Regards
Solid Cruver
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Issues with Logic 9

1) Frontier Designs Alpha Track would not work at first. Fixed this.
2) Mouse scroll ball will not work in EQ anymore? Anyone seeing this? I used this alot to tweak the Q and dB values without dragging.
3) Drum replacment enhancement is always greyed out with my drum tracks yet it is not with my other tracks? Haven't been able to use it at all!?
4) Install process did not ask me to insert any of the audio content DVD's. Why? Are they the same as those installed with Logic 8?
5) Why is the "Help" menu so worthless in logic?
6) Why is the website other than this forum so useless when it come to tch questions? Am I missing something?

Try looking here for your answer <http://duc.digidesign.com/>
I use a Digi 002r & an Mbox 2 Pro with PT & LP9 with absolutely no problems as you describe.

Focusrite Scarlett 2i2 clapping and crackling issues with Logic Pro x new iMac 27"

Hi, I have just purchased a brand new iMac and downloaded Logic Pro x, I also purchased the Focusrite Scarlett 2i2 interface. I have downloaded the drivers from the focusrite website and everything is set up, when I plug in guitar or mic I get really bad clapping and crackling to the point where the sound cuts out altogether. I have changed buffer size and sample rates and everything else I can think of but nothing seems to fix the problem. I also deleted the 2i2 drivers and logic and reinstalled them both but still have the same issue, when I record using the iMac built in mic everything is fine so it's deffinately something to do with the interface. I am waiting to hear back from Focusrite tech help. Does anyone else have this problem? Any help would be appreciated.

I'm having a similar issue which might indicate that the problem is not your interface.
Yesterday I migrated all my stuff from my 2009 iMac to a brand new iMac 27", and when I did a quick test to play back some old projects in Logic there was loads of annoying clicks and pops. My interface is a Roland Octa-Capture.
I also noticed some weird CPU spikes from time to time, which I never had on my older, much less powerful iMac...

Metronome click issue with Logic 8

Similar Messages

Maybe you are looking for