Anywhere, Inc. FAQs

Quartz Cron is

0 0/15 * * * ?

Effects Listed as Obsolete Require Updated Whitelist

Problem:

I am noticing there is a list of commonly used audio effects listed under Obsolete effects in Premiere 2017 11.1.0. When trying to add these effects I see a prompt that asks if I would like the new effect added in replacement of the obsolete effect. When I click "yes", there is no change and no effect is added or shows in the effects tab for the source. I tried several of these and had the same result. I also tried searching for the new effects by name and they do not show in the effects list.

If you upgrade your Adobe Anywhere system to version 3.3, and then restore a 3.2 backup, you will encounter this problem. The solution is to update the effects whitelist using the steps below.

You need to run a curl command to update the whitelist. There is no special requirement on where to run the command as long as there is curl and the whilelist.json file available and the machine you are using can access the collaboration hub. Note: Mac OS has curl bundled with the OS while windows does not. 1. Download the whitelist.json file to e.g. your download folder and then open a terminal and type (replace the <adminpassword> and the <url to your collaboration hub> with actual values): cd Downloads curl -v -u admin:theadminpassword -X PUT-F":enclosure=@anywhere_whitelist.json" http://collabhub :60138/content/ea/api/enclosures/eaenabledeffects.v1

that will update the whitelist on the server.

If your password contains certain special characters, you have to quote the username:password pair so the command would look like : curl -v -u "admin:passwordwithspecialcharacters" ...

If two editors are working on the same Adobe Anywhere cluster, usually they will have access to one anothers assets, even if they are working in different productions. The attached article in .pdf format gives two examples of how to use media assets between productions, followed bya quick description of how Anywhere handles file transfers.

As always, support for Adobe Anywhere is available at [email protected]

Create packages for deploying Adobe Creative Cloud apps.

https://helpx.adobe.com/creative-cloud/packager/creating-packages.html

Manually:

WIN:

Download .zxp from the webUI \ Extensions >> Rename .zxp to .zip >> Unzip the archive and copy the folder to:

- C:\Program Files\Adobe\[Adobe Premiere Pro CC 2015]\CEP\extensions\

Or

- C:\Program Files (x86)\Common Files\Adobe\CEP\extensions (this method will enable the panel in Prelude as well as Premiere)

MAC:

Download .zxp from webUI >> Rename .zxp to .zip >> Unzip the archive and copy the folder to: [

- Volume]/Applications/Adobe Premiere Pro CC 2015/Adobe Premiere Pro CC 2015.app/Contents/CEP/extensions

Or

Volume/Library/Application Support/Adobe/CEP(this method will enable the panel in Prelude as well as Premiere)

Using Extension Manager Command Line Tool - ExMan

Follow instructions under: https://www.adobeexchange.com/resources/28

The extension will be installed to:

WIN: C:\Program Files (x86)\Common Files\Adobe\CEP\extensions

MAC: [Volume]/Library/Application Support/Adobe/CEP/extensions

The menu item will appear under:

Window > Extensions > Anywhere Activity Feed

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"> <rdf:Description rdf:about="https://wiki.corp.adobe.com/display/EA/How+to+Add+Activities+Panel" dc:identifier="https://wiki.corp.adobe.com/display/EA/How+to+Add+Activities+Panel" dc:title="How to Add Activities Panel" trackback:ping="https://wiki.corp.adobe.com/rpc/trackback/1108968560"/> </rdf:RDF>

http://blogs.adobe.com/creativecloud/apple-quicktime-on-windows-update/

Recent security issues related to Apples QuickTime 7 on Windows have been of concern to users of Adobes products on that platform. Its always been Adobes opinion that as a company we want to provide high performance native support for as many formats as possible. Native support means that our software is able to access the media essence in a wrapper without relying on third party technology, such as QuickTime. Adobes view has been informed by an understanding of end-to-end workflows, which means that we want to be able to import / decode as many formats as possible and to export to as many industry standard formats as possible.

Today were pleased to announce that Adobe has been able to accelerate work that was already in progress to support native reading of ProRes. This new capability is fully licensed and certified by Apple, and barring any unforeseen issues during pre-release, these fixes will be included into an update to the relevant products in Creative Cloud shortly.

Additionally, we are planning on adding native export support to .mov wrapped files of DNxHD and DNxHR. This shows our commitment to the DNxHD/DNxHR codecs. This support augments our currently supported import of DNxHD and DNxHR in .mov and .mxf and native export in .mxf. Similarly, in an effort to allow as many legacy files to be supported as possible we will also be supporting the reading of AAC Audio and PNG Compressed frames and the reading/writing of Animation frames.

When these fixes are released most Windows users will have a seamless workflow for virtually all popular codecs even with QuickTime removed from the computer; however, we do anticipate that some older, less used legacy formats may not be directly supported and therefore no longer be accessible. Users may need to find a method of transcoding their legacy media.

