Tailscale and Rustdesk are my go to for family PCs.

Just clone the repo, chmod +x the install.sh and run that. ez

Also, it’s a low sample size so the variability will be massive.

A 50% increase sounds like a lot but, like you said, it could also just be one or two more than the previous year.

Given that they’re considering Flock, I’d guess that Flock is feeding them fear-porn statistics like this. It’s misleading but most people don’t understand statistics enough to know that they’re being misled.

Finally, the tyranny of the terminal is at an end.

I’m glad you got it figured out!

Just pay it forward, there’s always people with questions that need answered :P

Those are two different things.

You’re moving the goalposts, you said:

What matters infinitely more is who has access to your data. And Google is one of the worst offenders.

That’s completely different than who benefits financially from your phone purchase.

shaming the idiots

solidarity is required

Your team building tactics could use some work.

-An idiot

Buying a phone from Google (HTC really) does not give Google access to your data.

There are no Google services installed by Graphene, you have the option of running Google services if you choose, but even if you choose to do so they are kept in a sandbox and not given privileged information on the system.

“Why did you lock your doors, what did you steal?”

It shows that people internalize censorship and start doing it unprompted.

It’s a video of him speaking in his own words, not much salt needed.

Can I put that in some config to make it stick?

Make a file in pipewire.conf.d: ~/.config/pipewire/pipewire.conf.d/min-quantum.conf

With this, replace the quantum with one you’ve found works best:

context.properties = {
    default.clock.min-quantum = 512
}

Restart pipewire for it to take effect.

I have two loopbacks (I like having music and games each grouped separately from other audio), an echo-cancel and a noise cancel (filter-chain with a single rnnoise node), all configured via .conf files. As an aside, is there a “best order” to chain echo cancel and noise cancel?

Echo cancel seems to have a quantum/rate of 480/48000 across the board. Loopbacks, rnnoise and alsa_output (my headset) all have 0/0. I imagine it makes sense for the Loopbacks and rnnoise, but should it be something else for the main output?

I have been doing echo-cancel -> rnnoise. That way echo cancel gets a clean stream to do what ever correlations that it needs to do and then rnnoise de-noises what is remaining.

As far as the latency, I think it is because echo cancel needs a bit of a default wait in order to actually hear the sound coming out of your speakers (speed of sound is slow, smh) which is why I think that delay is there (though this is complete speculation, if someone knows better I’d love to know).

The quantum of all of the devices is propagated through the chain so if you have echo cancellation in a graph then all everything will use at least its quantum (if there are not higher quantum objects in the chain). If a device doesn’t have a quantum, it’ll either use the min-quantum or the highest quantum of any node in the graph.

Sounds like a compressor would be a good idea to have anyway. Is that also doable through the config? I’m not opposed to graphical tools, I just feel like working with the config directly is more educational. It’s also more prone to screwing things up, but that’s just bonus lessons on what not to do.

I agree, learning the underlying system pays dividends.

Any LADSPA filter will work as a node in pipewire. So the world is your oyster!

This explains how to set it up better than I can here: https://forum.endeavouros.com/t/pipewire-filter-chains-normalize-audio-noise-suppression/31661

Curiously, the reason I looked at echo-cancel in the first place is that Discord’s own echo fucks with things, cutting me out at times while also not cancelling the echo at others.

Yeah, I’ve had similar experiences. I typically disable any sound processing done by the application and depend on my own plugins to handle that.

If it’s consistently breaking then your distro is messing up something. Bad defaults, broken scripts, etc.

The problem is that the environment variables are expected to be there and they are not there.

So, if you’re not doing something odd, then your distro is pushing misconfigurations or some other piece of software is interfering with your environmental variables. Whatever the vanilla setup for your distro is, it is not setup correctly.

I do agree that it’s frustrating, just aim the ire in the right direction… whoever configured your system’s defaults.

You don’t understand, the problem isn’t the people who put in no effort.

It’s those evil LLMs, they are to blame.

New tip just dropped

everything

You’re in the right place, most social media users can’t properly formulate their thoughts into sentences, lol.

That’s not a pipewire problem, that’s a systemctl problem.

Failed to connect to user scope bus via local transport: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined

The error means systemctl --user can’t reach your user’s D-Bus session because the required environment variables aren’t set. This typically happens when you’ve switched users via su or sudo rather than logging in directly, because htose don’t initialize a full systemd/PAM session. It could also be that your session wasn’t properly initialized by systemd-logind or a number of other things. Try spawning a proper user session:

sudo machinectl shell your_username@

and try the systemctl command again.

My pipewire seems to have issues with crackling audio and severely dampening my mic and I have no clue why.

Pipewire’s default quantum (buffer size, effectively) is incredibly low, this is good for low latency audio but anytime your system is too busy to keep the buffers filled you get crackling.

If you look at pw-top you’ll see all of your devices and nodes. The quant column is probably 1 or a very small number for the devices.

You can increase the quantum with this command. This only lasts until pipewire restarts:

 pw-metadata -n settings 0 clock.min-quantum 512

At a sample rate of 48000, this is roughly a 10ms buffer. 1024 is 20ms, etc. You want it as low as possible without getting crackling. Start with 512 and adjust from there (you don’t have to use a power of 2, a quantum of 1234 works just as well).

severely dampening my mic and I have no clue why.

By default pipewire doesn’t do any ‘mic boost’, as Windows calls it. You can get the same effect by raising the maximum volume.

In your sound control panel you should be able to turn the mic up higher than 100%. In KDE Plasma, you can do this in System Settings -> Sound -> Configure Volume Controls… [top right button] -> Raise maximum volume.

Alternatively, you can use EasyEffects to add a compressor. This will boost your mic volume and also prevent it from getting too loud

Compressors basically reduce the dynamic range of an audio signal by attenuating loud sounds and boosting quieter ones, this would provide a better mix.

Other useful plug-ins are noise canceling, (kills background noise) and echo canceling (lets you play sound out of your speakers which won’t get picked up by your mic). Sometimes apps, like Discord, will do this signal processing for you while others, like Signal, do no signal processing.