Roku HD2000 manual Testing Scripts, Playlists, and .CSV, Testing Playlists

Testing Scripts, Playlists, and .CSV

An efficient way to test playback is to use the BrightSign Shell. By using the shell, you can see “debug output”. From the BrightSign Shell you can start your script manually and view output from the script. You can start a script from the shell by using the “script” command. Follow the directions above to connect the BrightSign to your computer, and access it using Hyperterminal.

As your script runs, you’ll see output in your terminal program. You’ll see a variety of output including mouse clicks or button presses, file names, audio and video settings, as well as any errors associated with incorrect use of functions or commands including the line numbers.

Testing Playlists

When your playlist contains the keyword “debug” the autorun.bas script provides detailed output to the BrightSign Shell during playback. To begin testing playlists, do the following:

1.Copy your content including playlist and autorun.bas to your CF card

2.Open your autoplay.bsp (main playlist file) and add the keyword: debug

3.Insert your CF card into the BrightSign, and add power

Testing Autorun and .CSV files

Running the autorun.bas in debug mode will provide detailed output to the BrightSign Shell while the script is running. To begin testing the autorun.bas script in debug mode, do the following:

1.Copy your content, including .csv file and autorun.bas to your CF card

2.Open autorun.bas and find the “debug=false” line near the top of the script

debug=false 'set to true to turn on debug prints; false to turn them off

3.Change to: debug = true

4.Rename autorun.bas file to “run.bas” for example, so it doesn’t start automatically

a)If you are testing a playlist, the main playlist must be named “autoplay.bsp”

b)If you are testing a .csv file, it must be named “autoplay.csv”

5.Insert your CF card into the BrightSign, and add power

6.At the Roku prompt, type the following: script run.bas

Testing Custom Scripts

To make troubleshooting your custom scripts much easier, we recommend adding checks and print statements like those found in the autorun.bas script. Here are a few examples:

•Add print statements telling you which portion of the script you are currently in

•Add print statements showing the type of event that just occurred

48