Capturing as HQ and dropped frame

[Martin_Gleeson]

When I capture HDv 1440x1080i as Canopus HQ, when there is a dropped frame on the DV tape, I get the Disk Drive is Too Slow error and capture stops. I have checked the setting "Skip errors and continue capture", so I would have expected the capture to continue. Is this a bug? Is there a workaround?

Thanks

[Bluetongue]

When I capture HDv 1440x1080i as Canopus HQ, when there is a dropped frame on the DV tape, I get the Disk Drive is Too Slow error and capture stops. I have checked the setting "Skip errors and continue capture", so I would have expected the capture to continue. Is this a bug? Is there a workaround?

Thanks

If you set the following under Settings / Application Settings / Deck settings
Automatically divide files
At Timecode Break
When recorded time data changes
Edius will treat the corrupt frame as a clip end, delete the dropped frame and should continue on with capturing
Regards Barry

[Martin_Gleeson]

If you set the following under Settings / Application Settings / Deck settings
Automatically divide files
At Timecode Break
When recorded time data changes
Edius will treat the corrupt frame as a clip end, delete the dropped frame and should continue on with capturing
Regards Barry

Thanks Barry.

I have those settings you mention. I have found that they normally identify dropped frames and split the file for me when they are encountered. This works when capturing DV or M2T footage. However, when capturing HDV as Canopus HQ, the capture stops. I think that if anything interupts or "glitches" the capture when it's conventing to HQ results in the "Disk drive too slow" error. If that is the case, then it's a bug (sorry, Pat).

Martin

[GrassValley_BH]

I don't think it's a bug. The problem is, how do you properly represent a dropped frame in the converted HQ file? If we simply drop the frame, the HQ file's timecode will now be off compared to the original.

Yes, "Disk drive too slow" is not the proper message that should be displayed, but until it changes otherwise, it's the "catch-all" message for anything that stops capture, disk-related or not.

[Martin_Gleeson]

I actually do think it's a bug.

When you capture m2t files and you encounter a dropped frame(s), the capture continues. It splits the file in two and timecode resumes on the second file after the dropped frames.

It should do the same when capturing and converting to HQ. The problem here (and has been resported elsewhere), that if ANYTHING happens during captures to HQ, the capture stops. It's far too sensitive.

[Khoi Pham]

I captured to HQ always, and I have a few dropout here and there, but mine never stop capture or get "disc too slow error", I can captured an hour straight all the time.
I have a dual Zeon 3.6 with 4- 250GB Hitachi drive in raid 0 using 3ware 9550sx card.
Actually I did get destination drive too slow back when my raid are more than half full when I was using RocketRaid 1820A, but eversince I switch to 3ware card all is fine.