Skip to content

Releases: zhdk/tpf-client

v2.0-beta18

20 Sep 14:30
Compare
Choose a tag to compare
v2.0-beta18 Pre-release
Pre-release

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

23 Aug 14:47
Compare
Choose a tag to compare
v2.0-beta17 Pre-release
Pre-release

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
tpf-client-reaper-track-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
  1. In REAPER, go to menu Options -> Preferences and select Control/OSC/web
  2. Add a new control surface with the following settings:
    image
    (Leave the IP address as it is, it is not editable, but auto-detected)

v2.0-beta16

04 Jul 08:46
Compare
Choose a tag to compare
v2.0-beta16 Pre-release
Pre-release

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

27 Jun 07:31
Compare
Choose a tag to compare
v2.0-beta15 Pre-release
Pre-release

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

20 Jun 13:14
Compare
Choose a tag to compare
v2.0-beta14 Pre-release
Pre-release

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

image

v2.0-beta13

30 May 15:53
Compare
Choose a tag to compare
v2.0-beta13 Pre-release
Pre-release

New in this release: OSC Bridge

image

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

11 Apr 09:38
Compare
Choose a tag to compare
v2.0-beta12 Pre-release
Pre-release

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

15 Feb 10:35
Compare
Choose a tag to compare
v2.0-beta11 Pre-release
Pre-release

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

v2.0-beta10

14 Dec 15:22
Compare
Choose a tag to compare
v2.0-beta10 Pre-release
Pre-release

The aoo library was updated to the current version. The new aoo version changed a few things, like order of arguments and message formatting. This pre-release of tpf-client was adapted to those changes. According to the author of aoo, aoo shouldn't significantly change anymore. Thus, we can assume that this pre-release of tpf-client is similar to the upcoming final release.

Other changes:

  • Set buffersize to 100 for [aoo_send~]. This is the send buffer and doesn't impact latency. There is no reason to keep it small. OTOH, a too small bu ffersize might cause glitches with larger jack blocksizes.

v2.0-beta9

06 Jul 14:00
Compare
Choose a tag to compare
v2.0-beta9 Pre-release
Pre-release

This release addresses the following issues:

  • UDP pipe feature was broken. When used, it broke OSC communication between peers. The problem was that messages from the UDP pipe set the OSC format to 'b' (blob) without setting it back to no pre-defined format.
  • Update Version of Wish.app this app is built on to version 8.6.11 (previously 8.6.12). Wish 8.611 seems to come with a significant performance gain. CPU usage is now much lower when channel indicators are flickering.
  • Based on Pd 0.54-0 (+ Christof Ressi's scheduler_fix branch that addresses issues regarding switching audio backends with callbacks enabled)