Edius 4.5 disc too slow error message

[merlinthegray]

Drive Too Slow - Try This

I could not believe my ultra360 scsi drive was too slow to accept a 25Mb datastream, there had to be something else hogging the data pipeline between firewire input and drive input. Then I noticed two things during input - 1) looking at the display on the video camera compared to the edius player window showed an appreciable lag, started at about 0.25 second then got longer and longer as the capture time got longer, then after about a delay of 3 seconds between camera and player window displays the "drive too slow message" appeared.

2) the XDcam icon re-appeared on the task tray ( even though I closed it when the program started).

If I left the icon open the stop time was repeatable using the same HDV 1440 x 1080i canopus HQ standard codec for rendering, if i closed the xdcam program the capture continued without the error, however the lag was slightly increasing as the capture time went on but it never went beyond 2 seconds over 45 minutes.

Then I tried raw HDV input as hdv mpeg stream rather than the HQ codec - this time the camera display and player display kept pace with no noticeable delay over a 1 hour capture. As the data rate must be higher in the uncompressed state it would seam to me the problem is not in the drive being too slow but the cpu(4) not being able to process the data stream with the software codec. Presumably as some buffer overflows it trips a generic message of "drive too slow". With multi cpu (dual 2.8 xeon) and 4gig memory (ok 3.2 available to xp) i would have thought the processing would be quick enough unless the program isn't multiprocessor aware or the parallelisation of the processes cannot be achieved. OK the HD storm board is out there but us lowly firewire guys can't benefit from HDMI input. As my sony FX1 only outputs 1440 x 1080 I gues you Full HD guys really struggle with software dedosing of the m2t file on the fly to avi.

Anyone else reproduce the timelag scenario and does it clear if you switch to raw HDV. Any other ideas welcomed.

[merlinthegray]

disk too slow pci latency

I joined the disk too slow club as well, however only on trying the v5.0 version and capturing 1440 x 1080 HDV via firewire into dual 2.8 xeon w/s with scsi drives. No problem with earlier release 4.52.

I guess something has changed again with this major upgrade, my buffers stay 0/1 during capture. With other capture (vegas 8 no problems and no reported dropped frames). I wanted to use this editing prog with the stormHD card, howeve if I can't get this program running with my current set up then I will be staying with earlier version as there have never been any of these error messages capturing the same HDV footage before.

Will try this pci latency tool and try to tune the video card back a bit and any other pci device with a higher latency than the firewire controller to give it more headroom - but I am not optimstic having seen all the other threads on this dreaded disease.

[eschmitz]

Solution to disc too slow error

Hi,

I had the same problems for Edius 4 -5.

Seems the edius developers used too few buffer space on the path to the disc drives.
This makes streaming dependent on the the PCI Latency time windows is using for the disc driving controller card.

Solution:
fetch and install:
PCI Latency Tool 3.1 v2 download from Guru3D.com

http://downloads.guru3d.com/download.php?det=951

Locate the Hard disk driving PCI-Slot/device.

adjust the PCI Latency to 16. This wastes overall bandwidth but prevents buffer overruns. Don't use 0!

optionally make this adjustment permanent with "Settings", "Apply at Startup".

This solved all my problems.

good luck
E. Schmitz

Ps: my System

Dual Opteron 248
Tyan Tiger 2875
ATI 7900 Pro grafix
Edius NX + Bay plugged into 32 Bit PCI Slot
Hard discs SCSI, SATA 750GByte, IDE.

None of the discs worked right before adjusting the PCI Latency. Standard PCI Lateny on my System was 64 except for the IDE drive (32). PCI Latency 16 made the IDE drive working stable and the SATA drive working at all.

Hi Simon,

Can let me know the specs of your laptop? My PIV 3.4GHz desktop system just died on me and I might end up with a laptop instead of another desktop system.

Thanks.

AM2 mobo and cpu seems much cheaper than Intel mobo and cpu. Any known problem of Edius 4.5 with AM2 systems? Which cpu is advisable?

[THoff]

When I Try to Capture a Clip in DVCPRO HD to this system (EDIUS VER 4.54) something happening, a pop up menu appears in a screeen tell me "destination drive is too Slow".

If that is a live capture (not a P2/MXF transfer), try changing the camera's timecode to FREE RUN instead of REC RUN.

I have just started receiving this error message when capturing to my laptop via OHCI Iee1394 firewire. I have been using Edius v4.52 and v4.54 for the last 3 months on pretty much a daily basis and my camera, computer set-up and my workflow has not changed in that time.
Since the problem has occurred recently on 2 different days but not consecutive days I have been trying to work out what has caused the error and right now it seems to me that it is connected to high and continuous audio levels coming from the source.

