Disc Too Slow Error - Not Enough RAM?

[Bluetongue]

I too cannot even capture a few frames of HDV using the HQ Codec. I've been able to capture native m2t fine, but I get the Destination Disc too slow error message about 2 seconds after starting starting capture using HQ.

Perhaps I'm not doing something right, as I just ventured into HDV land.

My system is a P4 3.0G hyperthread processor, 2 GIGS of memory and a G-Raid Raid 0 SATA array for the media. I have a Storm card installed, but I'm using OHCI to capture the HDV. Granted, I can capture m2t and then convert in the bin, but I'd prefer the one step process.

Sony Vegas can capture both modes fine, however when I bring the 24P captured in Vegas to the Edius timeline, I get field order problems which manifest themselves as jerky motion, and Edius says they are upper field first, rather than progressive. Changing the designator to progressive does not help.

Downsampling HDV to standard def is another story for another time.

Tom

Tom
First a 3G P4 is just a tad too slow for capture to HQ needs to be at least a 3.2 G with 800mhz bus

So far as 24P is concerned the jerkiness is also my dislike of this format so do not use it, but if someone can show me how to do it without then I will look at it again. Perhaps it is my cameras but I am not going to rush out and change just to go "P"

Down sampling to SD for DVD etc you will need Procoder to be able to get good results as a number of filters need to be added to get the results, there are a number of threads on how to do this
Hope this helps
Regards Barry

[mike0130]

Yes, I have this again with ver 4.6 on DV NTSC footage capture! I changed ny RAID 0 hard drives without any improvement. I captured 1 tape and got this error on the second one... Rebooted and captured the second tape.

We reported about this problem A FEW MONTHS BEFORE ver 4.6 reliese, wright? Than we waited for few months and got the same 4.5 with some minor changes... And you know what? I did not ask for AVCHD support, to say the truth, I do not care about this AVCHD, but I want to capture from my old DV Sony PD170 without errors! Is it too much? Is it not why I paid you for this software? This is exactly what we asked GV and you can see what we got...
Dear Green Valley guys!
Can we ask to have a "bug free" version of Edius without any feature "improvements"? Just make it work, please...
Thank you.

[GrassValley_KH]

Humor me - in the Canopus HQ Codec settings, switch to custom and reduce the Quantisation and Max size parameters and try again - does it drop out still? If so, is it dropping out sooner or later than previously?

[plasma_video]

Sorry about so many new to HDV questions, but I wonder if this is normal, or a symptom of the problem.

When I hook the camera up to a 1394 port and open capture in EDIUS, there is about a 2 second lag between a camera movement and when the overlay display updates. I bet this is telling me something, but I wonder if that is what anyone else sees.

Kennealy, to answer your question, making the custom settings change has no effect. Not a single frame captured yet (to HQ).

Also, for clarification, under Hardware HDV and Generic OHCI settings/Video Overlay, which is preferred, Direct Draw or Direct 3D9? Seems to make no apparent difference on this system.

Also, disabling Storm in device manager did not help either, nor disabling the 1394 port in my Audigy card.

Tom

[gdame]

I have been following the comments and complaints regarding this disk to slow error and I actually had to deal with it last week.

I believe that it is a good olé conflict or collision of traffic on the mainboards bus system. One of my clients has a fairly high end Velocity Q system at his home and a new NX system at his office. He loves his new quad core NX and wanted to be able to bring a project home once in a while. Should be no problem as long as OHCI mode is fine when at home. Well installed the same version of Edius (4.54) Pro and bang! Disk To Slow! That was to an U320 SCSI Raid!! After hours of searching for the problem, it turned out to be a conflict in the audio card that was in use for Edius. You see the Velocity Quattrus hardware is the windows audio card. When I disabled it in device manager and enabled the built-in audio on in the mainboards bios then all was well. So we had to do this audio card disable/enable switch depending on which editing product was going to be used.

So first question I would ask is "are you using a GV certified mainboard?" if not why? Secondly, if in fact you are using a recommended configuration and things where great with Edius 3.x then my question to GV is "Are things regarding audio handling and video handling different in these newer 4.5 and up versions of Edius?" The system resource needs may be completely different with the new versions. This happened with Velocity a while back as well and it was the audio that caused a whole lotta grief. But is the end we got it working and then stayed with that recipe.

So, hard drives and there cache memory are not where I would be looking. But I would definitely be looking at all the cards and there respective slots and the resources that are being allocated to each.

[pjsssss]

Yes, it might be a very good question ot ones that run into this problem...Are you using onboard sound or a sound card?

[tingsern]

We can post this into the sticky "10 things to try if you get "DISK TOO SLOW"" ...

[Bill Martz]

Hello to all

