| I agree with both of you - but for another reason. What bugs me more is the fact that these projects still keep obsolete file paths. So you can rename an event in FCPX -- in this case all projects related to this event (regardless of active or not active) should be changed. Even the event file keeps the wrong paths. While it works mostly seamless - cause of some internal routines of FCPX - it's a "sleeping bug". On Sep 9, 2013, at 4:22 PM, John F. Whitehead wrote: This bugs me too. I wish you could lock projects to keep this from happening. Time for us to file feature requests I guess…
On Sep 6, 2013, at 11:52 AM, Jon Chappell < email@hidden> wrote: When FCPX is open it will periodically write to projects that are not currently open. I don't like this because it unnecessarily increases the chances of corruption and it means that I cannot rely on the Modified Date being accurate for any project or event. The latter is important for current and future products.
Is there a particular reason for this?
|