Powercore 6000 problems, unstable and generally annoying

Question

Level 1

0 points

Powercore 6000 problems, unstable and generally annoying

Hello

I just got a powercore 6000 and am trying to get it to work with Logic 8 on a macbookpro. Most of the x8 plugins work ok but as soon as i try and use the 6000 ones ( MD3 / Vss3 etc ) after a second it corrupts the audio and then won't play back properly. It makes a kind of distotored sound, similar to dropping the bit rate really low. Once it goes I have to restart logic and powercore.

Soundcard i'm using is Focusrite Saphire Pro 8. It still happens when I go direct to laptop and miss out the Saphire/

Buffer in logic is set to 1024 and I've tried pretty much everything I can think of, TC haven;t got back to me. And after reading around it seems they are pretty useless.

I'm running 10.5.4 on a macbookpro. Powercore 3.2 software.

Anyone else had problems and managed to fix it ?

Cheers

Dan

macbookpro, Mac OS X (10.5.4), 4gb Ram

Posted on Jul 2, 2009 11:38 AM

Reply

Answer 1

Bee Jay

Level 6

10,900 points

Jul 2, 2009 11:41 AM in response to masda

Are there any Powercore user forums out there? - that's probably the first port of call while you're bugging TC..

Reply

Answer 2

Jul 2, 2009 11:48 AM in response to masda

Do you also have a external drive for your Logic projects on your firewire bus? You might find that your Powercore (very nice, BTW) needs it's own bus, requiring an ExpressCard34

Reply

Answer 3

masda Author

Level 1

0 points

Jul 2, 2009 11:54 AM in response to John Alcock

thanks for teh responses.

no i don;t have an external drive, the disturbing thing is that it happens when I put the Fw from powercore direct into computer port...

And forum wise, yeah I've checked them but the TC forum isn't great and their FAQ knowledgebase didn;t seem very knoweldgable on troubleshooting... Thought i might have more luck in with logic users.

Is there anyone running this on a macpro and logic without issues ?

cheers

Reply

Answer 4

Jul 2, 2009 12:28 PM in response to masda

Is there anyone running this on a macpro and logic without issues?

A colleague is using a 6000 just fine on a MacPro - but are you using a MacPro or a Mac Book Pro? It matters, because of the FW chipset - some don't play nicely with some FW devices, and the t.c. powercores are some of them. If you're using a MacPro, this shouldn't be an issue, but if you're using a MacBook Pro, then boot into single user mode by pressing Command-S immediately after the chimes. That screen should tell you if you're using Agere Lucent or Texas Instruments FW chip. Then type 'reboot' return to get out of single user and reboot normally.

The fix might be an ExpressCard, but first it would help to know exactly what you're using.

Reply

Answer 5

masda Author

Level 1

0 points

Jul 2, 2009 12:32 PM in response to John Alcock

sorry, i meant to type Macbook pro.

Its a 2.5ghz intel core 2 duo...

Reply

Answer 6

Pancenter

Level 6

14,788 points

Jul 2, 2009 12:42 PM in response to John Alcock

John Alcock wrote:

A colleague is using a 6000 just fine on a MacPro - but are you using a MacPro or a Mac Book Pro? It matters, because of the FW chipset - some don't play nicely with some FW devices, and the t.c. powercores are some of them. If you're using a MacPro, this shouldn't be an issue, but if you're using a MacBook Pro, then boot into single user mode by pressing Command-S immediately after the chimes. That screen should tell you if you're using Agere Lucent or Texas Instruments FW chip. Then type 'reboot' return to get out of single user and reboot normally.

The fix might be an ExpressCard, but first it would help to know exactly what you're using.

Right on John,

To the OP, if it is a Lucent chipset... back up your whole system, and download the combo updaters to 10.5, 10,6 & 10.7... depending on your net connect speed this could take a whle but combo updaters are the safest way to go.

When updating, unplug all Firewire and USB devices except keyboard and mouse, update one version at a time and tewst afterwards. Apple included some firewire updates that may improve things. Of you do get it working, stop!

pancenter-

Reply

Answer 7

Jul 2, 2009 12:43 PM in response to masda

OK.

So now try booting into single user, as I described above, to find out which FW chip your laptop uses.

Reply

Answer 8

masda Author

Level 1

0 points

