A: User Administration Section

This section allows you to create Users and define which FTP site and Directory they will use.

B: Playlist Section

Here you will select the Playlist to be Tracked.

C: Playlist Hour Segment / Status Section

This area allows you to set the specific hours to be Tracked and also displays the current status of the selected Playlist.

D: Status Information Section

This section provides a read-only log of the overall process and status of the creation of the Package, the status and retrieval of the completed work.

Sections A through C are discussed below.

First, lets create a user. Enter the User Name and a description pressing ADD when ready.

This will add the user to the list. Select that User and press the EDIT USER button. 

This opens the RTS User Management screen. Here you will define additional information such as the Password for the FTP site and the Drive Letter Path to the FTP site.

The H/T Copy Length refers to the amount audio that should be used for the Head and Tail. A value of 5.0 would copy the first five seconds of audio and the last five seconds before the Tail.

The Client to Server Library Mappings along with the Server to Client Library Mappings allow a user to directly create a correlation between two different Libraries.

For example, if the Station has a MUSIC Library database on the F: drive, you would use F: MUSIC in the Server field.   Your Remote User might have this same Library on their C: drive as the DETROIT Library.

You would in turn have:

C:DETROIT ==>> F:MUSIC   under the Server to Client
F:MUSIC ==>> C:DETROIT   under the Client to Server

This allows both the Server Application and the Client Application to route both audio and Library data to the proper Library.

This option can be very beneficial for the Remote User. Please review the section for Remote Audio Libraries.

If you chose not to define the Library Mappings, the Remote Tracker Client will create a temporary Remote Library on that workstation using the RTL#### name. While the overall operation is virtually the same as described above, the difference is that each time a Package is created, all audio cuts will be sent to the Client and a new temporary Library will be created for each Playlsit Package downloaded.

If a playlist does not appear automatically in the lower portion of the screen, you may manually type in the playlist name in the empty field at the very bottom of the screen.

Once the list has been selected, you may press ADD.  This will add that playlist to the upper portion of the display.  After adding that list you may select a 'From Hour' and a 'To Hour' for the hours of the day that are to be Tracked by this User. Press ADD when the hours have been selected.

You will now see the Hours listed and it's Status within the upper portion of the Server screen. 

The first part of the process is to Interrogate the Remote Client to determine what audio files need to be sent.

To force a transfer of ALL audio files for the hours selected, check the Force Audio Transfer option before pressing the GO ONLINE button.

A Package will be created containing the first and last few seconds of the audio cuts in the playlist and the playlist itself.

The state will change to ONLINE along with the control button changing to GO OFFLINE.

You may remove the Package from the FTP site by selecting that list and pressing GO OFFLINE. This can only be done if the Package has not been downloaded by the Client. This would only be done if a change to the Playlist has been made and an updated list needs to be sent to the Remote Client.

At this point, the Remote Client for this User will detect that the Package is ready and will prompt the User to BEGIN DOWNLOAD.   [Jump to Remote Client]

If the Package must be taken OFFLINE for any reason, the Client must RELEASE the Package first. This will all the Server control to take the Package OFFLINE, update the Playlist then repackage and upload again.

The Remote User can then begin to Track the Playlist they downloaded. When they have finished, they will simply press BEGIN UPLOAD to send the Tracks and the Playlist to back to the Server. [Jump to Sending Voice Tracks]

That playlist can then be loaded and played.

First, lets create a Site. Enter the Site Name and a description then press ADD.

This will add the Site to the list. Select that Site and press the EDIT SITE button. 

This opens the RTC FTP Site Management screen. Here you will define additional information such as the FTP URL (such as FTP.ENCO.COM), the Directory Path (which should be the SAME as the above Server User settings), the FTP Username and Password.

To being a download, select the Playlist and press the BEGIN DOWNLOAD button.

This will start the communications between the Client and the Server. The Client will respond to the Server telling it what audio is needed for the hours selected.

