I'm still having this problem worse than ever. I've sent a ticket to tech support but don't know if I'll ever hear from them.

Does anyone know where to find the OP, Quebec? He/She doesn't seem to be on here anymore. I'd be realy interested to know how they got on and maybe swap some ideas.

I'm now on the latest version of MM and the problem is worse than ever. Please see my new post on http://www.mediamonkey.com/forum/viewto ... 67#p209767 to avoid me double-posting.

I haven't deleted anything you mention, though Realplayer was never installed - that's not a windows component as far as I'm aware (thank god!!!!) and even if it was, I doubt that could be the problem. Anyway, I'm pretty sure I have RealAlternative on here.

Anyway, I thought I'd bump both topic since the new version was out. Please see my one about for more details.

i'm not getting this error in mm 3.0.3 or mm 2.5 is there some reason it is not happening to my systems?
um might be something to do with windows? what versions are you using again? and did you keep them updated.
and did you leave all the microsoft apps in the system or did you remove part of the ie browser or all of it? we know they are all connected to each other app from ms. and removing one can and does cause errors in the others.
so did you do any of that?

also mediamonkey needs things from wmp, real one or the old real player, quicktime, and itunes to play certian files. did you remove those or never get them? i don't use itunes and have no errors but i don't use any hardware from apple either.

but the error seems more of a database mess up then of mediamonkey. i know there was a sql update from ms a few months ago maybe you miss'ed that update?

I've got exactly the same problem, but luckily it only happens to one or two newly added albums at a time.

I have NO idea what anyone but the OP has said in this thread though...

Either not many people use auto-organise or this is a pretty rare problem.

That feature has supposedly been improved in MM 3.1 (currently in beta testing, available from the beta testing forum). I only say supposedly because I have not tested it for myself.

I need help with the locate moved/missing tracks function.

The given solution of rescanning the music doesn't work in my case because there is a ****load of music in the main folder, of which I only need a little. I have 9000+ track but the main folder has much moren than that. Refinding all the music I had in MM would take days.

So is the a way of making the locate moved/missing tracks function do the trick.

PS. The "same problem" is that when using the locate moved/missing tracks function it says the files don't exist (some he finds and fixes).

Thenx

Using the updated 3.1 library I was getting the result I expected from Substr(path, 1) but with the correct DB its working fine. Either I was being dense and am mis remembering it or something got changed in that version. Either way its working now, gone from about 3000 dead likes to about 250, most of which I can sort out with a bit more effort. Cheers for all your help!

Yeah in any SQL dialect SUBSTR() start from position 1, I tried your Select and gets result like:
:\Music:\My Music4\Tunnel
Don't you get that to?

Cheers, I've got a backup of the database from before 3.1 so not a problem.

With the SUBSTR thing I was working under the assumption that indexing starts from 0 as in languages like Java, C/C++/C# etc., so position 0 would be the first character, 1 the second etc. Like you say SQLite does it the other way with 1 being the first character. However the SELECT query above does do what I would expect it to do, not really sure whats going on there?

Hi,
1. I still mean that your syntax doesn't do what you want:
Substr(SongPath, 1) removes the first character (:) and leaves everything else
Actually no, Substr(SongPath, 1) means read from position 1. So Substr(SongPath, 1) does absolutely nothing since Substr(SongPath, 1)=SongPath.
You need to use Substr(SongPath, 2)
Substr('abcd', 1)-->'abcd'
Substr('abcd', 2)-->'bcd'

2. The gettracktype() function (which is used within a trigger that you trigger when you try to update) was introduced in MM 3.1, it looks like you have upgraded to 3.1 and then reverted to 3.0 without manually changing back the database copy of 3.0. The databases are not compatible.
Solution here:
http://www.mediamonkey.com/forum/viewto ... 88#p184188

Cheers for the heads up on concatenation, saw an example on some SQLite forum that used the standard operator so kind of just assumed it was ok. The substrings are correct though. Substr(SongPath, 1) removes the first character (:) and leaves everything else, so concatenating ':\Music' with the substring of ':\My Music.....' gives ':\Music\My Music....' which is what I want.

I have tested all the different bits out in a select statement:
SELECT SongTitle, ':\Music' || SUBSTR(SongPath, 1) FROM Songs WHERE SUBSTR(SongPath, 0, 10) = ":\My Music";

That works perfectly, outputting precisely the path I want it to. However copy and pasting those statements into an UPDATE statement:
UPDATE Songs SET SongPath = ':\Music' || SUBSTR(SongPath, 1) WHERE SUBSTR(SongPath, 0, 10) = ":\My Music";

Gives these 'no function: 'gettracktype(1, 1)' messages. I was just using Media Monkey generally and got the same error yesterday as well. Unfortunately I can't actually remember precisely where but it leads me to think its some idiosyncrasy of SQLite or Media Monkey's use of it? Has anyone else had the same error? I'm fairly sure that the statement above constituets legal SQL that does what I want it to.

Yes, you cant use + to concatenate you must use ||, also always use single quotes around strings since its better/faster (doesn't really matter in this case though.) But there is another problem with your SQL, I don't think you got the ':\Music' ||SUBSTR(SongPath, 1) right, shouldn't it be ':\Music' ||SUBSTR(SongPath, 2) or something.

Look at the result of this:

Cheers for the help. Getting there slowly.

Current problem:

UPDATE Songs SET SongPath = ":\Music" + SUBSTR(SongPath, 1) WHERE SUBSTR(SongPath, 0, 10) = ":\My Music";

That in theory should update all relevent rows in the correct manner, however whenever I run it I get a SQL error saying "no such function: gettracktype(1, 1)". Any ideas what is going on there?

Ta

I ran a rename not long ago that effected 8,000 or so files. Not exactly the 20,000 you mention, but the 8,000 went off without a hitch.

Yes. it's SQLite:
http://www.sqlite.org/lang.html

It uses SUBSTR() and Songs.SongPath doesn't contain the driveletter. Try something like this If you have more than one drive then you need to involve the IDMedia field as well. I'm sure you figure it out.