Andy Edwards
Forum Replies Created
-
Saw your other thread in the adobe forums dated in February. Interesting you have not found any fixes in 2 months.
Have you asked the same question on either apple.stackexchange.com or stackoverflow.com website?
Are your network user permissions for library/application support/adobe folder set up for Read & Write to all your users? If you have a network group for your users you can add it in the sharing permissions window.
Are you accessing your networked macs with Jumbo frames enabled in Network settings? I’ve run into issues where systems with Jumbo frames enabled had problems authenticating with Creative Cloud services.
Andy
-
Greg,
Are you an Adobe Enterprise user? Or plain Adobe CC accounts? Are you using Apple School Manager to set up your accounts since you are in a academic environment? Have you tried testing your set up with the new 5.3 Sierra server software? Were the Sierra network accounts set up fresh or just a software upgrade from El Capitan?
Do you have your firewall configurations for your network users set up properly? All CC accounts need to have a connection to Adobe servers for authentication of the accounts when first set up.
Here is a detailed list of sites you can white list for the accounts: https://helpx.adobe.com/content/dam/help/attachments/Creative_Cloud_for_enterprise_Service_Endpoints.pdfAdditional Enterprise CC set up PDF’s
https://www.adobe.com/devnet/creativesuite/enterprisedeployment.htmlWe had nothing but problems with network accounts and work via AD log in or local account instead. I recently installed a Sierra server for backing up our edit systems, so I’m new to Sierra’s server potential issues. Looking forward to following this to learn something as well. Adobe will be pushing Mac users to Sierra in the future since they only support 2 OS’s back with current CC app versions.
Andy Edwards
-
Which of the 3 codecs is your footage you are having an issue with?
What is your sequence settings set to?
Did you render anything in that area of the clip going black?
Did you try and purge your media cache for the render if you did?
Any plugins applied to the clip in question?
Any rogue keyframes in the clip in question?
Have you tried creating a new project and importing your problem multicam sequence through the media browser?
Which exact version of CC2017?Andy Edwards
-
Mike,
Did anything get it working again?
Andy
-
Nope, that was the previous version. Today’s release moves it to 2017.1 v11.0, Tanq
-
The LUTS are applied in the Lumetri Panel and not through an Adjustment layer?
Andy
-
Found an old adobe post talking about copying the LUTS to the AME technical folder you might be able to try.
https://forums.adobe.com/thread/2178493
Be careful doing this as some older LUTS are not supported and this could hose your system and cause export errors with your footage.If your LUTS are from an older version of the software this could be the problem with the AME export. I saw this with one of our shows and we had to dig into the Lumetri panel and make sure no old LUTS were applied. Try creating a new test project and import one piece of media you used with your old LUT. Apply one of the new Lumetri LUTS and see if you can Queue it to AME and retain the look once exported. If that works, it could mean your older LUTs are not supported. Regarding Miller’s LUTS, find out from him if his LUT’s are updated to work with the latest version of Premiere.
To see the new update go to your CC desktop app and log out. Log back in and see if the CC desktop app requires an update to the new version and then it should offer you the new application updates. Don’t dive into this new version if you are in the middle of a project. Finish the project and plan for the upgrade so you start fresh.
Here is the Adobe Blog showing all the new features:
https://blogs.adobe.com/creativecloud/dva/Andy
-
Are these custom LUTS or ones you chose from the previous versions of Premiere?
Did you upgrade to today’s new release?
Andy
-
Mike,
Where are you storing the LUTS? Are they local to your machine or in a shared folder like dropbox? I’ve seen issues where any “Cloud” based storage cannot be read by AME to apply the LUT. If they are located in the cloud, move them to a local folder and re-apply the LUT so both programs can see it.
Adobe removed a bunch of the older LUTS when they made the push from Speed Grade to the Lumetri Panel. Some of the older LUTS did not get ported to the new versions of Premiere and should not be used with new version of Premiere. They will play back in Premiere, but AME has a hard time reading these older versions and will not apply it to the footage when exporting via Queueing in AME.
In your AME prefs check to make sure you have “import sequences natively” box checked.
Andy Edwards
-
Thanks for the OS confirmation.
LTO tape jams, reliability to stay connected to our MAM system, needs a lot of rebooting to clear the issues.