Repository navigation
[Bug]: UI Issue with Library #656
Description
Before reporting
- I'm on the latest release and the issue still happens.
- I searched existing issues and didn't find a duplicate.
What happened?
I split the same song twice, by uploading twice (obviously). Two entries were made in the library, which is as expected but one has subtext saying Extracted -6 stems while the other one says -6 stems (extracted word is missing)
Steps to reproduce
A) When a song is being split, it makes sense to show how many stems are extracted and the red yellow green indicator.
B) when a song Hallelujah is in the library in the attached image, clicking the song shows all the stems and one can see how many were extracted, so I think it is not necessary to have a subtext line at all. Just taking up Library space, forcing to scroll vertically.
On that token I don't think the RECENT section adds any value. Just taking up space. When a new song is uploaded and being SPLIT (or RE-SPLIT in future version), just show the song in the library and process it there. Just like Moises.
I know I keep referring to Moises because I use it a lot.
Operating system
Windows
StemDeck version
0.17.2
How did you install it?
Windows ZIP
Logs / screenshots
Activity
Build library rows from the track, and remove the Recent section (#683)
thcp commentedon Sep 23, 2026
Thanks for this. It's fixed in #683 and will go out in the next release.
The missing "Extracted" was a real bug. That line used to come from a label saved with each track, and one of the ways a track can enter the library never saved it, which left the bare " · 6 stems" you saw. It's now built from the track itself, so every row reads the same way: length and stem count once it's done, and "Processing" while it's still being split.
I also took your suggestion on the Recent section and removed it. Every track in it was also in its folder, which is why Hallelujah showed up four times in your screenshot. New imports already land at the top of the list, and a track that's still processing shows that in its own row.
I kept the line under each title rather than dropping it, because it's also where a track shows that it's processing, has failed, or needs re-importing.
And no worries at all about referring to Moises. Comparisons like that are genuinely useful for describing what you're after. I use them as a reference point for the experience, not as a blueprint, since I'm not planning to replicate other services' UI, so keep them coming.