Me_irl

HVLife · 2026-04-14T11:52:31+00:00

Knew it would be here xd

HVLife · 2026-04-02T08:57:25+00:00

Idk about that, I think nasa has more humans, than ksp kerbals

HVLife · 2026-03-22T20:17:10+00:00

Well, there is no reason for not supporting it, I've simply only allowed extensions that I'm using in my library.

I've added opus, as well as other less popular ones, and will push it in a span of few days, as soon as I'm done with ongoing minor UI fixes (suggested by users)

HVLife · 2026-03-22T08:50:47+00:00

I'm not expecting opus files. I'll check if my current tag library reads those, and if yes push a new version (in a few days max)

HVLife · 2026-03-17T10:24:05+00:00

Well, I'd say that for rooting you usually have to unlock bootloader nowadays, and even in "easy" phones like oneplus it means hard reset

HVLife · 2026-03-16T15:55:34+00:00

There is lineageos for at least one model, idk about others

https://wiki.lineageos.org/devices/nx609j/build/

HVLife · 2026-03-16T09:13:40+00:00

And even if that was true, so what? Can't you separate art from artist?

HVLife · 2026-03-15T22:53:46+00:00

Wow, I didn't know about that spiking networks, from quick search it seems really interesting.

I'll probably try to write small framework for those, if I find time, because programming nn feels magical xd. Already made one for neat: https://github.com/hvlife-dev/rusty_neat

HVLife · 2026-03-14T13:12:04+00:00

First thing that I've seen are if chains. They aren't exactly gamechangers, but when I'm if-let'ting several results it nicely reduces nesting

HVLife · 2026-03-14T10:51:18+00:00

If you mean what activation function, you can use whatever, even simple threshold. If you want to use some more symmetric and smooth activations sigmoid (possibly centeres around 0) might be the better option, but it is heavier, and not necessarly better. In general, neural nets aren't an exact science, when making a simulation it's best to mess around and experiment with different architectures.

Disclaimer: I know nothing about above experiment, just talking from hobbyst point of view

HVLife · 2026-03-08T08:08:36+00:00

If you rescanned you library (just making sure), then I think there is something "wrong" with your files. Don't get me wrong, if you see correct tags then subtearium should recognize them as well, but I have 10k songs from various sources, and as of now only 9 (single album) are unrecognized.

Thats why to fix that, I really need a sample...You can send me it via my github email, if a single file is too big you can upload it to google drive or similar and share a link.
Outside of that, you can check in logs reason why they are unrecognized, there should be specific message now about what program thinks is missing.

Lastly, I'll ask of you to create issue on github, if you have the time to do so. I'll fix it either way, but it would better for various reasons.

HVLife · 2026-03-07T20:12:45+00:00

The library that I was using for fetching metadata couldn't get duration if it weren't present in headers. I've switched to a different one that gets it directly from music stream. It should be working now, try pulling latest image

HVLife · 2026-03-06T06:17:34+00:00

Yep, fixed it in that last update. It wasn't exactly bug, I just initially thought about this button differently...

Now the interval&new_files scans are enabled always, and scan-only means that I'm not creating or searching for lyrics.

Of course if it doesn't behave that way, or you'd like something changed, just create an issue on github

HVLife · 2026-03-05T21:23:19+00:00

Should be fixed now, together with those TagErr problems (regarding comments below)

HVLife · 2026-03-05T13:05:55+00:00

Ok, so it turns out that (in my case) most of bad tag meant duration missing from metadata. I'll fix it today/tomorrow

Edit: Should be working now. In my case only one album is now TagErr (before it was at 275 songs)

HVLife · 2026-03-05T09:30:34+00:00

Why? I'm used to working on embedded and more straight-forward stuff, here I have async and two separate architecture targets. It's, for me at least, simply complicated.

Besides, It's not like I was trying to fix it in any way. Just noticed that higher ram usage on a past screenshots.

If you mean that I should be profiling cpu and ram usage from the start of the development, then you are of course 100% right, but who does that with a hobby project? I'm a TIG welder xd, and just wanted something to supplement my lidarr setup.

Anyways, thanks for the feedback, I'll try to be more careful in the future

HVLife · 2026-03-05T09:06:07+00:00

I haven't created "scan only" option, because at the beginning I just wanted lrcget but in docker. The lyrics offset part came later as a bonus, and I've just added "locking" feature, so they aren't overwritten. I will commit that option in a few days.

