View Issue Details

IDProjectCategoryView StatusLast Update
0005494MMW v4DB/FileMonitorpublic2009-05-12 12:45
Reporterpeke Assigned To 
PriorityimmediateSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version3.1 
Target Version3.1Fixed in Version3.1 
Summary0005494: M4A Can't be Imported on XP x64
DescriptionAll M4A files are Playable if browsed thrum My Computer Tree Node but MediaMonkey can't import files into Library.

There were two CrossLoop Sessions where I've tested all known issues and recorded one Video that clearly observe the issue.

I've uploaded to FTP all logs and files from both sessions, along with MM.DB files, few example tracks, and Directory Listing of all tracks. Additionally I've tested same issue with both iTunes and Winamp and both imported tracks without a problem. Note that this issue is only related to M4A as all MP3s from HDD are correctly imported.

First session was done with 1232 and second with 1235 RC1.

I've also tried to move MediaMonkey Folder outside Program Files, and set MM.DB to be in unsecured location.

While making tests I've tried to disable Avast A/V and even uninstall it prior to starting of MM without success.

Note: All files are located on External HDD Western Digital MyBook connected via USB.
Additional InformationTickets: HSX-264362 (User that tested and initially reported ticket) & KBL-752354
http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=38518
http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=38496
http://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=4536
http://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=4501
Another fix confirmation:
Ticket ID: WDM-380590
TagsNo tags attached.
Fixed in build1245

Activities

peke

2009-04-11 11:41

developer   ~0017478

Both sessions lasted several hours where user let me to toughly inspect his PC settings, so please If you need any additional info about his hardware settings let me know.

There is big possibility that this issue is related to several other issues regarding unavailability to scan tracks into MediaMonkey library.

jiri

2009-04-13 18:35

administrator   ~0017481

There probably does happen some exception in f_aac.dll while processing the files. If nothing else, some debug messages in the dll should tell us more, Ludek please add them. Also, do we know whether the problem happens on all XPs 64, or is it just this machine?

Ludek

2009-04-13 20:48

developer   ~0017484

Peke, have you tried to import the same files on your machine in order to ensure us it is OS specific? It would be much easier to fix this (in case we could reproduce this).

peke

2009-04-13 21:56

developer   ~0017486

No issues on My XP SP3 x32, I'll be installing Windows 7 x64 tonight and give it a try.

rusty

2009-04-13 22:14

administrator   ~0017487

I'm not sure if the issue is OS-specific. Ticket KBL-752354 was on Vista 32 (though it's possible that that ticket was caused by some other issue).

peke

2009-04-14 19:46

developer   ~0017490

Testing on Win 7 x64 for last two days and I have absolutely no issues with MM importing M4A or any other files except that UAC warned me on startup.

Avast is not supported on Win 7, but even starting on limited Guest account with Highest Security all worked Ok when MM was moved outside Program files to unsecured location.

All bugs are related to Find Error: E58B0000 (Access denied)

Petr,
Is there any way that we can detect/log creation of .DB-jurnal file from SQLite?

Ludek

2009-04-16 12:10

developer   ~0017499

I added some debug messages in build 1237. Peke, it is not clear whether you used the same M4A files as the user when you tested this on your machine. Did you use them?

peke

2009-04-16 16:19

developer   ~0017503

I had no issues with those files. Yes, they are same as I requested them from user that observed the problem and which logs I supplied.

peke

2009-04-20 23:10

developer   ~0017532

I've sent native AAC plugin to user. Hopefully it will be able to replicate the issue.

Again no issues in Win 7 x64 on my PC. I even enabled CPU DEP function for additional Security.

Petr,
Can you add some Debug MSGS into SQLite when .DB-Jurnal file is created?
I noted looking into several bug logs and replicating Find Error: E58B0000 .DB-Jurnal is created each time.

Ludek

2009-04-23 22:37

developer   ~0017564

Assigning to me, Peke send me one M4A file on which I can reproduce the issue.

Ludek

2009-04-24 09:28

developer   ~0017572

Last edited: 2009-04-24 09:29

Peke, I fixed the possible crash in build 1239.

Nevertheless the crash has been related to the debug version only and to the debug messages I have added recenlty. So I guess that the original issue might not be resolved.

So there is a need to re-test this again on the user's machine and generate log by using the build 1239 or by using the updated f_aac.dll.

peke

2009-04-25 16:09

developer   ~0017593

I uploaded new log file from v1240 in XP x86, will retest and compare in Win7 x64 later today and upload it to ftp.

Ludek

2009-04-27 07:38

developer   ~0017598

Peke, I saw the log, but the exception isn't there. So I suppose there is no problem with the debug version on XP x86 and you are only confirming that the problem has been fixed, isn't?

peke

2009-04-28 11:56

developer   ~0017613

Last edited: 2009-04-28 11:56

Files are uploaded onto FTP and both do not play in any application.

MM will stop Scanning when encounter one of those two files.

Ludek

2009-04-28 13:47

developer   ~0017618

Yes, the files are corrupted and caused MM to be unresponsive and frozen.

Fixed in build 1241.

peke

2009-05-02 01:27

developer   ~0017665

Verified 1242

peke

2009-05-09 11:17

developer   ~0017761

Last edited: 2009-05-10 22:01

Edited by Ludek:

Another user has an issues, I've assigned ticket to you.

Reported in one eSupport ticket:
http://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=4536&offset=20

Ludek

2009-05-12 09:39

developer   ~0017801

Last edited: 2009-05-12 09:42

Both users in these tickets:
http://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=4536&offset=20

http://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=4501&offset=40

have problems to scan the M4P file (I uploaded it to our FTP, it is the '01 Flume.m4p')

Anyone of us cannot reproduce the crash (we tested on Win XP SP2, Vista x64 BE, Win 7 x64). Nevertheless I found out that the crash seems to occur in a part of code that is quite irrelevant for M4P tracks.
So if a track is DRM protected like M4Ps and some M4Bs then this part of code isn't called.

Fixed in build 1245.

Ludek

2009-05-12 12:45

developer   ~0017803

Verified by one of the users experiencing the issue:
http://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=4501&offset=40