Scala Media Players
You can find step-by-step instructions in the Setting up the SMP-S Device.
You can get support for Scala Media Players through your regular Scala support channels. See Services & Support for more information.
The first time you start up your Scala Media Player-S it may present a message that says:
The Recycle Bin on D:\ is corrupted.
Do you want to empty the Recycle Bin for this drive?
This issue affects a small number of units, and is a side-effect of how these systems were imaged. Simply click Yes, and the issue will be resolved. There is in fact no underlying data corruption.
The type of content you can display depends on the Player license. The Scala Media Player-S is normally paired with the Single HD player license, which supports playback of:
The intensity of content you can display depends on the Player hardware capabilities, number of screen zones, and so on. The Scala Media Player-S is powerful enough to display a wide range of dynamic and powerful content. It is a best practice to always test your content on the intended media players before deploying the content.
The Scala Media Player-S has about 33 GB available on its D: drive for content and related files.
How much content you can use depends on how often the content files actually change. This is because:
As a rule of thumb, a total content size of 1/2 to 1/3 the total available is fine, meaning 11 GB to 16 GB is a safe amount of content. The actual limit can be a lot higher or lower in cases of extreme content update patterns. Here are some examples:
Pattern of full daily change of content: Say you always have 5 GB of content, and it is fully replaced with a new 5 GB every day. In this example, you would need 10 GB of storage.
A media player is a very dynamic system. Although Scala designs and tests these systems to run for many weeks with complex content, there is always a small probability of degradation over time. To keep systems running smoothly, it is a best practice to schedule a weekly reboot. There are configuration scripts on the Scala Media Player to do this, or you can schedule reboots from Content Manager.
Windows 10 IoT has a feature called Unified Write Filter (UWF) that protects against unintended modifications to important files and registry settings, including most of the operating system. Any accidental or malicious changes to these files will appear to apply, but do not actually modify the on-disk copies, and are automatically undone at the next system restart.
As part of the security defense in depth of Scala Media Players, we recommend that UWF be enabled. This means that when you intend to make changes to the configuration or other important files and registry values, you need to turn off UWF before making those changes, and turn it back on after. We provide a script
C:\Tools\Disable_UWF_C.CMD to turn off UWF, and a reboot is then required for it to take effect. You can make your changes, and then use the companion script
C:\Tools\Enable_UWF_C.CMD to turn UWF back on, then reboot for that to take effect.
When using Content Manager maintenance jobs to modify protected files, such as when installing a Microsoft hotfix, you need to follow a specific sequence of steps to temporarily disable UWF in order for the changes to persist. See Remote Installation of Microsoft Hotfixes on a Player for more information.
Since UWF protects important files and registry values, any maintenance jobs that are designed to modify protected files should take this into account. Please follow the procedure described in Remote Maintenance on Players That Use Write Filters.
Unlike most versions of Windows 10, Windows 10 IoT allows rich control over whether and when Windows Updates are applied. On Scala Media Players, Windows Update is disabled by default for several reasons:
For instructions on how to remotely apply a specific Windows Update using Scala Enterprise Content Manager, see Remote Installation of Microsoft Hotfixes on a Player.
As configured, Scala Media Players do not any any antivirus or antimalware software enabled. Because the threat model of a digital signage network is very different than a PC used to access arbitrary web sites and documents, this is often the most appropriate choice, with antivirus and antimalware in place instead at the point of entry, namely Scala Enterprise Content Manager.
Should circumstances or policy dictate that antivirus software be used, a duly-licensed solution can be installed and enabled prior to deployment. Considerations include:
When adding or updating antivirus software, it is recommended you perform testing for stability and performance to ensure no negative effects. In addition, it is recommended to schedule nightly or weekly restarts of the Scala Media Player in order to help preserve stability.
Note that if you enable Windows Defender, it will not receive virus/malware definition updates unless you also enable Windows Update.
You can configure Player to require a numeric password after hitting <Escape> in order to exit playback. In your MMOS.INI file, set
To exit, you must then type <Esc> 12345 <Enter>. The password can be any number from 1 to approximately 4.2 billion.
Typically, you should also disable the Window close function (Alt+F4):
Storage devices only: To prevent Windows from accessing USB storage devices, use the registry editor, as follows:
To reverse this, change the registry value-data back to 3.
All devices: Using the Windows Group Policy feature, it is possible to blacklist all devices (including keyboards and mice), and even whitelist specific input devices from specific vendors.
Normally, if the HDMI cable is removed while a computer is running, Windows notices the loss of display and will reset the configured display mode settings.
The Scala Media Player–S is equipped with a Display Continuity toggle push-button. When the Display Continuity push-button is pushed in, the system will not notice the loss of cable, allowing the display mode settings to persist. When the Display Continuity push-button is out, the system behaves normally. You should configure your media player with the Display Continuity button in its out state, then push it in.
Generally, you can expect higher performance and stability if you use the Scala Player Configuration tool to set the display mode for 90 or 270 degree rotation, compared to using the device driver display rotation feature.
As configured, you can use either TightVNC or Remote Desktop to remotely access a Scala Media Player, unless these have been disabled. TightVNC lets you remotely access the Player's screen, keyboard, and mouse exactly as if you were at the media player. While TightVNC is connected, the player will continue to display its normal content, and you can see this content remotely although the update rate through TightVNC is not as smooth as being on site. If you escape out of playback to perform maintenance, any maintenance or diagnostic actions you perform will be visible to those who can see the display on site.
By contrast, a Remote Desktop connection will cause the local display to switch to the Windows account lock screen, and your remote access will show the Windows desktop. However, at the end of your Remote Desktop session, the local session will not log back in automatically. Therefore, Remote Desktop is suitable mostly for administrative cases when the Player is not running or does not need to be running. Your final action should be to remotely reboot the player, so that content playback will restart.
The way SSD storage works, each data cell can be re-written thousands of times, but there is a limit. By reserving some space, the drive can perform "wear-leveling", which means that the drive intelligently moves data around to maximize the overall working life of the drive, and to replace any cell that has reached its limit. In the partition manager, this reserved space appears as unallocated.
The Windows UWF feature requires that the paging file (virtual memory storage) be on a partition that does not have UWF protection. Therefore, a second partition is needed. On Scala Media Players, we also place the content and configuration folders for the Scala Player application, as well as various temporary files, on this second partition.
In addition to various operating system components and the Scala Player application, the system comes with installers for or links to some useful third-party software. Look in
Please contact your Scala representative for more information.
To restore the Scala Media Player image to its original defaults, follow these steps:
The Scala Media Player-S has many BIOS settings. Specific settings to note include:
The Linux Playback Engine only supports Feature Based Licenses.
For more information about compatible licenses, see the License Functionality Matrix.
The Linux Playback Engine is only available for use on the Scala Media Player-S.
Use the same basic steps as creating a Windows player.
1080p (1920 x 1080) / 2,073,600 pixels
The Linux Playback Engine supports most page and element transitions.
There are some limitations when using WebClip video. For more information, see Designing Content for Scala Enterprise.
The Linux Playback Engine does not support Windows Script Host languages.