Firmware and documentation for DMB400
RELEASE NOTE
IMPORTANT: After migration from a firmware Gekkota OS 4.yy.zz to a firmware Gekkota OS 5.11.10, some third party software allowing to publish your App may be not compatible. For further information, contact support@qeedji.tech
IMPORTANT: In case you wish to upgrade your DMB400 devices from firmware Gekkota OS 4.yy.zz to a firmware Gekkota OS 5.11.10, it is recommended to contact support@qeedji.tech to know the impact of this migration. Check also the software compatibilities below
IMPORTANT: your current App version running on the device may be not compatible anymore. You may have to upgrade your App version. For further information, contact support@qeedji.tech
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
2023-04-19 V5.11.10 download
BUG FIX, NEW FEATURES, MINOR UPDATES
- Initial version supporting:
- Power BI Online viewer
- MS OAuth user
- Azure AD tenant ID
- Azure AD client ID
- Azure AD secret
- Microsoft 365 credential identifier
- Microsoft 365 credential password
- MS OAuth application
- Azure AD tenant ID
- Azure AD client ID
- Azure AD secret
- URL launcher
- Simple Web server
- CIFS
- Microsoft 365
- MS OAuth application
- Azure AD tenant ID
- Azure AD client ID
- Azure AD secret
LIMITATIONS
- these video containers are not supported:
- .asf, .wmv, .vob, .mpg, .mpeg, .m2v, .avi, .ts, .wma
- XPF servers are not supported
INFORMATION
DOCUMENTATION
- User manual (5.11.10~002B_en) download
SUPPORTED MEDIAS
- Devices supported medias and performances download
QEEDJI POWERPOINT PUBLISHER FOR MEDIA PLAYERS
CONFIGURATION SCRIPT
POWERSHELL SCRIPTS FOR AZURE ACTIVE DIRECTORY APPLICATION SUPPORT
- PowerShell script for Azure Active Directory Application support 1.10.16 download for
- Power BI Online viewer application
- Microsoft 365 URL launcher application
INFORMATION
- Mouse pointer
- The mouse pointer is only supported when working with a touch screen monitor
- Monitor monitoring
- Some unexpected device reboot could be noticed when monitor monitoring is made on the wrong video input (when monitoring HDMI1 while cable is plugged on HDMI2)
KNOWN LIMITATIONS
- Media Source Extension
- In this version, the playback of all other MSE contents playbacks, meaning MSE video content displayed in an area inside the HTML page, without any device reboot is not guaranteed
- About the
Media Source ExtensionJavaScript:- 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
W3Cis working on to improve theMedia Source Extensionsspecifications 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.enabletofalse. 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
- Set the user preference
- H265-60Hz
- When playing H265 60Hz video, it is advised to configure the display output with a 60Hz mode
- HDMI-input
- When rotation 90°, 180°, 270° is activated, the HDMI-input is not supported and a message content temporarily unavailable is displayed
- HDMI-input content playback is not supported when the user preference
innes.video.renderer.defaultis set to the valuegpu. To support it, change the user preference value tooverlay - Some rare skip frame could be noticed on HDMI-input content zone when playing several medias at the same time
- Some rare skip frame could be noticed on HDMI-input content when there is audio on HDMI-input
- Note for MS-PowerPoint bullets
- Ensure that the appropriate fonts are properly embedded in the content
- Not yet supported in MS-PowerPoint medias rendering:
- Animation
- Effects
- WordArt, shadow
- Images
- Image with filtering
- Emf
- Animated image
- Gif & Png (displayed but not animated)
- Some shapes
- Smart Art
- Multi-colors shape texture
- Text
- Kerning is not supported
- Audio & video
- Vertical fading (in case mixed horizontal & vertical fading)
- Font
- Embedded
- Fail over & substitution fonts
- OLE injection (MS objects)
- Slide hiding
- URL launcher
- the web page content rendering must be suitable for the resolution of the display device connected to the DMB400 device
- keep in mind that the Web site must be suitable with the memory available on the device. For further information, refer to the user manual
- it is not navigate on the Web site by using the side scroll bar
- Microsoft Power BI
- keep in mind that the Power BI report must be suitable with the memory available on the device. For further information, refer to the user manual
- In case trouble to use the MS OAuth application mode, contact support@innes.pro