[1431] File Monitor does not work as expected [#8387]
Moderator: Gurus
[1431] File Monitor does not work as expected [#8387]
Build 1430:
It seems to me that the file monitor does not discover new songs as quickly as in MM3. It does add new songs to the library if I go in options->library->file monitor and just press OK. This seems to trigger an overall scan and not just the new songs.
I attached a log where only 2 songs of Blind Guardian out of 10 were detected. All my music is being stored on a network location.
Log use: Detection of new B.B. King & Eric Clapton\Riding with the King album was triggered manually using the method described above.
Detection of Blind Guardian/At the edge of Time was done automatically but only 2 songs of 10.
http://www.fayloobmennik.net/967419
It seems to me that the file monitor does not discover new songs as quickly as in MM3. It does add new songs to the library if I go in options->library->file monitor and just press OK. This seems to trigger an overall scan and not just the new songs.
I attached a log where only 2 songs of Blind Guardian out of 10 were detected. All my music is being stored on a network location.
Log use: Detection of new B.B. King & Eric Clapton\Riding with the King album was triggered manually using the method described above.
Detection of Blind Guardian/At the edge of Time was done automatically but only 2 songs of 10.
http://www.fayloobmennik.net/967419
Re: [1431] File Monitor does not work as expected
Build 1431:
I copy/pasted 32 songs in the watched directory and MM double registered some songs, totaling 40 songs.
http://www.fayloobmennik.net/980762


edit: complete debug log
I copy/pasted 32 songs in the watched directory and MM double registered some songs, totaling 40 songs.
http://www.fayloobmennik.net/980762


edit: complete debug log
Last edited by Orbi on Fri Sep 16, 2011 11:38 am, edited 1 time in total.
Re: [1431] File Monitor does not work as expected
Update for build 1431:
I copy/pasted 10 songs of Crowded House and only 2 songs were picked up by file monitor. The remaining 8 files were not moved to their respective folder along with the 2 songs that were detected by FM.
http://www.fayloobmennik.net/980770
edit: complete debug log
I copy/pasted 10 songs of Crowded House and only 2 songs were picked up by file monitor. The remaining 8 files were not moved to their respective folder along with the 2 songs that were detected by FM.
http://www.fayloobmennik.net/980770
edit: complete debug log
Last edited by Orbi on Fri Sep 16, 2011 11:39 am, edited 1 time in total.
Re: [1431] File Monitor does not work as expected
Update 2 for build 1431:
I copied another album and again 2 songs of 10 were detected by FM.
http://www.fayloobmennik.net/980774
One similarity between this and last post: only the first and last song were detected (track numbers 1 and 10 out of 10). Let me know if you want me to test this out more.
edit: complete debug log
I copied another album and again 2 songs of 10 were detected by FM.
http://www.fayloobmennik.net/980774
One similarity between this and last post: only the first and last song were detected (track numbers 1 and 10 out of 10). Let me know if you want me to test this out more.
edit: complete debug log
Last edited by Orbi on Fri Sep 16, 2011 11:40 am, edited 1 time in total.
Re: [1431] File Monitor does not work as expected
Build 1432:
Debug log (from line 2255) shows that all 12 songs are detected yet only song 12 has been added to the library.
http://www.fayloobmennik.net/980778
edit: complete debug log
Debug log (from line 2255) shows that all 12 songs are detected yet only song 12 has been added to the library.
http://www.fayloobmennik.net/980778
edit: complete debug log
Last edited by Orbi on Fri Sep 16, 2011 11:41 am, edited 1 time in total.
Re: [1431] File Monitor does not work as expected
Orbi,
I can't replicate, but tracking at http://www.ventismedia.com/mantis/view.php?id=8387
Thanks.
-Rusty
I can't replicate, but tracking at http://www.ventismedia.com/mantis/view.php?id=8387
Thanks.
-Rusty
Re: [1431] File Monitor does not work as expected
Orbi,
the codepad links contain only the first few lines of the log, so I couldn't review them fully. At least the first link contains the full log though: it seems that MM wasn't modified by Windows about any other change than those really reflected in MM. Are you sure that you see something different in MM4 than in MM3? There even weren't any relevant changes in our code.
One possible test would be to run MM3 and MM4 (both debug versions) simultaneously and see whether the result is the same in both. In case it isn't, a debug log would be interesting.
Thanks,
Jiri
the codepad links contain only the first few lines of the log, so I couldn't review them fully. At least the first link contains the full log though: it seems that MM wasn't modified by Windows about any other change than those really reflected in MM. Are you sure that you see something different in MM4 than in MM3? There even weren't any relevant changes in our code.
One possible test would be to run MM3 and MM4 (both debug versions) simultaneously and see whether the result is the same in both. In case it isn't, a debug log would be interesting.
Thanks,
Jiri
Re: [1431] File Monitor does not work as expected
I'm sorry, I didn't realize codepad limits the length of the logs. I will amend my posts tonight with the full logs when I get back from work, as well as test with MM3.
Re: [1431] File Monitor does not work as expected
Jiri,
one question though: you ask me to test the file monitor simultaneously in MM3 and MM4, but the debugview utility will register both the MM3 and MM4 activity simultaneously as well. How can I send you a meaningful debug log then?
one question though: you ask me to test the file monitor simultaneously in MM3 and MM4, but the debugview utility will register both the MM3 and MM4 activity simultaneously as well. How can I send you a meaningful debug log then?
Re: [1431] File Monitor does not work as expected
Orbi,
You're right. The idea would be to test concurrently without collecting a log from MM3 (i.e. run MM3 regular build, and MM4 debug build), and observe whether there's any difference in behavior, while only collecting the log from MM4.
-Rusty
You're right. The idea would be to test concurrently without collecting a log from MM3 (i.e. run MM3 regular build, and MM4 debug build), and observe whether there's any difference in behavior, while only collecting the log from MM4.
-Rusty
Re: [1431] File Monitor does not work as expected
Even mixed messages from MM3 and MM4 would be ok for me. The most important info now is whether there's any diff between MM3 and MM4 though.
Jiri
Jiri
-
shaunleeclarke
- Posts: 6
- Joined: Sun Mar 29, 2009 8:51 am
Possible MM4 File Monitoring Bug
I may have found a bug with the MediaMonkey 4 BETA.
Firstly, I am running the latest 1433 build of MM4.
I have my Library setup as follows:
Auto Organise: D:\MediaMonkey Library\<Album Artist>\<Album>\<Track#> - <Artist> - <Title>
File Monitor: D:\MediaMonkey Library Add
When I drop a new music file into the 'MediaMonkey Library Add' folder, it gets moved and renamed into the appropriate directory in the library.
I recently purchased two new tracks, but when I place them in the monitored folder, both files disappear, BUT only one of them ever appears in the library. The other file just disappears!
The file names are:
01 - 01 - What Else Is There (Jacques Lu Cont radio mix ).mp3
01 - 02 - What Else is There (Thin white duke mix).mp3
It's also possible that this isn't a bug but rather a consequence or problem with my configuration - but given that it results in the deletion of data, if it is indeed a bug, I hope this helps. And even if it's not a bug - I'd certainly appreciate some help with the problem.
Let me know if more information is needed and I'll be happy to help.
Firstly, I am running the latest 1433 build of MM4.
I have my Library setup as follows:
Auto Organise: D:\MediaMonkey Library\<Album Artist>\<Album>\<Track#> - <Artist> - <Title>
File Monitor: D:\MediaMonkey Library Add
When I drop a new music file into the 'MediaMonkey Library Add' folder, it gets moved and renamed into the appropriate directory in the library.
I recently purchased two new tracks, but when I place them in the monitored folder, both files disappear, BUT only one of them ever appears in the library. The other file just disappears!
The file names are:
01 - 01 - What Else Is There (Jacques Lu Cont radio mix ).mp3
01 - 02 - What Else is There (Thin white duke mix).mp3
It's also possible that this isn't a bug but rather a consequence or problem with my configuration - but given that it results in the deletion of data, if it is indeed a bug, I hope this helps. And even if it's not a bug - I'd certainly appreciate some help with the problem.
Let me know if more information is needed and I'll be happy to help.
Re: [1431] File Monitor does not work as expected
Jiri, Rusty,
I want to help out here, but not before I fix a problem I don't understand where it comes from. Yesterday, I installed build 1433 and I was running MM4 and MM3 simultaneously to test the file monitor. I copied a new album which was picked up by neither versions. Debug log doesn't show anything which could explain.
In MM4, I pressed the Ins button to trigger a manual add to library as I usually do since these odd file monitor issues. The result was about 500 songs were added with the $ sign on the end of the file name. I discussed this with debug log in another thread which seemed more appropriate: http://www.mediamonkey.com/forum/viewto ... =6&t=60528
I don't know if this behaviour is a consequence of build 1433 or because of running MM4 and MM3 simultaneously.
This morning, I deleted all these double entries from the library and triggered another manual scan. The result is that 604 songs were imported which already exist in my library and are no different except the $ sign was added to the file name in the library (the files actually do not contain the $ sign. Here is the debug log: http://www.fayloobmennik.net/982500


I don't understand what happens...
By the way, I updated all my earlier posts in this thread with full debug logs.
I want to help out here, but not before I fix a problem I don't understand where it comes from. Yesterday, I installed build 1433 and I was running MM4 and MM3 simultaneously to test the file monitor. I copied a new album which was picked up by neither versions. Debug log doesn't show anything which could explain.
In MM4, I pressed the Ins button to trigger a manual add to library as I usually do since these odd file monitor issues. The result was about 500 songs were added with the $ sign on the end of the file name. I discussed this with debug log in another thread which seemed more appropriate: http://www.mediamonkey.com/forum/viewto ... =6&t=60528
I don't know if this behaviour is a consequence of build 1433 or because of running MM4 and MM3 simultaneously.
This morning, I deleted all these double entries from the library and triggered another manual scan. The result is that 604 songs were imported which already exist in my library and are no different except the $ sign was added to the file name in the library (the files actually do not contain the $ sign. Here is the debug log: http://www.fayloobmennik.net/982500


I don't understand what happens...
By the way, I updated all my earlier posts in this thread with full debug logs.
Re: [1431] File Monitor does not work as expected
Are you sure the problem is in build 1433? We have reviewed it and there shouldn't be any regression introduced. Could you please try to reproduce it on an empty database (just backup the current one, in case you don't want to lose its content)?
Thanks,
Jiri
Thanks,
Jiri
Re: [1431] File Monitor does not work as expected
On an empty database, the problem does not occur. Do you have any theories why it happened based on the logs I provided? I mean, there must be a reason why it happened to my existing database and based on these conditions it could happen to another user as well...
Any clues on how to fix my DB? When I try to delete these $ signs from the file names, MM tells me the file cannot be moved because it does not exist.
Any clues on how to fix my DB? When I try to delete these $ signs from the file names, MM tells me the file cannot be moved because it does not exist.