Tracker + and PipeWire - a pipedream?

Tracker
1

Have just got my Tracker + and flashed it with the latest firmware. Works fine with a set of headphones.

I am trying to connect it to my laptop via USB-C. When I do, after selecting USB Input + output (you have these backwards btw input should be output and vice versa).

$> lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04.3 LTS
Release: 24.04
Codename: noble

  1. I get two devices in Pipewire. An input and an output. I can then take another output device - say spotify and send the signal not to my sound card but into the Tracker plus input. I can then record the signal. I can then proceed to take the output device and send the signal to a soundcard. I can then listen to Spotify though the plus. Spotify→Tracker→Soundcard. But I cannot hear anything the Tracker itself plays. Just spotify.
  2. When I then in the usb menu select “Storage” all of a sudden a new device, that I suspect is the general output appears and patches itself. It is only there for a split second and then dissapears.
  3. When “storage” is active the large patch output with individual tracks appears, and I can take the output - track for track - and put it into a soundcard - which then plays the music running on the Tracker +.
  4. As soon as I leave “storage” mode - this all goes away again.

I hope you plan to do some work to this in order to get better compability with PipeWire, because today - there really is no reason to install Jackd any more. The functionality is already there by default via PipeWire.

with regards

Nikolaj Hansen

2

:open_mouth: :thinking:

3

Thats interessting, because I don’t remember having any issues on my machine … so lets see:

$ lsb_release -a
LSB Version:    n/a
Distributor ID: Arch
Description:    Arch Linux
Release:	    rolling
Codename:       n/a

My pipewire is at 1.4.8 and I use a 6.16.8-zen Linux kernel. The PT+ has the latest 1.2.0 firmware. And something is broken, because I have to restart pipewire whenever I change the TP+ USB configuration.

  • On the first connect, pipewire shows the TP+ midi connections, but no audio connections.
  • After restarting pipewire (which runs as a user service: systemctl --user restart pipewire) the audio channels show up. But I need to restart pipewire after changing the TP+ USB configuration.

Ok, that is manageable. But the TP+ Midi configuration seems to be out of order, I did not set anything to send/receive from USB, still it shows up as Midi device.

Regarding TP+ USB Audio configuration:

  • Off: only midi channels shown (although did not configure Midi to be USB)
  • Input: TP+ shows up in the pipewire graph with 28 channels, no auto connection
  • Output: TP+ shows up as audio sink with two channels
  • Input + Output: as expected

Playback to my Linux machine seems to be fine, but recording to TP+ results in heavily distorted recordings, something is very wrong here.

4

If I restart pipewire I get results more in line with yours - not the same though. I think it is a little beside the point - USB is supposed to be hot pluggable and restarting the entire sound system every time a setting changes in a connected device is not really a way forward.

And yes, all the MIDI devices turn up over USB even if they are turned totally of in the MIDI config.

image
image790×834 106 KB

This config allows me to listen to and record via (through) the TP. However there is no way to get just a stereo signal of the music the tracker itself makes. This should be simple since this is already being mixed for the physical line out jack.

With regards to distortion I think you need to watch the level meter in the Sample recorder as you send in signal. Never let it go yellow and definitely not red.

No, I hear it when I replay the recorded wav as well. Just not on the passthrough monitor signal.

5

I think I solved this.

In order to get better recognition of USB devices and streams I upgraded the Pipewire subsystem of my Linux box to 1.4.9. I do not think this is strictly necessary if you already see the different devices from the Tracker + in linux. After updating I now consistently see the Tracker + when I connect it.

sudo add-apt-repository ppa:savoury1/pipewire
sudo apt update
sudo apt full-upgrade
sudo apt install pipewire-audio pipewire-jack pipewire-pulse pipewire-alsa wireplumber

I still had the same distorted audio after upgrading. And I started looking into what was actually being sent over USB between the devices. pw-top is a good tool.

Turns out the sample rate of what is sent from the Tracker + is sampled in 44.1 kHz. Pipewire defaults to 48 kHz.

Prepare the wireplumber config for a user account

$> mkdir -p ~/.config/pipewire
$> cp /usr/share/pipewire/pipewire.conf ~/.config/pipewire
$> vi ~/.config/pipewire/pipewire.conf

Then change the system to run in 44.1 in place of 48 kHz.

## Properties for the DSP configuration.
    default.clock.rate          = 44100
    #default.clock.allowed-rates = [ 48000 ]
    default.format = "S24LE"  # Or "FLOAT32LE" if you prefer floating-point for DAW routing
    default.clock.quantum       = 256
    default.clock.min-quantum   = 32

Then restart the sound subsystem

$> systemctl --user restart pipewire pipewire-pulse wireplumber

Connect your Tracker + and your laptop. Make sure the tracker sends and recieves usb audio in the config / usb menu. Map the two first channels from the the Tracker plus to a soundcard / usb headset or other on your linux host (using Helvum or qpwgraph).

Now play something on the Tracker +

Verify the signal compability (same sample rate and bitwidth)

$> wpctl status

Find the id of your Tracker+ and the soundcard/device you patched it to.

$> wpctl inspect <id>

Make sure the signal sent matches what is recieved.

This makes my setup work. I know I now default to 44.1 kHz in place of 48 kHz, but my old heavy metal ears can’t tell the difference.

with regards
Nikolaj Hansen

PS. An option to switch samplerate (and bit width?) to what the hardware supports would be a nice update to the Tracker + firmware. Then I could probably just have flipped the sample rate from 44.1 kHz to 48 kHz and it would work.

3 Likes