[quote="Ludek"]Hi,
it really is a network traffic issue as MM is fresh when the DB is on a local HDD.

Are you sure this started after MM3->MM4 upgrade?[/quote]

Two instances of MM installed.

Fresh Windows XP Home install. Both MM installs are fresh also of course.

15798 tracks Location - NAS/Music/in/these/folders

MM3 - Database location - NAS/MM3/MM.DB. Database built on install of program

MM4 - Database location - NAS/MM4/MM.DB. Database built on install of program.

Time taken for program to start. Click of icon to ability to select a track.

MM3 - 4 seconds

MM4 - 40 seconds

Both running on the same network.


???

Hi,
it really is a network traffic issue as MM is fresh when the DB is on a local HDD.

Are you sure this started after MM3->MM4 upgrade?

Debug report sent - ticket raised.

[quote="nohitter151"][quote="KEP"][quote="nohitter151"]In fact you can even install [both MM3 and MM4 database files] and use them side-by-side.[/quote]
How?[/quote]
Install MediaMonkey 3 and 4 to different folders. Because the DB's are stored in separate locations, you can use both programs to manage separate DB's.[/quote]
Oh. The way you said it, it sounded like using two (or more) DBs in a single app. My misunderstanding.

I have a top level folder selected for monitoring and it only lists that folder in the File Monitoring area. Maybe an upgrade from 3.x issue?

[quote="KEP"][quote="nohitter151"]In fact you can even install [both MM3 and MM4 database files] and use them side-by-side.[/quote]
How?[/quote]
Install MediaMonkey 3 and 4 to different folders. Because the DB's are stored in separate locations, you can use both programs to manage separate DB's.

[quote="Lowlander"]
File Monitoring: File > Add/Rescan Tracks and in the File Monitoring area remove the folders to be monitored by deselecting both monitoring options.[/quote]

Hmmmm .... Having just unchecked every folder may I ask whether a shared folder on a NAS device - for example FOLDER1 (NAS/FOLDER1/) is treated differently to folder2 (NAS/FOLDER1/folder2/). Monitoring NAS/FOLDER1 led to every single folder in that folder being listed separately meaning that I had hundreds of different folders being monitored and not just the one plus everything in it. I could stop monitoring FOLDER1 but that still left all of the folders within it. Does MM not like monitoring a top level folder?

[quote="nohitter151"]In fact you can even install [both MM3 and MM4 database files] and use them side-by-side.[/quote]
How?

Debug log: http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=69
File Monitoring: File > Add/Rescan Tracks and in the File Monitoring area remove the folders to be monitored by deselecting both monitoring options.

[quote="jiri"]Panader,

I'd like to understand why you experience the slowdowns. MM4 is actually in many operations significantly faster that MM3, so your results are pretty different from what we measure here. Although it should be done automatically after upgrade, you could try to Optimize your library. If nothing helps, you could send us a debug log of some slow operations or even the complete database (with a description of how to reproduce the problems).

Jiri[/quote]

I reinstalled MM3, replaced MM.DB and all worked well.

Uninstalled MM3, reinstalled MM4 but in an attempt to speed things up went down the separate DB route for each machine.

(This worked pretty well but could you please tell me how to stop the program monitoring folders. I asked it to monitor NAS\Music which contains about 700 subfolders. I know have about 700 separate folders being monitored and can find no way to easily stop monitoring them. Whatever I do they are back next restart. Also the continuous folder monitoring was very hit and miss. Despite various "tests" not one track was added unless I instigated a scan or checked the monitoring was in fact on)

To check things I have reverted back to one DB on the NES device. It now starts slowly .... the splash screen appears for a few seconds then disappears. The interface appears 12 seconds later. The strange thing is that the next time I start the program it might start quickly or there might be the delay. It is not consistent. The trees open quickly now which is good.

I still feel MM4 is slower than MM3 - MM3 was rapid over the network, MM4 just feels a rad slower with a much slower startup.

Debug log? Wheres that then?

Now about that bloody monitoring - PLEASE tell me how to get rid of the damn thing as I don't need it using one database.

Thanks

--
Mick

Panader,

I'd like to understand why you experience the slowdowns. MM4 is actually in many operations significantly faster that MM3, so your results are pretty different from what we measure here. Although it should be done automatically after upgrade, you could try to Optimize your library. If nothing helps, you could send us a debug log of some slow operations or even the complete database (with a description of how to reproduce the problems).

Jiri

[quote="nohitter151"]Any change to the .ini file could not possibly generate the error you mentioned. It seems to me that you might have gotten your MM.DB files confused at some point.[/quote]

Not a chance.

My music file and MM.DB are both on a NAS device (different locations on the unit though).

These files are backed up to a number of drives (bit paranoid on that score :-? ) but this I do manually.

The .ini file pointed to the location of the MM.DB. On the new .ini file that MM4 uses I put that location under [System]

Starting MM4 for the first time it started the "Updating" process of the MM.DB. This took ages.

After this had completed MM4 started but was laggy as hell.

I the reinstalled MM3. I also replaced MM.DB from a backup location overwriting the MM4 updated one on the NAS unit.

There is no way I am confused about where any of my files are on this one.

Any change to the .ini file could not possibly generate the error you mentioned. It seems to me that you might have gotten your MM.DB files confused at some point.

[quote="nohitter151"]The error:

"Cannot load query data. Could not find field: Songs.TrackType, PT:0"

sounds to me like you are using MM4 with a MM3 database. TrackType is a new file property as of MM4.[/quote]

Well as I stated earlier I reinstalled MM3 and replaced the MM4 database with a previously backed up MM3 one. It appears that MM4 makes changes elsewhere .... the .ini file perhaps but that is in a different location so I don't see that it can.

I think I am going to have to drop the DB from the network and run it per machine with the other machine monitoring the Music folder (on a NAS device) for changes.

Not exactly the usual smooth upgrade I have always experienced with MM in the past.

Thanks for your thoughts

The error:

"Cannot load query data. Could not find field: Songs.TrackType, PT:0"

sounds to me like you are using MM4 with a MM3 database. TrackType is a new file property as of MM4.