I have used edius from the very beginning. The reason for using edius was primarily for the professional codecs that Hiro seemed to acquire long before the other editing software companies. I never had a "disk to slow error" till Grass Valley came into the picture. I was editing dvc pro50 at the time and was using a HP XW8400. I went back and forth with tech support for 4 months to try and resolve the problem. To be honest, they either don't have a clue as to what is causing the problem or they don't want to make the problem know to the public. I decided to remove the edius board from the workstation. Guess what. The disk to slow error went away. I could capture thru firewire with no problems with out the edius board in the machine. Tech support told me that I probably had a defective edius board. I sent the board to them to have it repaired. When I got the board back with a note from tech support, the note said that they replaced some faulty firewire components on the board and that now it was as good as new. I first checked the board for re-work but couldn't find any. That was disapointing. I installed the board and again I got the "disk to slow" message. The bottom line is, edius tech support doesn't have the knowledge to correct hardware or firmware problems. They appear to be grasping at straws. The problem is with Grass Valley's hardware and firmware, not with a certified end users machine. Remember, I spent 4 months trying to rectify this problem with Grass Valley at the cost of losing valuble editing time. I then jumped ship to Premiere CS3 along with Matrox Axio and never looked back. Sorry but I don't like to be treated like a child.

[gdame]

Hello to all

I have used edius from the very beginning. The reason for using edius was primarily for the professional codecs that Hiro seemed to acquire long before the other editing software companies. I never had a "disk to slow error" till Grass Valley came into the picture. I was editing dvc pro50 at the time and was using a HP XW8400. I went back and forth with tech support for 4 months to try and resolve the problem. To be honest, they either don't have a clue as to what is causing the problem or they don't want to make the problem know to the public. I decided to remove the edius board from the workstation. Guess what. The disk to slow error went away. I could capture thru firewire with no problems with out the edius board in the machine. Tech support told me that I probably had a defective edius board. I sent the board to them to have it repaired. When I got the board back with a note from tech support, the note said that they replaced some faulty firewire components on the board and that now it was as good as new. I first checked the board for re-work but couldn't find any. That was disapointing. I installed the board and again I got the "disk to slow" message. The bottom line is, edius tech support doesn't have the knowledge to correct hardware or firmware problems. They appear to be grasping at straws. The problem is with Grass Valley's hardware and firmware, not with a certified end users machine. Remember, I spent 4 months trying to rectify this problem with Grass Valley at the cost of losing valuble editing time. I then jumped ship to Premiere CS3 along with Matrox Axio and never looked back. Sorry but I don't like to be treated like a child.

Bill, I see your from the Northeast. I am also, in Massachusetts. Where are you located? I would not mind trying to resolve the problem with NX in your HP XW8400.

[gdame]

Yes, it might be a very good question ot ones that run into this problem...Are you using onboard sound or a sound card?

Pat, was that question for me?

Onboard sound when in Edius OHCI mode. That mainboard was an Asus P4C800-E Deluxe with a 3.2 P4, 2GB RAM. Remember this main board is before PCIe! It also has AGP.

I would like to find a new PCIe based system with this problem and is using an NX card. Maybe we could put this problem to rest soon.

[pjsssss]

Hi George. It was really an open ended question for everyone that has the problem. I am always looking for that commonality

[Bill Martz]

Hello George

"Bill, I see your from the Northeast. I am also, in Massachusetts. Where are you located? I would not mind trying to resolve the problem with NX in your HP XW8400."

I live in Manchester, NH. My phone number is 603.622.2800. The only interest I currently have with the Grass Valley products is that they are the only software vendor that has the avc-intra codec available. As I said previously, Hiro must be a brother of Mr. Sony and Mr. Panasonic as he always gets the codecs first.

[Imagine Video]

disk too slow............

I have 2 systems

1 As my sig at the bottom with NXe this is a Gdame inspired setup and it works without error up to now NO disk to slow.

2 system is a single core p4 3.8 ghz chip machine with 2 gig ddr2800 OCZ platinum memory. I can induce the disk too slow by crancking up the quality on the HQ avi capture from 1440 x 1080i HDV from Sony Z1 iF I USE ONLINE FINE the processor is running at 85 - 95% and if it peaks over 95 I will get the disk too slow error and capture stops. Drop down to online standard and the processor runs at 75 - 85% and no problem even from 1440 x 1080i to HQ to a single SATA 2 drive.

Cath

[mike0130]

I have this error from time to time capturing ONLY DV with CanopusDV codec. Not the HQ! I believe gdame is right about conflict in bus. The only things I want to know
1 Motherboard chipset?
2 Raid and it's chipset? Does it work without RAID?
3 What about software- only? No complains?
4 Size of monitors windows in the time of capture?
And why there is a dead silence from Canopus support? I wonder if any customers will care about new camcorders to work with Edius if they will not be able to capture without errors?

[COMPLETE VIDEO IMAGE]

Disc Too Slow Error

The latest I hear from GV is that it appears to have something to do with the extra realtime that they're trying to tweak out of the system and are working at remeding the situation. Would have been nice to know before I spent $1000.

Ted