TESSERA SOFTWARE 3.5.4 BETA 1

SX40 | S8

Due to a new hardware revision, SX40 and S8 processors with serial numbers starting with 02 are only compatible with software versions 3.4 and above. Any attempt to downgrade the processor software version lower than 3.4 will be rejected.

The Tessera S8 processor requires software version 3.0 or later.

3.5.4 adds SX40 support for our new data distribution units, the XD-S and XD-T, and moves the current XD over to our new distribution box upgrade mechanism.

There are no other features or fixes over 3.5.2, and there is no benefit to upgrading to 3.5.4 unless the new XD-S and XD-T data distribution units are being used.

• Support for XD-S
• Support for XD-T
• New Firmware upgrade mechanism for XD Original

New Distribution Box Upgrade Mechanism

From 3.5.4 Beta 1 onwards, data distribution units will have their own fixture packs, as panels currently do; features and fixes will be released via updated fixture packs, avoiding the need for a full processor upgrade to keep data distribution units running on the latest and greatest version.

Bundled in 3.5.4 Beta 1 is these Data Distribution Unit Fixture packs:

• Tessera Public XD 3.5.4 Issue A
• Tessera Public XD-T 0.2.5 Issue A
• Tessera Public XD-S 0.2.5 Issue A

Tessera Public XD 3.5.4 Issue A

This is the new fixture pack for the original XD. There are no feature changes, and it is functionally identical to the current 3.5.3 XD firmware included in 3.5.2.

• XD-S and XD-T discovery
• XD-S and XD-T firmware upgrade and downgrade capabilities
• Cable redundancy (using matched XD-S or XD-T pairs)

Current Limitations

We are currently working on adding the functionality and features necessary to reach parity with the original XD and will release fixture packs for the data distribution units as these become available.

Features not in 0.2.5 for the XD-S and XD-T include:

• Daisy Chaining of Data Distribution Units on a single 10G trunk
• Processor Redundancy and Failover
• Data Distribution Unit status information in Tessera Remote (port status, temperatures, fan speeds etc.)
• Status information on the Front LCD “Glyph“ (in this firmware will only show the Brompton Logo at this stage)

FAQs on XD-S / XD-T Support

Q: Will ports 11 and 12 on the XD-S and XD-T be functional when used with SX40 in the future?

A: No. Implementing support for the 2 additional ports on XD-S and XD-T within the SX40 is not on the roadmap.

Q: Do I have to use ports 1 through 10 on the XD-S and XD-T when used with SX40?

A: Yes, customers must use ports 1 through 10. Panels connected to ports 11 and 12 will not be detected when XD-S and XD-T are used with SX40.

Q: Can I mix my XD-S, XD-T and original XD Data Distribution Units?

A: Once at feature parity with the original XD, the XD-S and XD-T are expected to be fully interchangeable. However, for this initial release we recommend customers do not mix XD-S, XD-T and the original XD on a processor. If operating with cable redundancy, pairs of XD’s should consist of two of the same type of XD.

Q: Can I use the new XD-S or XD-T with an SX40 running 3.5.2 or earlier software version?

A: Yes – these units will function correctly as Data Distribution Units with an SX40 running an earlier software. However, note that XD-S and XD-T will be reported as Unknown devices in 3.5.2, so you will need to run 3.5.4 in order to do management activities such as upgrading firmware on the XD-S and XD-T or to access future new features of the XD-S and XD-T.

Q: Can I go back to 3.5.2?

A: 3.5.4. Beta1 has been made with safety in mind; therefore, you should always be able to upgrade to 3.5.4.Beta 1 and go back to 3.5.2 or a suitable older release. To make sure that the changes in 3.5.4. Beta 1 doesn’t risk existing show files, when you open a show file in 3.5.4 Beta 1, a backup of your 3.5.2 or older show file is automatically created.

Q: Can I use 3.5.4 to upgrade my XD-S/XD-T and then downgrade to 3.5.2?

A: It is completely legitimate to upgrade to 3.5.4. Beta 1 to enable you to upgrade XD-S and XD-T to the latest features and then downgrade to 3.5.2 to continue using them. However, note that XD-S and XD-T will be reported as Unknown devices in 3.5.2. Whilst we expect XD-S and XD-T to pass panel data, there may be unknown edges to this behaviour in the future as features are added to XD-S and XD-T.

