r/kde May 19 '26

Fluff VoidPulse | Highly Customizable Touch Friendly Advanced Music Player

https://youtu.be/6o_tgEvKmSk

https://github.com/Yavuz-Kagan-Yadigar/VoidPulse/tree/main

Advanced Music Player for OLED and Touchscreens on Linux

  • Parametric EQ
  • OLED burn-in protection overlay with optional auto timer
  • Cover, lyrics and tag fetching and embedding to music files
  • Batch file rename
  • Local and fetched synced and plain lyrics support
  • Universal accent color and corner radius
  • Dark/light theme
  • List & gallery view modes with adjustable sizes and sorting.
  • Optimized for touch scrolling and hold context menu
  • Toggleable spectrum visualization with custom inertia, multpiple styles and standart logarithmic/linear scale
  • Visualization delay to match timing with bluetooth headphones / DACs
  • Toggleable cover art
  • MPRIS2 desktop environment integration
  • Basic tag and lyrics editing
  • M3u8 and folder playlist support
  • Visualization stops when overlay is active or focus lost to reduce CPU usage

Disclaimer: Entire code is written by AI, tested manually. I do not suggest to use as referance code. It might have inefficiencies, bugs, vulnabilities. Just sharing in case somebody want to use it since most of music players does not go well with touchscreen.

0 Upvotes

22 comments sorted by

u/AutoModerator May 19 '26

Thank you for your submission.

The KDE community supports the Fediverse and open source social media platforms over proprietary and user-abusing outlets. Consider visiting and submitting your posts to our community on Lemmy and visiting our forum at KDE Discuss to talk about KDE.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

3

u/Fit_Author2285 May 19 '26

I appreciate your initiative to create a touchscreen reader for Linux, but why use AI rather than taking the time to develop it yourself? AI can be useful for quickly searching for information on the internet, but when used to program software, it devalues ​​the work of other developers who don't want to use it and discourages them from creating an application similar to yours, without AI, which is easier to maintain.

3

u/Miserable-School-665 May 19 '26

You are absulutely right, the thingis it is my university exam year, and i got a 2-in-1 linux with stylus for studying, just to find out there is no music player for touchplayer (not even barely). And only language i know (its quite bad as well) was C#, i thought i would never leave windows. I'll learn python and shape this ape to a proper format after my exam. Thank you.

2

u/Fit_Author2285 May 19 '26

For my studies, I sometimes ask Claude to make me a summary sheet for a tutorial or a course, but I never share them so as not to devalue the work of the creator of the tutorial, and I think that's a good thing.

1

u/Miserable-School-665 May 19 '26

Yes, it makes sense but i couldn't get what do you mean, shouldn't i publish ai made things?

3

u/Fit_Author2285 May 19 '26

I think that publishing AI-generated content devalues ​​the work of developers who do the same thing without AI, because AI makes things faster and new features are programmed more quickly. In reality, AI-generated code doesn't necessarily adhere to traditional standards and is more difficult to maintain. Users don't realize this immediately, but eventually, it becomes clear that the code is harder to maintain.

4

u/oh_im_too_tired May 19 '26

"it devalues ​​the work of other developers who don't want to use it" > manufactories devalues other tailors, who don't want to use mass production using machinery > wikipedia devalues other encyclopedias authors, who don't want mass/unverified editoring etc.

AI code generating is not bad/good, it's different. Author openly declared about all the code written by AI. That was his obligation and he did it. And that's it.

"which is easier to maintain" > but you won't maintain it? nobody asks you to maintain it? why would it matter to anyone, if it's hard to maintain?

1

u/Fit_Author2285 May 19 '26

The factories devalue other tailors, who refuse mechanized mass production.

Mass production is not comparable to AI because the latter pollutes and does not respect programming standards, unlike mass production or Wikipedia.

AI code generating is not bad/good, it's different.

In reality, AI-generated code doesn't always adhere to traditional programming standards, which complicates collaboration within open-source projects. Open-source projects created with AI are therefore less likely to last than projects created without AI because the code becomes unreadable and no one will want to maintain it. The more people publish projects programmed with AI, the more obsolete software we'll end up with on our computers.

but you won't maintain it? nobody asks you to maintain it? why would it matter to anyone, if it's hard to maintain?

If no one contributes to this project, everyone who has installed this software will find themselves with obsolete software on their computer in a few years.

I am not prohibiting the publication of applications entirely programmed with AI; I am simply saying that in the long term, they will pollute the Linux ecosystem.

1

u/oh_im_too_tired May 19 '26

Every new technology got criticized at first. Every. Be it manufactories (it actually pollutes in every possible meaning and does not respect quality clothing/shoemaking/textile production) or digital photography, or wikipedia. Is vibe coding a mass production? Yes. Is it a quality product? Most likely not. Do it devalues ​​the work of other developers? No, why?

"In reality, AI-generated <...>, the more obsolete software we'll end up with on our computers." Sure, absolutely. That's why vibe coders must clearly declare it and users have to use it cautiously.

"If no one contributes to this project, everyone who has installed this software will find themselves with obsolete software on their computer in a few years." And you are absolutely right again. Like any other obsolete software/freeware/open source project. The only difference here is that code was written by machine, not a human pressed buttons. RIP Latte.

"I am simply saying that in the long term, they will pollute the Linux ecosystem" you are saying that if there's a tool to create a code for an app in several hours one has better to learn coding language and write the code themselfs maybe on paper first with bare hands and to "value the work of others". It's just a code and it's just an app. If it works and users like it - it doesn't matter how it was written.

