Release 10.2 is now available for Content Manager, Playback Audit Parser, Designer, Player, Broadcast Server, Publish Automation EX and IAdea Android Players.
Hi, we’re pleased to announce our latest release, available at www.scala.com/updates
Multiple Products Release 10.2
Scala Enterprise Content Manager Release 10.2
Scala Designer and Scala Player Release 10.2
- The Web Clip element now supports multi-touch.
- Multiple Web Clip elements at the same time is now supported.
- The Web Clip element now supports playback of H.264 video within the web page.
- The Web Clip element now supports HTML drop-down menus / lists.
- The Web Clip element now has a Scrollbars() option.
- The Web Clip element now has an Interactive() option, that governs whether the Web Clip receives input and has a mouse-pointer.
- The Web Clip element now supports web pages with alpha-transparency, through the new CMode(opaque|transparent) option that controls the composition mode.
- Improved visual performance of Web Clip content.
- The Text element and TextCrawl element now support inline images. (Currently supported with the standard text-engine, not yet supported with the Complex Writing Systems engine.)
- For Text Crawl elements, now support a separator image that gets added between crawl-segments.
- The Box element now supports various corner styles (normal, rounded, angled, scooped, or notched), making it possible to have rounded rectangles and other useful shapes.
- ScalaScript variable names may now contain Unicode characters. Since variable names are used as the field-names when creating Scala templates, that helps get the template forms in Content Manager to be in the user’s own language.
- When defining a Text Crawl element, the text source may now be a variable, which can be an array variable.
- The Frame() command now supports the same If() parameter that most commands support.
- In ScalaScript, the various string-comparison operators have always been case-insensitive. This now works case-insensitively for Unicode strings too (i.e., accented or international characters are also treated case-insensitively).
- Fixed a problem where certain unusual compression formats in MOV or MP4 containers were not supported.
- Updated video playback to use FFMPEG version 2.1.1.
- Updated Web Clip playback to use Chromium version 31.1650.
- Playback now uses less memory when hardware-accelerated video is being used.
- The “User-Agent” string used for WebClip can be customized using the MMOS.INI setting:
- Added a new Python module named scws2 that wraps the “Version 2.0″ REST-based Content Manager Enterprise APIs.
- window.ScalaGetVariable(“variable-name“): Returns the value of the given Player metadata variable. (window.ScalaGetMetaDataValue() is a synonym.)
- window.ScalaDone(): Signals to playback that the web content is done, and the script or playlist can move on.
- Fixed a problem in the Data Source module where it would loop incorrectly when using a Custom Step Size.
- Fixed a problem where streaming of certain 60fps H.264 or MPEG-2 videos could stutter.
- Fixed a problem where certain H.264 streams could temporarily freeze for a few seconds.
- Fixed a problem where 60fps transport streams could gradually lose audio/video sync over time.
- Fixed an occasional crash cleaning up a Web Clip.
- Fixed a bug where the Python installer could fail on certain systems that had spaces in the path of both the installation folder and the Windows temporary folder,
- Removed an incorrect and unneeded parameter from the StreamingVideoStyle() and StreamingVideoClipStyle() commands.
- In some cases, the Caps option could do the wrong thing for non-English lower-case letters. This is now fixed.
- Fixed a problem in the scws Python module that could result in a “TypeError: None not callable” error.
Scala Designer Release 10.2
Scala Player Release 10.2
Scala Android Player Release 10.2
- Optimized Player logging and database activity for better long term behavior on Flash-memory devices. Note: Use of Diagnostic level logging can produce very large logs, and therefore should only be used during active debugging. (Otherwise, free storage on the player, and Flash-memory wear, could become a problem.)
- Log files and related files are now kept on the device’s internal storage instead of any SD card (helps with Flash-memory wear-leveling.)
- If you schedule a Message to an Android Player, it will display as a sequence of still-images.
- The Android Player now includes a watchdog that monitors various components of playback and communication, and will restart the media player if any of those components appear to be frozen.
- Reworked the Player Configuration screens to be more usable and generally better.
- The Player Configuration now has options to enable the player watchdog, and set the billing logs queue size and the status logs queue size.
- Cookies are now persisted by the HTML environment of the Player.
- In the event of a Player crash, the error report now includes a more complete stack trace, which can help Scala debug certain types of issue.
- On the IAdea Android Media Players, the auto-start and nightly reboot is controlled by the Android system properties, rather than by the Player application.
- Improved the recording of version/build information into the Player log and the status reports to Content Manager.
- When Android Players process maintenance jobs, the Retry Until date is now supported.
- Reimplemented how Android Players store local data, for improved robustness.
- The APK update on IAdea Players now handles low disk space properly.
- Fixed a problem where players could stop sending heartbeats.
- Fixed a potential hang that could occur if network connectivity was lost just after starting to download a piece of content.
- Fixed how the Player boot time is reported to Content Manager, so that Content Manager will correctly display it.
- Fixed the behavior of the HTML <select> element on Android 2.x devices.
- Fixed how the Player reports its build date, so that information is correctly displayed in Content Manager.
- Fixed a problem where cleanup might not occur on the Player’s Content folder.
Scala Samsung Smart Signage Player Release 10.2
- The Samsung Player can now connect to Content Manager via HTTPS.
- If you schedule a Message to a Samsung Player, it will display as a sequence of still-images.
- During the download of a new plan and its content, the Samsung Player will now continue to show the previously-received plan.
- Added support for framesets with multiple frames. This feature requires that your Samsung players have the Scala Samsung SSP HTML Enhanced Player license — please contact Scala for more information. Note that the are several hardware limitations:
- Video may only play in one frame at a time.
- In case of overlapping frames, the video will be underneath other rendering.
- The frame rate for any video file should be half the display’s refresh rate, to avoid a flicker / repainting at the beginning and end of the video.
- Added support for reporting various problems back to Content Manager.
- The Samsung Player now logs activity, and sends those logs to Content Manager, where they may be viewed.
- Added support for several transitions, including Wipe, Center, Curtain, and Corner.
- Optimized the checking for new plans, in the case where the plan is unchanged.
- Improved plan-status reporting so that it’s easier to see in Content Manager that the Samsung Player is functioning.
- When the Samsung Player cleans up unused files, it now also cleans up empty folders inside the Content area.
- If you schedule an HTML widget to play on the Samsung Player (which is not supported), it now reports a problem back to Content Manager.
- The Samsung Player now checks for available free storage before downloading new content. (This feature may require updating the firmware on the Samsung display.)
- The Player heartbeat rate and Plan Polling interval set in Content Manager are now respected on the Samsung Player. Before they were always one minute.
- Better recovery in case the Samsung Player encounters a malformed plan file.
- Fixed a rare stuck-problem that could occur if Content Manager is not reachable at the time the Samsung Player is turned on.
- In the case where the Samsung Player is downloading content but the network connection is lost, the Player was not always showing the red spinner, as it should have. This is now fixed.
- Fixed a problem where the Samsung Player would skip sub-playlists that contained only a single media item.
The Scala team