[Rob Maybury]

Thanks David,

I appreciate that I get paid to edit, but like most of us I’m just looking to be more efficient with my workflow and time. With so much footage I could do with a way of rough cutting footage from one camera, before knuckling down with the finer edits.

Its a dance show shot on three camera. Two static cameras and one which ‘hunts’ shots during the show. It’s this hunting camera which I could do with weeding out the unusable bits and was just wondering whether there is a clever, automated, way that this could be achieved in record fast time.

I guess this could be done with some clever scripting utilizing the tracking tool to monitor the position of a fixed point and once it recognizes a rapid reframe movement it slices the clip at that point and10 seconds before. Probably not going to be worth putting in the time for a job I do three times a year.

Thanks for your feedback tho – have a good day

[Rob Maybury]

Thanks Dennis.
Latest nvidia drivers updated last week and had the same issue before. I’m working mainly with Hdv footage.

I just find it really strange that I get a considerable difference in performance depending on where I click to move the play head.

I,ll take a look at the raid drive and give it a defrag but its relatively new and only about 50 percent full.

I’ve got another external raid array via e-Sata attached which isn’t really used for anything. I’ve turned off indexing on all drives too.

[Rob Maybury]

Its a strange one but try renaming your volumes. Changing the name of my drives from ‘Local Disk’ to something else worked for me.

I’d been struggling with the exact same problem for over a year on an extrernal raid array via e-sata – I could render QT to all my local drives but not that one. Every other file type was fine.

Just installed a new local raid drive and got the same problem – re-naming the array cleared it up.

Think it’s a Quicktime bug – hope it works out. Be interested to see if it clears it up for you guys..