Error Message (-9136), memory problems |
Fri 7 Sep 2007, 21:34
Post
#1
|
|
Newbie Group: Members Posts: 1 Joined: 07-Sep 07 From: Ferndale - US Member No.: 94,647 |
No matter how few plug-ins I use, or track counts, I continually get the following error message:
CPU usage is holding off USB audio. Remove some plug-ins, delete some tracks or increase the "H/W Buffer Size" in the Playback Engine dialog. (-9136) What is strange about it is that it happens frequently at the moment I touch the touch pad to make an edit, or the space bar to stop play. I don't trust that it actually has anything to do with buffer size or track or plug-in counts because occasionally it will just play through fine and any time I've actually had real memory limitations on earlier systems, this would never happen. I'm using a MacBook running OS X 10.4.10 (but had the same problem before I made the update to 10.4.10) and Pro Tools 7.3.1. My RAM is maxed out: 2 Ghz Intel Core 2 Duo Processor, Memory 2 GB 667 MHz DDR2 SDRAM For recording, I'm using an M-box (not the new ones) and recording to a separate firewire drive. Specific settings: H/W Buffer Size: 1024 Samples RTAS Processors 2 processors CPU Usage Limit: 90% RTAS Engine: checked to Ignore errors during playback and minimize additional I/0 Latency DAE Playback BUffer Size 8 Can someone please help me?? Daniel |
|
|
Sat 8 Sep 2007, 05:14
Post
#2
|
|
SuperHero Group: Members Posts: 1,616 Joined: 15-Oct 06 From: Paris - FR Member No.: 84,237 |
check it here you can type -9136 and it should do.
besides a HD optimization might solve this problem This post has been edited by groovebrother: Sat 8 Sep 2007, 05:15 |
|
|
Thu 13 Sep 2007, 17:43
Post
#3
|
|
Rookie Group: Members Posts: 33 Joined: 02-Oct 06 Member No.: 83,805 |
Or simply read it here!
DUC wrote. -9136 error messages can be caused by a few issues in OS X with Mbox: 1) You may have added more RTAS plug-ins than your Pro Tools system can handle. Pro Tools LE systems use the host processor in the computer to process RTAS plug-ins. At some point, the host processor will be maxed out in it's duties and throw a -9136 error message. Remove a plug-in or two to resolve this. Keep in mind 3rd party plug-ins use a lot of processing power and you may not be able to use too many of them (including software synths). 2) Recording to your system hard drive can bog down system performance and cause a -9136 error message. It's ALWAYS better to record to a secondary hard drive. When you launch your Pro Tools sessions, save the session to a different (supported) hard drive other than your system drive. This is recommended for all Pro Tools systems, but is more highly recommended for Mbox systems for a couple of reasons. Firstly, many Mbox users run their Pro Tools systems on an Apple laptop or iMac. These system hard drives are slower than 7,200 RPMs, which is required for recording a Pro Tools session. A supported firewire drive would be ideal in this case. Secondly, slower processor systems are greatly affected when recording to the system drive. There is always better performance when recording to a second hard drive. For information on supported hard drives see: http://www.digidesign.com/compato/osx/stg/le.cfm 3) Raise the hardware buffer size above 256 samples during recording to help prevent -9136 errors. (Setups menu > Playback Engine). 4) Playing a QuickTime DV movie via a Canopus converter can throw a -9136 error message over time. This is a known issue and has not been resolved. 5) Sometimes updating the firmware on Mbox can fix an unresolvable -9136 error message. To download the Mbox firmware update rev 20 for OS X from the Digidesign website: http://www.digidesign.com/download/mbox/ Download and run the Mbox firmware update for possible resolution of -9136 error. 6) An unresolved -9136 error message can sometimes mean hardware failure and Mbox would need to be repaired. Call Digidesign Tech Support for an RA. No matter how few plug-ins I use, or track counts, I continually get the following error message:
CPU usage is holding off USB audio. Remove some plug-ins, delete some tracks or increase the "H/W Buffer Size" in the Playback Engine dialog. (-9136) What is strange about it is that it happens frequently at the moment I touch the touch pad to make an edit, or the space bar to stop play. I don't trust that it actually has anything to do with buffer size or track or plug-in counts because occasionally it will just play through fine and any time I've actually had real memory limitations on earlier systems, this would never happen. I'm using a MacBook running OS X 10.4.10 (but had the same problem before I made the update to 10.4.10) and Pro Tools 7.3.1. My RAM is maxed out: 2 Ghz Intel Core 2 Duo Processor, Memory 2 GB 667 MHz DDR2 SDRAM For recording, I'm using an M-box (not the new ones) and recording to a separate firewire drive. Specific settings: H/W Buffer Size: 1024 Samples RTAS Processors 2 processors CPU Usage Limit: 90% RTAS Engine: checked to Ignore errors during playback and minimize additional I/0 Latency DAE Playback BUffer Size 8 Can someone please help me?? Daniel |
|
|
Fri 14 Sep 2007, 12:37
Post
#4
|
|
Junior Member Group: Members Posts: 122 Joined: 16-Jul 06 From: London - UK Member No.: 81,499 |
Elsewhere on the Digi site it recommends plugging your M-Box into the front USB port only (the one furthest from the screen). This wasn't hard to find so I guess you've already tried this.
This post has been edited by Jim Hoyland: Fri 14 Sep 2007, 12:38 -------------------- www.myspace.com/commercialmusicstudios
|
|
|
Fri 21 Sep 2007, 19:05
Post
#5
|
|
Newbie Group: Members Posts: 1 Joined: 21-Sep 07 From: CA Member No.: 95,101 |
Elsewhere on the Digi site it recommends plugging your M-Box into the front USB port only (the one furthest from the screen). This wasn't hard to find so I guess you've already tried this. This worked for me. I've been trying to figure out all sorts of conflicting plugins etc... and it turns out its the usb port! Same thing though, the error appeared to be related to me touching the mac book. Space or click to stop, if I used the trackball tere was no error. Very odd. try it out and I hope it solves your problem. |
|
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members: