View Issue Details

IDProjectCategoryView StatusLast Update
0020136MMW 5Playlists (Auto) / Search / Filterspublic2024-05-23 21:40
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status closedResolutionno change required 
Product Version5.1 
Target Version5.1 
Summary0020136: Removing a Genre that is contained within an AutoPlaylist, causes the AutoPlaylist to return all tracks
DescriptionIf an autoplaylist is set to Attribute=X and then all tracks with the AttributeX are removed, the Autoplaylist changes to Attribute=anything and all tracks in the Collection are returned!

For example:
1 Create an AutoPlaylist for Genres=Bubblegum and add that autoplaylist to the sync list
2 Edit the Genres of Bubblegum to a mix of X and Y
--> Because the Genre 'Bubblegum' no longer exists, the AutoPlaylist created in step 1 changes to Genres=anything and on the next sync operation, _all_ tracks are synced to the device!

Note: this doesn't always occur, it only occurs when the edit causes 'Bubblegum' to be deleted from the list of Genres. I haven't been able to figure out why this occurs sometimes and not others. I can get the issue to occur consistently by tapping the query (which causes the no-longer-extant Genre to be deleted from the query).
TagsNo tags attached.
Fixed in build

Relationships

related to 0020937 closedLudek Editing autoplaylist criteria sometimes fails (aka clicking outside an open combo box causes another combobox to open) 
related to 0020315 closedLudek Changing Genres causes nodes to switch 

Activities

Ludek

2023-07-16 20:35

developer   ~0072468

I am unable to replicate, can you please share MM5.DB including such an auto-playlist?

For me the auto-playlist rule changes to
Genre equals click to set

but the SQL query still is
SELECT Songs.* FROM Songs WHERE Songs.ID IN (SELECT IDSong FROM GenresSongs WHERE GenresSongs.IDGenre IN ( SELECT Genres.IDGenre FROM Genres WHERE Genres.IDGenre in (1)))
so it returns no tracks as there isn't a track matching the genre ID.

Ludek

2023-10-26 16:40

developer   ~0073236

ok, so based on the screencast video it is rather about fixing 0020315