KB342: Moxie Player starts in an unexpected window state
Symptom
Moxie Player application launches in an unexpected window state. For example, you expect it to launch as maximized, but it launches as minimized.
Moxie Player application launches in an unexpected window state. For example, you expect it to launch as maximized, but it launches as minimized.
When you add web content to a layout using Internet Explorer, a “Your browser does not currently recognize any of the video formats available” error appears. The error appears for various video streaming websites, such as YouTube and Twitch.
Moxie emulates Internet Explorer, which does not support HTML5 streaming on a Windows 7 operating system for some websites.
Moxie Players display a "No licensed Player connections remain at the Moxie Data Server. Check with your Moxie Administrators to ensure that connection are available" message. Either:
Depending on your symptom (a or b), either:
The following table lists events that you can monitor in your Moxie environment
ID Number
|
Sources
|
Message Type
|
Description |
Remotely upgrading a 32-bit Moxie Player to a 64-bit Moxie Player fails, and the original 32-bit Player is uninstalled. The Player still consumes a license and shows up in the Player Manager and System Manager module in Moxie Studio.
Moxie has two different types of synchronization:
These can be used to synchronize the playback of content across multiple Moxie Players. When using these features, consideration must be given to network topology and host firewall configuration.
The FEATURE_GPU_RENDERING enables Internet Explorer (IE) to use a graphics processing unit (GPU) to render content. This dramatically improves performance for webpages that are rich in graphics.
By default, this feature is enabled for IE but disabled for applications hosting the WebBrowser Control. Therefore, in order to take advantage of this feature for Moxie content, GPU rendering must be enabled for Moxie by changing registry keys.
Moxie installs with an extensive set of metadata to apply to content and players. This metadata can then be used in rules and events to contextualize your content and filter your log data.
Occasionally, you may want to add new custom metadata tags to Moxie to suit your own system requirements.
In previous versions of Moxie:
This article lists the new features and changes in Moxie version 7.02. It is intended for anyone planning to upgrade their installation of Moxie 7.01. All Moxie components, including Data Server, Player, Studio and services must be upgraded to 7.02 to ensure compatibility.