11. Appendix MX-FR Series Modular Matrix Frames – User's Manual 140
▪ Connecting an output to input 0 (disconnected) when at least one
dual link input card was present in the router may have caused
fatal crosspoint switching error.
▪ The Validity bit was set wrong in audio sample packets SB6 byte
when PCM audio was transmitted. Affected cards: MX-HDMI-
Preview output.
▪
used, then the SPDIF outputs sent copyrighted (copy protected)
material. Now the content protection is turned off on SPDIF
outputs on the MX-HDMI-OB card.
▪
SPDIF stream was marked as professional application. This
wasn't right for some professional SPDIF receivers.
▪
professional copyrighted material. Now it is marked as consumer
non-protected material because this prevents some SPDIF
interoperability issues.
▪ Digital signals with <40px back porch had sometimes strange
recolor effects with MX-DVII-IB and MXD-UMX-IB board.
▪ If the MX-DVII-IB or the MXD-UMX-IB has been received HDMI
YUV (444 or 422) signal and the user set the input video signal
source with the :DVII command again to auto or digital mode
greenish tint. This was because using incorrect YUV-RGB color
conversion matrix.
▪ If the MXD-UMX-IB has been embedded audio from the audio
input video signal source with the :DVII command again to auto
the image was blinking for a few seconds (and therefore audio
was also muted for a while). This was because the TMDS clock
and audio dropout is eliminated.
▪
to test pattern modes, HDCP and infoframes.
▪ If the IP address starts with 0 it is not displayed from now. e.g.:
▪
numbers were misindexed.
▪
status and audio infoframe content.
▪ MX-HDMI-3D-IB didn't work well with 4x20 character LCD display
3.3.2
Released: 2012-11-12
▪
when video signal was detected.
3.3.3
Released: 2013-01-17
New feature
▪ CPU SCH version is displayed in the LCD menu (among the
Installed cards - both LCD types are supported)
▪
card log during the boot process.
3.3.4
Released: 2013-01-28
▪ The image was shifted one pixel to the right with digital signals.
Affected cards: MX-DVII-HDCP-IB, MXD-UMX-IB
3.3.5
Released: 2013-03-04
▪ IO card SN numbers may cause stability issues.
3.3.6
Released: 2013-05-23
New feature
▪ MX-TPS-OB, MX-TPS-OB-A, MX-TPS-OB-S support (incl. serial
passthru and ethernet functions)
▪ MX-TPS-IB, MX-TPS-IB-A, MX-TPS-IB-S support (incl. serial
passthru and ethernet functions)
▪ File uploading to SD card through Lightware protocol. (needed
for TPS fw upgrade)
▪ The LCD screen didn't show the analog audio options for the MX-
HDMI-3D
▪ If a dynamic EDID memory slot had been empty and new EDID
was read from one output, then the output validity table was
showed as being invalid EDID after reading the EDID header until
▪ The audio sample frequency was unstable at 1080p60, this may
▪ HDCP keycounter sometimes resulted with 0 key with certain
▪ The MX-DVII-IB and the MX-UMX-IB boards sometimes didn't
detect the 36 bpp - 24 bpp deep color change, and remained in
36bpp mode.
▪ MX-DVII-IB, MXD-UMX-IB: SPD Infoframe was sent with wrong
header, could cause issues with deep color signal. Stored
settings block was too large on these cards.
▪ If an MX-HDMI-3D-IB card was present at the 1st input slot and
any output was connected to the 0th input (ie. disconnected),
then the matrix has coninously rebooted.
▪ A noisy incoming signal may disable input ports on MX-HDMI-
IB, MX-DVI-HDCP-IB, MX-HDMI-TP-IB and CPU test input (signals
were detected appropriately but not forwarded to the crosspoint).
The only solution was to restart the whole router, however the
3.3.7
Released: 2013-08-22
New feature
▪
▪
bandwidth (depending on the actual baudrate)
▪
on the LCD and they will not trigger the alarm LED.
▪
OB cards
▪ HDBase-T HDCD database is used to recognise remote devices
▪ The minimum assertion time for hotplug line is 1.5 sec on the
MX-HDMI-IB, MX-HDMI-TP-IB, MX-DVI-HDCP-IB, MX-DVII-IB,
MXD-UMX-IB, MX-HDMI-3D-IB (and variants), MX-TPS-IB (and
variants) cards and test input port. This is 15 times greater than
the required minimum by the standard. The intention of this extra
long HPD pulse is prevent the non-standard devices to miss the
hpd event.
▪ A false "SBTB error" message has appeared on the LCD screen
after boot if at least one MX-DVIDL-OB card was installed in the
frame. This issue persisted only with 3.3.6
To Next Page
Loading...