Preconfigured Players
Preconfigured Players
Quick Start Guide
PRECONFIGURED
PLAYERS
Software Version - Release 4
April 30, 2009
www.scala.com
Preconfigured Players
Copyright © 2009 Scala Incorporated. All rights reserved.
SOFTWARE VERSION:
DOCUMENT VERSION:
RELEASE 4
VERSION 2.0
JANUARY 22, 2009
APRIL 30, 2009
NO
PART OF THIS PUBLICATION, NOR ANY PARTS OF THIS PACKAGE MAY BE COPIED OR
DISTRIBUTED, TRANSMITTED, TRANSCRIBED, RECORDED, PHOTOCOPIED, STORED IN A RETRIEVAL
SYSTEM, OR TRANSLATED INTO ANY HUMAN OR COMPUTER LANGUAGE, IN ANY FORM OR BY ANY
MEANS, ELECTRONIC, MECHANICAL, MAGNETIC, MANUAL OR OTHERWISE, OR DISCLOSED TO THIRD
PARTIES WITHOUT THE PRIOR WRITTEN PERMISSION OF SCALA INCORPORATED.
TRADEMARKS
THE FOLLOWING ARE TRADEMARKS OR REGISTERED TRADEMARKS OF THE COMPANIES LISTED, IN
THE UNITED STATES AND OTHER COUNTRIES.
SCALA, INFOCHANNEL, SCALA CONTENT MANAGER AND THE
LOGO: SCALA INCORPORATED.
WARRANTIES AND DISCLAIMERS
THE FOLLOWING PARAGRAPH DOES NOT APPLY TO THE UNITED KINGDOM OR ANY OTHER COUNTRY
WHERE SUCH PROVISIONS ARE INCONSISTENT WITH LOCAL LAW .
SCALA INCORPORATED PROVIDES THIS PUBLICATION “AS IS” WITHOUT ANY WARRANTY OF ANY
KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE LIMITED WARRANTIES
OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW
DISCLAIMER OR EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS , THEREFORE THIS
STATEMENT MAY NOT APPLY TO YOU.
THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS.
CHANGES ARE PERIODICALLY MADE TO THE INFORMATION HEREIN: THESE CHANGES WILL BE
INCORPORATED IN NEW EDITIONS OF THE PUBLICATION. SCALA MAY MAKE IMPROVEMENTS
AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) IN THIS PUBLICATION AT ANY
TIME.
IT IS POSSIBLE THAT THIS PUBLICATION MAY CONTAIN REFERENCE
SCALA PRODUCTS OR SERVICES THAT ARE NOT ANNOUNCED
TO, OR INFORMATION ABOUT,
IN YOUR COUNTRY.
SUCH
REFERENCES OR INFORMATION MUST NOT BE CONSTRUCTED TO MEAN THAT SCALA INTENDS TO
ANNOUNCE SUCH SCALA PRODUCTS OR SERVICES IN YOUR COUNTRY.
REQUESTS FOR TECHNICAL INFORMATION ABOUT SCALA PRODUCTS SHOULD BE MADE TO YOUR
SCALA AUTHORIZED DISTRIBUTOR, DEALER OR YOUR SCALA MARKETING REPRESENTATIVE.
SCALA MAY HAVE PATENTS OR PENDING PATENT APPLICATIONS COVERING SUBJECT MATTER IN
THIS DOCUMENT. THE FURNISHINGS OF THIS DOCUMENT DOES NOT GIVE YOU ANY LICENSE TO
THESE PATENTS. SEND LICENSE INQUIRES, IN WRITING TO SCALA INC., 350 EAGLEVIEW BVD,
EXTON, PA 19341, USA.
2
Preconfigured Players
Contents
1.0
Overview ..................................................................... 6
1.1
Enhanced Write Filter (EWF)................................... 6
1.1.1
To determine the status of EWF ..................... 7
1.1.2
To disable EWF ................................................ 8
1.1.3
To enable EWF ................................................ 8
2.0
Basic Hardware Player setup steps ............................. 8
2.1
Hardware steps ..................................................... 10
2.2
Software steps ...................................................... 10
3.0
Detailed instructions ................................................. 11
3.0.1
Unpack and inspect the Hardware................ 11
3.0.2
Connect the AC power cord .......................... 11
3.0.3
Connect the monitor ..................................... 12
3.0.4
Connect any input devices ............................ 12
3.0.5
Connect to the network ................................ 13
3.0.6
Turn on power to Player and monitor .......... 13
3.0.7
Changing the password for the player account
& setting up auto-login ................................................. 13
3.0.8
Give the Player its unique IP number ........... 15
3.0.9
Give the Player its unique computer name .. 16
3.0.10 Change the machine’s default Administrator
password ....................................................................... 16
3
Preconfigured Players
3.0.11
Change the UltraVNC password .................... 18
3.1
Enable regular reboots.......................................... 18
3.4
Set Player and Windows display modes ............... 23
3.5
Player 5 Display Configurations ............................ 23
3.6
Single Channel Player ............................................ 24
3.6.1
Window (Single Channel) playback ......... 25
3.8
One Screen (Single Channel) ................................. 26
3.9
Custom Full Screen Playback ................................ 27
4.0
Two Channel Player................................................... 28
4.1
Two Channel (Spanning) ....................................... 29
4.1.1
Channel Options............................................ 29
4.1.2
Single Channel – Two Output Configuration. 31
4.1.3
Two Channel (Independent) ......................... 33
4.2
Channel 1 Options ................................................. 33
4.3
Channel 2 Options ................................................. 35
4.2.1
Configuring audio in Two Channel
(Independent) mode ..................................................... 36
5.0
Enable optional Scala EX modules ............................ 37
5.0.1
Edit the Player’s MMOS.INI file if necessary . 38
5.0.2
Set up Player for automatic system clock
updates ....................................................................... 39
5.0.3
Test playback and display ............................. 40
4
Preconfigured Players
5.0.4
Test basic network connectivity.................... 40
5.0.5
Alternative connection strategies ................. 41
5.1
Remote Desktop Connection ................................ 42
5.1.1
6.0
Tools to help with system administration..... 43
Systems with Content Manager Pre-installed .......... 43
6.0.1
Database Management ................................. 44
6.0.2
The Apache Tomcat HTTP Server .................. 45
6.0.3
Content Manager 5 ....................................... 45
7.0
Antivirus Considerations ........................................... 46
7.0.1
AntiVirus Software: ....................................... 46
7.0.2
Performance.................................................. 47
7.0.3
Stability ......................................................... 47
7.1
Windows XP’s Built-In Software Firewall .............. 48
8.0
Advanced Topics ....................................................... 48
9.0
Scala End User License Agreement ........................... 51
5
Preconfigured Players
1.0
Overview
This document describes the steps necessary to
correctly set up a preconfigured computer as a
dedicated Scala® Player machine for operation within a
simple Network.
This system comes with the Scala5 Player software preinstalled and with the system pre-configured to run with
Scala5 Content Manager Servers as a dedicated Digital
Signage Player. There are, however, certain setup steps
that must be done for each Player on-site.
The software and hardware setup tasks are simple, and
are outlined in this Guide. However, they must all be
done correctly for the system to operate reliably. These
instructions assume that the person who will perform the
setup has knowledge and experience with system
administration and networking issues. Additional
documentation is also available:
x
Scala Player 5 Quick Start Guide for detailed
descriptions of working with the Player
Configuration utility.
x
Scala Content Manager 5 User’s Guide for
customized IC5 network setups.
1.1
Enhanced Write Filter (EWF)
Some preconfigured systems are provided with
Windows Embedded, as opposed to Windows XP
Professional. If your operating system is Windows XP
6
Preconfigured Players
Embedded, there is a feature called Enhanced Write
Filter or EWF. This feature is disabled by default.
If EWF has been enabled for any system volume,
changes to that volume are not saved when the system
is restarted.
Since EWF _prevents_ changes being made to a
protected machine when it is enabled it is important that
you know the state of EWF _prior_ to attempting to
configure a machine. For instance, if EWF were
enabled: Let’s say you have configured an IP address,
changed the administrator password, and modified the
display settings. If you restart the system, you will have
to re-enter those settings every time the system is
restarted. So is is important that EWF be _disabled_
when you desire to make system configuration changes
and that it be ENABLED when you do not want unauthorized changes to be made.
1.1.1
To determine the status of EWF
1. From the Start Menu, select Command Prompt.
2. Type: EWFMGR C:
3. This will display the current EWF settings. On
the second line of the output, under Protected
Volume Configuration, the state shows either
ENABLED or DISABLED.
7
Preconfigured Players
1.1.2
To disable EWF
1. From the Start Menu, select Command Prompt.
2. Type: EWFMGR C: -commitanddisable.
3. Restart the system.
Now you can make any appropriate changes to the
system.
The start menu has a shortcut to enable or diable EWF
for your convenience.
1.1.3
To enable EWF
1. From the Start Menu, select Command Prompt.
2. Type: EWFMGR C: -enable
3. Restart the system.
Note: Once EWF has been enabled, all changes that
are made for that session will not be remembered.
2.0
Basic Hardware Player setup steps
x
This list outlined below contains the basic steps
for quick reference. The following pages go into
more detail about each step.
x
There are certain items of information that you
should have before you begin setting up the
Players in an Network:
8
Preconfigured Players
x
Player’s unique IP address.
x
Player’s unique computer name.
x
A login password for the Player machine’s
Administrator account
x
A login password for the Player machine’s Player
account.
x
A UltraVNC password for the Player machine.
x
URL and Username/Password to the Content
Manager 5 system.
x
The recommended playback display resolution
for the Player.
x
Whether playback of the content requires any
optional EX modules.
If you have not been provided with any of these items
beforehand, be sure to keep a record of the settings you
use.
No deviations from the system defaults, other than those
unique to this installation or described in this document,
should generally be necessary. If you do need to make
unspecified changes or new settings, they should all be
carefully documented and reported to the Network
administrators.
9
Preconfigured Players
Changes from the default settings that are not
necessary to the proper operation of the Player are
strongly discouraged.
2.1
Hardware steps
1. Unpack and inspect the hardware.
2. Connect the AC power cord.
3. Connect the monitor.
4. Connect any input devices.
5. Connect to the network.
6. Turn on power to Player and monitor.
2.2
Software steps
1. Change the password for the Player account and
setting up auto-login.
2. Give the Player its unique IP number.
3. Give the Player its unique computer name.
4. Change the machine’s default Administrator
password.
5. Change the UltraVNC password.
6. Enable regular reboots.
10
Preconfigured Players
Enter the URL and Username/Password to the Content
Manager and select the correct player (Player 5 only).
7. Set Player and Windows display modes.
8. Enable optional Scala EX modules.
9. Establish the desired log retrieval method.
10. If necessary, edit the Player’s MMOS.INI file.
11. Set up the Player for automatic system clock
updates
12. Test playback and display.
13. Test basic network connectivity.
3.0
Detailed instructions
3.0.1
Unpack and inspect the Hardware
The first step should always be to inspect the PC
immediately after unpacking it. Damage caused to
computer equipment during shipping is not uncommon.
Units put into service with unnoticed physical damage
may be unreliable, may fail to run, and may even incur
severe electrical damage.
3.0.2
Connect the AC power cord
Plug the power cord into the IEC socket on the rear of
the PC unit, and plug the other end into a three-prong
11
Preconfigured Players
AC outlet of the appropriate voltage (120V/60 Hz or
240V/50 Hz).
Use of an uninterruptible power supply (UPS) unit is
strongly recommended.
3.0.3
Connect the monitor
Plug the monitor’s RGB input cable into the DVI-I, DVID, HDMI or 15-pin VGA socket on the rear of the unit.
3.0.4
Connect any input devices
Dedicated Player machines have no need for external
input in normal use, so mouse and keyboard are not
included. The unit will boot without either. However, you
need some means of input during the setup process.
The unit accepts a standard PC mouse and keyboard.
Connect them to the PS/2 or USB ports on the rear of
the machine.
An alternative, if mouse and keyboard are not available,
is to access the system remotely from another
computer. This is simple using the UltraVNC utility, after
connecting the two computers through an Ethernet
crossover cable. UltraVNC is included on the Player in
either a DOWNLOADS or UTILS directory.
When vncviewer.exe is copied to another computer and
run, you can use the other computer’s keyboard and
pointing device to work with the Player.
12
Preconfigured Players
Note: some USB Keyboards might not be
immediately recognized. Wait a few seconds and
the USB Keyboard should be recognized.
3.0.5
Connect to the network
Plug the network cable into the RJ-45 socket on the rear
of the unit.
Note: If you are using the input alternative as
described in the “Connect input devices” step, you
will need to postpone this step until the end of the
setup process.
3.0.6
Turn on power to Player and monitor
Turn on the monitor, and then turn on the Player by
pressing the power button on the unit.
3.0.7 Changing the password for the player account
& setting up auto-login
To secure the system against unauthorized access, the
default player password must be changed. The
autologin procedure that is set up on the Player requires
this change to be made in two places.
First, change the player password in the usual manner:
1. From Start -> XPe_System_Config, open
Computer Management.
2. Open the Local Users and Groups > Users
folder.
13
Preconfigured Players
3. Right-click on the IC5P account and choose
Set password.
4. Ignore the warning in the resulting dialog and
click Proceed.
5. Enter the new password in the New
Password and Confirm New Password
boxes. The password you use does not have
to be unique to the machine, but it should be
at least 8 characters and difficult to guess.
6. Click OK to store the new password.
Second, the auto-login password for the process that
automatically logs in under the IC5P account at boot
time must be changed to match. This password is stored
as a registry key. However, a utility is provided to allow
you to edit the key without using Regedit:
1. Start Notepad.
2. In Notepad - open the file:
C:\config.xpe\RegKeys\HLM\HLM_
EnableIC5PAutoLogon.reg
3. In the final line, starting with
“DefaultPassword”=, replace the word scala
inside the quotation marks with the same
password that you entered through Windows
Security.
4. Save the file.
14
Preconfigured Players
5. To setup the player to automatically login to
Windows using either account, double click
IC5P (for Player 5).
Click Yes in the resulting dialog to import the
information into the registry.
3.0.8
Give the Player its unique IP number
The Player needs to have a unique IP number.
Setting a static IP address is described here:
1. From Start > Settings > Network
Connections, choose the default connection
for the Player, Local Area Connection.
2. In the connection’s Status dialog, click the
Properties button.
3. In the Properties sheet, double-click Internet
Protocol (TCP/IP).
4. In the TCP/IP Properties sheet, you see the
default (DHCP) IP address for the machine.
Enter the IP number that has been assigned
for this Player in the IP address box. Subnet
and Gateway settings do not need to change.
5. Click OK and OK to close the two Properties
sheets.
15
Preconfigured Players
3.0.9
Give the Player its unique computer name
All Player machines need to have a unique computer
name on the network—for example, PLAYER101,
PLAYER102 and so on.
1. From Start -> XPe_System_Config, choose
System Properties.
2. On the System Properties sheet, go to the
Computer Name tab and click Change.
3. In the Computer Name Changes dialog,
enter the computer name that has been
assigned to this machine.
4. Click OK and OK to close the dialog and
Properties sheet.
3.0.10 Change the machine’s default Administrator
password
To secure the system against unauthorized access, the
default Administrator password must be changed.
The default Administrator password is: test
On XP Pro systems the following accounts have been
pre-installed:
16
Preconfigured Players
Username
Password
Optimized for:
Scala
scala
General Use
IC5D
scala
For Designer Use
IC5P
scala
Auto Starts Player
Postgres
postgres
Internal use for
SQL Server
First, change the Administrator password in the usual
manner:
1. From Start -> XPe_System_Config, open
Computer Management.
2. Open the Local Users and Groups > Users
folder.
3. Right-click on the Administrator account and
choose Set password.
4. Ignore the warning in the “Set Password for
Administrator” dialog and click Proceed.
5. Enter the new password in the New Password
and Confirm New Password fields. The
password you use does not have to be unique to
the machine, but it should be at least 8
characters and difficult to guess.
6. Click OK to store the new password.
17
Preconfigured Players
3.0.11 Change the UltraVNC password
The machine is configured to allow remote
administration through the UltraVNC tool. UltraVNC’s
access password must be changed from the default
“test” to prevent unauthorized access. You do so
through UltraVNC itself.
1. Double-click the UltraVNC icon in the system
tray.
2. In the UltraVNC Properties sheet that appears,
enter the new password for UltraVNC access in
the Password and Password (View only) boxes.
The password you use does not have to be
unique to the machine, but it should be at least 8
characters and difficult to guess.
3. Click OK.
3.1
Enable regular reboots
To ensure stable and reliable operation over extended
periods of 24-hour playback, Players must be rebooted
at least weekly. By default, the sample weekly reboot
script is set to reboot the player every Sunday at 05:30.
If this schedule is satisfactory, you can simply run the
script.
Should your installation requires a different reboot
schedule, the following command file utility is provided
let you easily specify it. You edit this text file to specify a
new day and time for reboots to occur:
18
Preconfigured Players
1. Start Notepad.
2. In Notepad, open this file:
C:\Tools\ScheduleWeeklyIC5PlayerReboot.cmd
3. The default Administrator password is test.
If you have changed the password, you must
also change the password listed after the switch
/RP.
4. Save the edited file under the same name and
close Notepad.
5. Run the .cmd file, either by double-clicking on it
in Windows Explorer or using Start > Run.
If daily rebooting is specified for Players in this
installation, you can use another supplied command file:
C:\Tools\ScheduleDailyIC5PlayerReboot.cmd
Only the scheduled reboot time is available for
modification.
Set the URL and Username/Password to the Content
Manager 5 system (Player 5 only)
Within the installation, it is recommended that Player 5
be configured to retrieve plans directly from Content
Manager 5. By default, the player is configured to
retrieve its plans from a local folder using Push To
Player.
19
Preconfigured Players
To change the settings, you use the Player
Configuration utility to do this.
1. Open the Player Configuration utility by choosing
Start -> Configure Player 5:
2. On the Network tab, click the Plan delivery popup.
Select Pull From Content Manager.
20
Preconfigured Players
3. Click the Content Manager Location button.
4. Protocol – Choose the protocol in which to
connect to Content Manager. The default is
HTTP. If Content Manager PC was for the
protocol choice.
5. URL: – Enter the URL to the Content Manager.
The URL that you enter is case sensitive.
Depending on how Content Manager was
configured, you may need to specify a port
number in the URL.
IE: http://myserver:8080/ContentManager (note
the port number in this case is 8080).
6. Username: – Enter the username used to
connect to Content Manager.
7. Password: – Enter the password that is
associated with the chosen username.
8. Confirm Password: – Re-enter the password that
is
associated with the chosen username.
9. Click OK to exit the dialog.
10. Click Refresh, this will search for any available
Networks AND Players which you can use.
11. If you have defined your players in Content
Manager, you can select the Player that you
want to use from the Player Name button.
21
Preconfigured Players
Note: Once you have chosen a player and it has
received a plan, you cannot use that player
definition for another player installation. If you wish
to do so, you must first Reset the Player Signature
using Content Manager. Please refer to the Content
Manager 5 User’s Guide for more information.
12. Polling Interval – By default the Player will poll
Content Manager once a minute for a new plan.
If you want to change the interval, you would do
so here. However, the polling interval cannot be
less than one minute.
13. Click OK to close the Player 5 Configuration
utility.
14. Verify that you can successfully send content to
the player (you may wish to preload content
before deploying the player).
If you encounter problems, please examine the player
log file by navigating to Start -> Player 5 Logs. Open
ic.log using a text editor (i.e. notepad). The most recent
log messages are at located at the end of the file.
Note: If the player is to be installed at a remote
location via the public internet, please check that
22
Preconfigured Players
the URL entered in step 5 is publically addressable
from the player’s location.
3.4
Set Player and Windows display modes
On a Player, the display modes for the Player and
Windows desktop mode can be set independently.
However, you should make the desktop display mode
match the Player if possible.
Doing so prevents unwanted display mode changes
when the system switches back and forth between
content playback and the Windows desktop.
When the Player software starts, the display mode
changes to the settings you specified. This mode cannot
change during playback regardless of the resolution of
the content.
Note: If the display adapter built-in to the Player
machine does not match with any modes the
monitor can display, a third-party display adapter
card may be used. A 3rd party display adapter is
only a viable option if the machine in question has a
PCIeX16, PEG, Graphics Card Slot.
You need to edit the display settings the Player
Configuration utility and in Windows. Windows setting
can be changed via Start ->XPe_System_Config >Display
3.5
Player 5 Display Configurations
Two Channel Player configurations are possible when:
23
Preconfigured Players
1. A machine has a Dual-Output graphics card and
that card is configured in a "horizontal spanning
mode". [the task bar extends across both
displays on the Windows Desktop]
2. A machine has a Dual-Output, or Single-Output,
graphics card and a Matrox "Dual Head 2 Go"
external GXM module is attached and
configured.
3. A machine has a Dual-Output graphics card and
that card is configured in "Dual View" mode-independent display mode. In this configuration
it is required that the Windows Desktop be
"Extended" to the secondary output--however
the Task Bar will remain only on the Primary
Display. In this mode each monitor can have
differing resolutions and refresh rates. Please
note that it will not be possible to have a
consistent "V_BLANK"/Video Frame
synchronization in this configuration--moving
objects on the secondary display will exhibit
"shearing" effects.
3.6
Single Channel Player
By picking either Window (Single Channel) or One
Screen (Single Channel), the options on this panel will
change depending on the chosen setting.
24
Preconfigured Players
3.6.1
Window (Single Channel) playback
To make the Player playback in a window:
1. Set Display Configuration: to Window (Single
Channel).
2. Select the desired Screen Orientation: (in 90
degree increments).
3. Using the Content Scaling: selector, choose
your desired method of filling the screen:
x
Fit Inside Display (Preserves Aspect
Ratio)
x
Fill and Trim to Display (Preserves
Aspect Ratio)
25
Preconfigured Players
x
3.8
Fill Display Exactly (which stretches the
script to the edges of the display
boundaries).
One Screen (Single Channel)
The default for playback is full screen.
To make scripts fill the screen when the Player is
started:
1. Set Display Configuration: to One Screen
(Single Channel).
2. To keep the display mode from changing
from the current Windows setting, turn on the
Same As Desktop? option.
26
Preconfigured Players
3. Using the Content Scaling: selector, choose
your desired method of filling the screen:
x Fit Inside Display (Preserves Aspect
Ratio)
3.9
x
Fill and Trim to Display (Preserves
Aspect Ratio)
x
Fill Display Exactly (which stretches the
script to the edges of the display
boundaries).
Custom Full Screen Playback
Player will allow any script to be played back with a
specified resolution, color depth, or refresh rate. An
example for using this customizable feature would be if
you were using a laptop computer which offered only
one display mode.
To ensure full screen playback in a particular display
mode:
1. Set Display Configuration: to One Screen
(Single Channel).
2. Click the Same As Desktop? button
(unchecked or Off ) to activate the selectors.
3. Choose the active Screen: as well as the
resolution and color depth you prefer, from
the Screen Settings: selector.
27
Preconfigured Players
4. Select the desired Screen Orientation: (in 90
degree increments)
5. Using the Content Scaling: selector, choose
your desired method of filling the screen:
4.0
x
Fit Inside Display (Preserves Aspect
Ratio)
x
Fill and Trim to Display (Preserves
Aspect Ratio)
x
Fill Display Exactly (which stretches the
script to the edges of the display
boundaries).
Two Channel Player
If the computer meets the two channel player criteria,
you can also pick one of these two channel choices:
x
Two Channel (Spanning)
x
Two Channel (Cloned)
x
Two Channel (Independent)
The options on this panel will change depending on
which setting is chosen.
28
Preconfigured Players
4.1
Two Channel (Spanning)
(Recommended for best two channel performance.)
4.1.1
Channel Options
1. Choose the correct Screen 1.
2. Choose the correct Screen 2.
3. Screen Settings: Choose the size and color
depth you prefer.
29
Preconfigured Players
4. Screen Layout: Choose the position in which
screen 1 is relative to screen 1. The options
are:
x
Screen 1 Left of Screen 2
x
Screen 1 Right of Screen 2
x
Screen 1 Below Screen 2
x
Screen 1 Above Screen 2
5. Select the desired Screen Orientation: (in 90
degree increments).
6. Using the Content Scaling: selector, choose
your desired method of filling the screen:
x
Fit Inside Display (Preserves Aspect
Ratio)
x
Fill and Trim to Display (Preserves
Aspect Ratio)
x
Fill Display Exactly (which stretches the
script to the edges of the display
boundaries).
30
Preconfigured Players
4.1.2 Single Channel – Two Output Configuration
Screen 1 Options
1. Choose the active Screen.
2. Screen Settings: Choose the size and color
depth you prefer.
3. Select the desired Screen Orientation: (in 90
degree increments)
4. Using the Content Scaling: selector, choose
your desired method of filling the screen:
x
Fit Inside Display (Preserves Aspect Ratio)
31
Preconfigured Players
x
Fill and Trim to Display (Preserves Aspect
Ratio)
x
Fill Display Exactly (which stretches the
script to the edges of the display
boundaries).
Screen 2 Options
1. Choose the correct Screen.
2. Screen Settings: Choose the size and color
depth you prefer.
3. Select the desired Screen Orientation: (in 90
degree increments)
4. Using the Content Scaling: selector, choose
your desired method of filling the screen:
x
Fit Inside Display (Preserves Aspect
Ratio)
x
Fill and Trim to Display (Preserves
Aspect Ratio)
x
Fill Display Exactly (which stretches the
script to the edges of the display
boundaries).
32
Preconfigured Players
4.1.3
Two Channel (Independent)
4.2
Channel 1 Options
1. Choose the correct Screen.
2. Screen Settings: Choose the size and color
depth you prefer.
3. Select the desired Screen Orientation: (in 90
degree increments).
4. Using the Content Scaling: selector, choose
your desired method of filling the screen:
33
Preconfigured Players
x
Fit Inside Display (Preserves Aspect
Ratio)
x
Fill and Trim to Display (Preserves
Aspect Ratio)
x
Fill Display Exactly (which stretches the
script to the edges of the display
boundaries).
5. Audio Hardware: Choose the audio device
that you want to use. The options are:
x
Default Sound Device
x
No Sound
x
<Name of your audio device>
6. Speakers: Choose the speakers you want to
use. The options are:
x
All
x
Stereo, Front Speakers
x
Stereo, Back Speakers
x
Mono, Front Left Speaker
x
Mono, Front Right Speaker
34
Preconfigured Players
4.3
x
Mono, Back Left Speaker
x
Mono, Back Right Speaker
Channel 2 Options
1. Choose the correct Screen.
2. Screen Settings: Choose the size and color
depth you prefer.
3. Select the desired Screen Orientation: (in 90
degree increments).
4. Using the Content Scaling: selector, choose
your desired method of filling the screen:
x
Fit Inside Display (Preserves Aspect
Ratio)
x
Fill and Trim to Display (Preserves
Aspect Ratio)
x
Fill Display Exactly (which stretches the
script to the edges of the display
boundaries).
5. Audio Hardware: Choose the audio device
that you want to use. The options are:
x
Default Sound Device
x
No Sound
x
<Name of your audio device>
35
Preconfigured Players
6. Speakers: Choose the speakers you want to
use. The options are:
x
All
x
Stereo, Front Speakers
x
Stereo, Back Speakers
x
Mono, Front Left Speaker
x
Mono, Front Right Speaker
x
Mono, Back Left Speaker
x
Mono, Back Right Speaker
4.2.1 Configuring audio in Two Channel
(Independent) mode
The Player Configuration utility allows you to pick an
audio device per channel when using Two Channel
(Independent) mode. For instance, you can have two
separate audio devices in your computer and dedicate
one to channel A and the other channel B.
However, many audio devices do not work in a multiple
audio device environment. This is especially true when
both audio devices use the same or similar chipsets. In
this case, Scala recommends using two different audio
devices - for instance, the computer’s motherboard
audio and a dedicated sound card.
36
Preconfigured Players
If you want to only use one audio device, each channel
can be configured to use a subset of connected
speakers. This must be configured correctly, otherwise
audio will not playback properly. Even if your audio
device asks you what speaker is connected to a
particular input, it typically does not modify the Windows
speaker setup.
In order to configure this properly, go to: Control Panel >
Sounds and Audio Devices. On the Volume tab, click
the Advanced button in Speaker settings. Click the
Speaker setup: popup menu to configure how many
speakers are attached to the audio device.
At least some hardware vendors have a custom control
panel applet to select the number of speakers. This
custom applet typically overrides the setting used
Sounds and Audio Devices.
5.0
Enable optional Scala EX modules
Scala EX modules are similar to drivers. Through EXes,
Player content can contain commands that control
external hardware. Several EX modules are included
with; others can be purchased separately.
Optional EXes need to be explicitly enabled and
configured. Those that are not included with must first
be installed. Whether your installation requires any
optional EXes should have already been established.
You need to have the program disc and manual for any
add-on EXes. Follow the instructions in the manual to
install and configure an add-on EX on the Player
machine.
37
Preconfigured Players
EXes that are included are listed in the Player
Configuration utility’s Playback tab. To enable any EXes
needed within your installation:
1. In the Optional EXes column of the Playback
tab, click on the necessary EX or EXes to
enable them. A checkmark appears on the
button of enabled EXes.
2. If a button for an EX that you enabled
appears in the EX Settings column on the
left, the EX needs to be configured. Click the
button in that column to open the EX’s
Options dialog.
3. Make any changes that are required.
5.0.1
Edit the Player’s MMOS.INI file if necessary
You might need to edit the Player’s MMOS.INI file.
Scala software checks the file MMOS.INI on startup for
special configuration instructions on Player software
startup. It exists to allow special-case modification to
various -specific default settings that are not exposed in
the GUI.
This file rarely needs to be edited, and should not be
edited unless necessary. Most lines in the default
MMOS.INI are commented out. Additional lines for
unusual circumstances can be added.
You should have been provided with information about
any MMOS.INI changes that need to be made by default
for your installation. If problems appear during initial
38
Preconfigured Players
tests or later field operation, you can try to deal with
them through MMOS.INI after adjustments through
Player Configuration, Windows, or hardware settings
have failed.
The MMOS.ini for Player 5 is located in the folder
D:\Program Files\Scala\ Player 5.
This file can be edited directly using Notepad.
Leave MMOS.INI as it is if you do not currently have any
instructions to the contrary.
5.0.2 Set up Player for automatic system clock
updates
For reliable update schedules, accurate logging, and
consistent operation throughout large networks, all
machines in a Network need to be synchronized to a
common time reference.
To configure the player’s time server:
1. Click Start -> Settings -> Control Panel.
2. Double click on Date and Time.
3. Click the Internet Time tab.
4. Check the option Automatically Synchronize
with an Internet Time server.
5. Enter in the server hostname or IP address.
6. Click Update Now, the OK.
39
Preconfigured Players
Note: Most installations should use either their
Network Manager or Content Manager server as
their master time server. All Players should
configure their time services to check that one
source. That source should in turn get its time
reference from the corporate ISP’s time server or
another public NTP time server.
5.0.3
Test playback and display
Play the Ready script to verify that playback works
smoothly and the display looks good. To do so, reboot
the machine which causes the Player software to autorun.
Press F1 to watch the looping series of demo videos
until it begins to repeat. If possible, attach speakers to
the Player’s audio jacks so that you can evaluate sound
playback as well. Note any audio or display problems.
5.0.4
Test basic network connectivity
To verify that your network connection is good:
1. Exit the Player software to Windows desktop
by pressing the Esc key.
2. Open a command prompt from the Start
menu.
3. Test for local connectivity by entering ping
<name>, replacing <name> with the
computer name of a machine on the local
area network that does not have a software
firewall that would drop ICMP packets.
40
Preconfigured Players
4. Good connectivity is shown by a series of
Reply messages, and failure by a series of
Request timed out messages.
You could also open Windows Explorer by opening My
Network Places and looking to see that the resources
available on your network—particularly the Content
Manager 5 server—are visible. (This only works if the
Network Manager computer or the Content Manager
computer is on the same network segment as the
Player.)
5.0.5
Alternative connection strategies
These instructions assume that your Player uses the
methods outlined above for communicating to the
Network Manager or Content Manager server.
Nevertheless, additional connection options are
available on the Player for those installations that
require them.
Setting the Player up for the wide variety of connections
other than those outlined above is not covered in this
guide. Consult the Content Manager 5 User’s Guide for
detailed instructions on alternative connection
strategies.
Your Scala Certified Partner can assist you in planning
custom Network solutions.
41
Preconfigured Players
More on display modes
The display mode to use in your installation is important
and should have been previously installed and
configured.
There are several basic factors to consider:
x
Screen resolution of the Player content
x
Resolution capabilities of the display
adapter in the
x
Player PC
x
Resolution capabilities of the monitor
used for playback in the field
x
Hardware costs in monitor selection and
display adapter selection
These factors combine to determine the quality and
consistency of content playback. Ideally, the resolution
of the content is always the same, and matches both the
display adapter’s capabilities and a supported resolution
of the monitor. For this reason, the monitor you use
during setup should be the same model that will be used
for deployed in the field.
5.1
Remote Desktop Connection
The Remote Desktop Connection (RDC) / Windows
Terminal Services is installed and enabled. To connect,
use the Microsoft RDC/TSAC Client 5.0 or better. The
standard Microsoft RDP uses TCP port #3389.
42
Preconfigured Players
Note: The Windows XPe Remote Desktop Client is
derived from Windows XP Professional.
When connecting to the player using this protocol,
the termination of the Player software by the switch
out will result in the reboot of the Player PC by the
"WatchDog" software component of the
Transmission Client.
This is turn causes the player to be rebooted. As a
result, this method of accessing the player should
only be used in limited administrative cases when
the player software is NOT running!
5.1.1
Tools to help with system administration
As a convenience for the system administrator, various
freeware/ shareware administrative utilities are located
in the directory C:\Tools. Some of these tools can
greatly help in remote administration and configuration
of machines that can only be accessed over a network.
These tools are not licensed and their use is subject to
each individual End User License Agreement. Please
read each “README.TXT” file in this directory for more
information.
6.0 Systems with Content Manager Preinstalled
Some Preconfigured systems may come pre-installed
with Scala 5 Content Manager. Content Manager runs
43
Preconfigured Players
as a set of background Operating System “Services”-also known as “daemons”. [non-interactive programs
that continuously execute in the background without the
machine being “logged in”] There are several “System
Administration” considerations for the use of CM5 that
one must be aware of.
Since this image is intended to meet the needs of
several “roles”--Scala Designer, Player,
ContentManager, etc. the “Content Manager 5
'services'”--Apache, MySQL, the Transmission Engine,
etc. are not enabled to start by default. On the [Start]
menu of the Admistrator user account there are links to
two scripts, “ENABLE Content Manager 5 Services” &
“DISABLE Content Manager 5 Services” that are located
in C:\Tools\.
6.0.1
Database Management
CM5 is a “Database-driven” application—it requires a
SQL database in order to function. This database can
be installed on the same machine as the CM5
programs—or located on an entirely separate computer.
For small/moderate InfoChannel 5 networks there is no
need for an independent, dedicated, Database Server.
For this machine the PostgreSQL database is preinstalled and pre-configured. The specific configuration
information for this installation is:
The Windows User Account/Password that is used by
the service: postgres/postgres
The “Admin/SuperUser” account of the PostgreSQL
database: postgres/PostGRES
44
Preconfigured Players
***This is a user account within the database and is
totally independent of the Operating System user
accounts!
Database communications are configured to occur on
the default TCP port of 5432 and are limited to
“localhost” connections only.
6.0.2
The Apache Tomcat HTTP Server
CM5 uses the “Apache” web server for its HTTP
communications for both the user Interface and IC5
Player communications. The default “Admin”
configuration password for this installation of Apache is
“scala”. Apache is configured to use TCP port 8080.
6.0.3
Content Manager 5
The default “Administrator” account for the CM5 install
is: “scala”. When the CM5 services are running the login
screen is reached via a web browser using the URL:
'http://localhost:8080/ContentManager'. [...the “Home”
button on the installed FireFox web browsers under the
“Administrator” user account is set to this location!]
Default Network Name: At installation, CM5 configures
its databases with a master “NETWORK_NAME”. This
can only be changed with a “re-install”/over-the-existinginstallation installation. If you wish to change this
“Default Network Name”--either run the CM5 installation
located under C:\DOWNLOADS\Scala5 or a more
current, post 4.0, updater version obtained from a
Service Pack CD or from the www.scala.com/updates
web page.
45
Preconfigured Players
CM5-related system directories:
F:\SCALA\Apache Software Foundation
F:\FTProot
--the default “Home Directory” of the “scala” FileZilla
FTP Server User Account.
F:\FTProot\InfoChannel_Content_Manager_5_DATA
--the default “Media Storage, Transmission Files, and
Log Files” directory tree for CM5.
D:\Program Files\Scala\Content Manager 5
F:\SCALA\PostgreSQL
F:\SCALA\PostgreSQL\8.3\data
--the location of the Database files where the CM5
information is stored.
7.0
Antivirus Considerations
7.0.1
AntiVirus Software:
This HD image does not contain any AntiVirus software.
Depending on the nature of your working/deployment
environment the addition of an AntiVirus product might
be beneficial. Currently Scala has tested the following
versions of these products:
46
Preconfigured Players
x
x
x
x
Symantec AntiVirus 2009
McAfee AntiVirus v.8.5i(Patch 6)
McAfee AntiVirus v.8.7i
Trend Micro PC-cillin 200[7|8]
Effectiveness:
Symantec and McAfee had the best AntiVirus protection
attributes. [Found 50 out of 50]
PC-cillin was close, but did miss a few older viruses in
our test sample. [Found 47 out of 50]
7.0.2
Performance
AntiVirus products have an important, in the context of a
running Scala Player 5, issue: they degrade the
performance of the computer that they are installed on.
In terms of CPU utilization and run-time memory usage,
the products placed as follows in our tests* [from best to
worst]: Symantec, McAfeeAV, Trend PC-cillin, F-Sec,,
CA-eTrust.
Note: Please note that these observations and
opinions are not intended to be any form of a
comprehensive product rating or ranking and are
not intended for any purpose other than anecdotal
commentary as a part of an informal discussion on
general IT security practices.
7.0.3
Stability
AntiVirus products have yet another impact on
computers: They tend to destabilize systems. Especially
47
Preconfigured Players
if they incorporate some form of software firewall. We
suggest that any computer running AntiVirus products
be configured for OS-Scheduled weekly or nightly
rebooting.
7.1 Windows XP’s Built-In Software
Firewall
Windows XP systems have a built-in software firewall
installed and enabled. Scala’s applications interact with
this software firewall and configure/registry their
networking ports appropriately. Other programs may
require that the appropriate TCP/UDP ports be made
available in order for them to function correctly. Please
see Microsoft’s documentation for additional information.
8.0
Advanced Topics
System Administration
There are some IT/System Management functions
that one might not want to perform entirely within
the Scala IC5/CM5 framework for one reason or
another. This pre-configured system is set up to
accommodate a variety of IT Management
preferences:
1. By default, all of the Player 5 configuration files
and System Log files are NOT placed in the
“Documents & Settings” directory–but in a
specific sub-directory of the FTP Server’s
“FTProot”. This configuration facilitates an “Out
Of Band” method for log file collection and IC5
48
Preconfigured Players
Player configuration file modification through the
use of FTP. [note: the initial configuration of this
system has the FileZilla FTP Server set to
“Manual” startup–if you wish to use FileZilla-FTP
you will need to configure it to start
“Automatically”]
2. Scala5 Designer and Player are “DirectX
Direct3D Exclusive Mode” applications. As such
they cannot function correctly with Windows XP’s
“Remote Desktop Connection/Terminal
Services.” The free Open Source remote control
program “UltraVNC” does function well with
InfoChannel 5. Distribution installers of this, and
other useful OSS/Shareware, programs are
provided in the directory C:\DOWNLOADS.
[note: for VNC to function correctly the DirectX9
Software Raster Renderer Library must be
copied into the particular program's application
directory--this library file is located under
C:\DOWNLOADS\Scala5\.]
3. The directory “C:\Tools” contains references of
various freeware or shareware command line
programs that we have found helpful over the
years. There is also a collection of sample
command line (.CMD) scripts for performing
various common tasks i.e.: Scheduling Reboots,
Archiving Log Files, etc. Several of the scripts
contained in this directory reference command
line utilities that are NOT contained in this
directory due to licensing limitations. These
tools, while freeware or shareware, have
licenses which limit their distribution. In order to
use some of the example .CMD scripts for the
49
Preconfigured Players
various tasks, the local IT Administrator will need
to obtain these programs and install them in this
directory.
NirCMD can be downloaded from:
http://www.nirsoft.net/utils/nircmd.html.
The PStools suite of utilities can be downloaded
from:
http://www.microsoft.com/technet/sysinternals/uti
lities/PsTools.mspx.
4. RSH: C:\DOWNLOADS\ contains a SourceForge
port of the UNIX RSHd tools for Windows. This
tools can be extremely useful in the hands of an
experienced System Administrator. Since this is
not a “secure” application in itself—it's use is
only appropriate on isolated/secure networks.
50
Preconfigured Players
9.0
Scala End User License Agreement
This Software License Agreement (“Agreement”) is entered into between Scala, Inc. (which, for purposes of this Agreement, shall be deemed to
include any majority owned subsidiary of Scala, Inc.) (“Scala”), and the purchaser, licensee or user (“Licensee”) of Scala Software (as defined
below). The terms of this Agreement also apply to any Scala Software Updates, and/or Software Maintenance (as each term is defi ned below)
for the Scala software, unless other terms accompany those items. If so, those terms apply.
READ THIS LICENSE CAREFULLY. BY OPENING THE SCALA SOFTWARE PRODUCT PACKAGING AND/OR USING THE SCALA
SOFTWARE, LICENSEE AGREES TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS AGREEMENT.
If Licensee does not agree to the terms of this Agreement prior to opening the Scala Software pac kaging or installing the Scala Software,
Licensee shall cease using (or refrain from commencing use of) the Scala Software, and shall, as applicable, uninstall and/or permanently delete
the Scala Software, Documentation (and any copies thereof) from the computers or computer system(s) on which the Scala Software has been
loaded or stored, and return the Scala Software and Documentation, all media on which it is stored, all product packaging, an d proof of payment
to the Scala Partner (as defined below) pursuant to such Scala Partner’s return policy. If Licensee does not agree to the terms of this Agreement,
and has acquired the Scala Software as part of a pre-configured computer system on which the Scala Software has been installed, Licensee
must either promptly cease using the Scala Software, uninstall and/or permanently delete the Scala Software and Documentation (and any
copies thereof) from the computer system(s) on which the Scala Software has been preloaded, or return the pre-configured system pursuant to
the system vendor’s return policy.
1.
1.1.
1.2.
1.3.
1.4.
1.5.
1.6.
1.7.
1.8.
1.9.
DEFINITIONS.
“Commencement Date” means the ship date of the Scala Software from Scala or a Scala Partner to the Licensee.
“Documentation” means the user guides, tutorials, printed instructions, reference manuals, and other explanatory
materials developed by Scala that accompany or are stored on or in the Scala Software for use in connection with
the Scala Software.
“End User” means, as applicable, Licensee or any person or entity (including, for the avoidance of doubt, any
employee or agent of Licensee) that uses the Scala Software.
“Object Code” means the form of Scala Software wherein computer programs are assembled or compiled in
magnetic or electronic binary form on software media, which are readable and usable by machines, but not
generally readable by humans without reverse-assembly, reverse-compiling, or reverse-engineering.
“Software Maintenance” means the provision of Software Updates.
“Scala Partner” means any Scala Certified Partner, reseller or distributor of Scala that sold or licensed the Scala
Software to Licensee.
“Scala Software” means, as applicable, the Object Code form of Scala Starter Kit, Scala Designer, Scala Player,
Scala Content Manager, Scala Broadcast Server, Scala Ad Manager or such other Scala software products as
may be identified in a purchase order from Scala or a Scala Partner, and shall be deemed to include the
Documentation for such Scala Software, the license keys, clip art, fonts and multimedia files included in such Scala
Software, their related software options, software extensions, software upgrades and Software Updates, and Third
Party Software integrated into such identified products.
“Software Updates” means bug fixes, documentation improvements and feature additions, including all major (i.e., numbered)
and minor (i.e., point) releases, when and if made available by Scala.
“Third Party Software” means software, referred to as redistributable code that is licensed to Scala by third party
licensors for redistribution with the Scala Software. The redistributable code is the property of Scala’s licensors,
and protected under United States and international copyright, trade secret or other proprietary rights laws, and
international treaties.
2.
GRANT OF LICENSE RIGHTS.
2.1
License. Subject to the terms, restrictions and limitations set forth herein, Scala hereby grants to Licensee a nonexclusive, non-transferable, non-sublicensable license to use (and to permit its End Users to use) the Object Code
version of the Scala Software, including any Third Party Software included therein or therewith, along with any
graphical, textual, pictorial, audio or visual works or materials incorporated into or delivered with the Scala
Software, including the Documentation.
2.2
Term. This Agreement is effective as of the date at which Licensee accepts the license terms as set forth above,
and will continue unless terminated as provided in Sections 7.3 or 8.
2.3.
Scope of License and Use
A.
Internal Use. Licensee may use the Scala Software and Documentation only for its own internal use and only on one,
single-user computer. Licensee may internally transfer the Scala Software to a different, single-user computer (a
“Transferred Installation”), provided that the Scala Software and any copies thereof are permanently uninstalled
and/or deleted from the computer from which the Scala Software is transferred.
B.
Limitations. In connection with the development of content files using Scala Software, Licensee may publish files for
playback (i) to an individual player; (ii) to an audio visual network of screens showing identical content controlled by
an individual player, and (iii) for preview and approval purposes over the web or other means. Notwithstanding the
above, Licensee shall not directly or indirectly, distribute or cause to be distributed over a network, content files
created with Scala Software without also having properly licensed Scala Software for playback purposes.
C.
Copies. Licensee may make one (1) copy of the Scala Software and one (1) copy of the related Documentation for
archival or back-up purposes, only.
D.
Third Party Software. The license granted hereunder includes the right of Licensee to use the Third Party Software in
Object Code form, solely in connection with the authorized operation and use of the Scala Software in
conformance with the terms and conditions of this Agreement. For the avoidance of doubt, Licensee may not
decouple, disassemble or otherwise separate the Third Party Software from the Scala Software or use the Third
Party Software except in connection with the use and operation of the Scala Software as permitted hereunder.
E.
Restrictions. The Scala Software is licensed, not sold. This Agreement only gives you some rights to use the Scala
Software. Scala reserves all other rights. Unless and solely to the extent otherwise permitted under applicable
law, you may use the Scala Software only as expressly permitted in this Agreement. Except as expressly
permitted under applicable law, or as otherwise agreed to in writing by Scala, Licensee shall not, and shall not
permit any End User to: (i) work around any technical limitations in the Scala Software; (ii) publish the Scala
Software for others to copy; (iii) make more copies of the Scala Software than authorized under this Agreement ;
(iv) sell, lease, rent, redistribute, assign, sublicense, or transfer the Scala Software and/or Third Party Software; (v)
reproduce, decompile, reverse engineer or disassemble the Scala Software and/or Third Party Software; (vi) offer
the use of the Scala Software to third parties as an application service provider, service bureau or remote-hosted
service; or (vii) deliver, export, transfer or otherwise distribute the Scala Software acquired hereunder to, or use the
Scala Software acquired hereunder in, a country other than the country in which the Scala Software was
purchased (including, for the avoidance of doubt, in connection with a Transferred Installation).
51
Preconfigured Players
3.
LICENSE AND OTHER FEES. Licensee agrees to be bound by and pay the license fee(s) set forth in the Scala
Software price list in effect as of the date of purchase. License fees for Scala Software and maintenance fees for
Software Maintenance may be updated and changed at any time.
3.1
Software Maintenance Coverage. Where Software Maintenance is offered upon separate purchase terms from
the Scala Software, the Scala Software products are sold with one (1) year (the “Initial Maintenance Term”) of
Software Maintenance coverage included in the price of the product. During the Initial Maintenance Term,
Licensee shall be entitled to Software Updates if and when made available by Scala. All use of Scala Software
provided pursuant to Software Maintenance coverage shall be subject to the terms of this Agreement. Licensee
may elect to continue Software Maintenance beyond the Initial Maintenance Term, subject to availability, upon
payment to Scala (or, as applicable, a Scala Partner) of the Scala annual maintenance fee in effect at the time of
renewal.
3.2
Taxes and Duties. Prices to Licensee do not include taxes, duties, tariffs, handling fees, or other such
assessments of any nature. Whenever imposed, such assessments are payable by Licensee. Income or other
taxes that are required to be paid or withheld by Licensee or Scala under the laws of jurisdictions other than the
United States, in connection with the license and other fees paid by Licensee hereunder, are the sole obligation of
Licensee and shall be exclusive of the license and other fees paid by Licensee.
3.3
Other Services. Licensee acknowledges that any additional services offered by Scala, such as installation,
customization or professional services, are not provided under this Agreement, and any such services to be
provided by Scala (or, as applicable, a Scala Partner) shall be subject to the mutual agreement of the parties, the
terms and conditions for which shall be set forth in a separate agreement.
4.
CONFIDENTIAL INFORMATION, TITLE AND COPYRIGHTS.
4.1
Licensee acknowledges that the Scala Software, Documentation, Software Updates, enhancements, modifications,
additions, new releases of or to the Scala Software contain confidential information of, are trade secrets of, and are
proprietary to Scala and its licensors and that title to such materials is and shall remain in Scala and its licensors,
as the case may be. Licensee shall maintain in strict confidence the Scala confidential information, but, at a
minimum, to take those precautions that it utilizes to protect its own confidential information. Licensee sh all have
no obligation of confidentiality with respect to information that (i) at the time of disclosure is in or becomes available
to the public through no breach of this Agreement on the part of the Licensee; (ii) was lawfully in Licensee’s
possession prior to receipt from Scala; (iii) is received independently from a third party free to lawfully disclose
such confidential information to Licensee and who does not owe an obligation to Scala with respect to confidential
information; (iv) Licensee independently develops without the benefit of any confidential information disclosed
hereunder or (v) is required to be disclosed by a government agency; provided that the Licensee will use best
efforts to minimize such disclosure and will notify Scala promptly of any such demand, order or judgment in order
to permit Scala to seek an appropriate protective order.
4.2
All applicable rights to patents, copyrights, trademarks and trade secrets in the Scala Software and other
proprietary materials are and shall remain in Scala and its licensors. Licensee shall not assert any right, title or
interest in the Scala Software or other materials provided to Licensee under this Agreement, except for the limited
license rights expressly granted to Licensee hereunder.
4.3
Licensee shall not obscure or remove any copyright or other proprietary notice or legend contained on or included
in the Scala Software and shall reproduce all such information on all copies made hereunder. Licensee shall not,
directly or indirectly, disclose or distribute any technical information of Scala provided with or in the Scala Software
without the prior written consent of Scala, which consent may be withheld at Scala’s sole discretion.
5.
5.1
LIMITED WARRANTIES.
Media and Documentation. Scala warrants that if the media or Documentation is in a damaged or physically
defective condition at the time the Scala Software is delivered to Licensee, and if such media or Documentation is
returned to Scala within thirty (30) days of the effective date of this Agreement, Scala will provide Licensee with a
replacement at no charge.
5.2
Software Limited Warranty and Remedy.
A.
Provided that Licensee is not in breach of any of its obligations under this Agreement, and in addition to the warranty set
forth in Section 5.1, Scala warrants for a period of thirty (30) days from the Commencement Date (“Warranty
Period”), that the software will substantially conform to the Documentation provided by Scala with the Scala
Software. Licensee’s sole remedy and Scala’s and Scala Partner’s sole obligation under this Agreement for
breach of this warranty is, at Scala’s sole option, (i) the remedy of the nonconformity or (ii) the authorization of a
refund for the price paid for the media and or Scala Software by Scala or the Scala Partner from which the Scala
Software was originally obtained. Any request for the above remedies must be made within the Warranty Period
and proof of purchase (i.e., copy of the invoice or receipt) is required to be presented to Scala. In the event of a
refund, this Agreement will immediately terminate without further notice, and Licensee will have no further rights or
license to use Scala Software or Documentation.
B.
Any replacement software or media will be warranted for the remainder of the original Warranty Period or for an
additional thirty (30) days whichever is longer.
C.
This limited warranty is void if nonconformance of the Scala Software results from or is related to the (i) improper
installation or operation of the Scala Software by or on behalf of the Licensee, (ii) failure of Licensee’s hardware or
non-Scala software, (iii) incompatibility of such hardware and non-Scala software systems with Scala Software, (iv)
alteration, modification or unauthorized integration of Scala Software by or on behalf of Licensee, or (v) accident,
abuse or misapplication of Scala Software.
D.
If the Scala Software is provided as a trial or evaluation version, the grant of the license to use the Software shall
be on an “AS IS” basis and subject to the express limitations of the trial. Unless Licensee shall have entered into a
separate written license agreement prior to the expiration or termination of the trial period, Licensee agrees to
cease all use of the Scala Software provided on a trial or evaluation basis and to return such Scala Software, or to
return any license keys and destroy or permanently delete any and all copies of such Scala Software.
5.3
Disclaimer of Warranties. SCALA AND ITS LICENSORS MAKE NO WARRANTY, REPRESENTATION OR
PROMISE EXCEPT AS SPECIFICALLY SET FORTH IN THIS AGREEMENT. TO THE FULLEST EXTENT
PERMITTED BY LAW, SCALA AND ITS LICENSORS DISCLAIM AND EXCLUDE ANY AND ALL OTHER
WARRANTIES, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR RESULTS. SCALA AND ITS LICENSORS DO NOT WARRANT
THAT THE SCALA SOFTWARE OR DOCUMENTATION WILL SATISFY LICENSEE’S REQUIREMENTS; THAT
THE SCALA SOFTWARE AND DOCUMENTATION ARE WITHOUT DEFECT OR ERROR; OR THAT THE
OPERATION OF THE SCALA SOFTWARE WILL BE UNINTERRUPTED. TO THE MAXIMUM EXTENT
PERMITTED UNDER THE LAW, THE UN CONVENTION FOR THE SALE OF GOODS AND THE UNIFORM
COMMERCIAL CODE DO NOT APPLY TO THIS LICENSE AGREEMENT.
6.
LIMITATION OF LIABILITY.
52
Preconfigured Players
6.1
IN NO EVENT SHALL SCALA OR ITS LICENSORS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT,
PUNITIVE OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION,
DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS
INFORMATION, OR ANY OTHER PECUNIARY LOSS). REGARDLESS OF WHETHER SCALA HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. TO THE MAXIMUM EXTENT PERMITTED BY LAW,
SCALA’S AGGREGATE LIABILITY ARISING FROM OR RELATING TO THIS LICENSE OR THE SCALA
SOFTWARE AND DOCUMENTATION IS LIMITED TO THE AMOUNT ACTUALLY PAID FOR THE LICENSE.
SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR
CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION OR EXCLUSION MAY NOT APPLY.
7.
INDEMNIFICATION.
Scala’s Obligation. Subject to the Licensee indemnification set forth at Section 7.2 and the restrictions and
limitations set forth herein, Scala shall indemnify and hold harmless Licensee, its officers, directors and employees
from and against any costs or demands awarded against Licensee by a court of competent jurisdiction pursuant to
a final judgment as a result of a claim or action by a third party against Licensee that the Scala Software or
Documentation infringes a registered copyright, trademark, valid patent or other intellectual property right of a third
party in North America, European Economic Area or Japan. The foregoing indemnity is conditioned on Licensee (i)
promptly notifying Scala of such claim; (ii) permitting Scala to control the response thereto and the defense thereof,
including any agreement relating to the settlement thereof, and (iii) assisting and cooperating with Scala, at Scala’s
expense, in the defense or settlement thereof. Licensee may participate, at its own expense, in such defense
directly or through counsel of its choice on a monitoring, non-controlling basis. Scala shall obtain Licensee’s prior
written consent to any compromise or settlement of any claim which would require an admission of liability on the
part of Licensee or which would subject Licensee to any injunction or other equitable relief . Notwithstanding the
foregoing, in no event shall Scala or its licensors be liable to indemnify, defend, settle or hold Licensee harmless
from and against any or all claims which allege infringement of intellectual property that reads upon or is infringed
by a generally recognized audio, video, technology or patent standard, including without limitation MPEG-1,
MPEG-2, MPEG-4, JPEG, DV, Flash, VC-1, AAC, AC-3, DVCPRO or AVS (each including all profiles, options,
parts or levels);
Scala shall have no obligation under Section 7.1, and otherwise will have no liability for, any claim of infringement
caused or alleged to be caused by: (i) the use or combination of the Scala Software with non-Scala software,
hardware, data, or content, including but not limited to software, hardware, data, or content of Licensee; (ii)
infringement that would have been avoided without the use or combination of the Scala Software with other nonScala software, hardware, content, or data; (iii) the presence of any alteration or modification of the Scala Software
by Licensee or any third party acting on Licensee's behalf; or (iv) the Licensee's continuing the allegedly infringing
activity after being notified thereof or after being informed and provided with modifications that would have avoided
the alleged infringement.
In the event that a claim of infringement of a valid North American, European Economic Area or Japanese software
patent or copyright is made against Scala or Licensee or if Scala reasonably believes that such a claim will be
made, Scala, at its option and in lieu of indemnification, may (a) procure for Licensee the right to use the Scala
Software without patent or copyright infringement; (b) modify the Scala Software to make it non-infringing; (c)
replace the Scala Software with substantially equivalent software that is non-infringing; or (d) direct Licensee to
cease use of the Scala Software, and refund to Licensee a percentage of the aggregate fees received for such
Scala Software that are the subject of such a claim, based on a five (5) year straight line depreciation
The foregoing Sections 7.1-7.3 set forth the exclusive remedy and entire liability and obligation of Scala with
respect to third party claims against Licensee alleging intellectual property infringement or misappropriation.
7.1
7.2
7.3
7.4
7.5
Licensee Obligation. Except for the infringement claims set forth in Section 7.1, Licensee shall indemnify, defend
and hold Scala, its directors, officers, agents and employees harmless from any claims, demands, or causes of
action whatsoever by a third party against Scala arising as a result of Licensee’s use or operation of the Scala
Software. For the avoidance of doubt, and without limiting the scope of the immediately preceding sentence,
Licensee shall indemnify, defend and hold Scala, its directors, officers, agents and employees harmless from any
third party claims, demands, or causes of action whatsoever arising from or related to the display, broadcast,
reproduction, performance or other use or distribution of audio, visual, graphical and textual information developed
by or on behalf of Licensee and not included in the Scala Software.
8.
TERMINATION.
8.1
By Licensee. Licensee may terminate this Agreement at any time without notice to Scala. The license fee is not
refundable and Scala will have no obligation to refund any amounts paid by Licensee under this Agreement upon
its termination (except for any right of refund as set forth in Sections 5 and 7.3).
8.2
Scala. Scala may terminate this Agreement and all licenses granted hereunder upon thirty (30) days prior written
notice if Licensee fails to comply with any of the terms and conditions of this Agreement or any Schedule to this
Agreement, and such noncompliance is not cured within such thirty (30) day period.
8.3
Return of Software. Upon any termination of this Agreement, Licensee must cease all use of the Scala Software,
and return to Scala all copies of the Scala Software, including license keys, together with the Documentation, or
shall return all license keys and certify to Scala’s reasonable satisfaction the destruction or permanent deletion of
all copies of the Scala Software and Documentation from its computer systems.
9.
GENERAL.
9.1
Audit Rights. Scala shall have the right reasonably to audit the deployment and use of the Scala Software by
Licensee, including without limitation Licensee’s conformance with the provisions of Section 3 herein. Licensee
agrees to cooperate with Scala’s reasonable request for access to Licensee’s computer systems to ensure
Licensee’s adherence with the license terms hereunder.
9.2
Purchase in Canada. If Licensee acquired this software in Canada, Licensee agrees to the following: The parties
hereto have expressly required that the present Agreement and any exhibits hereto be drawn up in the English
language. / Les parties aux présentes ont expressément exigé que la présente convention et ses Annexes soient
rédigées en langue anglaise.
9.3
Notices. Any notice required or permitted to be given by Licensee hereunder shall be in writing and shall be
deemed to have been duly given (i) upon hand delivery, (ii) on the third day following delivery to the postal service
as certified mail, return receipt requested and postage prepaid, or (iii) on the first day following delivery t o a
recognized overnight courier service, fee prepaid and return receipt or other confirmation of delivery requested.
Any such notice shall be delivered or sent to Scala at the address as set forth below, or to such other address as
Scala may designate from time to time. Scala, Inc., 350 Eagleview Boulevard, Suite 150, Exton, PA 19341,
USA.
NOTICE ABOUT THE MPEG-2 VISUAL STANDARD. This software may include MPEG-2 visual decoding
technology. MPEG LA, L.L.C. requires this notice: USE OF THIS PRODUCT IN ANY MANNER THAT COMPLIES
WITH THE MPEG 2 VISUAL STANDARD IS PROHIBITED, EXCEPT FOR USE DIRECTLY RELATED TO (A)
DATA OR INFORMATION (i) GENERATED BY AND OBTAINED WITHOUT CHARGE FROM A CONSUMER
NOT THEREBY ENGAGED IN A BUSINESS ENTERPRISE, AND (ii) FOR PERSONAL USE ONLY; AND (B)
OTHER USES SPECIFICALLY AND SEPARATELY LICENSED BY MPEG LA, L.L.C. If you have questions about
53
Preconfigured Players
the MPEG-2 visual standard, please contact MPEG LA, L.L.C., 250 Steele Street, Suite 300, Denver, Colorado
80206; http://www.mpegla.com.
NOTICE ABOUT THE AVC VISUAL STANDARD. This software may include AVC visual decoding technology.
MPEG LA, L.L.C. requires this notice: THIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO
LICENSE FOR THE PERSONAL AND NONCOMMERCIAL USE OF A CONSUMER TO (i) ENCODE VIDEO IN
COMPLIANCE WITH THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC VIDEO THAT WAS
ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL ACTIVITY AND/OR WAS
OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR
SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG
LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM
9.4
9.5
Governing Law.
A. United States Sales. If you acquired the Scala Software in the United States, Pennsylvania state law governs
the interpretation of this agreement and applies to claims for breach of it, regardless of conflict of laws principles.
B. Sales Outside the United States. If you acquired the Scala Software in any other country outside the United
States, the laws of the country of the majority-owned Scala subsidiary that sold the Scala Software to you applies,
regardless of such country’s conflicts of law provisions.
Legal Effect. This Agreement describes certain legal rights. You may have other rights under the laws of your
state or country. You may also have rights with respect to the party from whom you acquired the Scala Software.
This Agreement does not change your rights under the laws of your state or country if the laws of your state or
country do not permit it to do so.
9.6
U.S. Government Restricted Rights Legend. The Scala Software, hardware, and Documentation provided
under this Agreement bear restricted rights. Use, duplication, or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the rights in technical data and computer software clause at
DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of the Commercial Computer Software Restricted Rights
clause at 48 CFR 52.277-19, as applicable. Scala, Inc., 350 Eagleview Boulevard, Suite 150; Exton, PA 19341
USA.
9.7
Assignment. Neither party may assign any rights, duties, obligations or privileges under this Agreement without
the prior written consent of the other party. A change of control or ownership shall not be deemed to be an
assignment under this Section so long as the new owner has expressly assumed in writing all of the duties and
obligations of the assignor and further provided, that Licensee shall remain liable and responsible to Scala (and its
licensors) for the performance and observance of all such duties and obligations.
9.8
Severability. Should any part or provision of this Agreement be held unenforceable or in conflict with the law of
any jurisdiction, the validity of the remaining parts or provisions shall not be affected by such holding.
9.9
Limitation on Effect of Waiver. Failure on the part of Scala to exercise, or Scala’s delay in exercising, any of
Scala’s rights hereunder shall not be construed as a waiver or waiver of other breaches of this Agreement. Any
single or partial exercise by a party of any right shall not preclude any other or future exercise thereof or the
exercise of any other right in the Agreement.
9.10
Entire Agreement. This Agreement contains the entire understanding of the parties with respect to the
transactions contemplated and supersedes any prior agreements or understandings among the parties with
respect to the subject matter hereof. This Agreement may be amended only by a writing that refers to this
Agreement and is signed by both parties.
9.11
Export Law Assurances. Licensee acknowledges that the Scala Software included herewith is subject to
restrictions and controls imposed under the U.S. Export Administration Act and Canadian Exportation Laws.
Licensee must comply with all domestic and international export laws and regulations that apply to the software.
These laws include restrictions on destinations, end users and end use. Licensee hereby expressly agrees to
defend, hold harmless and indemnify Scala, its directors, officers, and employees, from any claim, suit or dispute
alleging that Licensee has exported the Scala Software in violation of any domestic or international export laws.
9.12
Construction. The headings in this Agreement are for convenience of the parties only. They do not constitute a
portion of this Agreement and shall not be used in interpreting the construction of this Agreement.
9.13
Third Party Beneficiary. Licensee hereby agrees that the licensors of Third Party Software shall be considered
third party beneficiaries of this Agreement and shall be entitled to bring a direct action against Licensee in the
event of breach of any applicable provisions of this Agreement, pursuant to the terms and conditions of this
Agreement.
9.14
Force Majeure. Neither party shall be in default if failure to perform any obligation hereunder is caused solely by
unforeseen supervening conditions beyond that party’s reasonable control, which could not have been prevented
by the non-performing party’s reasonable precautions, commercially accepted processes or substitute services,
including acts of God, civil disturbances, strikes and labor disputes.
9.15
Negation of Agency and Similar Relationships. Nothing contained in this Agreement shall be deemed to create
an agency, joint venture or partnership relationship.
54