If you're licensing pieces from the Exchange marketplace, you still have the option to integrate them with your station's automation system. Episodes won't automatically deliver— you'll still have to trigger them— but after a one-time setup you can have episodes ingested by your automation system with minimal lift on your end. Please note: your station must have its own FTP in order to use this feature (not a PRX FTP).
Step One: Visit the piece you want to ingest
There are a few ways to do this. If you need to license the piece still, just use the search bar to find the program and then click the blue "Buy For..." button in the top right. Once you've licensed the piece you'll be brought to a page that gives you an option to download or start delivery, and you can move on to Step Two.
If you already bought the piece, you could log into your station account and go to "Purchased Pieces" under My PRX. Click on the date next to the piece you want to access.
Step Two: Choose delivery option
When accessing the audio, you'll have the option to Download or Deliver. Click the "Start Delivery" toward the bottom of the page.
Step Three: Fill out delivery settings
Here you will be able to designate the file type, naming convention, etc. Then you'll be asked to give it an FTP destination. Again, this must be your station's own FTP server, not a PRX FTP server.
We recommend selecting the WAV-wrapped MP2 version so that the metadata accompanies the file delivery. Once all the information is populated, click "Start Delivery!"
Step Four: Set up file ingestion from your FTP
At this point, the technical configuration depends on your unique setup. If you are in the process of setting up your station's FTP server and you'd like some tips, read on.
- FTPs must have multiple ports open in order to work. The range of ports you need to have open depends on the FTP server, but in general, your server should have a defined range of passive data connection ports. The firewall should likewise be open for this same range.
- Port 21 is the command port and must be open. This is also the port that PRX will use as a default.
- If you would like to limit what IPs can connect to your server, we recommend whitelisting all the AWS ports (as that is where PRX FTP clients are hosted).
- If you whitelist certain IPs, keep in mind that they are not static and will need to be updated in your firewall rules as they change. AWS maintains a public list of IP ranges for this purpose: https://ip-ranges.amazonaws.com/ip-ranges.json
Stations will need a third-party software to get files from an FTP server to a local folder where your automation system can ingest them, without having to do this manually. Here are some recommended solutions:
- enConveyor (will work with any automation system).
- WinSCP (Paid FTP Client)
- CoreFTP (Paid FTP Client)
- CuteFTP (Free FTP Client)
- SyncBack (Free FTP Client available)
- Second Copy (Paid FTP Client)
- Radio Spider (Paid FTP Client)
- Yummy FTP Watcher (For Mac) (Paid FTP Client)
Once you determine a third-party ingestion software, you will need to create a rule for it to scan the directory where your files are landing. You can reach out to your ingestion software's support team for assistance with this, or drop PRX a line and we can try to help you out.