The RELEASE button will tell the Server application that this Package is not going to be used. This allows the Server to take the Package 'OffLine'. The Package can then be updated by the Station Facility and reposted to the FTP site for downloading.

When the Voice Tracking session has been completed, select the Playlist and Hour - pressing BEGIN UPLOAD to send the finished Package back to the Station.

The Playlists will automatically be given a name using RTP##### for Remote Tracking Playlist <number>.

The Playlist Description will be the SAME as the Playlist Description entered as the main Station Facility.  The Playlist Description will help you determine which playlist is for which station facility.

This allows for one person to Track for several different Stations and prevents one Stations Playlist  from interfering with another Stations Playlist. 

A few notes on Remote Audio Libraries

Within DAD, a special Library can be created for the downloaded audio. These Libraries will be created using the RTL##### naming format. These Libraries will be created if the User does not pre-define a Library name as part of the 'Mappings' when defining the User values within the Remote Tracker Server. If one does create Mappings, then the Remote Client will in turn create the Library names defined in the Server User Management screen.

This is an important item to make note of.  This actually allows you as an administrator to help your Remote User by creating a Library Name for your Market or Station.

For example, if you have a Remote User in Austin, you would set your User mapping to use: F:CUTS ==>> C:AUSTIN

This would in turn create an AUSTIN Library on the Remote Users workstation. When they download audio, that audio is saved to the Austin Library. Each time they download a Playlist, both the Client and Server will determine if the audio exists in the Austin Library. If it does not exist, that cut will be part of the Playlist Package. If the cut does exist, then the Server will not package that item as the Client already has the audio. 

If you chose not to define the Library Mappings, the Remote Tracker Client will create a temporary Remote Library on that workstation using the RTL##### name. While the overall operation is virtually the same as described above, the difference is that each time a Package is created, all audio cuts will be sent to the Client and a new temporary Library will be created for each Playlist Package downloaded.

This can save time and bandwidth when sending Playlists to Remote Users.

You should run DAD in Local Mode.

Once DAD has started, you can being to work on the Remote Tracks.

There is a complete overview of Tracker within the DAD Help guide.

Important: Remote Tracker Server will ONLY transfer Voice Tracks that are Production Elements.  These types of cuts will use a DAD Library Cut Number and can be either inserted as a Production Element within Tracker or can be Scheduled within the Playlist as a normal cut then loaded into Tracker and recorded over. Remote Tracker Client will not send the temporary Voice Track that is created by Tracker. These type of Tracks do NOT use a DAD Library Cut number but instead a temporary cut based upon the Playlist name.

Now that a Playlist Package has been downloaded you should be able to view that Playlist by going to the Main Playlist Modify screen (go to Library then select the Playlist button in the top center).

In the Main Playlist Modify screen, select the Playlist button again on the upper right side. This will display a list of Playlists you can use.

Please remember that the Playlist Names will be listed as RTP#####. Please make sure to verify that this is the correct Playlist by checking the Playlist Description. To load this list, select it and press LOAD.

You may adjust the placement of the Outro cut and the Intro cut along with independent Level control for each Track.

When you have finished recording, press SAVE.

You could then either press NEXT to advance to the next position or press EXIT to close the Tracker screen.

Once all Tracks have been created you should Save the Playlist. To Save the Playlist, right click on the Playlist Bar and select SAVE PLAYLIST.

After the list has been saved, return to the Remote Tracker Client screen. Select the playlist you just finished and press the BEGIN UPLOAD button.

The Client application will create a Package that contains the recorded voice tracks and the Playlist itself.

This Package is then uploaded to the FTP server.

Once downloaded, the Playlist hours are 'unlocked' and injected into the main Playlist along with the recorded Voice Tracks being copied into the proper audio directory and Library database updated.

At this point the process is complete.

If these hours of the Playlist are no longer needed, you may select that list and press GO OFFLINE and DEL to remove the list from the Que.