![]() ![]() I can only simple mix using the built in line out. If I cange my playback engine to my Mac Pro built in line out, power down my 003 Rack+ and restart my computer all is fine when I relaunch Pro Tools, this however leaves me with no interfaace available for recording. Has there been any resolution on this? I am currently having a similar issue with Pro Tools 11 and a 003 Rack+ - my kernel_task ramps up to over 100% and stays high even after I quit Pro Tools. If you have any further advice for me, shoot away. ![]() Hopefully, I made sense and it will help some of you. Your rig will still run fine, but check out your activity monitor and just check. I would venture to say some of you aren't even aware of this problem. Please, check your activity monitor and look at your CPU usage. If any of you have had any other experiences please let me know. Hurry up Apple and send me my darn download code. I already paid Apple for Mountain Lion and I guess it's back to creating a boot disc and reinsntalling AGAIN. X locks up great to my 003 rack and syncs up with ADAT. Everything is great, but no sound out of Logic X. It's frustrating because I'm soooo close. Remember, I have to use this driver because the version 11 drivers kill my CPU. My problem now? When I launch Logic X, it will not output any sound on Avid driver 10.3.3. When I use driver 10.3.3 I can use Pro Tools like a champ and my CPU functions as it should. ![]() When I select the 003 device, all is good. Low and behold, anytime I selected the AVID 003 device my CPU shot up like a rocket. I then decided to load the Avid driver 10.3.3 and I was able to go into my audio preferences in both Logic X and PT and select the AVID 003 (the version 11 drivers) or the 003 audio device (the 10.3.3 driver). These drivers are lighting up firewire and creating the kernel task issue. It turns out the problem is with the AVID drivers for the 002 or 003 family. I still tried everything in the book, and through trial and error figured it out. I hopped online and noticed the kernel task issue with non-DAW users. I could reboot and it would drop down to 65%. It was eating up to 120% of my CPU, but only when I launched Logic or PT. They both ran great, but I started noticing the KERNEL TASK issue in my activity monitor. I did a fresh install of Mavericks, loaded up Logic X and PT 10. Yes, I know Pro Tools 10 is not qualified on Mavericks and you have to manually uninstall if needed. X only runs on Mountain Lion or above, so an upgrade was in the cards. So, I was on Snow Leopard, but recently was gifted Logic X and really liked it for composing. My home rig is more or a pre-production rig, but still very important to my work. I really like to sit tight on my OSX when it's running solid and I do a ton of work for my production company. I'm on the latest version of Mavericks, a Macbook Pro 7,1 (mid-2010) 2.4ghz with 8 gigs of ram and a brand new 6G SSD. Here's my rig specs to better help you all understand, and maybe draw some similarities if you might be having some of these symptoms. I figured posting this might help some of you having similar problems and no idea why. I wanted to share some information with you about things I have discovered using my Pro Tools 003 rack with PT 10.3.9 and Logic X 10.7. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |