Edius 4.5 disc too slow error message

[Stereodesign]

If your hardware worked before then it should work now. Its a code error in v4.5x that is taking time to fix.
GV can come up with any manner of inventive reasons as to why people get this error but its down to some poor code somewhere.
Edius is priced and marketed as a professional application and as such I don't think its too much to expect it to perform basic operations like video capture without errors such as this.
Until things like this are fixed (really it should never have got into a release) as soon as they occur then it will be thought of as an amateur application by video editors worldwide and never compete with FCP or Avid even though its easily as good, even better in a lot of respects than those.

[SRsupport]

You know the problem is that a few of us are trying to come up with a way to reproduce this at will.
I for example have not experienced that disk to slow error.
I know a few people who also don't have that problem and they use their systems day in and out for work.
I am not saying that the problem is not there but we are trying really hard to reproduce this among us to help with the reporting.

The strange thing is that most power users here on the board don't have this problem.
If I am not wrong Anton, StormDave, Pat, Srsupport to name a few don't see this. ( ALL NON GV PEOPLE )

If GV does not have a write up of how to reproduce it at will it will be hard to fix.
I have tried as I sometimes send Gv some emails in which I explain how to reproduce something.
But this one got me scratching my head. So many user reporting but there are many who can not reproduce it.
We tried different system configs from desktop to laptop.

Strange.

I do hope that we can find away to reproduce it at will so we can submit it as a bug. Until then I think ( could be wrong on this) it will get labeled a system specific issue.
Steve

[pjsssss]

Steve is exactly right. In order to fix something, you have to be able to reproduce it and isolete the problem. There has been much discussion over this and no one can accurately reproduce the problem.

Maybe if people that do incur it offer some more information such as more system specs it might help to find the common thread.

[3chip]

Disc Read Error

I get such a message every once in awhile. But I just go right back and select OHIC capture again and the program has always captured correctly. It's a little agrivating but something I just live with. Doesn't happen often but it does happen. Defraging drives has seemed to help for I used to get the error more often before I routinely defraged drives. I now have all scheduled for defrag routinely.

God help me in Montana, Phil

[zard]

I have a Pentium IV MSI board, 3 GB ram, P IV 3.4GHz.
Highpoint SATA Raid Card, 2220, PCI-X but put in a normal PCI slot.
(1) 2 Raptors 36GB striped as boot.
(2) 4 Seagate 160GB, 2 striped and 2 mirrored.
(3) 1 Seagate 300GB, non raid.
(4) CDRW and DVDRW to mobo primary IDE.

Captured to (2) striped setup and (3), same problem of hard disk too slow. Even with an empty hard disk (3), the problem exist.

I even tried last night to pull out (2) mirrored set and (4) to reduce any concerns of power supply but still, the same problem exist.

Previously, I was using PIV 2.8GHz and 1 GB ram with the same drives. After upgrading to PIV 3.4GHz and adding 2 more sticks of 1GB ram, I was able to capture. The only difference was the tape I used was different between then and now.

One more thing left that I can try, is to plug in a IDE drive to secondary IDE of mobo. Just RMAed a 80GB WD hard drive last week. Once I get it back, I'll try it.

[Stereodesign]

Steve is exactly right. In order to fix something, you have to be able to reproduce it and isolate the problem. There has been much discussion over this and no one can accurately reproduce the problem.

I'm quite aware of this but postings here have been very detailed in their descriptions of the error, its circumstances and the PC spec.
I realise that applications like Edius have millions of lines of code but there is a starting point, the error did not occur in versions prior to v4.5x so its something that has been added/altered since.
I'd like to be able to set Edius capturing then go and do something else then return to find it waiting for me to name the clip, not finding that "disk too slow" occurred 2 minutes after I left the room. When this error happens frequently its a real waste of time, and if you have client with you and you have to capture and you get this error its rather embarassing to say the least!

[JPowell]

Yep, it's hard to pin down the common thread for this error message. I can say for sure I never saw it before 4.51c. Haven't seen it yet in 4.54, having done several long captures from tape with scene detection turned on successfully. But with a thread view of over 2000, I'm thinking the error is being seen quite a bit still...

In the meantime, how about an option to simply "report" the disk too slow error after the fact, rather than halting the capture?

It's hard to tell if there is really a problem if Edius won't just close out the file and let us examine it for dropped frames after capture.

[pjsssss]

Your post made me think Jason (a rarity some days). Under SETTINGS > DECK SETTINGS, how many of you that are having this problem have the "skip errors and continue capture" checked?

[muleferg]

Thanks for reminding me. I tried to capture some old dv footage today and was having the same error msg after upgrading to 4.52. so I change the deck set and it ok dokey.
Mule

[Stereodesign]

with me its doesn't matter if "skip errors and continue capture" is checked or not it still occurs.
Sometimes when I get the error I can just click on the timeline, play a few seconds of video and than start the capture again, other times (yesterday) Edius stops responding to the extent that Task Manager was not showing Edius as running under Applications, but the Processes tab showed Edius still running. Trying to end the Process failed repeatedly and I had to re-start Windows to get Edius to run.

[SimonD]

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

[Stereodesign]

Very interesting, I far as I'm aware you are the first person who is able to re-create the error.
I've tried but frustatingly the same footage that caused the error re-captured perfectly after a reset.

Would you be willing to make this footage available to others (inc GV) to see if it does the same for us?

[GrassValley_KH]

If it's within reason (size wise), I might be able to arrange some temporary FTP space..

[SimonD]

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

[GrassValley_KH]

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