Hello, Someone said on here recently that many users want changes or features but few step up to get involved. So here is my attempt at getting involved.
Problem: Pro Audio enthusiasts see Linux command line as a blocker to creative output.
Solution: Build an app that tries to take care of system setup, allowing artist to create.
I’ve been trying to build a little program. I’ve collected most(?) of the pro audio low latency tweaks that I know of and wrapped them in one place with a GUI.
I’m not a coder, I’ve used language models; Opus 4.5 codes, GPT 5.2 plans and oversees progress but both work to a plan in order to keep focus.
I realise many coders will hate this but I’ve no other means to address the issue and It’s open for anyone to check and build upon or just copy the idea.
I did intend to build for all Linux flavours but we’re only at v0.1 and if this kind of thing was in YaST/ Myrlyn, it would make OpenSuse much more awesome!!
Anyway, please take a look and feel free to discuss or flame me for ‘vibe’ coding. I’ve put time, effort and £xpensive AI models into this just to share it.
It SEEMS to be working as expected but I’m sure it will be buggy or more difficult to implement it to a professional standard.
Hiya. Your repository at Github seems to be private. If you want to make your program available on OpenSUSE you need to package it and submit to Factory. Do note that packages can’t be submitted directly to Factory. You can read OpenSUSE’s packaging wiki on how to do it.
Thanks for flagging that… I’m not pushing to OpenSuse just yet, I’ll wait for someone more knowledgeable to help out with that… Just testing the concept for now.
Even if you’re not planning to push to Factory yet you can experiment with it in your home project in OBS. That way you can have signed RPMs for yourself. Also looks like your project relies on rpm to build itself, making it difficult to build on anything that doesn’t rely on rpm (Debian, Ubuntu, Mint, Arch, SteamOS).
Thanks, I’ll snoop around at OBS site, see if I can gt to grips with things.
As for RPM, yes, depending on how things go here, I’ll stick with RPM but it’s not too difficult to port for any distro, really. I already built some tooling for multi-distro stuff for this app but OpenSuse has been really solid so far - Might as well keep the tool here if there’s demand or if it sparks a talented dev to build something into Suse
A short test in a Tumbleweed Plasma (grubs-bls) VM shows severe flaws.
inconsistent naming in several places of the code: audioknob-gui vs audioknobs-gui
Audio Groups knobs errors out: “audio: Cannot run program usermod: No such file or directory”
severy GUI flaws: you can doubleclick in ALL fields and delete ALL GUI content
first column has no description. It is not obvious what the question mark means…
CPU Mitigations knob has zero effect: It states it needs a reboot. After reboot it still states it needs a reboot and the parameter is not applied to the kernel command line
Kernel Audit knob has zero effect: It states it needs a reboot. After reboot it still states it needs a reboot and the parameter is not applied to the kernel command line
KDE Indexer knob has zero effect: no feedback in status column on a Plasma system. Baloo is not stopped
Gnome Indexer knob changes in status column on a Plasma!!! system
Thanks for that. Are you by any chance using the dev branch instead of master? I’ve just been rebuilding a new branch with some of those expected bugs (at this point) that you mention. Your machine should run the master code just fine… I may have pushed the wrong branch, will check and figure out a better failsafe. thanks again
I followed your instructions on github (which by the way already fails at this point as the cd command calls for audioknob-gui whereas the git clone is called audioknobs-gui. See first point in the above test description.)
+ install -D -m 0755 packaging/audioknob-gui-worker /home/knurpht/rpmbuild/BUILD/audioknob-gui-0.2.0-build/BUILDROOT/usr/libexec/audioknob-gui-worker
Inavlid parameters: '-D' and '-m'
fout: Bad exit status from /var/tmp/rpm-tmp.4TnGOG (%install)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.4TnGOG (%install)
…but tweaked for OSTW. Once everything is stable there might be a few more ‘knobs’ to add but I’m doing whack-a-mole for now based on feedback from here. I’ve also got some trouble writing the correct prefix into qjackctl gui but i should have that donetoday.
I’m also pretty sure there are many optimisations to make!!
Thanks so much, both for the feedback and helping me find things I missed.
I think I’ve squashed most of the bugs with v0.3.5.1. I’ve also done some more work on features. I would love some feedback or help to make it better.
you can now see exactly what each knob does via info, see live cli statuses, and there’s some fancy stuff going on under the hood - at least, I think it’s fancy.
I’m pretty proud of myself so you’re welcome to to shatter my confidence with awful bugs and oversights.
Now has an unsigned .rpm release for install with YaST/ Myrlyn. (ignore the error message - it’s expected for unsigned rpm). Only tested on Tumbleweed - I’m not sure if Leap uses the same paths for the optimisations yet.