I have clips on a tape that will now always produce this error yet I can capture from other areas of this tape in DV PAL 4:3 downconverted by the camera and also in HDV. There is no difference in camera and laptop set-up, the only variable is the footage and audio on the tape.

The footage on the tape has a sustained period of high-volume audio ( I was quite close to a large engine on the back of a boat).
When capturing I can see the Buffers climb from 0 to the maximum (32 in this case) then the error occurs. When I playback what I am able to capture of these clips the meter on the Edius Audio Mixer hits the big red max and stays there.

I am able to capture more of these clips using PP2 on the same laptop but did receive 'Unknown recorder error'.

I am able to capture this footage without error on my more powerful desktop machine (faster processor, more RAM). There's no dropped frames or corruption of any kind to the captured clips but the 'buffers' while capturing do climb.

I think I am seeing these errors now as I forgot to reset the camera's audio level back from 'manual' to 'auto'. That's what I think happened anyway but will test this theory again in a few days.

I hope this helps. If you do want to know my laptop and desktop specs I'll be happy to provide them but they haven't changed and Edius has worked for me on every day but 2 for the last 3 months.

regards
Simon

Hi Simon,

Can let me know the specs of your laptop? My PIV 3.4GHz desktop system just died on me and I might end up with a laptop instead of another desktop system.

Thanks.

[Stereodesign]

Was this exact same hardware setup capturing OK prior to v4.5x?

In both my systems the hardware has not changed at all, leads have not even been unplugged from the PC, only the version of Edius changed from v4.2x to v4.5x, as soon as the software version changed the error started. Therefore it has to be software related.
Error happens using Composite or s-video in on NX card or DV in on NX card in my case, so I doubt that its 1394 related.

[Larry Bantle]

A possible scenario for those who are experiencing this problem. I got the same "Disc to slow" message and with the hardware set up I have (incl. dual SATA Raptors in RAID1) concluded something was crazy. So I started switching and swapping and came to the conclusion it's some weird contention of the on board 1394 port in my Dell 690. I have an Audigy SB sound card in the box which has an on baord 1394 port so I plugged my HDV player into that port and voila no more problem. Went back to the onboard 1394 port with the HDV player and that evil "Disc too slow" message came back. Went back to the 1394 port on the Audigy card and no more problem since then.

[Stereodesign]

Welcome to the club.
As you can probably guess by the number of pages and post in this thread you are not alone.
At present nobody can find the cause of this error or replicate it reliably to track it down.
It is known to only occur in v4.5x not in earlier versions.
Some users have never experienced it, other have, its wierd one.
Until it is either fixed or goes away magically in a new release I can't see this thread going away.
Can you replicate it reliably?

[seprimo]

Hi,


I found a problem in EDIUS 4.54 version.

When I Try to Capture a Clip in DVCPRO HD to this system (EDIUS VER 4.54) something happening, a pop up menu appears in a screeen tell me "destination drive is too Slow".

When I try to Capture to other system (EDIUS VER 4.52) nothing happens or everything gooes OK.

The two systems have the same configuration, in (edius 4.54 system) i hev more space avaiable then teh system (EDIUS 4:52). In my ideia something is not ok with EDIUS 4.54. in others version and realeses I don't have any problem. (Edius 3 or 4 ).

Anybody know something about this issue.

[Stereodesign]

I have found that this incorrect display of remaining capture time is part of the error.
I always get this when the error is displayed but don't always get the error (if you see what I mean!) sometimes an incorrect time remaining is displayed but when this reaches 00:00 the remaining time displays correctly and capture continues.
If the remaining capture time is displayed correctly at the start of capture then capture is faultless.
I am sure some part of Edius regarding the way it "sees" the discs has been altered in v4.5x, probably for a good reason, but its just too flakey.

[johnsirb]

Hello All, well add me the the slow disk club. I just upgraded from 3.6 to the current 454. was capturing thru a Storm2 to an Ext Seagate 750 SATA ( I've got 2 hooked up). kept getting the error and noticed the counter said I only had about 55:00 of capture time left. it would go for a minute or so then dump. cleared some footage off and still no joy.

switch to the second Sea 750 ( said their was 8+ hrs available) and captured the 14:00 of footage, no problem

as the skip errors check box is on.

[SimonD]

Sorry team,
Had a 'not enough hours in the day' issue.
Right, good news/bad news; I have captured the problem clips as M2T how do I get them to who wants them?
Bad news is that I have captured them in their entirety. No error messages. Can't think of anything I have changed since they caused an error at every capture attempt. I have tried and tried and now they capture without fault downconverted to SD from the camera or straight in as HDV.
Anyway, if you'd like to check the footage I can send it....

regards
Simon

[GrassValley_KH]

The native format (of the problematic footage). So if it's 50i HDV, capture 50i HDV M2T.

[SimonD]

I can make the clips available. How would you like them captured?