[ Post New Message | Post Reply to this One | Send Private Email to Adam Abraham | Help ]

Response to Report on MotoDV Studio 2.0

from Adam Abraham (digital@earthlink.net)
While I have had similar experiences, my conclusions or sentiments aren't quite the same as yours. Our system: Dual Processor (Pentium II 400 MHz), NT 4.0, 256 MB RAM, MotoDV Studio w/ Premiere 5.1(a), 34 GB SCSI disk array.

We have experienced the same kinds of problems editing with Premiere, and have now begun evaluating other editing packages, currently testing EditDV for Windows (beta), which appears (thus far) to be a much more stable product than Premiere.

Even when we had problems editing in Premiere (drifting audio syncs, "phantom" frames inserted between cuts, high rendering times for transition effects, etc. -- likely due in part to our unfamiliarity with the program), we had no problems capturing. The MotoDV card sends the signal to the Medea SCSIRaid system which gobbles it up without burping. No dropped frames ever.

We've had to involuntarily reformat our capture drive... twice... which was likely due to our own ignorance of the 2GB file size limitation that most systems of this type work under. It's frustrating, but also part of the risk we take for trying to save money, cut costs and do things on our own (as opposed to buying more expensive "package" systems like Avid, Media 100, etc.).

There are so many different components involved, each of which have to be "set" just a certain way in order to make the system work, it is difficult to single out one and make it the villain. I've heard good things about Canopus, but even they are dropping Ulead as their editing system, and going with Premiere. I hope that your experience with it is better.

(posted 9074 days ago)

[ Previous | Next ]