Support and General Use > Audio Playback, Database and Playlists

Hacking database_changelog.txt

(1/1)

Yard-Ape:
Is it safe to manually add records to database_changelog.txt for re-import?

I've put some 300 albums on to a new 64GB uSD in my Clip+ and Rockbox has successfully built the database for it all.  But of course the fresh db doesn't include useful runtime values for all the albums---specifically, "rating" and "lastplayed". 

Inferring the format from my exported database_changelog.txt, I could set up the rest of these records from my unix and then try re-importing.  Awk tells me there are 22 fields. But I don't know if I can get all the fields exactly as Rockbox will expect upon re-import---specifically, "bitrate", "length", "playtime" and "mtime" I guess might be delicate.  I could script some values into those with some shell utilities like id3v2 but maybe that's little better than random or null values?  What would happen if I left every field null except "filename", "rating" and "lastplayed"?

Thanks!

Navigation

[0] Message Index