[Chris Reynolds]

to edit a shot into the timeline! 3 point editing! to fill in a gap with multipal tracks and the x key wouln’t work. to back time, to cut to miusic, to edit in graphics, etc. I have had this discustion with so many editors and most of them agree, and also claim that they almost always have to press the arrow back before marking an out.

Cheers, Chris

[Chris Reynolds]

go to next edit, snap to next edit or even type in a specific time or duration then press the o key for out and you will either chew into your next frame of the following edit or be one frame too long on the edit you are trying to make. I am not saying that anyone is inexperienced at editing. All I am saying is that 95% of the time when I mark and out in the timeline I have to back up a frame before I mark the out. I don’t see the point!! Yes it is only one extra keystroke and in one day that makes alot of extra keystrokes.

Peace, Chris

[Chris Reynolds]

“I edit more than I time.”

So do most of us editors and we would rather have the out point as an out point like it has been in the whole history of editing rather that an arrow back then out. If you like the out point to be one frame late would you also like the CTI to look at the frame before rather that the frame after.

Cheers, Chris

[Chris Reynolds]

Lightworks, Discreet Edit and Avid DS all have the out point as out and it works like a treat. If your editing all day the less keystokes the better!!

[Chris Reynolds]

It is still more key strokes. If out was just out it would save a lot of key strokes.

Cheers, Chris

[Chris Reynolds]

I know what you mean. X marks the clip but thats not always what you are after. I have had this beef with FCP and avid forever. The problem is that the mark out is one frame late. If you ever cut on any tool (with the exception of FCP or Avid) it marks the out as out. This includes decades of liner editing. I spend my life editing by pressing the back arrow every time I have to mark and out in the timeline and it has driven me crazy forever.

Chris.

[Chris Reynolds]

Hi Dave
We have a few large projects on the go 30-40mb 80min timelines with thousands of cuts and one of our project slowed down like you were saying. We found that we needed to turn off dupe detection in every sequence in the project.

Cheers Chris

[Chris Reynolds]

Thanks to all
Dupe Detection was the cause. Once turn off in every sequence throught the whole project the system is running as if is only 5 min of footage digitised.

Thanks again

Cheers, Chris

[Chris Reynolds]

Thanks Mark
I will give that a try tonight

Cheers, Chris

[Chris Reynolds]

Thanks Kevin
How short are we talking. The other long form with 50 hours in it had longer clips and it ran fine. At leased %50 of the clips are around 15min long in this project and the other %50 around 30 min each. Once all captured the first week of cutting was fine. As more of the footage has been mark and a few more select sequence have been created then the project slow down. If we capture even smaller clips (less than 15min) then aren’t we just adding more information for the project to track. I have heard rummors of people having a corrupt clip in the project that slowed everthing down. Never has happened to me so I don’t know if this can happen or not.

Cheers again, Chris