Hi tux, EQ is all done by the libasound plugin for the EQ:  libasound2-plugin-equal, so it's all native alsa doing the work, AlsaTune is just a gui frontend for the alsamixer and eq that you can access in terminal, plus some other features added like saving EQ pre-sets and such.

Working on 2.0

Yeah...so it seems there's no scroll function or auto-sizing for the yad list dialog, at least not in the old versions being used in the repo. For the moment I added a little height. arrgh.

I added an error check to look for ~/.asoundrc right at the start and exit if there isn't one. But now i'm thinking in the error message to also add the ability to copy a simple .asoundrc (to be shipped with the mxeq/AT package) to the users home if there isn't one, and then continuing (or hit cancel to back out of course).

I'll be modding AT a fair bit to add a button for the card-switcher and some other functions including a button to test sound, using aplay to play a .wav file I made, just 3 seconds of a 500hz note, the idea being you can test whatever changes you made with the card-switcher right there in the gui after doing it, without having to cycle audio/video apps on and off.

Hah, I love it...yep...Vuu-do Linux, handcrafted using stepwise refinement and multi-solutional iterations (hit-or-miss).

Thanks for the help, I really appreciate it and at some point i'll take you up on the offer to test the next version.

724 lines in asound.conf? Holy crap, that's epic! Yeah I can see where my little script probably wouldn't be good for that system, but it's a dang fine one for testing the limits of it for sure.

Thank you @fsmithred!!

I'm so sorry y'all are having to deal with stuff like this right now. Seems like there's quite a few of these upstream shenanigans going on with this release of debian.

Ahh I see, so yeah it's pretty close to the old school way of measuring ram, what's actually being used, nice.

If you run conky it's easy to check without ever opening anything at boot-up, you can use the "mem" command to get ram usage, and that's the newer way with all buffers and cache and such added in. But you can get the old behavior still at least in Daedalus by using "legacymem" in place of the mem command.

I use the new method generally to get a fuller picture of usage, but I tried legacymem last night for giggles on Vuu-do, and the mini runs 230-240 mb at idle, and the max runs about 260-270.

Openbox FTW.

Lol, more hilarity as the world flails about, the reason Cloudflare went down wasn't a DDOS or other attack, it was shit coding in the cloudflare challenge that everybody hates to start with that took down 20% of the internet.

Ahh I gotcha, and that's the kind of thing I need to know to proceed, problem is I don't have a machine around here to test, I get one line on my single-card lappy, two on the library machine...without having a complex machine with multiple outputs around to test on it's gonna make it really hard for me to extend this script. I kinda need to see what things are doing, my methods involve a lot of trial-and-error.

Basic philosophy/use-case is for Vuu-do as it already has a working alsa system, and is meant for simple everyday garden-variety use, just a quick switch for those machines that have an analog and an HDMI output as most of the time the dual-setups default to HDMI as card 0.

At least at this stage...baby steps...but i'd like to pursue it and figure out all the edge-cases and sub-devices and such so I can package it with AT for general use at some point.

Ummm, GPU? Ya lost me there somewhere...

Sorry, I have a tad bit of the 'tism so sometimes I don't recognize sarcasm.

But I don't think everyone is whining, lots of folks contributing new info about sound and potential solutions.

But I should stay out of Pipe-how-to threads in general as I am a founding member of TDAM (The Devuan Alsa Mafia).

I'm afraid I agree. But there's a lot of work to be done to make pure alsa more accessible to an average non-technical user. Working on that myself, and forum member @rations just posted some nice work on alsa+jack systems. Even Igor's doing some good, lol, so hopefully there's some resurgence in interest for a nice low latency system without a lot of software on top of it, just needs some simple gui methods to control configs really.

I never removed anything but gnome-keyring in mine, the pkcs11 package had to stay because Exaile wouldn't play internet radio without it (more gnome crap, this is why i'm making my own music player).

Yeah it might take a re-boot, but you can try logging out and back in on a live session after removing just the gnome-keyring package.

Or you can try just editing the exec line for chromium, that will definitely work.

There's been a LOT of updates to Excalibur since I made those iso's, might be better to just go for the new Devuan netinstall iso and choose Mate for the DE during that portion of the install, some things have been fixed in the newer versions.

Believe me, there was a lot that I wanted to do on those iso's, but I was committed to putting out something that was pure Devuan as-delivered without any of my hackiness, lol.