That is in invalid assumption.
As far as I can tell, opening a later version file in an earlier version software has never been supported. Not officially anyway.
Since it is a rough cut, try exporting it to an FCP XML file and then import that into CS6. It should get you part of the way there. I just tried it and there were some issues with the motion and the audio levels. But a rough cut might make it through OK.
It is a very valid assumption. Adobe has created a world in which their customers are heavily split between the CS6 version and the CC version of their products. This means that in order for continued seamless collaboration between project personel to occur, project files created in one version need to be readable and usable in the opposite version.
If this doesn't get fixed, then that means all CC subscribers who collaborate with CS6 users will be forced to also purchase and install CS6 versions of the same software, and to work on collaborative efforts entirely in the CS6 versions.
And if I, as a CC subscriber, am having to do all of my work in the CS6 versions of the products, then subscribing to the CC versions of the products is a waste of money for me.
Either Adobe fix this, or CC subscribers who collaborate with CS6 users such as myself will simply cancel the CC subscriptions and revert back to CS6.
Thank you for your thoughts on exporting to FCP XML - that isn't going to work for my needs.
Premiere has never been official downwards compatible.
The following applications support the ability to export to the CS6 version of the application:
- Flash® Professional
For Premiere Pro CC file a feature request.
Thank you for your input.
I wasn't questioning the history of application compatibility.
I'm not concerned with applications other than Premiere Pro, hence the post in the Premiere Pro forum.
I appreciate the link, but I'm not going to continue paying for a CC subscription with the hopes that some day Adobe implements such as fix. I'll simply cancel my CC subscription and revert back to CS6.
Doing this project with your collaborators in a version you all use... is a logical and seemingly obvious solution. ie. 'project planning 101'.
What you call a "fix" for your issue, (backwardly compatible) is unlikely to ever happen IMHO.
Everyone want latest versions to upgrade with new features... so accomodating those backwardly is like seeing into the future.
FWIW - cross machine collaborating is never that easy ...but why was an XML or EDL "solution" not viable for you?
It is an invalid assumption that Adobe will do that. It is certainly a valid concern, and a need for some people. However, it has never been possible. So, assuming that it ever will be is not logical.
You can put in a feature request.
all CC subscribers who collaborate with CS6 users will be forced to also purchase and install CS6 versions
There is another (and in my view, preferable) solution.
Everyone update to Premiere Pro CC. It's really is a better editing experience than CS6.
1 person found this helpful
...all CC subscribers who collaborate with CS6 users will be forced to also purchase and install CS6 versions of the same software, and to work on collaborative efforts entirely in the CS6 versions.
The CS6 versions are free to CC subscribers through a simple download.
It doesn't solve the problem, but it is the ultimate solution at this point in time.