LEGACY Creating and Working with Proxy Assets (Deprecated)

Sagi Malka
  • Updated

Setting Up a Proxy

A proxy enables you to play your media assets and view your image assets in both the Core / MAM / Reviewer UIs.
You can adjust your existing import workflow so that it automatically creates proxies for both image and media assets.

When you upload, the proxy it is treated as a child of that asset. This is shown below in the Core UI:

proxy_example.png

There are two methods in which to set up a proxy for your image assets.

Method 1: Creating an Import Workflow with an Inbox for Image Assets

To create an import workflow with an inbox specifically for images assets,
consult the A Basic Import Workflow guide.
This includes creating a proxy for your images assets.

Method 2: Updating Your Current Import Workflow

To set up a proxy for an image asset, you will need to do the following:

  1. Create and configure a transcode resource.
  2. Create and configure a transcode profile.
  3. Create a proxy action.
  4. Create a decision action so that your workflow can create proxies for both media and image assets in the same workflow.
  5. Adjust your existing import workflow so that it contains the create image proxy, and decision node.

Create a Transcode Resource

To create a transcode resource, follow these steps:

  1. On the toolbar, click the New option.
    create_a_transcode_resource_step1.png
  2. From the drop down, select Resource.
    create_a_transcode_resource_step2.png
  3. In the Create new Resource… screen, you will need to enter the details for your transcode resource.
    create_a_transcode_resource_step3.png
  4. In the Name field, enter a name.
    create_a_transcode_resource_step4.png
  5. In the Description field, enter an optional description.
    create_a_transcode_resource_step5.png
  6. From the Visibility field, select the workspaces, accounts, and groups that will have access to this transcode resource.
    create_a_transcode_resource_step6.png
  7. From the Plugin field, select Transcode Resource.
    create_a_transcode_resource_step7.png
  8. From the Polling Interval field, select a polling interval, for example 1 minute.
    create_a_transcode_resource_step8.png
  9. Click Save.
  10. Next, click the Configuration sub-tab.
    create_a_transcode_resource_step10.png
  11. Click the Edit option.
    create_a_transcode_resource_step11.png
  12. In the Transcode Engine field, select Flex Stream Processor.
    create_a_transcode_resource_step12.png
  13. In the Transcode Host Names field, specify a hostname.
    create_a_transcode_resource_step13.png
  14. In the Transcode Management Host field, specify the host name.
    create_a_transcode_resource_step14.png
  15. In the Transcoder Management Port field, enter the following port: 18110.
    create_a_transcode_resource_step15.png
  16. In the Transcode Platform field, select Unix.
    create_a_transcode_resource_step16.png
  17. In the Path field, specify a path.
    create_a_transcode_resource_step17.png
  18. Click Save.
    create_a_transcode_resource_step18.png
  19. Click Enable.
    create_a_transcode_resource_step19.png
  20. Click Start.
    create_a_transcode_resource_step14.png

Create a Transcode Profile

To create a transcode profile, follow these steps:

  1. On the toolbar, click the New option.
    create_a_transcode_profile_step1.png
  2. From the drop down, select Profile.
    create_a_transcode_profile_step2.png
  3. In the Create new Profile... screen, you will need to enter the details for your transcode profile.
    create_a_transcode_profile_step3.png
  4. In the Name field, enter a name.
    create_a_transcode_profile_step4.png
  5. In the Description field, enter an optional description.
    create_a_transcode_profile_step5.png
  6. In the Visibility field, select the workspaces, accounts, and groups that will have access to this transcode profile.
    create_a_transcode_profile_step6.png
  7. From the Type field, select Media Transcode.
    create_a_transcode_profile_step7.png
    If you are creating an image proxy, you _must_ select Image Transcode, otherwise the transcode will not work.
    create_a_transcode_profile_step7_image.png
  8. Click Save.
    create_a_transcode_profile_step8.png
  9. Click Enable.
    create_a_transcode_profile_step9.png

Create a Proxy Action

