mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
MusicAlbum and MusicArtist items cannot be marked played #1452
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Aanok on GitHub (Mar 27, 2020).
Describe the bug
In the context of a Music library:
/Users/{UserId}/PlayedItems/{Id}endpoint to mark a MusicAlbum or MusicArtist item as played has no effect, the item remains marked as unplayed.System:
To Reproduce
Use your favourite client to mark a MusicAlbum or MusicArtist as played.
Alternatively, mark played all tracks under an album or artist.
Expected behavior
The MusicAlbum or MusicArtist items are marked played.
Of note: watching all episodes of a TV show season or series correctly marks either as played. Likewise, playing all tracks in a Folder within a Books library correctly marks the entire Folder as played.
Of further note: when a Music library is accessed via the Folder view and thus the artist and albums are presented as Folder items, the Played property is set correctly for the album but not the artist.
Logs
Nothing shows up.
@JustAMan commented on GitHub (Apr 4, 2020):
I don't think music was expected to have a "played" state at all. Let's ask @dkanada
@stale[bot] commented on GitHub (Aug 2, 2020):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or nightlies, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.
@Aanok commented on GitHub (Aug 9, 2020):
The bug is still present.
@stale[bot] commented on GitHub (Dec 8, 2020):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or nightlies, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.
@Aanok commented on GitHub (Dec 12, 2020):
I confirm this is still the case with 10.6.4.
@simonmicro commented on GitHub (Dec 16, 2020):
Imagine a user using Jellyfin for podcasts... I would need that too :)
@Aanok commented on GitHub (Dec 16, 2020):
For podcasts you should use a Books library, those track progress and watched status correctly. The items won't show up in Next Up, though. The web client also doesn't show them in Favorites.
@simonmicro commented on GitHub (Dec 16, 2020):
Oooh, Audio-Books! I thought that category would be for pdf files... Like the photos category is also for non-video/music files!
I propose a name change 😁
@cvium commented on GitHub (Apr 9, 2021):
This is basically a feature request. Re-open at https://features.jellyfin.org.
MusicAlbum and MusicArtist aren't real entities in the current db schema. They are basically just "folders" for encapsulating songs.
@Aanok commented on GitHub (Apr 10, 2021):
@cvium I can't say I really agree with this. You're talking about an implementation detail, but there is no way to know about this from a user's point of view, whether end user or API user: the application behaves inconsistently in a very arbitrary manner. To me, this is a bug caused by (whatever the Emby people where drinking when they designed) the schema.
Now, if you mean to say this isn't worth addressing until the DB rewrite, that's 100% valid on the other hand!
@cvium commented on GitHub (Apr 10, 2021):
Both. It works as "intended" even if it's terrible UX. And it's not worth fixing until the db rewrite.