Another unannounced 10.0.6 feature

...and I thought there weren't any more!

On my Mac version 10.0.6 can read events and projects that have been updated to work with version 10.0.7.

Before updating 10.0.6 in the middle of a project, I unmounted the disk image holding the job. I then duplicated 'Final Cut Pro.app' and moved the duplicate into a different folder and renamed it 'Final Cut Pro 10.0.6'. I then went to the Mac App Store and updated Final Cut.

When 10.0.7 first ran, it warned that it would update the events and projects that it could access.

Later, when I wanted to go back to my current project, I quit from 10.0.7, mounted the disk image and ran 10.0.6.

10.0.6 didn't have a problem reading 10.0.7 'updated' events and projects.

10.0.6 can also use effects created and modified using the newer version of Motion (5.0.6).

Cool.


@alex4d

alex4D wrote: ...… 10.0.6 didn't have a problem reading 10.0.7 'updated' events and projects. …

so, and due to its tiny size, it's more a 10.06.2 update …?

what frightens me a lil' is, what fox_m posted here about the Motion5 update
discussions.apple.com/thread/4580000?tstart=0

Karsten,

I tried to recreate Fox M's problem in 5.0.6, but all seemed well for me - 3D particles interleaving with each other and a shape in 3D....

@alex4d

alex4D wrote: .
When 10.0.7 first ran, it warned that it would update the events and projects that it could access.
@alex4d

Did not do that with my .06 Events or Projects. Maybe those were older than .06?

thanks Alex for YOUR report.

me no pro, I'm the guy with the no-budget-at-all budget, so I'm in no hurry to update or getting the latest.-

and, I'm in the midst of my habitual Xmas-year-in-review projects - I wouldn't DARE to update right now ...

looking forward for further reports dropping in ............ :lol:

Karsten Schlüter wrote:

alex4D wrote: ...… 10.0.6 didn't have a problem reading 10.0.7 'updated' events and projects. …

so, and due to its tiny size, it's more a 10.06.2 update …?

what frightens me a lil' is, what fox_m posted here about the Motion5 update
discussions.apple.com/thread/4580000?tstart=0

If you read mine and the post after mine on that thread, nothing is wrong.