PLEASE, if you're having a problem with the File Monitor, please [url=http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=341]send a debug log[/url]?

That'll give us the information needed to figure out why this is happening and hopefully fix it. Thanks.

-Rusty

As usually, we can't do anything about it without a debug log and as many info as possible (OS, etc.)

Jiri

MM v4.0.0.1436 hangs when I start up. It hangs while monitoring.

What exactly do you mean by File Monitor hanging? A screenshot or video might help. Also, please include a debug log.

Thanks,
Jiri

I am having problems with the File Monitor hanging MM when I start MM 4.0.0.1434.
This is the first time I have experienced this problem in MM4.

Back to MM 4.0.0.1433 for now.

You're welcome, I'm glad you were able to pinpoint the issue.

Thanks.

Orbi,

Thanks for all of the detailed information and logs. Jiri has analyzed this further, and it looks like the root of the problem is a networking issue. We have a potential solution, but it'll only be implemented post 4.0.

See: http://www.ventismedia.com/mantis/view.php?id=8387

Thanks.

-Rusty

Orbi,

unfortunately I'm not able to help any more, the log indicates that MM really isn't notified about any other file change than those that you see in MM. I'm not sure what could be the reason for such a thing. :-?

Jiri

Jiri, Rusty,

After fixing my DB after what happened above, I tested the file monitor of MM3 and MM4 simultaneously as you asked. I tested by copying 3 albums (not in once, but capturing a new log every time)

The first album: both MM3 and MM4 detected 2 out of 11
[url]http://www.fayloobmennik.net/990073[/url]

The second album: MM3 detected no songs, MM4 all of them
[url]http://www.fayloobmennik.net/990075[/url]

The third album: MM3 detected no songs, MM4 all of them
[url]http://www.fayloobmennik.net/990079[/url]

The results are so random, I hope you can make some sense from the logs...
I'll be adding more albums over the next days and be posting more results.

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.

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

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: [url]http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=60528[/url]
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: [url]http://www.fayloobmennik.net/982500[/url]

[img]http://i51.tinypic.com/o8z60x.jpg[/img]

[img]http://i52.tinypic.com/fa27n7.jpg[/img]

I don't understand what happens...

By the way, I updated all my earlier posts in this thread with full debug logs.

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.

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

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