View Issue Details

IDProjectCategoryView StatusLast Update
0021907MMW 5Extensions frameworkpublic2026-01-16 15:03
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status closedResolutionreopened 
Product Version2024.2 
Target Version2024.2.1Fixed in Version2024.2.1 
Summary0021907: 3D Album Art view fails to display currently playing track (regression)
DescriptionIn MMW 2024.1, the Playing [3d album view] displays the currently playing track, and adjusts when a new track starts
In MMW 2024.2, this no longer works.

Steps To ReproduceConfirmed by Peke:
Yes 3d Album Art behave strange in 3200:
1. Load bunch of tracks from different albums in Now playing
2. Start Playback on first track
3. Select PLaying Node -> 3D Album View (Preview is set to playing)
4. Expected that 3D View Focuses on Playing Track Album and Auto Switch.

Note: 3d album view refers to https://www.mediamonkey.com/addons/browse/item/3d-flow-album-view/
Additional InformationReported by Pepper in relation to ticket 14851
TagsNo tags attached.
Fixed in build3202

Relationships

related to 0021628 closedlowlander Playlist in Grid (by Album) shows full Albums instead of actual files on Playlist 

Activities

michal

2025-12-24 13:10

developer   ~0080243

Quick fix for addon: Drakinite, please change in FlowAlbumViewNowPlaying class line:
var idx = this.dataSource.indexOf(currentAlbum);
to
var idx = await this.dataSource.indexOfPersistentIDAsync(currentAlbum.persistentID);

First function is for searching given object instance in the list, but in your case it could be different instance of album object.

Assigning to Petr to find out, whether we could fix, so in this situation there will be the same instance of album object. I.e. when reading album from tracklist.getAlbumList[idx] and the same one from track.getAlbumAsync.

rusty

2025-12-25 16:34

administrator   ~0080246

The fix is working correctly.

petr

2026-01-15 21:46

developer   ~0080317

Fixed

rusty

2026-01-16 14:57

administrator   ~0080326

This is re-broken in 3202.

i.e. 3201 + the updated 1.2.1 version of the addon (posted to the addons site) fixed the problem. But after updating to 3202, the problem is recurring.

rusty

2026-01-16 15:03

administrator   ~0080327

I can't replicate the issue. Re-resolving.