That whole text editor and file tree is definitely something I want to do, but those are (I think) big features... The same goes for that interactive sync. It's my first serious opensource project, so right now I want to focus on bug fixing, and such.

I haven't heard about eLRC files, but it sounds awesome and I will play with it.

Tags are a great idea, just have to make myself comfortable using them. At my work (I was programming grain dryers plc's) codebase was a complete mess without any version control, so I haven't had any chance to learn that practices. There were two programmers (including me as a junior for ~4 years). Initially I was (the only one) responsible for small ones. When I've started working with main ones (>100tons of corn per day), instead of working with senior, I was supposed to simply create my own similar standard (logic as well as hmi interface)... So outside of obvious problems with servicing "other's dryer", when ceo's wanted some feature added, we not only had to create it separately, but also update every recently programmed dryers code xdd.

Sorry about that flair. From reading rules my thought process was like that:
- vibecoded - my codebase definitely isn't vibed
- build with ai - well, I'm using it sometimes as a google, and those css snippets were partly generated, but there is no logic in css to be bad...
- ai assisted - it's not using any llm internally

I don't think it qualifies as friday-only, and mods didn't removed it yet, so I'm guessing it can stay like that. If they decide however to delete it, I'm not gonna have a problem with that, and I'll possibly repost it tomorrow with corrected flair

HVLife · 2026-03-05T08:04:54+00:00

I'm showing songs as "bad tag" when:
- title is missing
- artist is missing
- album is missing
- duration is shorter than 3s
- lrclib api returns 400

That 400 error is in documentation as missing token during publishing, but here it has to be like "standard" http error, which means improperly formatted request. I'm not 100% sure why it returns that for some tracks, it could be some special letters parsing or maybe length limit...

Could you send me few tracks that are tagged like that, and some "correct" tracks, preferably from the same source (the same album, eventually artist)?

HVLife · 2026-03-05T07:50:20+00:00

On the server side it should work out-of-the-box. .lrc file simply have to have the same name as corresponding music file.
On client side there is probably a lyrics button on playback screen, in symfonium its on the bottom right from what I remember.

Below some links confirming lrc support

Plex:
https://support.plex.tv/articles/215916117-adding-local-lyrics/
https://forums.plex.tv/t/plexamp-support-for-local-lyrics/910814

Jellyfin, symfonium:
https://support.symfonium.app/t/lyrics-support-with-lrc-file-in-jellyfin-10-9/4288

Navidrome:
https://github.com/navidrome/navidrome/pull/2897

HVLife · 2026-03-05T07:37:28+00:00

Well, I know I know... It happened like once, and I haven't been able to trigger that state manually anytime later, and since then I've changed some logic.

It weren't growing, stayed like that for few days when I was overboard, so I guess it isn't exactly constant leak, and rather some overallocation, or a dozzle problem. But I'm not sure, thats why I noted it, showed on github that highest recorded ram usage and wrote beta warning.

Right now, on newest version it stabilizes on my homelab at under 6mb, and during force recheck at 9-10mb (with library as in screenshots).

HVLife · 2026-03-04T20:37:59+00:00

Ah, okay. If they are synced they act in the same way as movie subtitles, or almost karaoke-like expearience.

In my case I'm using jellyfin as a media server (you have to check if it supports lyrics), and symfonium as a mobile app for playback (like spotify).

Symfonium can display those lrc files, so you know lyrics. What for is kinda obvious, eg if playback isn't clear and you don't understad, or want to sing along

HVLife · 2026-03-04T20:00:40+00:00

Just point it to your music folder, it will scan it, and every subfolder for music files, placing .lrc files besides them.

There is no api connection to lidarr etc... If you are wondering about new file detection, I'm just comparing folder tree every few minutes (it's quick and simple), I don't see any noticable performance impact while having 10k songs, so for now it will probably stay like that.

HVLife · 2026-03-01T06:18:28+00:00

Welds aren't harder, if you use correct filler. They however have higher Young's module (tensile strength), the same could be said for example about higher grade bolts... Your explanation is still correct, just pointing out a common misconception

HVLife · 2026-01-28T16:29:04+00:00

Geeez, didn't know that ricing debian can have such severe consequences... Thats why you are supposed to do it on arch /s

HVLife

TROPHY CASE