Depends on the program, they don’t use system libraries so if they have a lot of dependencies then they’ll be larger.
An example:
Steam Flatpak: 35MB
Steam pacman: 19MB
On one hand, it’s only a few MB. On the other hand, it’s 54% larger.
Flatpaks can also depend on other flatpaks. For example, graphics card support requires about 1-1.5GB of flatpak dependencies even though your system already has graphics card drivers.
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.
JET FUEL DOESN’T MELT 5G SIGNALS WAKE UP SHEEPLE