Adobe thanks Apple for their support and timely certification of our new native technology for our Creative Cloud applications. Wed also like to thank our users for their support in helping us test our work as we have accelerated release of our native media support plans.

Background

Two security issues have emerged related to QuickTime on Windows, as a result Apple is recommending removal of QuickTime 7 for Windows: https://support.apple.com/en-us/HT201175

Adobe issued a blog post to outline status on this issue on April 16, 2016:

http://blogs.adobe.com/creativecloud/quicktime-on-windows/?segment=dva

Announcements, Motion Graphics & Animation, The Latest, Video Editing

Apple (5), QuickTime (2), Windows (3)

David McGavran

David McGavran is the Director of Engineering for Adobe Pro Audio and Video. He has been at Adobe longer than he can remember. Dave has worked on many of the video apps at Adobe and is known for his work on Dynamic Link. Unfortunately, as an engineer, Dave isn't clever enough to write a funny bio so this will have to do.

Dan McSweeney 22 minutes ago

Hi John,There are two ways to review yourproduction version history. You access it through the media browser. The first is to select your production and then click theicon at top right of that panel, thistoggles on/off the production history slider at right. The second view is to right-click your production and select production history.I think that these two screen shots will explain it further.The production activity panel is an extension add-in, it doesn't come pre-installed. My colleague, Ahmed, will follow up with those instructions later today.-Dan McSweeney

Screen Shot 2016-05-...png

Screen Shot 2016-05-...png

Here is how to installthe Anywhere Extension for Premiere Pro:1. Go to the Adobe Anywhere WEB UI -> Extensions and download the Activities extension2. Rename the downloaded .zxp file to .zip and extract the contents to a folder using your preferred unzipping tool (On OSX, the native unzipper will not work. Instead use the command line tool for unzipping i.e. unzip com.adobe.anywhere.activities.signed.zip -d ActivitiesExtension)3. Copy the extracted folder into the CEP extensions folder (see below). Create the folder if it doesn't exist already.OSX - ~/Library/Application Support/Adobe/CEP/extensions/Windows -C:\Program Files (x86)\Common Files\Adobe\CEP\extensions\Restart Premiere Pro and the extension should be available under Window->Extensions->Anywhere Activity Feed.

Hi Support,

I am trying to find the Production Activity Panel that is shown in the "03 - Client Demo" Vimeo tutorial. Does that panel still exist in CC 15?

I'm also trying to find where the Production version history is. Can you help me locate that in Premiere?

install the exact same otf package on PProclients and MSE's. Fonts need to match.

Avenir is a really good example to describe the problem and solution. The font, Avenir, is native to MacOS, but not Windows. No problem;we have lots of fonts here at Adobe.I grabbed Avenir from our server and installed it on Windows. But myMac PPro project with a title usingAvenir, whenopened on PPro Windows failed; Avenir would default to Courier, as in your video. And the reverse is true, also, moving the project back to MacOS. By digging into this, we learned (were told by the type guys) that different OS platforms have different flavors of the same fonts, and they are named differently - but slightly. On Windows, I had installed AvenirLT while the MacOS version is AvenirLT Std. Same font, but the titler sees them as different fonts.The way to get around it - and we tested this with Avenir - is to install the exact same otf package on PProclients and MSE's.

Anywhere has some limitations on the use of plugins:- plugins need to be cross platform (so they can be installed on the mercury streaming engines)- plugins need to be available on client and server side- plugins may not access any local files (since they would not be available on the streaming engine)This means that you would need to install them on every streaming engine in order to enable their support.You also need to white-list the plugin on the server. The steps how to do that can be found in the anywhere documentation in the plugins.html fileBest regards,Alexander

some components of the server not starting at all

Look in the AdobeAnywhere\server\anyhwhereserver\logs\anywhere.log

was there any particular thing in the log file that made you think of 7Zip?

Alexander Riss [8:58 AM] yes the cache complained about something ... which is absolutely odd.

the files missing are most of the time configuration files - which are at a very deep nesting level

if these are not in the folder it will lead to some components of the server not starting at all

If a client performs any edit on the timeline, this change will be propagated to the collaboration hub and finally picked up by the streaming engines. During the transition time of saving the change on the remote side, the client will instead request the raw stream of the used assets and apply effects and other compositions locally, using the local GPU/CPU as required. This also means that during that time the streaming engine will only stream unprocessed frames and not use the GPU for effects or similar.

In conclusion this means two things the client should match the minimum system requirements of the current Premiere Pro version (as if editing the remote media locally), so it is able to perform the local composition without a mayor performance impact.

On the other hand i would expect this transition period to only last seconds instead of minutes. So there might be something impacting the total performance of either the Premiere Client detecting the changes to be saved, or the Collaboration Hub persisting the changes to disk.

How many assets does your test production hold?

C:\AdobeAnywhere\server\AnywhereServer\launchpad\config\com\adobe\ea\settings\mountpoints\3c45393d-1cb2-4d78-add2-60857253a040.config