I get an error that “one or more items couldn’t be added to the database” when trying to add either ALL files, some files or a selection of random ones (ie: I’m certain you have a bug and it’s not my files!)…
Also - the Multiple Artists feature, is this to be used to assist with scheduling so that related artists like Beatles, John Lennon etc can be defined or is it just to denote a duet song ?
Yes, for now, it’s only for manual editing. It will help you to locate “Ain’t No Mountain High Enough” easier when you only recall that it’s by Marvin Gaye and some other person you can’t remember right now
It will also help the Scheduler to separate “Ain’t No Mountain High Enough” from “I Heard It Through The Grapevine” (because now, both songs are by Marvin Gaye, and possibly someone else).
It’s not meant for the John Lennon vs. Beatles thing. We will need to establish something like “artist groups” for that. If you put “John Lennon” and “Beatles” into the artist field of “Imagine”, the song would appear as “John Lennon/Beatles” in your log and online playlist, which is certainly not what you want.
Internally, mAirList stores the artists as separate strings (and also as multiple … nodes in the XML output). In the playlist, players and log file, the strings are joined by “/”. But mAirList will never split single artist fields found in file tags by itself. On the other hand, for the tags which supports multiple artist fields (e.g. ID3v2), mAirList will now import them one by one rather than joining them into a single field (which was the case in v2.2).
OK Torben, thanks for the explanation - I was hoping that this was the case. I agree that the scheduler/database should be the place to define “related artists” so that soloists and groups are kept apart etc.
Yes, I did wipe the database a start again (re-created and tested the connection and tables were OK in the Config)… I’ll have another play later on… Admittedly, I didn’t try “All Files” as I had sub-folders of MP3s that I didn’t want to add
Actually, there’s a new table (“itemArtists”) which I haven’t included in the connection test yet. And an existing table has been altered (column “artist” removed from table item"), a circumstance the connection test would not notice either - as it simply checks the existence of the table but not the column. (Making it detect any change made during the beta phase would not be worth the effort.)
Oh, and did you upgrade your sqlite3.dll?
If you know a little SQL (which I suppose you do), you can download sqlite3.exe from www.sqlite.org, place it alongside mAirList.exe and run it from the command line with "sqlite3 ". You can then check if all tables are ok, in particular the “itemArtist” introduced in b506.
Regarding the issue with the files not being added, I found a mistake which prevents any item which has cue points imported from an MMD file or file tag from being saved to the database. You should also get an error message when trying to save any of these as a playlist from within mAirList.
