Quote:
|
I don't understand how or why you appear to have the track number in the ID3 tags connected to the name, none of mine have this, its just in the track number field.
|
You asked this question yesterday in the "ID3-TitleTag(##-title)->ID3-TitleTag(title)"-thread
http://www.misticriver.net/index.php...pic&t=3424. If it is not clear enough, then please ask again there instead.
Quote:
|
I once read somewhere that one of the ID3 tags is put at the start of the file and another of the types is put at the end of the file.
|
Yes, the ID3v1 tags are positioned in the start of the mp3 and have fixed size. ID3v2 tags have variable size and are positioned in the end of the file. I was actually wondering if ID3v1 would speed up the startup even more, but I like the features of the ID3v2 so I have not tried it. If anyone have experience with a pure ID3v1 TAG collection, then please post your results.
Quote:
|
I also seem to have missed this folders first trick. From what you're saying, it appears that you need to copy all of your directories to an empty player and then after you've got those written to the start of the drive, you copy the information after them filling them but actually all the data they contain is written to the drive after the folder structure.
|
Yes, that's about it. The folders first gets created and allocated at the first sector grouped. Then the music files (these are placed after the folders) + folders (which are already on the harddisk, so they will have no effect on the position on the harddisk). It is easy to see the harddisk layout with OO defrag. Unfortunately OO don't move folders eventhough they are no positioned at the startup of the harddisk.
The question is have much a well-structured TAG means for the DB startup-time and if similar TAG type or a special type (ID3v1 or ID3v2 or ID3v2.3) is to be prefered.