Mac Book Pro Shizzle

bleepsnbreaks · Post by **bleepsnbreaks** » Sat Oct 13, 2007 9:47 am

I already have a firewire audio interface.
Its a CME UF400e in my UF7 keyboard, which cost about 400 bucks. They are made by terratec. Its a great card and I have tried this with a brand new one, a fireface, presonus and an M-box round at mates studios. Its not the audio interface thats causing a problem. Also, this only started happening a few weeks ago, after an apple update. I think its a problem with coreaudio.
Also didnt have this problem with my old Macbook (non pro) 2.0 coreduo it WAY out performed my new Macbook pro 2.4 core2duo.
There is something funky going on and no one seems to be able to tell me what.
I even have these problems using no VSTs at all, only operator, so its not amessed up VST or AU causin it either.

leedsquietman · Post by **leedsquietman** » Sat Oct 13, 2007 5:22 pm

that sucks man...

Maybe you should let Apple know. Microsoft broke firewire on windows XP SP2 with an update that slowed firewire 400 to firewire 100, they had to implement a fix but that took a while to surface.

Are your drivers up to date on the CME keyboard, I've read a few times on forums that their drivers are not too great. Although if you're having the same problem with other interfaces then I don't know.

Usually this forum is filled with mac geeks and there are hundreds of posters on here using macbook pros, maybe one of them has an answer.

bleepsnbreaks · Post by **bleepsnbreaks** » Sat Oct 13, 2007 5:37 pm

You dont use drivers for most audio interfaces on macs. The all usually all use coreaudio.
Yeah, Im kinda hopin that when MacOSX 10.5 comes out this month that it fixes it.
I dont have tis problem with reason, or logic, would be good to be able to test this out on the beta of Live 7 but havent been able to get a on to the program yet.

m.Lo · Post by **m.Lo** » Wed Oct 17, 2007 10:59 am

Thanks for Information, so, can you tell more about firewire interfaces, are you experienced to use one or more of them?