Andy Edwards
Forum Replies Created
-
Yes, you can keep CC2015 version and CC2017 version on the same machine. You most likely didn’t use the “advanced” menu where you tell the CC desktop application to “not” remove your older version when installing apps. In the advanced menu, if you uncheck the box when you are installing the newer version it will keep the older version. This is only good on major version releases like CC2015 or CC2017. If Adobe releases a “patch” for a specific version, i.e. CC2017 .02 upgrading to CC2017.1, you cannot keep the older .02 version on the same machine. You can keep CC2015 & CC2017 version separate on your machine, but remember CC2015 has various bugs that were patched or fixed in CC2017. Some plug ins that were good on CC2015 have to be updated if you want to move to CC2017.
You can read more about upgrading your Adobe apps here:
https://helpx.adobe.com/creative-cloud/help/download-install-app.html#topic-3
Make sure to read the Not in Step 3 of Install previous versions of apps. This explains how to use the advanced menu to keep older versions.Advanced option instructions
https://blogs.adobe.com/adobecare/2015/06/15/creative-cloud-delivering-more-choice-for-installations/Additional info to consider here:
https://blogs.adobe.com/creativecloud/keeping-previous-versions-installed-when-installing-cc-2015-applications/Newer projects created in CC2017 are not backwards compatible to CC2015. So once you move forward with your project, you are stuck using that version unless you make an XML and import it into the older project. Also remember Lumetri effects used in one version or the other will act differently and you will see differences in your color correction.
Andy Edwards
-
Known issue over the past couple of Premiere releases with Wacom drivers. Just depends on what OS you are using with Premiere and what Wacom Drivers. If you are on Sierra, you might try the V21 drivers as I have seen posts elsewhere talking about that combo working.
Andy Edwards
-
Unless you can get an XML out of the corrupt project, you will be stuck upgrading to the newer version of Premiere you had on the other machine. Projects are not backwards compatible when a new version is released.
-
Have you tried creating a new project and importing your old project through the media browser?
Andy Edwards
-
Watch the 2 parts of these proxy tutorials:
https://www.dylanosborn.com/training/done-with-dylan/When you work with the proxy workflow from inside Premiere, you are given some basic presets that Adobe provides. You can always add your custom ingest presets you create inside Media Encoder. Once you have created your encoder preset and Ingest preset in Media Encoder, right click on the presets and reveal them in your system folder. Take note of the location so you can add them to the “Add Ingest Preset” when you are back inside Premiere. If you are using multiple systems to edit with, copy those presets into a folder you can then path to when you use the “Add Ingest Preset” option.
Audio channels are very important when dealing with the proxy workflow, so make sure you create your custom encode preset to have the proper amount of channels of audio you have in your media. If you don’t, you will get errors from premiere when trying to attach master media to proxies.
Andy Edwards
-
Did you try syncing with the audio sync tools built into Premiere? Use the multicam workflow and and sync your audio to your video clips. If you updated to the latest Premiere, the Adobe Extension Manager was deprecated 2 versions ago, so it cannot be used to load plugins the old way. Plural eyes 4.1 or above is needed to work with CC2017 version of Premiere.
Did you move your original media to another drive at any time? The danger stripes on your clips can be dealt with by taking your media offline and reconnecting it again. Test this option in a new project and bring your old sequence in through the media browser, not the import menu.
Andy Edwards
-
How about applying watch folders to your workflow instead of queuing multiple presets? You can apply multiple presets to a watch folder. Have the original comp render out to a watch folder and AME will pick it up and auto export your additional presets.
Andy Edwards
-
Greg,
Thanks for all the answers. I’d recommend bringing this issue to the Enterprise forums as you get unlimited Adobe support there as a Enterprise customer. There have been so many tweaks done to OS Sierra, Adobe might not have tested it in your type of network user configuration. From SIP and SMB changes alone in El Capitan, they could have tweaked Sierra to work differently from your last deployment.
Post back if you get anywhere as I might be going down a similar path with our users.
Andy
-
Jason, what Premiere version are you using?
Can you try the same steps but in a default workspace (Editing) vs. a custom workspace. See if that keeps the audio track names. Also, you are not using any custom track presets by chance?
Andy Edwards
-
Only issue with reimporting the old LUTS is they are no longer fully supported by newer versions of Premiere and AME. With all the changes made to the Lumetri engine in the past 3 versions of Premiere, you could be introducing issues to your footage when exporting. So use the old LUTs at your own risk.
Andy Edwards