I completely understand that newer features would not be supported but if you can do the loop da loop you describe then it sounds like it's more metadata flags in the project that trigger Adobe to deny access to earlier versions. I realize they update code but this is very similar to when Avid use to prohibit the user from installing Avid on an unqualified OS. Granted opening that up can lead to quirky problems but at least you have a chance to see if it will work. I would prefer Adobe let me open up newer projects with a warning that issues may occur. Obviously Adobe's intent is to force migration and earn more money not to do what is in the user's best interest.
---In avid-l2@yahoogroups.com, <jeff@...> wrote :
------------------
Jeff Hedberg
Union Editorial
575 Broadway,6th floor
New York, NY 10012
On Jul 21, 2015, at 10:09 AM, Wilson Chao wilsonchao@... [Avid-L2] <Avid-L2@yahoogroups.com> wrote:Oliver, does that also apply to AE? John asked about AE, not Premiere.On Tue, Jul 21, 2015 at 8:52 AM, oliverpeters@... [Avid-L2] <Avid-L2@yahoogroups.com> wrote:There is no backwards compatibility with Premiere Pro CC. Your option is to rent the software for a month or more in order to complete the project. Or you can rent annually.
Oliver
Posted by: bigfish@pacbell.net
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (8) |
No comments:
Post a Comment