Summary
The following products have been retired and the last release is listed here. We do not test or support these products on current operating systems. In some cases these products have been replaced by other products with overlapping functions. Please contact Omnivex Sales for information on replacement products.
Summary
Omnivex legacy products are considered feature complete and will not receive additional functionality. In most cases these products have been replaced by other products; customers with annual maintenance and support (AMS) can migrate to the new product based on their existing license. Omnivex supports these products under our AMS program. Listed below is the most recent version of each Omnivex legacy product and their supported operating systems. The information below is subject to change. This article is regularly updated.
Omnivex products are designed to operate on a variety of Microsoft Windows operating systems. Not all Windows operating systems are appropriate for all products. Omnivex tests each new software update on multiple operating systems (English versions only) to ensure consistent performance and value to customers. Listed below is the most recent version of each Omnivex product and their supported operating systems. The information below is subject to change. This article is regularly updated.
Version update
The following problem listed in the known issues of the previous release has been fixed.
"In some configurations, a Player restart (not a computer restart) would cause the Player to revert back to the default name "Player (COMPUTERNAME)". The current workaround is to add a Metadata field such as "Location" to the Player Manager Window through the Home/View/Columns option. This also applies to any rules that used computer name in the Playlist Builder or player views in the System Manager."
Version Update to address reported resource allocation problem
A problem was identified where memory requirements for the SQLLink Service would steadily increase over time. This issue has been addressed and no other changes have been made in this version.
September 30, 2013
Version update to address reported issue in prior versions, no new features.
A problem was identified under certain scenarios where some data cells did not update properly. A new version of DataPipe Server (Service) and Client are available. This version (3.07.030) was included in the recent Moxie 6.10 release.
July 16, 2013
Symptom
Creating bar chart or column charts in the Layout Designer module and then changing content properties frequently can result in a user experiencing their computer becoming unresponsive or Moxie Studio experiencing a memory allocation error and become unresponsive.
Cause
Summary
Moxie Studio reports ID 0 when the user submits an exception log to Omnivex.
Cause
This happens in certain circumstances where the Omnivex server does not report the correct Incident ID to Moxie Studio.
Solution
A new version of Moxie has been released. The Moxie Server is supported on Windows Server 2008 and 2012. The Moxie Studio and Player are supported on Windows 7 and 8. This version of Moxie also supports .NET Framework 4.0 and 4.5.
New features
Symptom
When you add the time to your content, the time displayed on your device isn't correct.
Cause
The time shown on your device is based on the time and geographic time zone indicated in the Control Panel settings of the PC from which you are controlling your device. If time or time zone setting on that PC is not configured correctly, the displayed time will be wrong.
Solution
