Scratching Sounds Tidal Cycles (+ SuperCollider + SuperDirt)

Thanks for your hint. I tried rtcqs some time ago and optimised my system regarding. But I could not notice any improvements.
At the moment I use the internal Intel soundcard. As soon as I have some more time I will try to use a Fast Track Ultra 8R and/or pipewire.

I am quite sure you are bound get problems by using the internal soundcard. At least in my experience there is much more headroom with an external USB device (I have a quite old Scarlett Focusrite 2i2 which works well). You might also have a look here to analyze your setup - but I doubt there will be any major improvements possible if you use the internal sound card.

jackd is not designed for consumer / desktop audio. You will need a reasonable good soundcard probably. I think all the usb audio devices that work on a ipad / ... works on Linux too.

Contrary to the above I've used jack with internal soundcards and had no problems for many years. I'm surprised there's a problem with a Lenovo T480.

Despite being fairly new, pipewire is really surprisingly good and easy to use. It emulates both jack and pulseaudio seamlessly, you can even use qjackctl or whatever to wire things up.. The only difference is the start/stop jack buttons don't do anything because pipewire is always running.

A huge plus for me is that it integrates all the sound devices together, so you can e.g. connect one soundcard to another, or output to more than one.. When performing I love that I can get everything running and tested on my internal soundcard, then plug into my USB di on stage, have it appear in jack so I can wire it up and play without restarting anything. It's the future!

1 Like

Connecting sound devices together should also be possible with jack.

Hm I can imagine that doing all the stuff Pipewire does, can also be a disadvantage. It's more complex in the background. But for newbies Pipewire might give benefits, such as easier to setup and support for bluetooth devices, I don't know. I've no real need for it atm and stick with what works.

Hopefully my future will be that I can hear some Tidal sounds. :grimacing:
I updated SuperCollider from 3.11.0 to 3.13.0-dev (compiled from source). The first run with the new SuperCollider looked promising: I got no xruns when using the # legato (irand 4) effect. But then I got some late messages. So, I increased the latency in the SuperCollider startup script. After rebooting the SC server I got the following error message:

SuperDirt: listening to Tidal on port 57120
Server 'localhost' exited with exit code 0.
server 'localhost' disconnected shared memory interface

Only rebooting the PC and starting SC again helps.
I'm about to take drastic action and install Tidal cycles on a Windows machine.

I don't think these drastic measures are the right approach. Patience.
Is buying a 25 Euro/$ ( Behringer U-Control UCA222) usb card a option, or is that too drastic as well? :wink:

Just ordered one of these, will post on Monday if it solves the problem.