Edius 4.5 disc too slow error message

[Stereodesign]

When capturing from DV in v4.5 I get the error meassge "disc too slow" and capture stops. Edius then has to be re-started before it will respond properly.
The target disc is a 300Gb RAID 0 array so I can't see it being too slow.
Any ideas or is this a known v4.5 bug with a workaround?

[antonsvideo]

are you using capture hardware like NX or do you use OHCI card capture?

the disk should be fine, especially Raid0

you can always test the disk with a free utility called diskspeed fro www.roadkil.net

[Stereodesign]

I have the NX PCIe card and used the Firewire input on that.

I have two near identical PC's (one has the NX HD expansion card the other doesn't) and this has happened on both when I installed v4.5.
I've rolled then both back to v4.23 and they capture fine now.

[DENHAM]

Disc to slow message

Hi I also have this problem since updating to 4.51! Any other ideas? also the defualt renderer always come up as HQ codec? change it back to dv but does not always solve the problem...

[editpoint]

I get the same problem only since upgrading to 4.51
Using NX card.

[Rusty]

Have you tried capture without file division?
Sometimes Edius needs to be reminded that there is no problem. (the proverbial pants kick)

Rusty

[Hitecrd]

When capturing from DV in v4.5 I get the error meassge "disc too slow" and capture stops. Edius then has to be re-started before it will respond properly.
The target disc is a 300Gb RAID 0 array so I can't see it being too slow.
Any ideas or is this a known v4.5 bug with a workaround?

I have this problem as well. Was capturing from NX Bay Composite-S from a VHS tape when the record window froze and the player window was sort of flickering. Error message was "drive too slow". Edius appeared to be locked up. Rebooted and it seemed to work. I was capturing to a 250Gb SATA drive of which almost all of the space was free. This started happening with upgrade to 4.51c.

[skier-hughes]

I've had this a couple of times when starting capture. Turning off edius and restarting it has sorted it both times. I also have a raid 0 set up.

[mike0130]

I have NX Epress and had same problem. I thought this came after I updated BIAS for motherboard... I rolled back to previous BIOS and... well I am not sure right now...
Just in case- motherboard P5B Deluxe, QUAD core Extreme, NX Exopress, RAID 0.
mike

[Stereodesign]

I spoke to the UK Edius importer (Holdan) who said they had not heard of this happening before and asked me to send a detailed email to them so their expert could take a look at the problem (he was away at a show when I 'phoned) which I sent straight away.
I recieved an email asking for yet more details fairly quickly, but nothing since and its been 10 days.
I know it sounds bad but I'm glad others have had this happen to them as it means when Tech support say its an isolated problem I can set them right.
If Holden come back with a solution then i'll post it here ASAP

[mattmatt]

Just for the record, me too. (since 4.51c) No nx board, just OHCI firewire on Sata drive.

[RonnieMartin]

I know this probably sounds stupid but the only time this has happened to me is when my raid needed defraging.

I have found that both my machines that are running raids need defraging more often that when usng a single drive for capture.

Ronnie

[PaulTV]

Before 4.51c, my buffer was always showing 2/3 during HDV capture via NX converting to HQ on the fly.

Now with 4.51c the buffer shows 0/1 - mostly zero. This to a clean 1.2Tb raid 0 sata array.

I've had repeated crash/freezes during capture since upgrading to 4.51c I guess we're all just putting up with this issue, as Edius becomes less and less robust with each "upgrade" For what it's worth, I think Edius was solid because it was simple, now it's just catching up and getting more and more wobbly with each release. Personally I don't think we'll ever see a rock solid version again.

[mike0130]

probably sounds stupid but the only time this has happened to me is when my raid needed defraging.

Not stupid at all. This is the first thing I did when I got a message about "destination disk is slow"- I defragmented the disk (RAID-0). But it did not help. I never had this message before 4.5 (or 4.51c). I thought that was a hardware problem (NX-Express), bad BIOS (I do updates regulary) or someting else. But looks like I am not alone here...

[tuyle]

I got 2 to 4 the "disk is slow" msgs for 60 min to 120min video. I tried on 320GB or 500GB or RAID0 (2x500GB) all Sata II or eSATA (happened more than internal drives). The source: DVCAM with NX card - 4.51c software.
Whatever reason, only happened with capture. It never happened with previous software, however I like 4.51c for other things.