I had a similar error after I upgraded to MM 3. I'd get an error something like this:
"there was a problem querying the database" "select distinct"

(Sorry I don't have the full message!)

The problem was that in MM s.5, I had renamed the custom fields, and that renaming did not migrate to MM 3. The solution was to correct the refference to the custom fields in the script.

Hope this helps someone!!

Yeah, this was easy when I got your file. You could take a new version of the script with removed bugs from my thread.

Thank you very much for your help.

I tried 1.5.0.1b tonight on MM2.5 and MM3. I ran the sort by script and received the same errors in both programs. So something is still wrong...

I have the mediamonkey.mdb file ready to send you, but I need your email address to do so. YouSendIt requires that I specify a destination email.

Could you private message me your email?

Thanks for working with me on this.

http://solair.eunet.yu/~zvezdand/MagicNodes-1.5.0.1b.vbs

Here is a new version of the script with a removed bug with Custom fields sorting. Could you try it, please?

About a problem with Blues genre, I don't know what is a reason for that, but it is definitely not this specific genre, because it works fine to me. I think there is something in connection with specific data in your database and I suggest that you send MM.DB to me, so I can look on it. You can use some free hosting server as http://www.yousendit.com. Thanks for your involvement in this.

Thanks ZvezdanD,

I got MN 1.5.0.1a yesterday. Today, I ran two scripts on this Magic Nodes in MM2 and MM3. Here is what I found.

I ran this mask:
Composer by Genre|child of:artist|icon:top level|SQL filter:Songs.SongPath LIKE '%FLAC%'\<genre|unknown:no>\<composer>\<artist|unknown:no>\<album>

In MM2 the above script worked fine. In MM3 I got exactly the same error with the Blues genre that I described several posts ago.


I also ran this mask (where Original Album Release Year = Custom 2):
Artist (By Original Album Release Year)|child of:artist|icon:top level\<Artist|unknown:no>\<Album|sort by:max(Original Album Release Year)|unknown:no>

As you can see, I tried to correct this mask as you suggested in your last post. The mask created correctly this time, but when I attempted to expand any artist node in this magic node I received three error messages. This happened in both MM2 and MM3. The error messages were quite long and were related to script execution and database query. The error number in both MM2 and MM3 was 2147418113.

I am running MM3RC5 (3.0.1.1120) and MM2.5.5.998.

I took screenshots of all the errors. If these would be helpful to you, let me know and I can email them.

Did you tried to download version (1.5.0.1a) which link I posted? It has some change in connection with this what is happened to you. I am not sure, but this could solve a problem. I don't believe this problem has a connection with specific genre, maybe there is another problem with the script and the Artist field.

There is a problem with the mask you mentioned because it has one many blank character between [i]sort by:[/i] and [i]first[/i]. You should also know that [i]First[/i] and [i]Last[/i] aggregate functions are not supported by SQLite and MM3 and you should avoid their usage, instead you could use [i]Min[/i] and [i]Max[/i].

Actually, I already ran MagicNodes 1.5 in MM3. That's where I ran into the problem with the composer mask not recognizing composers in the Blues genre. I just replaced 1.4 with 1.5 for my MM2.5 installation. I ran the composer by genre mask and I had no problems with the Blues genre.

Does this mean that the script is ok, but MM3 has a bug related to blues? If so, where and how do I report that?

I also ran the Magic Nodes 1.5 and tried the sort by for a custom field and got nowhere in either MM2.5 or MM3. I was using this mask:

Artist (By Custom 2)|child of:artist|icon:top level\<Artist|unknown:no>\<Album|sort by: first(Custom 2)>

So maybe support for custom fields isn't quite there yet.

MM3 looks nice, and I'm pleased to see that they are taking Magic Node ideas and using them (Album Artist, Artist & Album Artist, etc.). Good work!

[quote="doubleij"]The composer mask above works fine in my MM2.5 installation running MN 1.4[/quote]
Could you please try a next version of the script with both MM2 and MM3 and let me know if it works better? Thanks.

http://solair.eunet.yu/~zvezdand/MagicNodes-1.5.0.1a.vbs

Update 2

The composer mask above works fine in my MM2.5 installation running MN 1.4

Update:

MagicNodes 1.5 works fine. Great job!

I found a possible bug when writing a composer by genre mask. The mask worked great except that all the artists that are in the "blues" genre were listed as "unknown" in the genre node. Classical, Jazz and all other artists were listed under their genres without problems.

Here's the mask I used:
Composer by Genre|child of:artist|icon:top level|SQL filter:Songs.SongPath LIKE '%FLAC%'\<genre>\<composer>\<artist>\<album>

Any ideas?

Thanks, I will give the new Magic Nodes script a try today. I installed MM3 RC1 and the multi-album artist mask encountered no errors. I'm fine with the mask displaying incomplete albums at this point. The mask did display a few artists that actually only have songs on one album, so I'm wondering if there's a way I can remove these artists manually.

I will put in 1.5x and see if I can get the sort by fields to work well.

Artists with more then one album|SQL filter:Songs.IDArtist IN (SELECT CountArtist FROM (SELECT DISTINCT IDArtist AS CountArtist, IDAlbum FROM Songs WHERE IDAlbum > 0) GROUP BY CountArtist HAVING Count(CountArtist) > 1)\<Artist>\<Album>

[quote="doubleij"]Unfortunately, I can't seem to use custom 2 with the sort by qualifier. It says the mask is invalid.[/quote]
This is now possible with 1.5.0.1 version of the script. Please, take a look on it.

[quote="doubleij"]Right now, I'm using MM2.5x.[/quote]
Here is a same mask for MM2, but it is drastically slower (~40 seconds instead of 1 second for MM3):
[code]Artists with more then one album|SQL filter:Songs.IDArtist IN (SELECT CountArtist FROM (SELECT DISTINCT IDArtist AS CountArtist, IDAlbum FROM Songs WHERE IDAlbum > 0) GROUP BY CountArtist HAVING Count(CountArtist) > 1)\<Artist>\<Album>[/code]
You could also use [i]Statistic:Count(Items)[/i] introduced with the new version of the script to display number of albums for each artist.

Maybe I need to mention that this mask displays artists which have tracks on two or more albums, but there is not testing conditions for complete albums in this filter. If you want such thing, the mask would be more complicated and much slower.

[quote="doubleij"]if I won't have any problems updating MM3 late beta to the official release then I'll be happy to get MM3 now. What do you think?[/quote]
Well, I am not sure, but I think there shouldn't be any problem for upgrade. You could also use both versions (2.x and 3) on the same computer without a problem.

Thanks!

I tried extract fields last night. It worked pretty well. The script does not have a conditional replace yet, but I was able to transfer all the relevant year data to custom 2, which I renamed Original Album Release Year. That way, Original Year will be used for recording date (as you said was intended). Unfortunately, I can't seem to use custom 2 with the sort by qualifier. It says the mask is invalid.

I use: |sort by:first(original album release year)


Right now, I'm using MM2.5x. I've waiting for the official release of MM3, since I'm a gold user and want to upgrade that way. But if I won't have any problems updating MM3 late beta to the official release then I'll be happy to get MM3 now. What do you think?

[quote="Anonymous"]At this point, it's not possible to tell the script to use one field as a default value in a particular node but then go to a different field if the original field is blank for a particular track.

Is that correct? If so, that's definitely on my wishlist for future updates to Magic Nodes.[/quote]
Yes, this is correct. Next version of the script may have this possibility (by-product of another feature), but I could not give any promise about that in this moment. I'll see what I can do.

[quote="Anonymous"]I guess my other option is to run a script that transfers the year field to original year where OY is blank, so that OY always has content. Do you know of a script that does a selective field replace like that? It would need to avoid replacing fields where OY is already filled with a value.[/quote]
I didn't tried any of the scripts which could do mass-replacing of the fields, but I think you should try the ExtractFields script. I am not sure if it have any built-in conditional replacing, but maybe it could replace only those data which exists in the source field. Please make a backup of the database and then try mentioned script with following steps: 1. OriginalYear -> Custom1, 2. Year -> OriginalYear, 3. Custom1 -> OriginalYear. If you don't get what you want, you should post a request to its forum thread: http://www.mediamonkey.com/forum/viewtopic.php?t=10566

[quote="doubleij"]your artists with more than one album script had several errors when I tried to run the script.[/quote]
Which version of MM do you have? This mask is for MM3.

I fixed the unknown bug you mentioned with no problems this afternoon. However, your artists with more than one album script had several errors when I tried to run the script.

I recorded the errors carefully. Here they are in the order they appeared.

There was a problem querying the database.

Error # -2147418113 – SongsDB-SDBDBIterator
Field 'count_unknown' not found. line 1579, Col. 35

Error completing DIB section. The operation completed successfully. Aborting...


There was a problem querying the database.

Error # -2147418113 – SongsDB-SDBDBIterator
Line 1798 Col. 8

Error happened during script execution: SQL_ERROR


Any ideas? Thanks. I will try to find a field complete script this afternoon as I mentioned in my previous post. If you know of a good one, let me know.