yeah for sure! oh man, I was using subtracks for a bit as well, that was a great and i had even forked it and was trying to compile that codebase - in the end I went with tempo because it was further along in the dev process and my time is limited.
Sweet! The app has a lot of small, very annoying bugs. Still my fave, I just got tired of waiting for updates and did not want to see it go by the wayside.
Yup, no commits since Dec 2024, or much of any activity. I opened a discussion but never got a response. I did track him down, (i think its him) on linkedin to ask for repo rights when I first got started but then decided I was a little too stalking and didn’t want to invade his space, so figured I just fork it and keep going. My hope is that he is doing well and it looks like he started a small android app biz and it’s doing well.
Thanks, got a lot of community effort this time round. The album track list was something we introduced in the last release, 4.1.0, that caused albums to display multi disc tracks all goofy, screenshots -> https://github.com/eddyizm/tempus/issues/234
It was in effort to improve performance and deal with lag/large libraries. We will have to go back and figure it out.
I believe there is a ticket for what you are describing?
I have fixed a bunch of bugs/crashes but there are more as we peel back the layers as we also start to add new features.
Hi @non_burglar@lemmy.world yes it is active. Your backend has to support it and it is loaded from there.
My backend does not support it so I can’t walk you through it. Probably something we should add to the documentation.