Edius 4.5 disc too slow error message

[THoff]

Edius also used to display that message when capturing DVCProHD live from a Panasonic HVX200 and the timecode wast set to REC RUN instead of FREE RUN in the camera's RECORDING SETUP menu. Furthermore, the problem did not occur in 1080P, only 720P.

The last time I tried and encountered the problem was with V4.24 -- I haven't tried it with V4.5.

[JPowell]

I'm getting this error now in 4.52.

Premiere seems to be capturing the same tapes just fine.

I'm also on NX PCIe - firewire capture - NTSC DV 4:3 - 2 drive SATA Raid 0 - scene detection on

This error has only occurred with 4.5x builds for me. After reporting the error, Edius is sluggish and can't communicate with the deck or display overlay of the video in the player window. Restart/Reboot didn't help.

[Stereodesign]

The reply I got from the UK impoters was "try v4.52 and see if that works" which is not really what I expected, or was lead to believe at the Mnachester roadshow at which I was told Holden were going to be investing in full time support people, but something I will try once the current project is signed off.
Other than that its pretty obvious to me, based on the replies to this thread, that there is a problem.
I notice that GV have kept well out of it, probably so they can maintain the "we are not aware of any such error message" line of reply.

[GrassValley_KH]

I notice that GV have kept well out of it, probably so they can maintain the "we are not aware of any such error message" line of reply.

Incorrect.

I (and I suspect my co-Mods) only reply when we actually have some knowledge to contribute on the matter. "Disk Too Slow" errors have existed since the beginning. They are no secret.

They are however, usually solvable through hardware diagnosis and scenario testing - something I am personally ill-equipped to handle.

[createmedia]

I have 3 Edius 4.51c on a SAN and just got it working on HDV capture properly. Previously used Sanbolic Melio FS file sharing software for RAID array. RAID formatted MelioFS. No good gave the drive too slow errors. Reformat to NTFS, I have now got an evaluation of MetaSAN (used to be Image SAN2) and now I can capture on all three at once without difficulty. systems connected on optical fibre to QlogicSANbox switch with Axus Yotta 5TB Raid 3 array. It was only failing on scene splitter and I got about 2 frames of the next clip after it stopped. The Write buffer hits 32 then it stops. Putting I/O monitor on to trace the errors just set to your video drive only is useful. Then you can send the I/O monitor trace off to Canopus.

Under Melio FS the 2kB transfers were only showing up as 2MB/sec using the Atto Disk Benchmark tester, which isn't good enough for Edius to close the file open a new one and start appending data without pausing the tape at a split. Under NTFS I am showing 2kB transfers at 14MB/sec, 8192 transfers at 205MB/sec from the Raid array.

Hope there was something useful there for you.

[Stereodesign]

They are however, usually solvable through hardware diagnosis and scenario testing - something I am personally ill-equipped to handle.

and so, it seems, is anyone else connected with Edius, certainly in the UK.

[mike0130]

I had this message a month ago and looks like it's gone on ver.4.52... Well, cannot be absolutely sure, because I replaced my motherboard... Anyway, happy for now, my "old" disks are not slow anymore...
mike

[bhmm9999]

For the record, I have experienced similar error message on several occasions. My capture drives are dynamic raid 0.
edius version 4.51c

[Stereodesign]

I had this message a month ago and looks like it's gone on ver.4.52... Well, cannot be absolutely sure, because I replaced my motherboard... Anyway, happy for now, my "old" disks are not slow anymore...

Well that promising. Hopefully when I try V4.52 I will be able to report back that I no longer have this problem.

[Brookes]

I too am getting the drive to slow error on 4.5 with update using NX pciE. Any ideas please. I have raid drive also. Thanks

[Stereodesign]

Welcome to the club.

[JohnnyD]

I've had this error also. But only in firewire mode, not with analog in. Try changing to S-VHS capture, then back to firewire. Usually that will stop the error, at least it did for me. I changed firewire cables and tried a new fully scanned harddrive, and sometimes I still get the error.

JD

[Stereodesign]

I went through all the combinations of input to no avail.

However, yesterday I upgraded to v4.52 on one of my edit PC's and it worked fine, I captured by firewire and composite and everything looked good and functioned smoothly.
Then in a euphoric rush I installed it on my other edit PC and that worked OK as well. So far.....
So, fingers crossed that the latest upgrade is Ok.

[mike0130]

Yes, my problem with "disk too slow" also dissapeared since I upgraded to 4.52. Great work guys! I stil have problems with titler and waiting for 4.53 or so... But this is a small problem, ver 4.52 looks stable and nice...
mike

[bhmm9999]

Here is what I have found...

I reformatted drives and still received the disk too slow error. However, I followed the advice given here and rebooted and then was able to successfully capture. Unfortunately, this seemed to be temporary fix as it continued to happen. BTW, I don't remember this problem prior to my 4.51c upgrade.

Possibly related was the fact that my power supply showed signs of stress and may have been underpowered--thus causing current issues with the raid drives. I could always capture fine on non-raid drives. GV: YOU MAY WANT TO TEST RAID VS. NON-RAID.

I have found P/S issues to be the "sleeper" of stability issues and the source of many PC problems. This can happen easily as we upgrade systems by adding more hard drives, more power hungry graphics adapters, additional external USP/Firewire peripherals, without given a second thought to the draw on the meager 650w P/S.

Soooo, I upgraded from 650w to a 750w and have not had a freeze, crash or "disk drive to slow" error in two weeks of hard use. It appears this is a software issue that GV knows about, but there might be a chance this minght be related to either Raid configs or Power Supply. I wonder if the P/S upgrade may help in some hardware configuration.

Even if it doesn't solve the disk to slow problem, a good power supply is like money and hardrive space--you can never have too much :-)

Bob