Unable to process audio with Pluggo plug-ins (I/O error (-36))

[kingtinker]

I am running Pro Tools 8 with an Mbox. Since upgrading to 8 I can't use Audiosuite to process audio with Pluggo (Cycling 74) plug-ins. I get the following error:

"Unable to create a new audio file on drive "____" for track "_____" because I/O error (-36)."

My specs:
2 x 2.66 GHz Dual-Core Intel Zeon
10 GB 667 MHz DDR2 F8-DIMM RAM
Mbox (1)
Pro Tools 8 LE
Mac OS 10.5.6
A number of external Firewire drives used for recording/playback, all 7200RPM

Any ideas?

Thanks,
Matt

[kingtinker]

seriously? No one?

[guitfiddle13]

I get the same thing when trying to record guitar w/ "eleven" & "amplitube Metal"

Imac 2.33
osx 10.5.6
Pro Tools LE 8 w/ cs2
Mbox 2 Pro
Fire Wire 7200rpm


Help!

[guitfiddle13]

Anyone have any ideas?

[DigiTechSupt]

A -36 error is a Mac OS error and can be caused by many things. Most of the time it's due to drive or file corruption. Have you tried this on a different drive?

It could also be a permissions issue - are the files/folders you're using set for read/write access?

I would try this on a different drive first, as that is the most likely option to give us some insight as to the ultimate cause.

[guitfiddle13]

I've tried reformatting. Yes, read/write is on. It a new ezquest 750gb, 7200rpm fire wire 400.
Tracks ez drummer/ Dfh just fine.
Won't let me record any 'Audio' files.
Help!

[DigiTechSupt]

Originally Posted by guitfiddle13

I've tried reformatting. Yes, read/write is on. It a new ezquest 750gb, 7200rpm fire wire 400.
Tracks ez drummer/ Dfh just fine.
Won't let me record any 'Audio' files.
Help!

Can you give us your complete system specs, per the info in the Help Us Help You thread?

Have you tested this with a different drive? Have you always had this problem or is this something that's come up recently?

[guitfiddle13]

sure.

Imac 2.33Ghz, OSX 10.5.6 combo, 3GB ram.
Protools 8 LE w/ cs2 update
EZQuest 750GB-7200 rpm-FW 400

[guitfiddle13]

.....also using mbox 2 pro

[DigiTechSupt]

Have any of you contacted Cycling 74 about this and, if so, did they have any thoughts about what the problem may be?

I'm going to try to contact them directly - unfortunately I don't have those plug-ins to test with, so I'm not sure what could be causing this, especially if it's only happening with those plug-ins.