v2.0.0

Since the development of AOO has reached a level where protocols and internal interfaces can be considered stable, this release marks a stable release of the tpf-client.

Minor changes include:

• Switch platform detection from 'command' external to abstraction using 'Homedir' heuristics
• Switch 'Homedir' detection from 'command' external to [file] based 'Homedir' detection
• Skip 'command' external alltogether, thus enabling Windows support

This release features standalone apps for macOS (universal), Linux (amd64) and Linux (arm64).

v2.0-beta19

This pre-release contains minor bug fixes:

• REAPER: make sure that channel and spider labels are updated after switching session (e.g. 'DUO' -> 'HEXTET')
• finally get rid of blank window issue (thanks to IOhannes for the loading via plugin idea)
• use current Pd again
• many improvements to app building
• suppress dialog about documents directory
• Switch to TclTk 8.6.15 for tabbed view support (we had 8.6.11 previously for performance reasons)

The provided macOS app is code-signed and notarized properly for the first time. The app should run right away after downloading (no right-click -> 'open' necessary).

v2.0-beta18

This pre-release features various fixes and adds support for the plugin ICST_AmbiEnc's new feature to set channels through OSC messages:

• Peer names are now reflected in the ICST_AmbiEnc plugin (part of the tpf-jam-reaper package). For it to work OSC receive must be enabled and port set to 50001.
• Work-around visual artefacts in settings panel after loading settings with load from.
• Settings from load from are immediately applied (no need to load settings twice)
• Menu About shows tpf-client's README, not Pd's.

v2.0-beta17

This pre-release features:

• up-to-date Pure Data (contains some regression fixes)
• up-to-date AOO
• modest REAPER integration: Track names in REAPER reflect peer names

---

REAPER OSC configuration:

1. Save the following as OSC/TPF.ReaperOSC in the REAPER configuration directory:

DEVICE_TRACK_COUNT 128
DEVICE_SEND_COUNT 128
DEVICE_RECEIVE_COUNT 128
DEVICE_FX_COUNT 128
DEVICE_FX_PARAM_COUNT 128
DEVICE_FX_INST_PARAM_COUNT 128
DEVICE_MARKER_COUNT 0
DEVICE_REGION_COUNT 0
REAPER_TRACK_FOLLOWS REAPER
DEVICE_TRACK_FOLLOWS DEVICE
DEVICE_TRACK_BANK_FOLLOWS DEVICE
DEVICE_FX_FOLLOWS DEVICE
DEVICE_EQ INSERT
DEVICE_ROTARY_CENTER 0
TRACK_VOLUME n/track/volume n/track/@/volume
TRACK_NAME s/track/name s/track/@/name

2. In REAPER, go to menu Options -> Preferences and select Control/OSC/web
3. Add a new control surface with the following settings:
   
   (Leave the IP address as it is, it is not editable, but auto-detected)

v2.0-beta16

This release includes the following changes:

• Upgrade Pd to include regression fixes
• Upgrade aoo to the develop version from 2024-07-01
• Revert the workarounds to address Pd regressions in tpf-client

DO NOT USE
It appears the most recent fixes introduced a new issue, where the tpf-client window stays blank. Only after resizing the window, all elements become visible.

v2.0-beta15

This release includes the following changes:

• Suppress ugly scrollbars by working around a regression in Pd 0.55
• Upgrade aoo to the develop version from 2024-06-24
• Fix warning about default peer names

v2.0-beta14

This release includes the following changes:

• Pure Data is upgraded to version 0.55.0
• aoo is upgraded to the develop version from 2024-06-20
• mute buttons for up- and download streams are added to the osc bridge

v2.0-beta13

New in this release: OSC Bridge

The OSC bridge provides 8 slots for transmitting raw UDP or OSC data between peers. A possible use case is to synchronize the state of DAW plugins among peers.

Meaning of the fields:

• ambienc: Name of the channel. Peers can share data streams by agreeing to a channel name.
• 4300: Listening port on tpf-client. Configure your sender (plugin, etc.) to send to this port. Any incoming data will transmitted to the other peers
• localhost: This field defines the destination of the data received from peers. If the receiver runs on the same host, use localhost. You can also use any other hostname or IP address.
• 4301: Port of the receiving application (plugin, etc.). Any data received from peers will be sent to this port

The buttons:

• R: Reset all fields so that all data sharing is stopped on this channel
• P: Enable printing of sent or received data to the message panel for debugging purposes.

The indicators:

• ▲: Flashes green when OSC is transmitted to peers. Flashes blue for non-OSC data
• ▼: Flashes green when OSC data is received from peers. Flashes blue for non-OSC data

v2.0-beta12

This release incorporates the latest developments of aoo. No other changes have been applied to tpf-client.

NOTE: This version of tpf-client is not compatible with any previous version.

v2.0-beta11

This release incorporates the latest developments of aoo. No changes were made to tpf-client itself.