'disk too slow' problems when trying to record ONE TRACK on my ibook.

okay- help guys. my new ibook freezes after not even a minute of one track live recording and i ge the disk too slow error. i'm using a basic m-audio usb interface with the internal (4200 rpm) hard drive. i know this isn't a fast hard drive, but SURELY. one track? i've been in touch with m audio, reinstalled driver, repaired hard disk permissions. still no good. i only ever need to record two live tracks at a time, but then i do need to stack them up a bit. is my ibook really incapable of that? i'm shocked if it is. anyone want to buy an ibook?
any advice much appreciated as i'm going out of my mind.
happy christmas,
adam gilhespy

Adam:
You haven't given a lot of info, but here are a couple of ideas:
1) What sample rate are you using? You should be at 44.1 or 48 kHz. Don't even think of anything higher.
2) Are you recording in a new arrange window? Or are you overdubbing to existing tracks? If so, freeze all your existing tracks.
3) Are you attempting to use any plugins while you're recording? If you are, turn them off for now.
4) How much RAM do you have installed? You need at least 768 MB; more preferably.
5) You're going to need an external drive eventually, but to record one track should be easily done.

Similar Messages

  • How do i deactivate a device through icloud if the device is broken and i am unable to turn on find my iphone? Also i do not own a apple id as ive been using a family members due to problems when trying to make one?

    How do i deactivate a device through icloud if the device is broken and i am unable to turn on find my iphone? Also i do not own a apple id as ive been using a family members due to problems when trying to make one?

    Hey tyjox,
    Thanks for the question. After reviewing your post, it sounds like you need to deactivate Find My iPhone on a device that does not work. You will need to work with the family member of the account the iPhone is registered with. I would recommend that you use this article to help you resolve or isolate the issue.
    iCloud: Remove your device from Find My iPhone
    http://support.apple.com/kb/PH2702
    Remove an iOS device you no longer have
    If you no longer have the iOS device because you gave it away or sold it, you need to remotely erase it before you can remove it.
    Sign in to icloud.com/#find with your Apple ID (the one you use with iCloud).If you’re using another iCloud app, click the app’s name at the top of the iCloud.com window, then click Find My iPhone.
    Click All Devices, then select the device.
    Click Erase [device], then enter your Apple ID password. Because the device isn’t lost, don’t enter a phone number or message.If the device is offline, the remote erase begins the next time it’s online. You’ll receive an email when the device is erased.
    When the device is erased, click Remove from Account.All your content is erased and someone else can now activate the device.
    Thanks for using Apple Support Communities.
    Have a nice day,
    Mario

  • Disk too slow error when using M-Audio Oxygen 49 keyboard

    I bought the M-Audio Oxygen 49 keyboard. And when I plug it into my MacBook Pro to do some playing, the project will record for maybe a minute but then I get a 'disk too slow' error and the recording stops. This happens every single time, no matter if there's 30 tracks or 1 track on the recording. I know that it is the keyboard causing the error because I am currently working on a 59 track piece that has effects on almost every track and my setup doesn't even blink. (well it'll pinwheel for a second when I hit record sometimes, but the CPU and disk meters don't ever get near red-line levels).
    What on earth is causing this stupid keyboard to cause this problem, and how do I fix it? It's clearly the keyboard. When I unplug it and record a live track on a project that just gave me the 'disk too slow' error, everything works just fine!
    Grr...
    Any help is appreciated, thanks!
    Edit: I have the MBP plugged via firewire into an Echo Audiofire and then into a WD hard dtive (at 7200 RPM). The keyboard is USB into the MBP.
    Message was edited by: Zombie Flanders
    Message was edited by: Zombie Flanders

    hi
    i spoke with Apple pro application support staff who confirmed that the Tascam 1884 patch for 10.4.10 is the cause of the problem. The apple boot drive can reliably record 1 channel of audio under normal circumstances. Apple staff described the situation as "unfortunate" and recommended to wait for Tascam to release 10.4.10 compatible drivers.
    For anyone interested in the technical background, the Tascam 10.4.10 patch DOWNGRADES the audioFW component (messing with kernel headers etc.). This compromises the OS's ability to correctly communicate with FW devices.
    I had tried recording to a firewire 800 drive, but all FW IO is affected by the 10.4.10 Tascam patch: Logic simply didn't record anything to disk when I tried this, and the machine became unresponseive. I do not recommend anyone attempt recording to a FW drive with the Tascam drivers installed.
    I have recorded circa 400 hours of single channel 96K 24bit audio to my internal Macbook Pro boot drive using the same software/configuration under 10.4.9 without a single glitch. I do recognise that when requiring heavy disk IO it is not advisable to record to the boot drive. However, 1 channel of audio can be reliably recorded if the system is well maintained.
    Thanks to all for your comments and suggestions.

  • Too many values when trying insert records by bulk collect

    Hi
    Can anyone advice on the bulk collect error please?
    Following is my code where I am getting too many values error...
    TYPE p_empid_type IS TABLE OF emp%ROWTYPE;
          v_empid               p_empid_type;
       BEGIN
          SELECT DISTINCT emp_id , 'ABC'
          BULK COLLECT INTO v_empid
                     FROM emp
                    WHERE empid IN (SELECT ord_id
                                       FROM table_x
                                      WHERE column_x = 'ABC');
          FORALL i IN v_empid.FIRST .. v_empid.LAST
             INSERT INTO my_table
                  VALUES v_empid(i);
          COMMIT;
    PL/SQL: ORA-00913: too many values in line - BULK COLLECT INTO v_empid

    Hello, since you're SELECTing a constant string, why not:
    TYPE p_empid_type IS TABLE OF INTEGER;
          v_empid               p_empid_type;
       BEGIN
          SELECT DISTINCT emp_id
          BULK COLLECT INTO v_empid
                     FROM emp
                    WHERE empid IN (SELECT ord_id
                                       FROM table_x
                                      WHERE column_x = 'ABC');
          FORALL i IN v_empid.FIRST .. v_empid.LAST
             INSERT INTO my_table
                  VALUES v_empid(i), 'ABC';
    Edit Untested: may not work
    This would be the best BULK COLLECT of all:
    INSERT /*+ APPEND */ INTO my_table
    SELECT DISTINCT emp_id , 'ABC'
      FROM emp
    WHERE empid IN (SELECT ord_id
          FROM table_x
         WHERE column_x = 'ABC');
          COMMIT;

  • No Reason For Disk Too Slow Error, any ideas?

    Ok,
    So I've used Garageband for years from iLife 06 and up and I've never had an issue with any Garageband until now. Here's the deal, I still get the disk too slow error, and there is no explanation. Below is my computer config:
    COMP I'M USING:
    Macbook Pro 13 inch
    OS X Mavericks
    Intel Core 2 Duo (1st unibody)
    4 GB of RAM MAX
    BRAND NEW Hybrid 7200 RPM Drive Installed 500GB total, 300 GB FREE
    NO Other programs are open.
    I use Garageband for recording songs but mostly now for recording podcasts. So the track I am using is normally 1 hour in duration. I can't seem to skip around, from minute 1 to minute 54 and edit at my whim without beach ball and timeing out getting the disk to slow error I never had this issue before, I either get the disk to slow error when trying to navigate large gaps of time in the podcast as I said earlier or even during RECORDING a podcast it'll simply say disk to slow, stop recording and occassionally say there are too many tracks in use, when I only record using 1 track of audio.
    How can this be possible? Even my old G4 allowed me to jump all over the timeline with no issues. It seems there is some kind of flaw in the software. And yes, I just restored OSX Mavericks to my brand new Hybrid Hard drive, so there's no explanation as there are no disk errors or permissions errors of any kind.
    I'd rather not hookup an external drive to record too as that seems silly when I've never had too before. If this "modern" computer can't do something that my old G4 ibook can do, don't you think we're going in the wrong direction with this program?
    I've heard of so many people having this issue, and I thought upgrading my OS and getting a new HD would help but it hasn't. I'm at wits end with this issue.
    Any advice would be helpful, thank you.

    There are a few other reports of problems with 10.6.7
    Some audio device(s) inputs have ceased working, a few disk to slow messages...etc. I don't see the wisdom of upgrading a working DAW system if that's it main function. OSX has to support a lot of different hardware now, many, many Intel motherboard and/or processor revisions... it's not going to be as smooth sailing as it used to be.
    pancenter-
    Here's a search over the past 90 days.
    http://discussions.apple.com/search.jspa?threadID=&q=Disktoslow&objID=c231&dateRange=last90days&userID=&numResults=15&rankBy=10001

  • Disk Too Slow??? Why now?

    Hello all,
    I have been using Logic Pro for the last five years on my system with no problems and all of a sudden, now I can't record a single audio track without a "Disk Too Slow" problem. Literally, the project can have only one track and it will still give me an error.
    My System:
    PowerMac Dual G5 2.5GHz w/ 3GB RAM
    Mac OSX 10.4.11
    160 GB Hard Drive (provided by Apple) - 58.9 GB left - Logic installed here
    250 GB Hard Drive - 130 GB left - recording done on here
    M-Audio Project Mix I/O
    For years I have been recording with Logic and I've never had this problem. I haven't done anything new, haven't installed anything new, or anything like that and just now I've been having these problems. I'm a DJ and audio recording constantly for upwards of 90 minutes straight is vital.
    Here's what I've done:
    * Tried changing buffer settings (set from 128 --> 512)
    * Tried making sure no other applications are running
    * Tried emptying trash
    * Tried turning off Airport
    Nothing seems to work. Any ideas?

    Hi there,
    Sorry to read you are having troubles with this.
    I have had the same troubles since Tuesday. All of a sudden I started getting Beach Balls and "Disc too slow". A few occasions I had a message saying that my "midi port was not found" on my MOTU.
    Here what I spent the last couple of days doing.... I am sure you have tried them all but maybe something here may help
    With some kind help from a forum regular, I reset my MOTU interface to factory settings. I repaired my permissions on my system drive.
    I ran a "check disc" for my external audio drive, it past every time, but I repaired it any way.
    I took my drive out of the firewire case to check the connections because it seemed it could be a power issue, tried it in another case. (I put the drive together so I felt comfortable doing this)
    I also removed a plug in that I had added IK CSR reverb, I had installed it the day my system started giving me "disc too slow" messages.
    I also removed all of my TRacks plugins from sessions, they are resource hogs and may have not been helping.
    I also trashed my logic preferences.
    Things at the moment are looking better.
    If my problem still exists it may be in my case the drive being on its way out. It is only a year and a half old, and dose pass disc utility tests every time.
    So I am thinking that I may have been mixing out my machine with plugs then having to do hard re-boots not helping things.
    Sorry to hijack things, just hoping that we can maybe find a common cause, and solution,
    Good luck,
    Jay

  • Runtime Error 217 when trying to Record

    I am using Captivate 4 on Windows XP. When I hit the Record button in Cap 4, a microphone icon displays and counts down 3-2-1, then runtime error 217 displays. Cap 4 then crashes.
    I am not recording audio for this project. I am recording FMR and in Edit > Preferences > Full Motion Recording  I have the Working Folder set to C:\Test.
    Not sure why Cap 4 is doing this.
    Can anyone make any suggestions to help me?
    Thank you.
    Laraine

    I deleted everything in the folder then restarted Captivate 4, but still
    experiencing the same problem when trying to record.
    *Laraine Hofmann
    Sr. Instructional Designer
    804-444-7365 (T)
    501 South 5th Street
    Richmond, VA 23219
    mwv.com
    <http://www.mwv.com/

  • "Disk Too Slow..." problem solved...for me

    Lately my Macbook and Logic have been driving me nuts with the "Disk Too Slow" error message. But I notice it was happening on one particular song. I'll cut right to the chase....delete unused tracks. After doing this the song played thru without a peep. And has been doing so ever sense. The cpu meter shows little or no activity. I am happy and all is right in the universe. Just thought I'd pass it along. Your milage may vary.

    Yep.....it all makes sense now. The song was created on my i5 iMac. Empty tracks not a problem there. I got wise when freezing the tracks didn't help. So I temporary deleted all my audio regions except those on ONE track. Still got the error message. So I froze that track and STILL got the message. ***? So I reloaded the song and deleted all unused tracks and, well, the rest is history. For what it's worth, 4 of those tracks were audio instrument and 8 were rewire tracks. I suspect the rewire tracks were the actual hogs, but I don't care at this point. Just happy to get some work done on the laptop. Your tip makes perfect sense as well.

  • DISK TOO SLOW on a POWERBOOK G4!

    Hi can someone pleeeeaasse help me quick!!! I have just spend loadsa dosh buying a midi keyboard, mic and a fast track audio device for my powerbook! I have 34gb free on the hard drive, 256mb of memory, and a 1.33ghz powerPC G4 processor. The operating system is mac OS X 10.3.9! However, when i try to record guitar (and this is the first track in so who knows when i'm on the 10th what would happen) it just says 'disk too slow' about a minute to a minute and a half into the recording! I've read the solutions saying buying a external hard-drive is the way to go - but i can't afford to buy one if it won't help. Basically I want to be able to record quite a few tracks comfortably can you tell me what i need to buy (ie firewire harddrive) or what i need to do (ie install garage bands 2) to increase my performance and stop these problems.Thanks!!!!

    You should not be seeing "Too Slow" errors with a single track, even my stock 800Mc iBook with only 256MB of RAM could record 8-9 tracks on the internal drive.
    You're going to need to see what else might be causing that.
    Other Apps running? Checked Activity Monitor to see if anything is hogging resources?
    Have you tried logging out and back in, launching only GB? Logged in as another user?
    --HangTime [Will COmpute for Food] %-|>

  • Weird HD meter jumping... "Disk Too Slow" error... ?

    I'm just trying to record 2 tracks of live audio, but the HD meter in the Transport Bar keeps "jumping" every few seconds or so. And I had it quit last night due to a "Disk too slow" error.
    I have a fairly beefy computer, and a lot of room on my HD. However, today I moved my entire Logic folder to a 1TB internal drive where it's the ONLY files on that drive (to try and increase the scratch disk space). But I'm still getting that weird meter behavior.
    I've tried changing the I/O buffer size, but that doesn't seem to help either.
    I've worked on projects where I've had dozens of tracks running at the same time, while recording, and while running several plugins.
    I recently re-installed my system (don't ask), so I'm wondering if there's just some simple setting that's different. Or I need to tweak.
    Thanks in advance!
    e

    Hi Ed
    I was just about to post pretty much the same problem
    I'm trying to work on a project & i have only 14 tracks 7 of which are audio tracks 6 with loops on there & one audio with a filter on there for bussing tracks too
    I've hardly got any plugins going yet i am just putting the basics together
    My problem is intermittent but very very annoying when i'm trying to get on with it
    When it happens the top CPU meter goes right over into the red the other hardly registers
    I Am also running the 64 bit i have tried it on the 32 bit but getting same problem
    Need to struggle on as this is for an interview tomorrow
    Thanks

  • Focusrite Octopre causing "Disk too slow" Error

    Well, I am having perhaps the most frustrating and inexplicable recording issue that I have ever encountered.
    To start off, I am using Logic Pro 9 with a RME Fireface UFX and a Focusrite Octopre MkII - for additional inputs when tracking drums. I am using some third-party plug-ins, but they don't seem to my causing my issue (as I will get to shortly).
         Essentially, whenever I am trying to track drums, a "Disk too slow/ or peaked HD" error pops up - usually less than a minute into recording. This interrupts the session and makes it impossible to make any progress when recording. It is incredibly frustrating for obvious reasons. I even set the input buffer to Large, and all the fun stuff - didn't help. I began to notice that I only encountered this error when tracking drums.
         So I managed to narrow everything down and discovered that the Octopre was actually creating the issue. When I turn off the Octopre, the problem disappears. Obviously though, this is still troubling, as I need the additional inputs from the Octopre in order to track drums. I need help resolving this issue as soon as possible, because It's keeping me up from finishing a handful of songs. Clealry it is an issue that is beyond my expertise, so help would be greatly appreciated. Thanks!

    Do you have the digital clocks synced, or rather, how do you have the digital clocks synced?
    You should have only a Single ADAT lightpipe cable running from the OctoPre OUT to ADAT IN, the Focusrite will be the Master Clock Sync, the RME will be set to slave sync to  the ADAT Input.
    It has to be in this order, if you're not using a separate wordclock generator that runs digital sync to both units via BNC connector/cable.
    I don't know that this is your problem but it's best to start with basics first.
    Set the Focusrite to sample rate 44.1 for testing, the RME should follow (at 44.1) if it's set to slave sync.
    You're going to record at 44.1kHz / 24-bit.

  • Disk too slow / System overload HELP?

    I'm really hoping someone can help me out with this!:
    I purchased a G4 PowerBook around six months ago, with Logic Pro pre-installed. Since then, I have mixed and mastered lots of music that was recorded on a previous system and imported. I was running multiple tracks simultaneously with tons of plug-ins and everything ran smoothly on my new Mac. HOWEVER, within the last month, my playback capabilities have been severely reduced. When I try to play back even two tracks simultaneously (with just one compressor or reverb), I get the error message, "Disk too slow / System overload."
    My first reaction to this problem was to check my disk space and see how much room I had left: it turns out I have over one third of my harddrive space still available. I checked my memory capabilities and they seem to be more than adequate. I bought new virus protection, too, and ran scans to see if that might make a difference, but it hasn't. I don't understand why this is happening on a system so new. ANY ADVICE YOU CAN OFFER WOULD BE GREATLY APPRECIATED!
    Many thanks.
    Powerbook G4   Mac OS X (10.4.6)  

    It is generally not a good idea to run logic on the same drive that contains your audio files and samples. Most of the data involved with logic whether it be programs or individual audio files will be saved physically all over the place on your hard drive. At a certain point the actual part of the drive that reads the data will not be able to move around to all the little different audio files it needs to access for the session on top of running the program and whatever other software that is up. It is best to save all your audio files and samples to a fast external drive (7200rpm at least) otherworldcomputing.com has great drives that have high quality cases and the option to put any drive they have in stock into the case. (i would recommend seagate) If you are going to continue running your entire sessions off the internal drive then you need to keep up with your basic mac housekeeping. You should repair your permissions 2 times a month (use disk utility) You should buy a good directory repair program such as disk warrior. The directory is exactly what it sounds like. It keeps track of where everything is on the computer. If your directory is corrupt the computer will have to do an extra manual search to find what its looking for. If your directory is healthy your computer will make a straight shot to the file you are looking for.

  • Disk too slow and system overload error

    I like many other users am having problems with the "disk too slow or system overload error (-10010)." It only seems to occur during playback attempts, seeing as I recorded with no problems yesterday, and only began happening today (granted, I have not tried recording anything since this started happening). I have tried changing the buffer size (still occurs at all levels), and, as per noted in a similar post, ensuring that my computer does not at any time put drives to sleep. All my sessions are stored on an external Toshiba Canvio Connect 2.0 TB drive connected directly to my computer via USB.
    My setup (I know that this is going to draw a lot of criticism) is a macbook air with 2 gb 1067 MHz DDR3 ram and a 1.4 GHz intel core 2 duo processor, running OS X 10.9.3. While I am fully aware (I promise) that these are well below the recommended numbers, I have been using this configuration since June without any problems whatsoever.

    Clancy,
    No problem!
    I also added it to the Useful links and resources for Logic Pro X  page in the tips sections....
    Cheers..
    Nigel

  • "Error Disk too Slow" Macbook Pro 2011 - Maverick and Yosemite - The Great Grand Mystery Unfolds!!!

    Hey everybody,
    Logic Pro X user here, have a late 2011 Macbook Pro, upgraded to 16gb of ram, 2.8ghz intel core i7, running latest version of Mavericks and more recently on a separate partition I tried Yosemite with a  clean install of only Logic Pro X.
    I use Apogee Quartet as my audio interface, I have a OWC Mercury Elite Firewire 800 external drive that I record to, all LPX files are on my internal drive.
    Before Mavericks I had 0 issues with this setup, no with just one sole drummer track, or one single audio or software track, I get the various disk too slow errors after a few seconds.
    I have tried reinstalling LPX, I tried a clean partition with nothing but Logic Pro on it (both Mavericks and Yosemite).
    I have reset my PRAM and used Apple Hardware diagnostics as well as memtest (i think it was called) and even reverted back to my old original RAM that came with the computer.  All hardware tests passed, I have verified and repaired disks from disk utility as well as from the recovery partition.
    I have worked with Apple a bit over the phone doing these things, I have also read just about every thread on this pervasive issue.  And its ruining my experience as a user.  I absolutely loved Logic on Mountain Lion, no issues whatsoever! I'm considering reverting back to it actually.
    On a side note I also have a HDMI Tv connected through the thunderbolt display, and a self powered USB hub that I connect my wireless mouse, iPhone cable and WD MY passport drive (which I only use for Time Machine).
    I'm basically at my wits end and open to anybodies suggestions, I even tried resting the SMC and several other things advised in these forums.
    I'm Stil under Apple Care and wondering if going into them is my only hope left.
    I find that garageband acts the same, but I have no other system issues! its so bizarre, performance on all other programs is totally fine, its only when I want to record that I get issues.
    For the record I do have some 3rd party VTS (Arturia V collection, EZ drummer 2 and AMplitube) but when I did the clean partition they weren't there and I still had the disk to slow error, so I'm not convinced its because of those.
    Also Since the partition I obviously have played with my storage but I still have 75 gas of space on the mavericks partition (out of 500gb ) and on Yosemite partition I have 125 gbs available and on my Firewire external drive I have about 150gb left on a 500gb drive, so I'm not convinced its a space issue either (especially since before Mavericks Mountain Lion seemed to work just fine.)
    HELP! Please help...I'm so exhausted trying to fix this on my own, and admittedly I've run to the end of my own capacity and don't know where to go from here.
    Thank you for any suggestions, sorry for the long post, and if I have left anything out please let me know, this is my first post.

    And yes I did upgrade my apogee drivers to the recent ones they just released.

  • Core Audio : Disk too slow (prepare)

    Can anyone help me. I have created a track that will not bounce
    because it always comes up with this error message: Core Audio: disk
    too slow (prepare). I cannot bounce tracks individually for the same
    reason. I have tried deleting some tracks that i dont need but it still does
    the same. I have 700 and something ram. Is this not enough. I have
    logic pro 7.1 and am using a few ultrabeats in the song. Know Any
    tricks i can get around this problem easily with. Any help would be
    greatly apreciateddd. thanx in advance.

    The drives in the rear positions are on an ATA-100 Bus, those in the front are on an ATA-66 bus. The CD is on an ATA-33 bus, and no Hard drives should be sharing the CD cable. ATA-66 and ATA-100 are plenty fast enough not to be a bottleneck, as long as you are not experiencing low-level correctable Disk Errors.
    A Disk Error will result in retries, both Hardware and Software, which often produces the data, corrected, after a delay.
    My recommendation would be to find a time when you can back up all data from the troublesome drive, and take the \[several hours] to Initialize with the "Zero all Data" option. This writes Zeroes to every data block, then does a read-after-write to check the data.
    If the Drive's error correction was required to recover the just-written zeroed data, that block is declared bad, and the drive will make a near-permanent substitution of a nearby spare block for the one found defective. This process has the effect of laundering out marginal blocks and returning the drive to "factory fresh" condition of all good blocks.

Maybe you are looking for