View Issue Details

IDProjectCategoryView StatusLast Update
0004251MMW v4Main Panel/Toolbars/Menuspublic2011-04-27 15:40
Reporterrusty Assigned To 
PriorityurgentSeverityminorReproducibilityalways
Status resolvedResolutionwon't fix 
Product Version3.0 
Summary0004251: Currently playing APE file doesn't appear in the My Computer node
DescriptionIf the user plays an APE file, then goes to the My Computer node containing the file (e.g. find more from same Folder (My Computer), then the currently playing APE file will be invisible--no metadata will appear for it.
Additional InformationTicket: KPI-453187
TagsNo tags attached.
Fixed in build

Relationships

has duplicate 0005652 closedpeke APE Files Are not Read/shown correctly. 

Activities

jiri

2008-01-10 15:08

administrator   ~0012830

I suppose that it's caused by the in_APE plug-in we are using, because it probably locks the file so that it isn't possible to open it for reading then. Assigning to Peke to confirm.

peke

2009-05-22 02:28

developer   ~0017963

When APE file that is not in Library is not read correctly when viewed thru My computer tree node.

1. Extract Example File to some empty folder.
2. Double Click on file to open in MM
3. When File is shown in MM now playing correctly
4. Right Click on File -> FindMore... -> Folder (My Computer)
5. Track should be shown with Length 0:00 and no artist.
----- Optional Test -----
6. Playing Track in MM will repopulate track Info Correctly
7. Moving focus from folder containg the track and return back will render invalid length
8. When File is Read correctly and played it will be converted without the issue and with correct tag data, but if not read correctly converting will work but without progress bar and any indication that it is converted correctly.

Note: I was not able you replicate Sync Auto-Convert MSG, but something is not correct with that file.

jiri

2011-04-27 15:40

administrator   ~0024513

I'm resolving this, since it's a minor issue that will be fixed automatically anyway later when we implement a cross-platform solution (since the WinAmp input plug-in would be replaced then). It doesn't make sense to fix in any other way until then.