Q: What are the Hex codes for the XD-S and XD-T?

A: XD-S “0x09b4,06,00”, XD-T “0x09b4,06,01”

Data Distribution Unit Fixture Pack removal requires project close

If you remove the data distribution unit packs in the Manage Packs menu, the data distribution units will still show as Identified in online panels until the project opens and closes again.

XD Fixture Pack Labels

The data distribution unit fixture packs are not yet golden and therefore are labelled as “Testing” in the manage packs menu. The original XD fixture pack the manufacturer is missing and will show as “Unknown (0x032c)” instead of Brompton.

XD and panel firmware updates when Failover is enabled

It is not recommended to have Failover enabled when updating the firmware of Panels and XD’s, otherwise the update may fail. To recover from this state, both of the processors should be rebooted.

Processor fails to lock to certain YCbCr 4:2:0 HDMI inputs

Certain resolutions and bit depths, and changing source bit depth can cause the processor to fail to lock to YCbCr 4:2:0 inputs. This can normally be resolved by a hot plug of the source.

Adding additional video delay in the processor settings causes video snapshot to be non-functional

Eyedropper tool in Colour Replace will also become non-functional when additional video delay is used.

Switching the Phase Offset type to Absolute when on Active Input can state “Not locked”

If the processor gets into this state, switching to the opposite control method (Remote or Local) where you saw the problem will rectify it.

Processor output can be affected by some operations when Freeze is enabled

– Enabling/Disabling frame store test pattern with a non-native colour space changes the colour space to the whole frame
– Changing the input from HDMI to SDI or vice versa, with different scaling settings, causes displacement of a frozen frame store frame.

Exporting a frame store with 12 images to USB can cause the processor to watchdog under certain circumstances

Disabling the watchdog in processor settings can allow the USB export to complete.

IP Control and firmware reload

IP Control can cause issues with firmware reload when upgrading or downgrading from software versions prior to 3.4.3. It is recommended to either disable IP Control or close the project before initiating a firmware reload from software versions prior to 3.4.3

S4 firmware reload

When upgrading an S4 processor to/from 3.1.0.BETA4 firmware, after firmware reload has finished, the processor will not reboot automatically and will require a manual reboot. After reboot, the processor will operate as normal.

Version compatibility

In order to use V3.0.1 or later, it is necessary to run all elements of the system (processor, XDs and panels) on V2.3.1 or later. For panels where V2.3 firmware is not available please continue using V2.2 processor firmware.

Restore factory defaults/format SD card can cause fixture library instability

If you perform either of these operations please reboot your processor before browsing to the fixture library window as this may otherwise be unstable.

Tessera Remote may fail to import project files
In some cases, Tessera Remote may fail to import project files from local storage. As a workaround create the project from scratch or use a local monitor, keyboard and mouse to import the project file before connecting with Tessera Remote.

Some input devices on KVM switches do not work
We have had reports that trackpads may not function correctly when connected to the processor via a KVM switch. As a workaround we recommend using a mouse, or connecting input devices directly to the processor’s USB ports.

Monitors connected via DisplayPort-to-VGA adapters may be unstable
Local user interface monitors connected to the processor via certain active DisplayPort-to-VGA adapters may give an unstable image or the monitor is not detected at all. As a workaround we recommend using a DVI or DisplayPort monitor.

Some Display Port connections can result in a failure to boot
We have had reports of cases where some Display Port monitors connected to the local user interface output can lead to the unit failing to boot, there are three work arounds for this issue:

• Disconnect the monitor whilst the processor is booting and reconnected once booted
• If the monitor has a HDMI input, connect to the monitor via a DP++ to HDMI Adapter
• Connect to a different model of monitor

SX40 crashes when closing a project when failover is enabled but no redundant partner
An SX40 can be caused to reboot when all the following conditions are met:

• Closing a project
• Processor Failover is enabled
• No failover processor physically connected OR failover processor is not running a project

Once the processor has rebooted it can be controlled as normal.