Introducing ROCS|Player
ROCS|Player is a basic performance tool primarily for music playback. It doesn’t have any direct editing capabilities like Stage|Tracks, but it offers a simple alternative for basic playback. The ROCS|Player mobile application is exclusively available for legacy shows.
For standard titles, you will have access to one or both of the following desktop applications:
- For information about the rehearsal tool, check out How to Use Show|Ready.
- For information about the performance tool, check out How to Use Stage|Tracks.
As ROCS moves forward with additional exciting advancements to Stage|Tracks, and with the limited capability of the ROCS|Player app, we are limiting access to the mobile app for standard titles. As such, we no longer send out the mobile codes. For more information, check out this page: ROCS|Player Rebrand and Limited Access.
Menu
1. ROCS|Player vs. Stage|Tracks
Before you use ROCS|Player, we want you to be aware its limitations:
- Stage|Tracks and the ROCS|Player app (previously known as Stage|Tracks Mobile) are not the same app and do not integrate. Any edits made in Stage|Tracks do not automatically pull through to ROCS|Player.
- ROCS|Player is limited in functionality. It is a basic media player with no ability to make edits to tracks in the mobile app. While edits can be manually added by request, not all edit types are supported in the mobile app (vamps, skips).
Legacy Titles
- If you have a legacy show, you won’t have access to Show|Ready or Stage|Tracks so all edits need to be typed out in email and sent to licensing@rightoncueservices.com.
Standard Titles
- For all other shows, you will have access to either Show|Ready or Stage|Tracks. If you have access to ROCS|Player all edits must be completed inside the desktop applications, not the mobile app. Once your edits are ready, you need to send changes to the ROCS server so the ROCS team can ensure accurate edits are made for my production. Edits typed outin email won’t be accepted.
- While the first edit submission is free, there are additional costs for more edit submissions ($75 an hour). Any additional edit requests require payment to be received before the ROCS team begins work.
- Once edits are submitted for ROCS|Player, these edits can take 2-5 business days to be completed. You can pay an additional $40 for a rush edit if you need it sooner. To avoid this fee, we recommend submitting edits two weeks before your opening night.
Therefore, if you want the flexibility to customize your show, we recommend using Stage|Tracks instead. With Stage|Tracks, you can access the full editing feature set. When you make edits in Show|Ready or Stage|Tracks you can immediately playback and hear your changes. After sending changes for distribution, those edits will appear instantly in both Show|Ready and Stage|Tracks on the devices and computers of all members of your production. This is the recommended route, and there is no additional cost. However, if you are doing a legacy show, your only option will be to use ROCS|Player.
However, sometimes you may not have access to a computer to play your music for your performance. This is when you might want to use ROCS|Player on your mobile device. With ROCS|Player, be aware that edits are not applied instantaneously. Also, indefinite vamps and skips are unavailable in ROCS|Player.
Also, unlike Stage|Tracks where you can hear the edits to your tracks instantly, to hear your edits in ROCS|Player, you first need to make your edits in Show|Ready or Stage|Tracks and upload the change log of your edits to the ROCS server. Then, our staff will manually apply the edits to the songs, and upload new tracks that your device will download. You can then “hide” the original unedited tracks and instead play back the edited tracks. While using this tool is included automatically to you at no charge, there are additional costs associated with edit submissions. For more information, check out: Submitting Edits for ROCS|Player.
Here is a comparison chart showing the differences between Show|Ready, Stage|Tracks, and ROCS|Player for easy reference.
2. Managing Your ROCS|Player License
Legacy Titles
- For legacy shows, as soon as your order is processed, Right on Cue Services (ROCS) will automatically send you the following email from licensing@rightoncueservices.com with your access codes for ROCS|Player.
Standard Titles
- For all other shows, codes will not automatically be sent out for ROCS|Player. However, if you have access to codes from before access was limited, you will receive your codes 30 days before your opening night. Right on Cue Services (ROCS) will automatically send you the following email from licensing@rightoncueservices.com with your access codes for ROCS|Player
Licensing Email
Once you have the codes, we recommend that you send the codes to the relevant members of your production staff (up to 5 total users/devices). This will allow your production staff to play your show in ROCS|Player. You will input you will input these codes into the ROCS|Player mobile app to get access to your show.
We always recommend downloading the most recent version of ROCS|Player.
To download the app for your iOS device (iPad, iPhone, etc):
- Go to the Apple Store and search “ROCS|Player.”
To download the app for Android device:
- Go to the Google Play Store and search “ROCS|Player.”
Activating Your ROCS|Player License
When you open the app, you will input your viewer code to activate the show. ROCS|Player will then download the show to your device.
To get play access for the director and production staff, do the following:
- In the Username field, add the username.
- In the Password field, add your password code.
- Click Continue to download your show.
NOTE: Be aware that every time you enter the authorization code for the same show, it will consume one of the total authorizations granted to your organization. If more authorizations are needed, please reply to your licensing email with your request, and ROCS will be happy to help.
The first time you launch ROCS|Player on your device, a pop-up window will appear reminding you that music playback will be interrupted by texts, phone calls, etc. We recommend you turn on airplane mode to avoid disruption during your performance.
Silence Reminder
3. Navigating ROCS|Player
Below is the main window for ROCS|Player. We will review what each button does.
If you have submitted edits for ROCS\Player, make sure to click the Check for Updates button in the app to get the latest version.
This section displays the name and number of each song. It also includes information about the playback state. You will notice that songs are broken up, and sometimes combined, differently than in the score,
ROCS|Player tracks are broken up at caesuras, and combined at attaccas (or “segue as one“). Decimal points are used to identify segments of the song. Hyphens are used to combine songs. Also, when you receive new tracks with your edits, the song numbers will have an “E” for “edit” to distinguish the edited tracks from the original unaltered tracks.
The Selected Song indicates you have loaded it for playback, represented as a highlighted gray bar.
Selected Song
Next to the song name, the symbols show the Playback State. These symbols determine the behavior of which song loads next or if playback continues automatically. To utilize this function, click on the symbol in the Song List to change the playback state.
Playback State
Here is a list of the Playback State Symbols and what they do:
– automatically plays the next song (attacca). – queues the next song, and you need to trigger the song to play it. – song is skipped.This section controls the playback of the selected song and allows you to navigate your show easily.
Here is a list of all of the Transport buttons and what they do:
- Previous Song – go to the previous song in the Song List.
- Play – play / resume the song progress.
- Pause – pause the song progress.
- Next Song – go to the next song in the Song List.
For an even more simplified play, click the Performance Mode button and you will be presented with a large Play button. Hit the button to play the music and it will change to a Pause button. Hit it again to pause. From this view, you can also click the double arrows to move between songs.
Play Button
Pause Button
If you would like to add a fade to the end of your song, click on the Set Fade Duration button and a pop-up menu will appear. Select from one of the options to add the fade.
To adjust any of the settings, click the Settings button and you can change the screen brightness, system volume, hide the silence reminder, and more!
4. Submitting Edits for ROCS|Player
Costs of Edit Submissions for ROCS|Player
To add edits to ROCS|Player, you need to submit your edits to ROCS. We will manually make the edits for you, and upload them into the mobile app. Because this takes us additional time and effort, we charge the following for this service:
- First submission of edits = free
- Additional submissions = $75/hour (minimum of $40 for a partial hour)
Costs of Rush Orders for ROCS|Player
If you are short on time and need your edits sooner than 2 – 5 business days, we consider this a rush order. We charge the following for this service:
- $40 to be completed in one full business day.
- $75 to be completed the same business day (must be submitted by 10 am Mountain Time).
If this is a rush order, please also call us to notify us that you submitted it so we can make it a top priority. Payment for the additional edit submissions and rush orders must be completed before we work to process your order. If you don’t have time to wait, and you have access to Stage|Tracks on your computer, we recommend you use that application instead. Any edits made in Stage|Tracks are applied instantaneously and there are no additional costs.
Before you can send your edits to ROCS to upload into ROCS|Player, you need to make the edits in either Show|Ready or Stage|Tracks first. You must make your edits directly in Show|Ready or Stage|Tracks, as we won’t accept a list of edits typed out via email. This policy is to ensure we can make those edits accurately and promptly.
To learn how to make edits to your show, check out the following sections:
NOTE: Due to the limited functionality of ROCS|Player, please be aware that indefinite vamps are skips are unavailable. If you have indefinite vamps or skips on your change log, we will have to reach out to you to ask for clarification, as the ROCS|Player doesn’t support those features. This can slow down the time our production team takes to process your edits. If you want more functionality, we recommend using the full performance tool, Stage|Tracks instead.
Sending ROCS|Player Edits to ROCS
When you’re done making all your edits in Show|Ready or Stage|Tracks, be aware that they do not automatically appear in ROCS|Player. You need to send your edits via the change log, and inform ROCS they are ready. Our team will manually make edits and upload your changes to your app. This process takes 2 – 5 business days and may have an additional cost.
To submit your edits to ROCS, you need to upload your change log to the ROCS server. This can be done one of two ways:
- Click Send Changes button in the Change Log area.
- Go to the top menu and click Admin > Upload Current Log.
Once you’ve uploaded your change log, email ROCS at licensing@rightoncueservices.com to inform them you have an edit submission for ROCS|Player. We recommend that you respond to your original licensing email with your authorization codes listed. If you can’t find it, provide your name, organization, and show name. Make sure to list your Change Log Version number.
NOTE: Due to the limited functionality of ROCS|Player, please be aware that indefinite vamps are skips are unavailable. If you have indefinite vamps or skips on your change log, we will have to reach out to you to ask for clarification, as the ROCS|Player doesn’t support those features. This can slow down the time our production team takes to process your edits. If you want more functionality, we recommend using the full performance tool, Stage|Tracks instead.
For your first submission, we will forward your edits to our production team who will work to process and upload your edits into the mobile app. We will notify you (via email, or how?) when your tracks are ready in ROCS|Player. This process takes 2 – 5 business days. This first edit submission is free. Any additional edit submissions will be an additional cost.
NOTE: Due to the limited functionality of ROCS|Player, please be aware that indefinite vamps are skips are unavailable. If you have indefinite vamps or skips on your change log, we will have to reach out to you to ask for clarification, as the ROCS|Player doesn’t support those features. This can slow down the time our production team takes to process your edits. If you want more functionality, we recommend using the full performance tool, Stage|Tracks instead.
For additional edit submissions, we will assess the estimated time it takes to complete your edit request. We will reply with the cost and include a link to your invoice in PandaDocs. We need to receive payment before we process your edits.
- To see pricing for edits, see Costs of Edit Submission for ROCS|Player.
- To see pricing for rush orders, see Costs of Rush Orders for ROCS|Player.
Once you have paid, we will forward your edits to our production team who will work to process and upload your edits into the mobile app. We will notify you via email when your tracks are ready in ROCS|Player. This process takes 2 – 5 business days.
NOTE: Due to the limited functionality of ROCS|Player, please be aware that indefinite vamps are skips are unavailable. If you have indefinite vamps or skips on your change log, we will have to reach out to you to ask for clarification, as the ROCS|Player doesn’t support those features. This can slow down the time our production team takes to process your edits. If you want more functionality, we recommend using the full performance tool, Stage|Tracks instead.
