Hi,

Has anyone had luck with v3.00-alpha3 on a player that was filled with mp3tofid and rsync?

So far, these are the issues I've seen:

• The database is now called database3
• This database now stores tags encoded in UTF-8
• Something has changed with the system fonts; my hacked rsync will no longer display text on the VFD screen
  

There may be even more changes inside the database. These are a couple of things I picked up from Roger at the Amersfoort BBQ: UTF-8, table-driven, string compression. So far, I've only seen evidence of UTF-8. Otherwise, the database looks the same to me.

Unfortunately I haven't been able to address any of these issues (and add ogg and flac support), as my player crashes as soon it has finished rebuilding the database. It's being killed by the VM, as it takes too much memory. And not just a little too much, adding 2 GB of swap does not help. Trimming down the database (removing all but the essential tags) does not help either.

v2.00-final would rebuild my database fine, though.

Pim

# Something has changed with the system fonts; my hacked rsync will no longer display text on the VFD screen

Hmmm. I bet that means GPSapp is also sad.

table-driven, string compression

This is on the agenda for a later release of 3.0. Currently, the database is the same, just in UTF8.

as my player crashes as soon it has finished rebuilding the database. It's being killed by the VM, as it takes too much memory

I finally got around the crash, just by reducing the number of tunes from about 16.000 to about 1600.

So this raises the question: how much tunes do you have on your v3.00-alpha3 player, regardless of how they got there?

Thanks,
Pim