View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005500 | MMW v4 | Now Playing | public | 2009-04-14 20:43 | 2011-09-13 00:16 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.1 | ||||
| Target Version | 3.1.2 | Fixed in Version | 3.1.2 | ||
| Summary | 0005500: Linked Album Art doesn't display for currently playing track on restart | ||||
| Description | For linked album art (i.e. stored to folder.jpg), the art of the currently playing track sometimes won't appear. To reproduce: 1) Set the AA window to show Now Playing art 2) Play track 1 (that has AA stored to folder.jpg) --> AA is displayed correctly 3) Close MM, and restart MM -->Observe that AA isn't shown for track 1 4) Click the Play button to play track 1 -->AA still isn't shown Album Art only appears when tracks transition to another track | ||||
| Additional Information | Reported at: http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=37774 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1276 | ||||
| parent of | 0005899 | closed | peke | AudioCD: Playback, Virtual CD, Sync Functionality Broken in 3.1 |
| parent of | 0005979 | closed | petr | Windows 7 Shell Integration |
| related to | 0005789 | closed | Ludek | Tracks from iPhone/iTouch cannot be played in MM interface (regression) |
| related to | 0008360 | closed | jiri | Regressions in artwork handling |
|
|
Fixed in 1237 |
|
|
Verified 1238 |
|
|
This issue was re-introduced in 1242, as reported at: http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=37774 |
|
|
Fixed in 1249 |
|
|
Tested 1250. It's still not fixed. |
|
|
Fixed in 1251 |
|
|
Verified 1251. |
|
|
There is a regression of this problem reported in build 1274. I haven't tested to see when it was re-introduced, but have confirmed the regression. |
|
|
Be careful fixing this issue as this issue caused many regressions like 0005899, 0005789, 0005848, 0005997, 0006001, etc. Probably by re-fixing one of those regressions I introduced this regression. We should review whether we shouldn't rather defer this issue in case there will not be a safe fix. |
|
|
I found a safe fix. Fixed in build 1276 and tested for the regressions. |
|
|
Verified 1279. |
|
|
Re opened for testing of 0008360 |
|
|
Verified 1431 no regressions found |