Jul 2, 2009 1:07 PM in response to John Alcock

Ok,

it said :
4.170.469FIIREWIRE (OHCI) TI ID8205 built-in now active

not sure which one that is!
I could update to OSX 10.5.7. Been debating it a while so guess i should just do it anyway. Anyone had any grief with 5.7 ?
I'll get an express/34 anyway.

Thanks to all for assistance, much appreciated.

Reply

Answer 9

Jul 2, 2009 1:15 PM in response to masda

Good news! It's a T.I.

Now you should follow pancenter's advice and upgrade OS versions one at a time. You could go direct to 10.5.7 but it may not correct the problem. Although it takes longer, I'd try one at a time.

If you decide to get a card, then make sure it uses a T.I. chip. Pyro, Papyrus and Unibrain all use T.I.

Reply

Answer 10

masda Author

Level 1

0 points

Jul 2, 2009 1:33 PM in response to John Alcock

cool, dwnloading 10.5.5 now.

just checked out a few cards and not many specify the chip, I'm thinking this one looks like it'll do the trick
c http://www.amazon.co.uk/Sonnet-Technology-FireWire-USB-ExpressCard/dp/B000TMI0VU /ref=sr12?ie=UTF8&qid=1246566636&sr=8-2

thanks again guys

Reply

Answer 11

Jul 2, 2009 1:51 PM in response to masda

Be careful if the chip isn't specified.

These are T.I.

http://www.adstech.com/products/PYRO1394DVForNotebooks/intro/API601intro.asp?pid =API-601
http://www.papyrus.co.il/Products/ieee1394aexpresscard_34_2ports( tichipset).htm
(you have to copy and paste the last link, for some reason)

Reply

Answer 12

masda Author

Level 1

0 points

Jul 3, 2009 11:07 AM in response to John Alcock

just an update on this, incase anyone is having or has similar grief

the update on OS X fixed the problem when only the PoCo is running. As soon as I try and chain up the soundcard it freaks out after a while.. same low bitrate sound issues...
Express card comes on monday so i think that should sort the problem.

cheers

Dan

ps.
TC got back they said so will try that this too to see if i can run a couple of things through one port :
"Try a reset in the POCO Control Panel.
If you have any other firewire devices on the same firewire port, please disconnect and keep only the POCO connected for testing.

Follow the description below and reinstall the software:

Run the two PowerCore un-install scripts located in your Home folder. If you have a PowerCore Compact, FireWire, X8 or 6000 power it off.
Restart your system.

Go to ./Library/Audio/Plug-ins/Components and verify that all PowerCore plug-ins are un-installed. If they are not, delete them manually.
Go to ./Library/Audio/Plug-ins/VST/PowerCore/ and verify that all PowerCore plug-ins are un-installed. If they are not, delete them manually.

Go to Applications>Utility>Disk Utility
Repair permissions

Download and install PowerCore 3.2
Restart your system. If you have a PowerCore Compact, FireWire, X8 or 6000 power it back on.

Latest Software:
http://www.tcelectronic.com/Default.asp?Id=12699 "

Reply

Answer 13

Jul 3, 2009 11:13 AM in response to masda

Thanks for coming back and posting this - very helpful.

the update on OS X fixed the problem when only the PoCo is running

Just curious: which OSX version fixed it? Or did you go straight to 10.5.7?

Reply

Answer 14

masda Author

Level 1

0 points

Jul 3, 2009 1:09 PM in response to John Alcock

I went to 10.5.5 and then jumped to 10.5.7.

it seemed to fix it at 5.5 but wanted to see if i could chain soundcard up and it still work. Am begining to wonder if its my focusrite saphire pro10 that doesn't like being chained with a Poco.
still having greif, will let you know on monday if the extra firewire ports let me run saphire / liquid mix and pop without any freakouts

cheers

Reply

Answer 15

Jul 3, 2009 2:33 PM in response to masda

it seemed to fix it at 5.5

That would have been my guess

focusrite saphire pro10 that doesn't like being chained with a Poco

I think that's highly unlikely. Focusrite seems to have this very well sorted out, and t.c. makes no secret that the PC wants its own bus. I still have a Focusrite 26I/O almost the same as yours and it works great with other FW devices.

Monday's update should fix your system completely - fingers crossed!

Reply