Gekkota OS for SMA300

RELEASE NOTE

IMPORTANT: In case you wish to upgrade your SMA300 devices from Gekkota 3 middleware (3.12.XX) to Gekkota 4 middleware (4.10.1X), it is highly recommended to contact Innes to know the impact of this migration. Check also the software compatibilities below, and remember that you won’t be allowed to downgrade to a Gekkota 3 middleware afterwards. The specific SMA300 RMA (or Return Merchandise Authorization) consisting in downgrading the middleware Gekkota 4 back to the middleware Gekkota 3 is not covered by the warranty of the device

Never make electric unplug on your player while software upgrade is in progress (green led blinking 6 times every 4 seconds) else the player may not be able to work properly

2019-02-27 V4.11.10 download

IMPORTANT IN CASE MIGRATION V3.12.XX TO 4.11.10
  • Before upgrading to Gekkota 4 middleware:
    • Ensure that your current SMA300 middleware version is at least 3.12.20 (and not a beta version)
    • In PlugnCast environment, be careful when you launch middleware upgrade to Gekkota 4 middleware for only some of your SMA300 devices. Indeed, if you don't pay attention when using PlugnCast, it is easy to upgrade afterwards by mistake all your SMA300 devices even if you did not want to.
  • Once the migration Gekkota 3 to Gekkota 4 is done:
    • You'll not be allowed to downgrade to a Gekkota 3 middleware afterwards
    • **In case using Screen Composer, you will have to create specific new projects Gekkota 4 SMA300 embedding Playzilla 4.XX.YY to be able to publish a content on your device. Ensure you have the required licences to use Playzilla 4.XX.YY
    • In case using PlugnCast G3, change the player type Gekkota 3 to Gekkota 4 otherwise a message App format not recognized will be displayed after a publication. Ensure you have the required Playzilla 4.XX.YY licenses for all your devices
  • In case you need to use the CEC playout script, you have to set the user preference system.connector.*.*.cec.cec_1.enabled to the value true. Activating the CEC feature may imply some unexpected device reboots with some monitor requiring a HDMI-DVI adapter or a HDMI-VGA adapter