To create a proxy action, follow these steps:

  1. On the toolbar, click the New option.
    create_a_proxy_action_step1.png
  2. From the drop down, select Action.
    create_a_proxy_action_step2.png
  3. In the Create new Action… screen, you will need to enter the details for your proxy action.
    create_a_proxy_action_step3.png
  4. In the Name field, enter a name.
    create_a_proxy_action_step4.png
  5. In the Description field, enter an optional description.
    create_a_proxy_action_step5.png
  6. From the Visibility field, select the workspaces, accounts, and groups that will have access to this proxy action.
    create_a_proxy_action_step6.png
  7. From the Plugin Type field, select Create Proxy.
    create_a_proxy_action_step7.png
  8. From the Plugin field, select Create Proxy Action.
    create_a_proxy_action_step8.png
  9. Click Save.
    create_a_proxy_action_step9.png
  10. Next, click the Configuration sub-tab. 
    create_a_proxy_action_step10.png
  11. Click Edit.
    create_a_proxy_action_step11.png
  12. From the Transcode Profile field, select the transcode profile that you have just created.
    create_a_proxy_action_step12.png
  13. From the Folder Resource field, select a destination that is pointing to a storage.
    create_a_proxy_action_step13.png
  14. Click Save.
    create_a_proxy_action_step14.png
  15. Click Enable.
    create_a_proxy_action_step15.png

Updating Your Import Workflow

If you have an existing media asset import workflow set up, you will need to adjust it, so that it creates a proxy for both image assets and media assets. You can do this by creating a groovy scripted decision action. The groovy scripted decision action uses a script that can determine whether the asset you have imported is either an image asset or a media asset and then create a proxy.

Creating a Groovy Scripted Decison Action

To create a groovy scripted decision action, follow these steps:

  1. In the Ooyala Flex console, on the toolbar, click New.
  2. From the drop down, select Action.
  3. Give your action a name and optional description.
  4. In the Visibility field, select which accounts, workspaces, and groups in which you want the action to appear.
  5.  In the Plugin Type field, select Decision.
  6. In the Plugin field, select Groovy Scripted Decision Action.
  7. Click Save.
  8. Click the Configuration tab.
  9. Click Edit.
  10. Expand the Script field, by clicking the + symbol.
  11. In the text box, enter the following script:
    def execute(){ Long resourceId = context.getMioObjectVariable("resource").id
    String name = context.getStringVariable("resourceItemName") ResourceService
    resourceService = services.getResourceService() if (resourceService.capacityItemSupportsImageType(resourceId,name)){
    return true } return false }
  12. Click Save.
  13. Click Enable.
  14. Navigate to your existing workflow.
  15. Update your existing import workflow, so that it contains:
  • A decision action
  • An additional import node so that images can be imported
  • A create image proxy.

The workflow will look like this:

create_image_proxy_workflow.png


Proxy Settings

To make full use of the rough-cut tool. An Elemental Server license will be required with the following settings.

Recommended proxy details:

Video

  • Codec: H264
  • Profile: Baseline
  • Level: 3.1
  • Pixel Format: YUV420
  • Bit Rate: 1600Kbps
  • Size: 1024x576
  • Aspect Ratio: 16:9
  • Frame Rate: Same as source
  • GOP size: 50 (no scene detection, closed GOPs and 1 ref frame)

Audio

  • Codec: AAC-LC
  • Channels: 2
  • Bit-rate: 132Kbps
  • Sample Rate: 44100
  • Format
  • MP4 with fast streaming (MOOV at start of file).

Recommended Proxy details

If the proxy is stored in S3 make sure the cors headers, create a cors configuration from the AWS console:

 resource "aws_s3_bucket" "Name" {

  bucket = "Bucket_Name"

  acl = "private"

  cors_rule {

  allowed_headers = ["Authorization"]

  allowed_methods = ["GET"]

  allowed_origins = ["*"]

  //expose_headers = ["ETag"]

  max_age_seconds = 3000

  }

  }

Related articles

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk