Copy link to clipboard
Copied
And past 2015.xxx projects?
Thanks all
Copy link to clipboard
Copied
Hi Roger,
Premiere Pro CC 2017 is compatible with Windows 10. To my Knowledge, there are no Windows 10 specific known issues with Premiere Pro CC 2017 version.
Thanks,
Vidya Sagar.
Copy link to clipboard
Copied
As to projects from earlier versions ... Best Practice is to keep in their current version until finished. Start new projects in the new version. As versions with different build numbers can 'live' together on a machine.
For example ...
2017 ... build 11.x
2015.3/4 ... build 10.x
2015.0/1/2 ... build 9.x
2014.1/2 ... build 9.x
If you use the other "DVA's" (digital video/audio applications) you need to have the 'matched' versions, and that can be sort of fun, as they don't have matched numberings.
On my new machine, I won't be loading 2014.2, as I've finally completed everything I'd need use that for.
I do have 2015.2, 2015.4, and 2017 'loaded' and in use for their appropriate projects.
When it is necessary to upgrade an in-process project, I highly suggest creating a new project in the newer PrPro version, then using Media Browser to navigate to the project file you wish to use in the new version, and importing that into the new project. It seems to have fewer issues this way.
Neil
Copy link to clipboard
Copied
There are a few issues I've encountered, but nothing work stopping. Some effects have their parameters mislabled, but they still work. The Soften parameter of the Ultra Key effect will crash the display driver every time, but you can still key in After Effects. The DeHummer audio effect won't export properly through AME, but works fine using Export instead of Queue.