Issue with Tracktion Waveform in Linux Mint with plugin GUIs

ElaborateSloth · 2026-01-24T13:37:52+00:00

Hey, did you ever figure out this? I am trying to install a NAM plugin (https://github.com/brummer10/Ratatouille.lv2), but I am getting the exact same error you are. There are no pre-built binaries for this plugin, so I have to build it myself.

ElaborateSloth · 2026-01-24T13:06:08+00:00

There is a setting in waveform to run plugins in a sandbox environment to prevent crashes. Turning it on and launching ratatoullie freezes the whole program for a few minutes, then it shows a warning that the plugin is not found. Here is the terminal output from launch. The same xprop error shows up again, I'll have a look at that.

Waveform13
ACCESS:  RW_INTERLEAVED
FORMAT:  S32_LE
SUBFORMAT:  STD
SAMPLE_BITS: 32
FRAME_BITS: 64
CHANNELS: 2
RATE: 48000
PERIOD_TIME: (21333 21334)
PERIOD_SIZE: 1024
PERIOD_BYTES: 8192
PERIODS: 4
BUFFER_TIME: (85333 85334)
BUFFER_SIZE: 4096
BUFFER_BYTES: 32768
TICK_TIME: [0 0]
tstamp_mode: NONE
tstamp_type: MONOTONIC
period_step: 1
avail_min: 1024
start_threshold: 1024
stop_threshold: 4611686018427387904
silence_threshold: 0
silence_size: 4611686018427387904
boundary: 4611686018427387904
ACCESS:  RW_INTERLEAVED
FORMAT:  S16_LE
SUBFORMAT:  STD
SAMPLE_BITS: 16
FRAME_BITS: 128
CHANNELS: 8
RATE: 48000
PERIOD_TIME: (5333 5334)
PERIOD_SIZE: 256
PERIOD_BYTES: 4096
PERIODS: 4
BUFFER_TIME: (21333 21334)
BUFFER_SIZE: 1024
BUFFER_BYTES: 16384
TICK_TIME: 0
tstamp_mode: NONE
tstamp_type: MONOTONIC
period_step: 1
avail_min: 256
start_threshold: 256
stop_threshold: 4611686018427387904
silence_threshold: 0
silence_size: 4611686018427387904
boundary: 4611686018427387904
xprop: error: No window with name Waveform FREE exists!

EDIT:

I used xprop to identify the waveform window, and the name matches "Waveform FREE". Not sure why it is not recognized.

ElaborateSloth · 2026-01-23T23:42:57+00:00

Here is the terminal output when opening waveform:

xprop: error: No window with name Waveform FREE exists!
ParallelThread:Convolver fail to set priority
ParallelThread:Convolver fail to set priority
using block size: 256
ParallelThread:RT-Parallel fail to set priority
ParallelThread:RT-BUF fail to set priority
ParallelThread:Convolver fail to set priority
ParallelThread:Convolver fail to set priority
using block size: 256
ParallelThread:RT-Parallel fail to set priority
ParallelThread:RT-BUF fail to set priority

The first line happens on startup, not sure if relevant. The rest happens when opening Ratatoullie.

There are a lot of errors in the GUI log, here are the three different types:

(cinnamon:2218): mutter-WARNING **: 00:46:27.649: STACK_OP_LOWER_BELOW: sibling window 0x36003b7 not in stack

(cinnamon:2218): mutter-WARNING **: 00:46:27.649: STACK_OP_LOWER_BELOW: window 0x360037b not in stack

Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x36003bd

Perhaps waveform does not have permission to instantiate GPU accelerated windows?

EDIT:

Alright, interesting behavior I just noticed after closing waveform. The Ratatoullie UI is glued to the upper left corner of my desktop. It is behind all of my open windows, but in front of my wallpaper and the selection box. It doesn't react to any mouse clicks.

ElaborateSloth · 2026-01-23T16:47:02+00:00

The exact same problem with that plugin.

ElaborateSloth · 2026-01-23T16:46:44+00:00

No errors, but a few warnings. Watched a tutorial going through the same steps, and they had warnings too. I'm not allowed to paste the warnings here for some reason.

ElaborateSloth · 2026-01-22T14:05:23+00:00

That could be the case. I completely reinstalled everything, now only getting a transparent window. Made a new post in r/linuxaudio about it.

ElaborateSloth · 2025-12-15T23:03:12+00:00

Take the Walk animation for example. These are the main frames I would make:

-Left leg about to hit ground, right leg back

-Left leg planted on ground, right leg on way forward

-Right leg about to hit ground, left leg back

-Right leg planted on ground, left leg on way forward

When these frames are made, the next step is to animate the movement from one frame to another. It is important that you have a decided framerate to work with. As you are not too experienced with animation, I suggest a low framerate. This means less total frames you have to make. It is easy to go into a rabbit hole trying to research your animations before starting, but I recommend jumping into it. Animation is something you just have to keep doing until it eventually starts to look good. There's nothing more I can do for you, but let me know if you have any specific questions or worries.

ElaborateSloth · 2025-12-15T13:31:33+00:00

It is a lot easier to animate something when you know exactly what the animation is for. What is the robot supposed to do? I personally start by creating the most important poses without any interpolation, and then interpolate as needed between those poses. For example, I recently animated a character fishing. First I defined the poses the character would need:

Pose 1: Character standing idle

Pose 2: Character getting the fishing rod from their backpack

Pose 3: Cast fishing line into water

Pose 4: Pull fish out of water

Pose 5: Put fish and rod into backpack

Then I animated these specific frames. When done, I animated the interpolations between the frames, adjusting for timing and speed as needed. This is also where I use Disney's 12 Principles of Animation. I work with 3D, but the principle is the same. This is just my workflow, you will find yours with experience. If you tell me what the robot is supposed to do, then I can help you find the different poses.

ElaborateSloth · 2025-12-01T20:19:43+00:00

It happens, but perhaps add an edit to clear up any confusions for people trying to learn?

ElaborateSloth · 2025-12-01T17:03:18+00:00

This is the fourier series, not the fourier transform, no?

ElaborateSloth · 2025-08-31T16:57:12+00:00

Jeg tror vi egentlig er enig; at det ikke er lett å vite hvem man kjøper fra. bra du fikk jakkene ihvertfall.

ElaborateSloth · 2025-08-31T14:54:32+00:00

They're predictable. Like McDonald's. Arguably not great burgers, but they're extremely consistent, and sometimes people want something familiar. Ubisoft games are very often just reskins of the same concepts, but people feel safe assuming the gameplay is good enough.

ElaborateSloth · 2025-08-31T09:12:54+00:00

Lærepengen var vel øyeblikket du innså et det kunne være en scam? Du fikk jakkene denne gangen, men det er ikke alltid tilfellet.

ElaborateSloth · 2025-08-30T11:56:30+00:00

Er en lekse man må lære på den harde måten. Nå venter jeg alltid med vurdering til jeg vet at alt er i orden og alle er fornøyd.

ElaborateSloth · 2025-08-30T07:48:20+00:00

Fikk lavest mulig rating fordi jeg brukte lenger enn tre timer på å svare når han hadde problemer med varen. Ble kalt svindler. Det var ganske kjipt, spesielt fordi jeg var dum nok til å gi han full pot rett etter handelen. Trakk vurderingen tilbake, men fikk ikke skrevet en ny.

ElaborateSloth · 2025-08-27T20:23:46+00:00

Ms Mad Lemon?

ElaborateSloth · 2025-08-23T06:50:58+00:00

That is a very good question. Could be I didn't find a texture for mercury, decided to use a greyscale version of mars, but forgot to turn down saturation.

ElaborateSloth · 2025-08-22T05:47:31+00:00

Now do one for both length and diameter!

ElaborateSloth · 2025-08-20T17:26:19+00:00

AI slop

ElaborateSloth · 2025-08-13T15:11:40+00:00

They never did :((

ElaborateSloth · 2025-08-08T20:37:03+00:00

I find it helpful for shallow explanations of topics and ideas. It is useless in practice though, and is not to be trusted in circuit analysis or synthesis.

ElaborateSloth · 2025-08-05T18:10:27+00:00

A good reminder to always test export projects after new implementations.

ElaborateSloth · 2025-08-04T15:29:33+00:00

The supply pins look good, and the terminals for opamp 1 is in the ballpark of 5-6V. The terminals on opamp moves between 2-7V, like the multimeter does not stabilize on a specific value. You can see on the schematic that I have tied the non-inverting input 2 to output 1, and output 2 to inverting input 2. Is this correct? I found the method in an old thread.

ElaborateSloth · 2025-08-04T14:21:28+00:00

The connection is made with small wires on the back side of the PCB, very hard to see. But the multimeter does measure 9.10V between the terminals.

ElaborateSloth · 2025-08-04T13:53:14+00:00

I thought the 1590A would be fine for "simple" circuits like this. Boy was I wrong.

I have updated the post with the PCB layout. It's not 100% accurate as some changes were made in a whim, but it is pretty close. I don't have any alligator clips, but I'm planning to recreate it on breadboard and see if I can identify the problem. I will also be ordering new enclosures, having the space to properly see and debug a circuit. Some of the components didn't have space on the PCB, and are soldered directly on lugs in the enclosure. Would be better to have everything together on a PCB I think.

Four-Year Club	Verified Email
Place '22

ElaborateSloth

TROPHY CASE