BUG FIX, NEW FEATURES, MINOR UPDATES
  • Add support for HTML5 WebUI
  • Add support for a new directory .playlog/ in the WebUI
  • Add support for new monitor display configurations
    • 128x96 60Hz
    • 112x96 60Hz
    • 96x96 60Hz
  • Add support for the user preference innes.video.decoding-group.enabled:
    • true: in case a second video media is trying to start while a first one is already running, the second video does not start. A message content temporarily unavailable is displayed for the second video media
    • false (default value): in case a second video media is trying to start while a first one is already running, the first video is stopped and the second video media is starting. A message content temporarily unavailable is displayed for last stopped video media
  • Add a message No partition was detected when the SD Card is removed from the device
  • Add support for the display of a key pictogram showing the MAC address value needed for the license
  • Add support for CEC Web IDL
    • The CEC feature is inactivated by default
    • To activate the CEC feature set the user preference system.connector.*.*.cec.cec_1.enabled to the value true
  • Add support for Power management Web IDL
  • Change: add an error message when the WebUI is launched with the MS-Internet Explorer 11 Web browser
  • Change: the max. number of Web socket opened at the same time is limited to 550
  • Change: embeds a new time zone database (version: 2018g, source: https://www.iana.org/time-zones)
  • Change: when the sound card is inactivated in the device WebUI, the audio is not decoded anymore
  • Change: replace Linux armv7l by Linux in the device user agent
  • Fix: it was not possible anymore to connect to the device WebUI after having changed first the device WebUI login, then the device WebUI password
  • Fix: in some case, it was not possible to save the hostname value in the WebUI
  • Fix: a DVB-T video over UDP could be jerky after having unplugged the Ethernet cable for a while
  • Fix: some unexpected device reboots could occur after a couple of minutes or after a couple of hours when playing some specific medias
  • Fix: sometimes some unexpected video freeze could be noticed after a while when playing a live DVB-T through UDP
  • Fix: sometimes the audio could be slightly in late after a while when playing a DVB-T live through UDP
  • Fix: some unexpected device reboots could occur when playing a DVB-T live through UDP, especially when facing stream discontinuities
  • Fix: some PDF media could not be rendered properly except after having been edited inside Screen Composer
  • Fix: in some case, when 2 scrolling texts overlay was launched at the same time, any of both wasn't displayed
    • Now when a 2nd scrolling text overlay is starting, a message content temporarily unavailable is displayed for this 2nd scrolling text overlay.
    • To run 2 scrolling texts at a time, inactivate the option if possible, use an overlay for one of them
  • Fix for MS-PowerPoint medias:
    • Table object was not supported
    • Some bullets was not rendered properly
      • note when using Screen Composer: in case some bullets of some MS-PowerPoint slides are not rendered properly, it is required to add the appropriate fonts manually in the playout manifest
    • Alternate content, allowing to support for example shape background images, was not supported:
      • 3D models
      • equations
    • Sometimes arrows shapes could be not rendered properly
    • Sometimes some pages numbers could not have the right value
    • Some font letters could be not be aligned vertically when the text had an orientation different from 0° (modulo 90°)
  • Fix: inside a HTML page, some font could have a wrong size
  • Fix: inside a HTML page, the check box default colour could be not the right one
  • Fix: some scrollbar could be displayed along the edge of a system scene when the rotation was 90°
  • Fix: some skip frames could be noticed when playing some video media when a new content was pushed on the WebDAV directory at the same time
COMPATIBILITIES
  • Screen Composer G3 V3.20.14 (or above)
    • App Playzilla 4.10.20
  • PlugnCast V3.10.49 (or above)
    • App Playzilla 4.11.10
  • PlugnCast Studio 2.51.11 (or above) / PlugnCast Server V2.50.32
    • Note: Plugncast V2.xx.yy does not support multi-video decoding
  • App SignMeeting 1.12.XX is not supported on Gekkota 4 middleware
    • Note: SignMeeting 1.13.10, working on Gekkota 4 middleware, should be available Q1/2019

INFORMATION


DOCUMENTATION

SUPPORTED MEDIAS

  • Gekkota supported medias and performances download
KNOWN LIMITATIONS
  • Not supported
    • Player synchronization with PlugnCast G3 synchronization script
    • App SignMeeting
    • AVI container
    • inter-media transitions & zone exit transitions
    • Bitrate limitation
    • Color ajustment
  • Anomaly
    • In case the WWAN option is activated, the video decoding through UDP in multicast is not supported
  • Media Source Extension
    • In this version, the playback of all other MSE contents playbacks, meaning MSE video content displayed in a thumbnail inside the HTML page, without any device reboot is not guaranteed
    • About the Media `Source Extension Javascript:
      • Each MSE content provider has its own algorithm implementation in its MSE Javascript. Consequently, it is possible that some MSE content having a specific MSE Javascript is not fully supported making that the video does not start properly (for example, with some MSE video content replay)
      • When playing a MSE content, an error message if playback doesn’t begin shortly, try restarting your device could be displayed sometimes after a while telling that the video has stopped and will not start anymore. To work around, play another media, then play again the MSE content. The best practise consists in playing the MSE content URI with a fixed duration (ex: duration 1 hour).
    • About other MSE content: for example, the MSE video content displayed in a thumbnail inside the HTML Web page:
      • Warning: the MSE content provider can decide at any time to remove a content. So an MSE content can be available one day and not available the day after
      • When the MSE content is displayed in a thumbnail inside the HTML Web page, a lot of other objects need to be displayed as well and could require a lot of memory. Depending on the Web page played, the device could sometimes reboot after having played it after a while. The W3C is working on to improve the Media Source Extensions specifications so that the MSE Javascript is more suitable also for devices that have a limited available memory amount
    • To inactivate the DASH MSE feature,
      • Set the user preference media.mediasource.enable to false. The error message An error occurred. Please try again later (Playback ID: ...) should be displayed when trying ten to play an MSE content in this condition. This message could be seen also when playing another video at the same time when the dual video decoding is not supported on this device.
  • Not yet supported in MS-PowerPoint medias rendering:
    • Animation
    • Slide transitions
    • Effects
      • WordArt, shadow
    • Images
      • Image with filtering
      • Emf
    • Animated image
      • Gif & png (displayed but not animated)
    • Some shapes
      • Smart Art
      • Multi-colours shape texture
    • Text
      • Kerning is not supported
    • Audio & video
    • Vertical fading (in case mixed horizontal & vertical fading)
    • Font
      • Fail over & substitution fonts
      • some characters whose fonts is 32 bits may be not displayed (ex: fontawesome.ttf)
    • OLE injection (MS objects)

OLD VERSIONS HISTORY


2018-10-31 V4.10.16 download

IMPORTANT IN CASE MIGRATION V3.12.XX TO 4.10.16
  • Before upgrading to Gekkota 4 middleware:
    • Ensure that your current SMA300 middleware version is at least 3.12.20 (and not a beta version)
    • In PlugnCast environment, be careful when you launch middleware upgrade to Gekkota 4 middleware for only some of your SMA300 devices. Indeed, if you don't pay attention when using PlugnCast, it is easy to upgrade afterwards by mistake all your SMA300 devices even if you did not want to.
  • Once the migration Gekkota 3 to Gekkota 4 is done:
    • You'll not be allowed to downgrade to a Gekkota 3 middleware afterwards
    • **In case using Screen Composer, you will have to create specific new projects Gekkota 4 SMA300 embedding Playzilla 4.XX.YY to be able to publish a content on your device. Ensure you have the required licences to use Playzilla 4.XX.YY
    • In case using PlugnCast G3, change the player type Gekkota 3 to Gekkota 4 otherwise a message App format not recognized will be displayed after a publication. Ensure you have the required Playzilla 4.XX.YY licenses for all your devices
BUG FIX, NEW FEATURES, MINOR UPDATES
  • Fix: in some custom network configurations, a message content temporarily unavailable could be displayed when playing some multicast streams

2018-10-03 V4.10.15 download

IMPORTANT IN CASE MIGRATION V3.12.XX TO 4.10.15
  • Before upgrading to Gekkota 4 middleware:
    • Ensure that your current SMA300 middleware version is at least 3.12.20 (and not a beta version)
    • In PlugnCast environment, be careful when you launch middleware upgrade to Gekkota 4 middleware for only some of your SMA300 devices. Indeed, if you don't pay attention when using PlugnCast, it is easy to upgrade afterwards by mistake all your SMA300 devices even if you did not want to.
  • Once the migration Gekkota 3 to Gekkota 4 is done:
    • You'll not be allowed to downgrade to a Gekkota 3 middleware afterwards
    • **In case using Screen Composer, you will have to create specific new projects Gekkota 4 SMA300 embedding Playzilla 4.XX.YY to be able to publish a content on your device. Ensure you have the required licences to use Playzilla 4.XX.YY
    • In case using PlugnCast G3, change the player type Gekkota 3 to Gekkota 4 otherwise a message App format not recognized will be displayed after a publication. Ensure you have the required Playzilla 4.XX.YY licenses for all your devices
BUG FIX, NEW FEATURES, MINOR UPDATES
  • Add support for DASH MSE (Media Source Extensions)
    • The DASH MSE is activated by default (meaning the preference media.mediasource.enable is set to true)
    • This feature allows to play some Web TV channels compliant with the DASH MSE in some conditions:
      • The DASH MSE video content has to be displayed in full screen inside the HTML page:
        • This is the typical YouTube MSE content URL in full screen:
          • https://www.youtube.com/embed/<YouTube_video_uuid>?autoplay=1
        • The Web TV channels available in full screen are available for download in the content models and uri models packs delivered the 3rd of October 2018
    • To know whether other Web TV channels may be well supported in full screen on the device, check first that the URL is properly displayed inside your Web browser
  • Add support for new WLAN chip supporting 2.4 GHz and 5 GHz bands
  • Add support for LDAP IDL
  • Add support for Web SQL
  • Fix: the video control overlay (play, pause) was not displayed on touch screen device
  • Fix: the email address consistency was not tested before sending an email
  • Fix: the device could crash when playing DASH Live stream
  • Fix: attachments could be not properly attached in the email when containing some non-ASCII characters
  • Fix: a message content temporarily unavailable could be displayed at the loop back of a RTSP stream
  • Fix: the device could reboot when playing RTSP stream with the TERADEK Cube 105 encoder/streamer
  • Fix: sometimes, a message content temporarily unavailable was displayed when playing a RTSP Live stream in outband mode with VLC
  • Fix: in some case, the video could be frozen with audio running when playing RTSP live stream from the VLC software
  • Fix: some interlaced video could be rendered in a wrong orientation when the rotation was 90°
  • Fix: playing the inconsistent URI HDMI-input could make reboot the device systematically
  • Fix: the player could reboot when playing a wrong RTP/SDP Audio Video Profile
  • Fix: UDP stream could not be played in case using the DME204 streamer whose the WebUI parameter Output > Ethernet > Audio was unselected

2018-08-09 V4.10.13 download

IMPORTANT IN CASE MIGRATION V3.12.XX TO 4.10.13
  • Before upgrading to Gekkota 4 middleware:
    • Ensure that your current SMA300 middleware version is at least 3.12.20 (and not a beta version)
    • In PlugnCast environment, be careful when you launch middleware upgrade to Gekkota 4 middleware for only some of your SMA300 devices. Indeed, if you don't pay attention when using PlugnCast, it is easy to upgrade afterwards by mistake all your SMA300 devices even if you did not want to.
  • Once the migration Gekkota 3 to Gekkota 4 is done:
    • You'll not be allowed to downgrade to a Gekkota 3 middleware afterwards
    • **In case using Screen Composer, you will have to create specific new projects Gekkota 4 SMA300 embedding Playzilla 4.XX.YY to be able to publish a content on your device. Ensure you have the required licences to use Playzilla 4.XX.YY
    • In case using PlugnCast G3, change the player type Gekkota 3 to Gekkota 4 otherwise a message App format not recognized will be displayed after a publication. Ensure you have the required Playzilla 4.XX.YY licenses for all your devices
BUG FIX, NEW FEATURES, MINOR UPDATES
  • Add support for scrolling text in overlay
    • Note when using the model Scrolling text from file: has to be displayed in a zone whose height is maximum up to 20% of grid height
  • Fix: the download of a playout containing a media whose size is above 2GB was taking too much time (ex: 3 hours instead of 10 minutes for a media whose size is 7GB)
  • Fix: in some case, the device could reboot after a while after having played several PDF medias
  • Fix: an unexpected message "video can't be played because the file is corrupt" could appear when playing some Web page
  • Fix: the gradient background of MS-PowerPoint medias could be not rendered properly
  • Fix: a unexpected message content temporarily unavailable could be displayed when playing some video medias with PCM audio (Mp4 container)

2018-06-06 V4.10.12 download

IMPORTANT IN CASE MIGRATION V3.12.XX TO 4.10.12
  • Before upgrading to Gekkota 4 middleware:
    • Ensure that your current SMA300 middleware version is at least 3.12.20 (and not a beta version)
    • In PlugnCast environment, be careful when you launch middleware upgrade to Gekkota 4 middleware for only some of your SMA300 devices. Indeed, if you don't pay attention when using PlugnCast, it is easy to upgrade afterwards by error all your SMA300 devices as you did not want to.
  • Once the migration Gekkota 3 to Gekkota 4 is done:
    • You'll not be allowed to downgrade to a Gekkota 3 middleware afterwards
    • **In case using Screen Composer, you will have to create specific new projects Gekkota 4 SMA300 embedding `
    • to be able to publish a content on your device. Ensure you have the required licences to usePlayzilla 4.XX.YY`
    • In case using PlugnCast G3, change the player type Gekkota 3 to Gekkota 4 else a message App format not recognized is displayed after a publication. Ensure you have the required Playzilla 4.XX.YY licenses for all your devices
BUG FIX, NEW FEATURES, MINOR UPDATES
  • Add support for MS-PowerPoint media
    • 2007/2010/2013/2016
    • *.pptx, *.ppsx
      • note: in case you have some medias MS-PowerPoint *.ppt (or *.pps), save them into respectively PowerPoint presentation *.pptx, (or PowerPoint presentation *.ppsx)
    • Note for PlugnCast G3: in manifest tab, in case some font is missing for your MS-PowerPoint media, add the appropriate font in your CMS font library Change: embeds Mozilla Gecko 47
  • Add support for DASH MPEG (live & VOD) adaptive streaming (.mdp)
    • Dynamic quality value switching is not yet supported. The constant quality value can be set in Mbps with the user preference innes.video.has.max-bitrate (set to 5 for example 5 Mbps max.)
    • The server DASH Live and the SMA300 device need to be on time and synchronized with a NTP server
    • For video with high rate, in case the video is stopping after a while, it could be needed to increase the media.cache_size from 16364 KB (default size) to 65536 KB
  • Add support for subtitles SRT, VTT
  • Add support for RTP
  • Add support for RTSP V1.0 (live & VOD)
  • Add support for monitor-monitoring
  • Add support for touch screen devices over USB
    • The user preference innes.hid.keyboard-event.*.authorized needs to be true (default value)
    • The user preference innes.hid.pointer-event.*.authorized needs to be true (default value)
  • Add support for user preference system.display-output_1.sync.force-hv-positive
    • system.display-output_1.sync.force-hv-positive = false (default): the device is taking account of the vertical and horizontal synchronization values set in the chosen resolution/frequency/mode screen configuration
    • system.display-output_1.sync.force-hv-positive = true (default): the device is forcing the vertical and horizontal synchronization values to positive
  • Add support for PTP/IEEE1588
    • supported mode: PTP L2
    • default user preferences
      • system.clock-sync.enable = false (PTP/IEEE1588 not activated)
      • system.clock-sync.ptp.timeout.lock-on-master = 30 (30 seconds)
      • system.clock-sync.ptp-domain = 0 (domain_id = 0)
      • system.clock-sync.source = ntp (ntp, ptp-l2, ...)
  • Add support for AVCommand activation and configuration (WebUI)
    • Connectors
      • LAN
        • port (used by the monitor),
        • protocol name (supported by the monitor)
      • DDC/CI through video connectors
        • HDMI
        • DVI
        • VGA
    • Commands
      • Standby
      • Power mode
      • Brightness
      • Backlight
      • Video input
        • to know the list of possibles values for DDC/CI, please refer to AVCmd Web IDL (Gekkota OS GitHub Repo)
      • Mute
      • Volume
      • Custom commands (not supported for DDC/CI)
    • Protocols
      • eiki_xb42
      • nec_np3150
      • philips_m2
      • extron_m1
      • nec_x461s
      • samsung_m1
      • hitachi_m1
      • nudam_m2
      • sanyo_m1
      • optoma_m1
      • sharp_m1
      • lge_m1
      • panasonic_m1
      • sony_m1
      • mitsubishi_xl6x00
      • panasonic_m2
      • toshiba_m1
      • nec_m1
      • philips_m1
      • toshiba_tdpt420
      • custom_protocol
        • Add,
        • Edit,
        • Copy (an existing protocol by adding the suffix _custom)
        • Delete
  • Change: display all the available network interfaces in menu Information > Network (WebUI)
  • Change green LED behaviour depending on these different states
    • 1 flash every 4 seconds: Nominal behaviour
    • 2 flashs + 4 seconds OFF: Fail soft mode level1
    • 3 flashs + 4 seconds OFF: Fail soft mode level2
    • 4 flashs + 4 seconds OFF: System data partition check disk
    • 5 flashs + 4 seconds OFF: Error noticed on system data partition: partition format is required
    • 6 flashs + 4 seconds OFF: Firmware upgrading (or patch installation)
    • 7 flashs + 4 seconds OFF: Not possible to write on SSD anymore. If persistent, contact support@innes.fr