Announcement

Collapse
No announcement yet.

Drive disk too slow

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • GrassValley_BH
    replied
    Since not all systems experience the problem, it still could be hardware-related.

    The problem seemed to have appeared somewhere in the v4.x series.

    And before someone asks, No, we can't simply replace the capture module with the old capture module. There were very significant architecture changes between v3 and v4.

    Leave a comment:


  • Stereodesign
    replied
    It has already been established that it is a bug in Edius 4.5x that causes this error it is not a hardware problem.

    Leave a comment:


  • pjsssss
    replied
    Originally posted by murat unal View Post
    Hi again,
    I can capture via OHCI 1394. This means there is no bad sector on HDD. I hope my new Edius NX PCI-e card isn't defective. I guess 4.61 version contains bug. I'll try uninstalling 4.61 and setup Edius 4.
    Before yo get to crazy, read the sticky post on 10 things to do when getting the disc too slow message. This has happened to quite a few people since 4.5 came out. Some have solved it with things done with the computer and some have just had it randomly pop up. Bottom line is it is possible that there is nothing wrong with your computer.

    Leave a comment:


  • murat unal
    replied
    Hi again,
    I can capture via OHCI 1394. This means there is no bad sector on HDD. I hope my new Edius NX PCI-e card isn't defective. I guess 4.61 version contains bug. I'll try uninstalling 4.61 and setup Edius 4.

    Leave a comment:


  • easy_edit
    replied
    Use scenalyzer software and forget disk to slow error if you work with SD.
    I capture on one disk and burn DVD in same time or edit in Edius with files on second disk. In task manager set Affinity use CPU0 for Eius and CPU1 for scenalyzer on my C2Duo E6600
    http://www.scenalyzer.com/main.html
    ScenalyzerLive now supports capturing from the Storm, the EZDV and the Raptor RT Canopus Cards

    Leave a comment:


  • tonyblueeyes
    replied
    I'm getting the same message as well using a NX PCIe

    I did not do anything wrong, of course.

    IOT continue capturing, I'm using OHCI.

    After capturing is finished, restart the PC and then NX works fine again.

    Actually I don't know what's going on.

    Leave a comment:


  • skier-hughes
    replied
    If this was built for video editing and they installed the card and programme, maybe this would be a good opportunity to get someone to inpsect the pc and rectify the problem for you?
    It does mean you won't have it, but may help determine the problem.
    The responsibility would of course be theirs in ensuring you have a proper working pc, and you could get them to read all the stickies and threads relating to disc to slow messages already here to help them in their quest.

    I'd be interested in knowing the outcome if you follow this route.

    Graham

    Leave a comment:


  • Aristotelis
    replied
    Hi Mark, i just got a new station a couple of days ago. I started my new documantary editing with DV format. After 5 minutes capturing, "destination drive disk too slow" warning appeared. I'll try Mpeg2 capture, but working Mpeg with this station is sad. I don't know what to do...
    For DV capture you can use other applications like DVCapture or even Windows Movie Maker and you will be able to capture ok...

    Leave a comment:


  • murat unal
    replied
    Originally posted by Mark View Post
    Hi there,

    I was just trying to down load a fifteen min' tape and after about 2 min's a message came up say "Destination drive disk too slow". Can anyone please explain what I need to do? Thanks in advance!

    Mark
    Hi Mark, i just got a new station a couple of days ago. I started my new documantary editing with DV format. After 5 minutes capturing, "destination drive disk too slow" warning appeared. I'll try Mpeg2 capture, but working Mpeg with this station is sad. I don't know what to do...

    Leave a comment:


  • Stereodesign
    replied
    It is a bug, it wasn't in the older versions using identical harware, and if you revert back to a later version it magially vanishes.

    Lets hope that GV are working ona fix.

    Leave a comment:


  • mike0130
    replied
    I have a feeling that this is a bug. Ver 3.x and 4.x up to 4.26 worked without this message on the same machine. I cannot recall somebody asking about this problem on the forum too.
    I think this may be serious problem for some users.

    Leave a comment:


  • GrassValley_BH
    replied
    And most drives that ship nowadays have Write Verify enabled for the first 10 or so powerups. Write Verify lowers write performance.

    The idea behind it is sound though - with Write Verify on, if any problems are detected early on, especially during format, those bad sectors will be reallocated to spare sectors. This is all done internally on the drive - the system doesn't "see" anything different, except for some write performance degradation.

    Leave a comment:


  • GrassValley_MD
    replied
    To add to Brandon's thoughts here, it can also be caused by a drive going out on you. I know this is a brand new system but watch it closely because you might have a bad drive


    Mike

    Leave a comment:


  • GrassValley_BH
    replied
    Destination drive is too slow can mean a number of things, but the root cause is that there is a buffer overrun during the capture.

    Essentially, something interrupts the data flow enough to cause a frame drop.

    This can be from background scanning programs, CPU power management (SpeedStep or the like), drive errors, bus contention, or other odd things.

    It can also show up when capturing to a FAT32 volume and you hit the 4GB filesize limit.

    Leave a comment:


  • kikillo
    replied
    Hey
    I have the same problem when I tried to capture i have a warning with destination drive to slow.So i can't capture on this way.For the moment i do this with the mpeg capture.I ask were i buy the computer en she told me that the problem is bij the update from 4.51 to 4.52.Maybe a bug.
    I think we need another update to fix this problem.Can anyone tell this problem to Grass valley.Here in Belgium I have a few friend with the same problem

    Thanks

    Kikillo

    Leave a comment:

Working...
X