MoIP Firmware v4.1.2.4 Release Notes

New features

  • Adds support or B-960 devices

Improvements

  • HTTPS is now the default

  • The local user interface password is now force-change on initial login

v4.0.2.4

Improvements

  • Updates non-AC devices to firmware v1.5.5 and AC devices to v2.5.5

  • Improved compatibility with Direct TV Genie C61k-700 to resolve black screen issues.

Known issues

We are actively investigating an issue when using the v39 C4 driver and the MoIP 4.0 FW where a Binary blue screen may occur when using the audio output of a MoIP TX connected to an audio matrix. This firmware update does not address this specific issue. We anticipate a resolution in the form of a Control4 driver update soon. We apologize for the inconvenience.

Version 4.0

New features

Enhanced configuration and monitoring features are now available in OvrC

  • MoIP firmware version 4.0 moves the MoIP configuration from the local interface to OvrC’s MoIP System Management, found under the MoIP controller’s Configure tab. All configuration options are now only available in OvrC.

  • MoIP Endpoint status: All MoIP TX and RXes now appear as individual devices within the OvrC device list, providing real-time status and notification support.

  • Easier Configuration: With all configurations now available in OvrC, making changes to the MoIP system is now much more convenient and easier.

  • Platform Updates: With this transition to a new technical architecture for MoIP in OvrC, Snap One can deliver additional features in the future which would not have been possible otherwise, such as increased network visibility, health status, and more.

Caution: -.If you cannot use OvrC at the location, do not upgrade to firmware v4.0.

Caution: -.The MoIP Client Control App is no longer available in MoIP 4.0. If your client requires this feature, do not upgrade to MoIP 4.0.

Note: -__.The MoIP controller local interface now only displays general status information of each endpoint, as well as the ability to change sources on receivers.

Ryff to MoIP

The Ryff to MoIP feature, available in Control4 OS 3.3.2, enables Ryff audio streams (formerly Control4 Digital Audio) to be sent over the network without the use of physical audio cabling and output to any MoIP receiver.

System requirements:

  • MoIP driver v39 or above

  • An EA or CORE controller running Control4 OS 3.3.2 or above

  • MoIP controller firmware v4.0 or above

This is the first step to bridge the Control4 Ryff audio platform with MoIP in order to ease pain points in installation and deliver audio experiences around the home where it may have been impractical before.

Read the Ryff to MoIP page for installation instructions and more information.

Example use cases

  • Listen to Pandora or TuneIn in a home theater AVR connected to a MoIP receiver.

  • Listen to TIDAL or Spotify on a TV‘s active soundbar connection driven by a MoIP receiver connected to the TV's HDMI input.

  • Extend lossless audio over the network to a remote location using a MoIP audio receiver connected to a 2-channel amplifier with a pair of speakers.

  • Listen to a turntable connected to a Triad One analog input in any of the above examples.

Version 3.2.1.2

  • Supports multiple versions of PoE, HDCP, and MCU modules.

Version 3.2.0.8

The key area of focus in this release is a modification that allows for much faster switching times. The switching process has been completely rewritten based on our historical experience with the platform, and a much more efficient process was implemented that eliminates some redundancy. In addition to that functional change, some audio related bugs have also been addressed.

Note: -__.If the MoIP system is connected to Pakedge MS Series network switches (MS-1212, MS-2400, MS-2416, MS-2424, MS-4424) follow the instructions in this article.

Change Logs for 3.2.0.8

  • Updated source switching process for faster switching times

  • Resolved issue where audio format change could cause DSP-lockup

  • Resolved an issue where some instances of DTS HD Master audio could be improperly decoded

Version 3.1.0.4

Caution: -.This firmware is required before adding B-900-MoIP-AUDIO-RX and B-900-MoIP-AUDIO-TX devices.

Key area of focus is the addition of audio return support via HDMI ARC and Toslink. This functionality is currently enabled to pass audio from the B-900-MoIP-4K-RX-2AC to another receiver, either another B-900-MoIP-4K-RX-2AC, a B-900-MoIP-4K-RX or a B-900-MoIP-AUDIO-RX.

Also updated are the EDID settings to support full pass-through of Dolby Atmos and DTS-X. This can be enabled in the Audio EDID setting drop-down option of the transmitter by selecting the Full Pass-Through option.

Change Logs for 3.1.0.4

  • Update webPagePort in dxGetNetworkSettings to return dynamic port (so OvrC knows whether to show the HTTP or HTTPS WebConnect options)

  • Reverted change to SDDP messaging that caused some to lose integration

Change Logs for 3.1.0.2

  • Added audio return support

  • Added “full pass-through” to support Dolby Atmos and DTS-X

  • Re-pair RXs and TXs after upgrade

  • Increased maximum IR code length to accept up to 2046 characters

  • Added support for dynamic IR routing feature

  • Removed colons from MAC in SDDP messages

  • Added support for HDMI audio mute and exposed commands via control API

  • Updates for cyber security

  • Modified mobile view to render input box instead of slider for volume control

  • Enhanced logging capabilities on Download log button as well as individual RX and TX details pages

  • Enabled firmware update via control API and automated upgrade/downgrade test cases

  • Generate HTTPS certificate before reboot if necessary

  • Updated local UI TX and RX cards from overflowing with long names

  • Fixed video details page from showing garbage data for offline devices