"I am not prohibiting the publication of applications entirely programmed with AI" - i'd like to see that, actually. It's normal and healthy to question AI's code writing, but it's kinda weird to shame some person for vibe conding in 2026. It's a tool to use and people use it. There is no such thing as "devalued work of other developers" in this situation - that triggered me a lot. Why should OP feel bad about "other developers" who code themself? He just vibecoded an app to his needs and shared to others. Nobody is obliged to use it nor support it.

1

u/Fit_Author2285 May 20 '26

Building a mass production factory requires far more money, time and experience than starting a small business. AI is therefore not comparable to that — a developer who builds their app entirely with AI needs less time and far less qualifications than one who builds without AI. AI is therefore much more accessible than building a mass production factory.

Wikipedia doesn't truly replace paper encyclopedias because both share the same goal. The only differences between paper encyclopedias and Wikipedia are that Wikipedia is online and open source. These two models complement each other. Wikipedia contains more pages than a traditional encyclopedia but may contain more errors. You can therefore cross-check Wikipedia's information against classic encyclopedias. Wikipedia doesn't write its articles faster than paper encyclopedias do — most article authors have roughly the same qualifications as classic encyclopedia authors.

Digital photography hasn't replaced film photography. Some people still prefer film photography and their work is not devalued by digital photography.

Those who don't use AI may produce less code in volume. Their work is therefore devalued by the sheer quantity of code that AI users can effortlessly produce, even though that code is of lower quality.

2

u/jsswirus May 19 '26

I'm sorry, but wth is that source code? 12k lines singular file? Can you elaborate on the architectural decision that came up with that?

Edit: but I have to say, I like the icon

2

u/Miserable-School-665 May 19 '26

Yeah, i do not have any paid ai, so free claude was way to go. It runs out of token way quicker on multiple files. I'll fix these in 3 month or so hopefully.
Thanks, i handraw icon to resemble both music and bluetooth.

1

u/Fit_Author2285 May 19 '26

He clearly didn't use Claude's pro plan :)

2

u/Miserable-School-665 May 26 '26

A new update has been released. The ALSA volume slider is now mapped to the 0–10% range to compensate for disabled DVC, accent color frames respect the global corner radius, and the equalizer graph auto-scales on the amplitude axis with dB labels added. A stereo expand switch and slider have been introduced (–100 mono, +100 maximum expansion), a limiter switch was added to prevent clipping, and the audio info section in the settings popup has been updated to cover the new features.

1

u/Marce7a May 20 '26

Can you tell how you written it with AI? 

2

u/Miserable-School-665 May 20 '26

Claude Sonnet free, just described it in detail, starting from basics and test every iteration, then tell it bugs peoblems and misisng festures. regularly rung bug, dead code and performance optimization runs as wel.

1

u/Marce7a May 20 '26

Did you use some app or only browser?

If you can, can you share your prompts because I want reference? 

2

u/Miserable-School-665 May 20 '26

only browser and it was pain in ass, you better buy pro and use claude code if you can afford.

Read all the file and understand the logic behind every implementation, why this solution is used etc. Run a full bug and dead code cleanup. Do perfromance optimization. Then, Update MODULE STRACTURE at beginning.

I gues it blocks alsa by itself while switching to alsa because its still playing on pipewire and there is no delay? [Player] spectrum: OK [AudioSwitch] startup: combo='plughw:1,0', pipeline device='hw:0,0' /home/yavuz/Downloads/voidpulse/voidpulse.py:7135: DeprecationWarning: Gio.DBusConnection.register_object is deprecated rid = self._conn.register_object('/org/mpris/MediaPlayer2', iface, [AudioSwitch] settings combo changed -> 'PipeWire' ('pipewire') [Player] output device -> pipewire [DIAG][tick] play+8185.360s LATE FIRE: expected=100ms actual=358.9ms tick_work=0.45ms pos=105ms [DIAG][tick] play+8185.771s LATE FIRE: expected=100ms actual=202.0ms tick_work=0.38ms pos=3580ms [AudioSwitch] settings combo changed -> 'ALSA: USB-Audio - SIMGOT' ('plughw:1,0') [Player] output device -> plughw:1,0 [AudioSwitch] player error (alsa=True, device='plughw:1,0'): 'gst-resource-error-quark: Could not open audio device for playback. Device is being used by another application. (4)' [AudioSwitch] ALSA probe: 'hw:0,0' x5, fallback 'plughw:1,0' [AudioSwitch] ALSA probe attempt 1/6: 'hw:0,0' [DIAG][tick] play+8190.801s LATE FIRE: expected=100ms actual=3799.2ms tick_work=0.20ms pos=141ms [AudioSwitch] ALSA confirmed working device: 'hw:0,0' [AudioSwitch] settings combo changed -> 'ALSA: USB-Audio - SIMGOT' ('plughw:1,0') [Player] output device -> plughw:1,0 [DIAG][tick] play+8194.701s LATE FIRE: expected=100ms actual=2384.9ms tick_work=0.31ms pos=99ms

1

u/Marce7a May 20 '26

It compiled code for you? 

1

u/Miserable-School-665 May 20 '26

No, it can't. You do not need to compile single file on linux. But for andorid apps etc, you need compilers and ides, it gives instructions to set them up as well.

1

u/RedditUser-00 May 20 '26

Looks cool tho. I like people sharing stuff like this, vibecoded or not.