destination disk too slow

[PaulTV]

Just to say that since updating to 4.61, I now get this error - never occured in previous versions - all defragged - raid 0 - clean drives etc etc etc.

I hope this gets fixed in the next version.

Paul

[Stereodesign]

....you never know......

[pjsssss]

I don't know...it's been a tough one to pin down.

[DigitalDave]

Join the club- but the GOOD NEWS is that there is a Club members T-Shirt coming out soon.
On a serious note, it would seem that using any other SW to capture with will work - DO NOT take any notice of some posts suggesting - anything from Re-Booting, Reformatting to castration. All twaddle and extremely (however well meaning) unhelpful. It is NOT your system or your drives. It would seem that GV engineers have not managed to find out what got broke for the very reason that Pat mentioned. I now only capture on E3.6 but I have Caddies on multi systems. For guys with single systems and raids, it is a real bummer.

DD

[PaulTV]

Thanks for the cool reply's - just got back from the beach - I guess I can deal with this one 'till it gets fixed - AE3 and VST ?? mmmm

Paul

[RonnieMartin]

I knew there was a reason why I had not gone up to 4.61. I am always behind at least one version when I am busy if it is running smoothly. It is when I get caught up on my projects that I try only one machine up to the next update. If it takes the next project without a problem then I bring the other machines up to the latest and greatest.

Even my socks say Edius\GV

Ronnie

[PaulTV]

I kinda needed to update as the import of EX1 files is so much easier with 4.61 - but I really know what you mean - except for clip browser 2, doh!

Paul

[antonsvideo]

can you try a test capture with waveform generation unticked

[DigitalDave]

Anton, where is the option to turn off waveform generation during capture. I cant seem to find it.

DD

[antonsvideo]

Hi DD

your not alone, I can't find it either

I could swear that we had this option

[Stereodesign]

It would seem that GV engineers have not managed to find out what got broke for the very reason that Pat mentioned

Hmmm..... that really gives me confidence in their application.......

[PaulTV]

I get that same feeling over the VST bridge - here we are about to enter V5 and it's still broken -why? Every other application has VST's that work. Version 1 of Speed Edit has, version 6 of FCP has, Vegas has, Avid, Premiere.. I think Lego Studio too!

There does appear to be a divide between the guys that write the code and the people that use the application with Edius - the "Disk too Slow" error could and should be fixed with a quick patch - likewise the VST thing, likewise the After Effects errors - not to mention keyframes - I SAID DON'T MENTION KEYFRAMES.

OK, I guess this thread will now be closed.

Paul

[pjsssss]

Of course the basic premise for creating a patch is that you have identified the root cause of the problem. AFAIK that root cause problem for the disc too slow has not been identified. Believe me, I know a lot of people here on the forum that have put in a lot of time trying to isolate it and so far there is no real common denominator.

I get very frustrated at GV with some things but to be fair, a lot of the people that are working on Edius are not the ones that originally coded the project. From an engineer's view, there is nothing worse than trying to work on someone else's code.

[redgum]

I get very frustrated at GV with some things but to be fair, a lot of the people that are working on Edius are not the ones that originally coded the project. From an engineer's view, there is nothing worse than trying to work on someone else's code.

True, but that's why coders get paid big money and clients pay big money for their product.

[PaulTV]

Maybe its time for "Edius Pro HD" and a new codebase - a la Premiere Pro.

Paul