B.B wrote:EDIT...Well..it turns out that i were missing something..
"The requirement is that Path fields <......> are same in the backup and current database files"
nynaevelan wrote:I would suggest filename.ext after checksum.
nynaevelan wrote:What combination would make it unique??
nynaevelan wrote:For example, I have exact copies of all my tracks in wma, mp3 and m4a. They all have the same bitrate.
nynaevelan wrote:I supposed file size would work.
ZvezdanD wrote:nynaevelan wrote:For example, I have exact copies of all my tracks in wma, mp3 and m4a. They all have the same bitrate.
Are you sure about that? Are you using CBR? If you are using VBR it is very unlikely that they have the same bitrate. What is a point of your switch from mp3 collection to the wma or m4a if you keep the same bitrate? Those audio formats have advantage over mp3 because you could get smaller bitrate (and file size) for the same quality.
ZvezdanD wrote:nynaevelan wrote:I supposed file size would work.
Maybe, but you suggested filesize.ext, not file size. By the way, there is also a possibility to have two different tracks with same file size, so it should be also in combination with some another metadata. Maybe filename.ext and file size.
nynaevelan wrote:It is my intention to switch from mp3 to another format, but I haven't gotten around to testing the sound quality of them yet. And I do not know enough about bitrates and CBR/VBR to use something different yet.
nynaevelan wrote:I was thinking filename and filesize, that should be unique enough.
ZvezdanD wrote:There is a new update: v1.4 - 2009-08-28
- Added: option to restore playlists (both auto-playlists and static ones);
- Added: option to merge playlists (if Clear Playlists... option is turned off);
- Added: extra matching test for FileName/SongLength/Artist/Album/Year/TrackNumber fields (useful if audio format of tracks is different between backup and current database).
Users browsing this forum: Bing [Bot] and 20 guests