Re: Backwards compatibility
Re: Backwards compatibility
- Subject: Re: Backwards compatibility
- From: Alex Gollner <email@hidden>
- Date: Tue, 04 Dec 2012 12:30:54 +0000
- Thread-topic: Backwards compatibility
On 04/12/2012 12:14 pm, there was a message to me that included:
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <!DOCTYPE ozxmlscene>
>>> <ozml version="5.5">
>>>
>>> <displayversion>5.0.5</displayversion>
>>
>> ...it starts with
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <!DOCTYPE ozxmlscene>
>> <ozml version="5.2">
>>
>> <displayversion>5.0.4</displayversion>
>
> I've done similar things to Motion projects for my own use, but am a little
> bit nervous doing it in a shipping product, but I guess if it's just
> metadata...
>
> So an ozml version of 5.2 will get me back to FCP 10.0.5 or will it work
> earlier?
The OZML goes back further than 10.0.5, but the version number included
might preclude earlier versions of Motion (as standalone app or withing FCP)
opening the template.
To be compatible with Final Cut Pro 10.0.4
<ozml version="5.2">
<displayversion>5.0.3</displayversion>
To be compatible with Final Cut Pro 10.0.3
<ozml version="5.2">
<displayversion>5.0.2</displayversion>
To be compatible with Final Cut Pro 10.0.2 (!)
<ozml version="5.0">
...no <displayversion>
In practice, if Apple could give the proportion of people who've updated to
each version of Final Cut Pro, that would be very useful!
Alex
..........................................................................
Film Editor, Zone 2-North West, London
@alex4d . alex4d.wordpress.com . alex4d.com . +44 775 367 7918
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden