Rockbox.org home
Downloads
Release release
Dev builds dev builds
Extras extras
themes themes
Documentation
Manual manual
Wiki wiki
Device Status device status
Support
Forums forums
Mailing lists mailing lists
IRC IRC
Development
Bugs bugs
Patches patches
Dev Guide dev guide
Search



Donate

Rockbox Technical Forums


Login with username, password and session length
Home Help Search Staff List Login Register
News:

Thank You for your continued support and contributions!

+  Rockbox Technical Forums
|-+  Support and General Use
| |-+  Audio Playback, Database and Playlists
| | |-+  Hacking database_changelog.txt
« previous next »
  • Print
Pages: [1]

Author Topic: Hacking database_changelog.txt  (Read 813 times)

Offline Yard-Ape

  • Member
  • *
  • Posts: 3
Hacking database_changelog.txt
« on: December 31, 2015, 01:55:02 PM »
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!
Logged

  • Print
Pages: [1]
« previous next »
+  Rockbox Technical Forums
|-+  Support and General Use
| |-+  Audio Playback, Database and Playlists
| | |-+  Hacking database_changelog.txt
 

  • SMF 2.0.17 | SMF © 2019, Simple Machines
  • Rockbox Privacy Policy
  • XHTML
  • RSS
  • WAP2

Page created in 0.044 seconds with 15 queries.