Skip to main content

Fourier Audio transform.core v1.7.0 Release Notes

  • transform.core Version: 1.7.0
  • Windows transform.client Version: 1.7.0
  • macOS transform.client Version: 1.7.0

Summary​

transform.core v1.7 is upon us! Featuring:

  • ⚡ HYPERPORT: A new, lightning-fast audio protocol delivering a 1.2 ms round trip to DiGiCo consoles.
  • 🔌 Patch Bay: Easily see and modify the patch for your entire system in one view.

…and many other exciting improvements to the transform world!

New In This Release​

  • TF-3658: HYPERPORT supports a low-latency, single-cable audio link between a transform.engine and a DiGiCo console. Controls to select an audio transport (Dante or HYPERPORT) have been added to the Settings tab.
  • TF-870: Added a patch bay in the Settings tab, allowing you to quickly adjust the patch between chains and input/output channels.
  • TF-1114, TF-4567: You can now steal patches from other chains, unpatch individual channels, and unpatch a chain entirely. This makes it easier to rearrange the patching of your show.
  • TF-32: You can now see and modify the engine's IP configuration, such as its IP address and subnet prefix, in the transform.client desktop application.
  • TF-4480: A readout of the subnet mask (for example, 255.255.255.0) associated with a configured subnet prefix (for example, /24) is shown in the Networking tab.
  • TF-4662: A close button has been added to the chain detail pane, allowing you to create more space in the UI if needed.
  • TF-4673: macOS users can now copy and paste throughout the application.
  • TF-28: A button to reboot the connected engine is available in the System menu of the transform.client desktop application.

Changed Functionality In This Release​

  • TF-4370: The OLED on the front of transform.engine will now display a warning triangle instead of “err!” when an erroneous condition is detected, improving international recognition and consistency with transform.go.
  • TF-4822: You can no longer configure a device with the static IP address 0.0.0.0.
  • TF-4792: Under certain circumstances, transform.engine could enter an undesirable Energy Efficient Ethernet (EEE) mode. This is no longer possible.
  • TF-4646: Improved logging if a service fails.
  • TF-4824: Logs downloaded from an engine now include logs from a test run.
  • TF-4892: Logs downloaded from an engine now include additional information about low-level system performance.
  • TF-4804, TF-4898: Clarified the instructions for cleaning a unit if it is overheating.
  • TF-4918: The front-panel warning indicator is now cleared when a system mode change means the unit is no longer in an error state.
  • TF-4715: The subnet prefix field now limits input length during value entry.
  • TF-4188: Improved the clarity of some network configuration validation errors.
  • TF-4168: The desktop client now consistently uses “unit” rather than “engine”.

From this release, the software that runs on transform.engine and transform.go hardware is called transform.core.

Bugs Fixed In This Release​

  • TF-4704: A rare plugin behaviour could allow a plugin to escape the transform.engine per-core isolation sandbox, resulting in interference on other DSP cores. This route for sandbox escapes has been closed.
  • TF-4735: In certain cases, repatching multiple chains very quickly could cause DSP spikes.
  • TF-4623: Under certain circumstances, after switching to Offline mode, the plugin host could still be running while the system believed it to be stopped. This caused actions that require the plugin host to be offline to fail.
  • TF-4963: Under certain circumstances, after loading a showfile, the renderer could take a long time to reconfigure or become stuck while reconfiguring.
  • TF-3629, TF-4392: Very rarely, misbehaving USB devices could cause the plugin host to go offline while being connected or disconnected.
  • TF-4827: A potential security flaw, RUSTSEC-2026-0111, was discovered in a third-party component used by transform.engine. The issue has been patched; there was no known impact on transform.engine software.
  • TF-4920, TF-4921: In certain very rare cases, Maestro could fail to start with an error relating to licensing.
  • TF-4592: Keyboard navigation is once again possible through the list of plugins in the Library tab.
  • TF-4687: On the connection screen, device metadata was not shown when the client computer's IP address changed from outside a device's subnet to an address within it.
  • TF-4688: On the connection screen, the “discovered device not connectable” display was not shown when a previously connected device was discovered at an IP address that was not currently connectable.
  • TF-4696: On the connection screen, discovered engines could briefly be displayed as unconnectable on startup.
  • TF-4778: On the connection screen, clicking a device could cause the list of devices to reorder under the cursor.
  • TF-4796: On the connection screen, a device that ceased to be available would remain listed as “Discovered”.
  • TF-4807: On the connection screen, two instances of a device could be shown under certain rare circumstances.
  • TF-4808: On the connection screen, previously connected but currently unconnectable devices could cause discovered devices to flicker.
  • TF-4861: In certain pathological cases, log files could grow very large and then fail to download. Log-file downloads no longer fail in this case.

Compatibility Notes​

Showfiles are fully backwards and forwards-compatible with transform.engine v1.1-v1.7.

transform.engine v1.7 is fully backwards compatible with transform.client v1.0-v1.7, and vice versa; you can connect to an engine running v1.6 from a client running v1.7, and to an engine running v1.7 from a client running v1.6.

Downgrading to versions prior to v1.7 is not possible once v1.7 has been installed.

Known Issues​

Users should be aware of the following known issues in this release, which we hope to address in a future update:

  • TF-2698: When bx_limiter and AMEK EQ 200 are used in a chain, recalling cues can cause a momentary increase in DSP load. We are working with the plugin publisher to resolve this issue.
  • TF-3434: It is possible for multiple network interfaces to be configured with overlapping subnets via DHCP, causing IP network issues.

A small number of plugins may experience compatibility issues running on transform.engine. For details, see our plugin compatibility database.

Docs, Support & Bug Reports​

We warmly welcome bug reports on our discussion site. We'll also be happy to chat and answer any questions you may have there!

To learn more about using transform.engine, please check out our documentation, where you can also find handy walkthrough videos showing how to get started.

If you need support with transform.engine, please contact your local dealer or distributor, or email us at support@fourieraudio.com.