What are the recommended quality settings for editing proxies?

The editing proxies that are downloaded & imported by the Skies Adobe panel are based on the standard streaming proxies which Strawberry creates on a continuous basis. The better the visual quality of the streaming proxies, the better the visual quality of the editing proxies. Visual watermarking helps to distinguish editing proxies from HighRes media and signals the editors that they are working off of proxies. If you are already using visual watermarking within Strawberry, you may keep your current settings unchanged. Alternatively, you can create and upload your own watermark or use our template instead.

We recommended configuring proxy files to the Same as Source preset. Editing proxies created under this preset will always have the same resolution as their high-resolution counterparts, which simplifies conforming workflows.

How do I prepare existing proxies for remote editing? Do they need to be re-encoded?

In order to get your existing proxies ready for remote editing, you will need to update their structure version. If your proxies have been created with Strawberry 5.4 or newer, then this process does not require any re-encoding. Proxy files created with Strawberry versions older than 5.4 only require full re-encoding if they have more than 1 audio track. Editing proxies can not be created from archived assets.

How are audio and image files handled in an editing proxy workflow?

If a user imports audio or image files via the Skies panel, these files will be imported “as they are” and without any conversion. An editing proxy is not created for these file types.

Can remote editors use local media in their projects?

For our remote editing workflow, local media is defined as media that has not been imported into the Premiere project via the Skies Adobe panel extension but from another location (e.g. media downloaded from a stock website). If editors use such media in their projects and upload the projects back to the on-premise system via the Skies panel, then they can choose which local media files they want to upload in the process.

Can archived assets be used as editing proxies?

Working with editing proxies which source files are are in the archive

Proxies for assets that are located in the archive can be used as editing proxies if they either have been encoded by Strawberry 6.0.4 or newer or if their proxy structure has been updated while they were located on the production storage.

Conforming a project that has its source media partially or fully located in the archive

If the HighRes media is located in the archive during the conforming process, Strawberry will attempt to pull it from there automatically. For this to work, the user who performs the conforming process must have the capabilities “Can retrieve individual assets from own projects” and/or “Can retrieve individual assets from other people’s projects” enabled in his or her user roles.

Are there any file types for which Strawberry can not create editing proxies?

For Strawberry to be able to create a Skies editing proxy, the source file must meet all of the following criteria:

  • The source file is a video
  • A streaming proxy version of the source file has been created by Strawberry
  • The source file is in a project or library that is located on the production (online) storage
  • The source file has video and audio wrapped inside a single container (e.g. .mov or .mxf)

This also means that the following file types can not currently be converted into editing proxies:

  • Image Sequences
  • MXF files imported via Avid Media Composer (as each video and audio track is a separate file on the storage)
  • P2 media (as video and audio tracks are distributed across various card folders)
  • Any file in the archive that has an unsupported proxy structure version (Read “How do I prepare existing proxies for remote editing?” above)
Last modified: Sep 24, 2020

Need more help with this?
Visit the Projective Support Websites

Thanks for your feedback.