View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006185 | MMW v4 | Other | public | 2009-11-16 04:33 | 2009-11-16 16:23 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | sometimes |
| Status | resolved | Resolution | not fixable | ||
| Product Version | 3.1.2 | ||||
| Target Version | 3.1.2 | ||||
| Summary | 0006185: Aeropeek fails when Auto-Tag from Web dialog is open (using MusicIP Tagger) | ||||
| Description | It's confirmed that Aeropeek fails if the user tries to switch tracks while the Music IP tagger is being run (See: http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=44366 ). I don't think that this needs to be resolved for 3.1.2, _unless_ the problem is likely to occur in many other scenarios. 3 different users are complaining about it, so if you can have a look at how often this issue is likely to occur, we can make a decision re. whether to create another update. | ||||
| Steps To Reproduce | 1 Install MusicIP Tagger and restart MM 2 Play a playlist and verify that AeroPeek is working 3 Select a few tracks, right-click Auto-tag from web, choosing option of using the MusicIP Tagger as source 4 Put another application into focus 5 Hover over the MM application in the toolbar and wait for earopeek window to appear 6 Click 'next' in the Aeropeek window --> Album Art window doesn't populate (and will not populate as long as the Auto-tag from Web window remains open). | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
This issue seems to be caused by specific scripts rather than the scripting framework generically. In the case of the MusicIP script, the MusicIP library anylyses a track, but MediaMonkey doesn't receive any WM_COMMAND message. Because a variety of Win7 features such as Aeropeek are dependent on this, they fail as well. |
