Vendor Instructions

This page contains information required to help us configure your Shotgun Vendor accounts, setup your Aspera accounts and instructions on how to use GPL’s Create Delivery app.

  • Vendor Details: In order to help us better service your team, please take a moment and answer a few questions on this FORM.

  • Download Shotgun Desktop: If your Studio is already using Shotgun Desktop, please ensure you have the latest version. If you don’t have Shotgun Desktop please follow these INSTRUCTIONS on how to download.

  • Setup Aspera on Cloud: Please follow these INSTRUCTIONS on how to configure Aspera on Cloud with the Create Delivery app.

  • Create Delivery Tutorial: Please follow these INSTRUCTIONS on how to use the Create Delivery app.

Next Steps

  • After the GPL Softspeak Team gathers all of your form data we will reach out by email to answer any questions.
  • We will then arrange a time for a video training session to go over our GPL Tools.
  • If you have any questions please feel free to Contact Us

Troubleshooting

Slow Delivery Times

If you are experincing slow or stalled delivery times when sending files through Create Delivery app, here are some common problems and solutions.

  1. Windows: If you are loading files on a Windows machine from a networked storage and seeing very slow processing times in Create Delivery;
  • FIRST try copying the media to your local machine
  • SECOND drag the media into CD2 from the local drive

This should speed up the process. Network storage on Windows is notoriously slow so your IT team may want to investigate tweaks to your network configuration to help speed things up

Shotgun Desktop

  1. “Info.yml error”:

Aspera on Cloud

If you are having problems with your Aspera connection, here are a few tips:

  1. Test your Aspera connection HERE
  2. Information about Aspera and your Firewall HERE
  3. Allow outbound connections from the client machine: 33001 TCP/UDP and 33001-33010 UDP (This range allows 10 concurrent transfers. Expand range beyond 33010 to allow more than 10)
  4. Verify http://local.connectme.us resolves to 127.0.0.1. Check DNS settings on delivery machine if URL does not resolve correctly. In rare instances the hosts file needs to be modified on delivery machine to map local.connectme.us to 127.0.0.1
  5. If the delivery machine is a a shared transfer station, the last user might be signed into a different AoC account, causing the correct workspaces not to show up. Select “Log out of IBMid” when logging out.
  6. More advanced problems can be directed to IBM’s support alias