KB352: Remote Player upgrade results in “Not a valid Omnivex signed upgrade file” error

Symptoms

When performing a remote Player upgrade from Moxie Studio, one or more Moxie Player upgrades fail with the following error message "Not a valid Omnivex signed upgrade file"

Cause

When a remote Player upgrade is initiated, the upgrade file is sent over to the Player PC and its signature is verified to ensure the file is not corrupted. Sometimes, due to certain security reasons if the Player PC can not verify the file's certificate, it aborts executing the installation file.

KB350: Specifications for Video Capture with Moxie

For Moxie 7.03 and lower

Note: Moxie 7.03 64-bit does not have video capture

For Moxie 7.03 and lower the tested Video Capture USB devices are:

  1. Hauppauge WinTV-HVR-1950
  2. Hauppauge WinTV-HVR-1955

PCI versions of these devices are 1600 and 1800.

These devices use MPEG-2, which is not installed by default on Windows 10. However, the codecs are available for installation from Hauppauge.

KB348: Moxie Player or Studio restarts unexpectedly and throws an “OutOfMemoryException”

Symptom

Moxie Player or Studio will restart automatically if certain conditions are encountered such as repeated failures to render video files or when unexpected exceptions are thrown. As part of the Moxie’s process to recover, it will write a timestamped incident log file to C:\ProgramData\Omnivex\System for analysis and then trigger a process restart.

Subscribe to Software