Hi,
I received my Tangara yesterday, and have been playing around with it. First I flashed the 1.0.1 firmware, then I copied my moderately large library over. Tangara created its database automatically.
However, I noticed the database is missing several tracks/albums. I can listen to those through the file browser feature, but they don't show up in the indexed views.
My best guess is that one of my tracks has a tag that Tangara doesn't like, and it aborts the database scan early? I have no direct proof, but the albums I noticed are missing are ones with later file creation dates (newer additions to the library) so I suspect they would be scanned last. It's possible there are older albums also missing, but I haven't noticed any yet. I manage all my music through beets so I think all my tags should be more or less consistent.
I'm trying to debug this issue, but I'm not sure how to get the data I need about which tracks are missing. What is the best way to inspect the Tangara database contents? I might be able to do a diff with my beets track list and figure out where it's choking, if my theory is correct. My LOG and LOG.old files are both empty - 0 bytes. I tried getting the info through the Lua console in Tangara Desktop Companion but anything more complex than a one-liner gives me Command returned non-zero error code: 0x1 (ERROR). Even running t = true in the console gives this reply. My database schema version, according to Tangara, is 8.
Would love some help debugging this!
Thanks!
- JS
PS: very minor, but my Tangara Companion is showing the database file size incorrectly as X GiB instead of X KiB.
I received my Tangara yesterday, and have been playing around with it. First I flashed the 1.0.1 firmware, then I copied my moderately large library over. Tangara created its database automatically.
However, I noticed the database is missing several tracks/albums. I can listen to those through the file browser feature, but they don't show up in the indexed views.
My best guess is that one of my tracks has a tag that Tangara doesn't like, and it aborts the database scan early? I have no direct proof, but the albums I noticed are missing are ones with later file creation dates (newer additions to the library) so I suspect they would be scanned last. It's possible there are older albums also missing, but I haven't noticed any yet. I manage all my music through beets so I think all my tags should be more or less consistent.
I'm trying to debug this issue, but I'm not sure how to get the data I need about which tracks are missing. What is the best way to inspect the Tangara database contents? I might be able to do a diff with my beets track list and figure out where it's choking, if my theory is correct. My LOG and LOG.old files are both empty - 0 bytes. I tried getting the info through the Lua console in Tangara Desktop Companion but anything more complex than a one-liner gives me Command returned non-zero error code: 0x1 (ERROR). Even running t = true in the console gives this reply. My database schema version, according to Tangara, is 8.
Would love some help debugging this!
Thanks!
- JS
PS: very minor, but my Tangara Companion is showing the database file size incorrectly as X GiB instead of X KiB.
