[Ladislav Zamba]

Bill and all guys here,

I appreciate your answers. I work with high speed RAIDS. This USB2 experience was extreme a occasioanal case.

As old SQL database developer I’m aware of not optimal programming. For example not optimal SELECTs work fine with small databases on speed hardware, but with thousands of gigabytes of data such SELECTs are weak. And if thousands of users run such SELECTs at same time, servers are in trouble then.

My USB2 experience tells me that something can be made better.

Do you remember problem with doubling project file size when compound clip was made? Apple fixed it.
So, I believe that FCPX developers can avoid some unnecessary disk activity and make editing on slow drives and machines faster.

[Ladislav Zamba]

No, it’s not going to sleep.

[Ladislav Zamba]

I understand you, but my example:

Timeline has displayed all waveforms, disk is quiet. Then I trim last clip by one frame from right. Disk is working 15 seconds and then it is quiet again. Then I trim same clip by one frame again and disk is working another 15 seconds. I don’t think that it is optimal behaviour and I don’t understand reason for this disk activity.

Remember – disk contains media clips only. No project or event files.

[Ladislav Zamba]

Yes, it’s my case.

But why it is so? Why it is accessing all clips? What is it checking? If they still exist? Alter every edit?
If I append new clip to the end of timeline how does it affect existing clips on timeline?

I hope taht FCPX developers read this thread and make some little change 🙂
I want to help make FCPX even better.

[Ladislav Zamba]

Why optimize when my timeline is ProRes422 and media files are too?

Why is FCPX so heavily accessing all media files with every edit?

It’s not problem to buy thunderbolt external RAID. But what if I will have 30 hours timeline with 5000 clips?

All I ask is to optimize this step. I think that FCPX is doing something unnecessarily.

[Ladislav Zamba]

USB2

[Ladislav Zamba]

I mean same as it is with TextEdit in Lion. Read about it for example here https://www.tuaw.com/2011/07/20/os-x-lion-auto-save-and-versions-to-the-rescue/

But I found one tool from Digital Rebellion – Pro Versioner 2.0 – seems like working solution. I’m testing trial version.

[Ladislav Zamba]

Thank you Oliver,

I was fighting with it today for four hours.

I was absolutely unable open FCPX in Project Library when broken project was in FCP Projects folder. FCPX was rebuilding thumbnail views and it crashed it always.
Backup project was not working too.

Once it opened Project Library, so I duplicated broken project three times with different options, but it didn’t help. Duplicates were broken too.

Then I moved broken project away from FCP Projects folder and made fake empty project with same name and opened it. Then I closed FCPX and replaced fake project with broken one.
FCPX opened and after few seconds was crashing again, but randomly. At last it stayed opened, so I exported timeline and I’m happy now.

It was really nightmare 🙂 Now I have to set TimeMachine and be very careful in the future.