I got my Tangara the other day and updated it to 1.1.2.
I prepared a microSD with exFAT, and put my whole 150GB music library on it. Songs are in the format /Music/<Artist>/<Album>/<Song>.ogg. There are 40k files over 19k folders, broken up into 16k .ogg files, 10k .lrc files, and 12k cover.jpg files.
Unfortunately, that may have been a little too much for the Tangara. The DB icon in the top right is always there, which I assume means it's indexing the database.
I've left it plugged in for a day, but it just seems to crash and reboot after some amount of time and never finishes the database. Tangara Companion always says the database size on disk is 2 kib, so it doesn't seem to be getting anywhere.
I can use Files to browse to music, but the file browsing is quite slow, and it can take multiple minutes to load a file.
Any suggestions? It would be nice if I could build the database on my computer using the companion app.
Hi! This is a fairly large library, so indexing may take some time. It does sound like the indexer might be choking on some of your files however; this isn't the first we've heard of large ogg collections causing crashes during indexing. Unfortunately we haven't gotten a repro case for the crash yet however. Sorry about that!
You *might* be able to get through indexing by transcoding to a format like Flac, but obviously this is far from idea. Being able to do the indexing step via the companion is indeed a good idea, we'd like to implement something like that eventually to make the experience with very large collections a bit nicer.
I would be happy to 7zip up my whole library and send it via Dropbox link, but I get that may be impractical to work with, lol.
Instead, I replaced all the files with 0 byte files, and I was able to reproduce the issue with that. There are quite a few folders with unusual unicode names in my library, so that might be the issue.
Here is an archive of all the empty files that should be easy to repro:
https://www.dropbox.com/scl/fi/o12j9r73x...t3ayl&dl=0
Oh awesome, thank you! Will get this loaded up and see if we can repro your crashes.
Unfortunately, I'm experiencing similar issues.
My (large) library is 433GB in size, mp3, ±48000 songs. I store everything on a 1TB SanDisk SDXC ExtremePRO 200MB/s SD card (which is regular size). Manufacturer code: SDSDXXD-1T00-GN4IN.
My library is organised similar as UberKitten's library: Music | Artist | Album | Song . I also have a 'podcast' folder on the root level as I read elsewhere that Tangara recognizes this and plays podcasts from where you stopped the last time (which I haven't tried out yet but would applaud if it did).
I have upgraded the firmware to 1.2.0. I have the database upgrade several times afterwards. It never goes past 15000 KiB. Upgrading again sometimes results in less KiB being recognized than the previous time.
A second problem (which might or might not be connected to my initial problem) is that all recognized folders (artist, album and song folders) are all NOT in alphabetical order but seemingly random. However, that same random order is always maintained identical throughout my different 'database upgrade' attempts. My library always starts with Justin Timberlake. [So many jokes to make about this...]
I don't really know what else to try to get Tangara to recognize the full library. Any hints are appreciated.
Cheers from the Netherlands!
emsho
My workaround for this issue was to create a /Playlists directory that mirrors the structure of the /Music directory, but instead of files at the lowest level folder, it has a .playlist file that then plays all the files for the corresponding /Music folder in the numerical sequence of the file names. I posted a thread about it with the python code I wrote to automate the task. It's not perfect, but it got me to the point where I can use my Tangara.
2025-02-08, 07:05 PM
(Edited 2025-02-08, 07:09 PM by emsho.)
Wow. That's an impressive effort to fix this problem. I almost understand half of what you talk about in your linked thread.. :-)
I applaud your initiative but I don't think I'm up for this operation.
I hope that the bright souls behind the Tangara can come up with an 'inside the box' firmware solution for this.
Thanks for your quick response!
Cheers,
emsho
We sorted through the issue tracker late last week, and as far as we're aware the only major outstanding crash bug that seems relevant here is an issue with embedded album art in files that use ogg containers (so '.ogg' and '.opus' files). We'll try to get it fixed soon, but in the meantime stripping out any embedded art might help!
Thanks for your reply. I'll see in how far I'm able to find the ogg files in 433GB worth of music.
Any idea why the recognized parts of my library show up in a seemingly random order (yet always in that same order)? It seems that the Tangara sorts it by another factor, but I have no idea which one it could be. Justin Timberlake isn't the first artist I put in my iTunes library, nor the smallest file, nor the largest... ?..
(2025-02-10, 04:03 PM)emsho Wrote: Any idea why the recognized parts of my library show up in a seemingly random order (yet always in that same order)? It seems that the Tangara sorts it by another factor, but I have no idea which one it could be. Justin Timberlake isn't the first artist I put in my iTunes library, nor the smallest file, nor the largest... ?..
It sounds like you're navigating in the file browser, so it's probably because of this issue: https://codeberg.org/cool-tech-zone/tang...issues/118
Thank you for your reply, redshift!
Indeed, I was using the file browser (not knowing that there is a problem). Browsing "Albums by Artist" give me alphabetical order. Excellent! I didn't even try that after the file browser didn't sort everything alphabetically. One problem solved.
Having not solved my initial problem of getting my large library to be initialised (as described above in this thread), I left the Tangara alone for some time.
Today, I did a firmware update (v1.3.0) and had it initialise my library again. Unfortunately, the Tangara behaves identical to what I described above. After a few minutes, the initialising process seems to be done (the DB logo disappears) and it still recognises only a tiny fraction of the artist folders, within those folders recognised, it will only recognise one or two albums, and only a few songs of an album. Sometimes, it names the tunes but give a length of 0:00 seconds.
From previous comments, I learned that the Tangara might have problems if files like album covers are also in the library. I have checked some artist folders of whom I only have one album to make sure there were only mp3 files in the folder. But Tangara would still not see the artist folder after initialising again.
Is my library somehow corrupted? My Fiio player uses the exact same library and it works fine; I actually copied the data from the Fiio player's SD card to my MacBook and then onto the newly purchased Tangara SD card. (A long, slow, overnight operation, by the way..)
Am I using an SD card which doesn't gel with the Tangara? (I didn't see a database on this here.)
I don't really know what to try next in order to make this work. Any ideas anyone?
Cheers!
Emsho
(2025-03-30, 05:49 PM)emsho Wrote: Having not solved my initial problem of getting my large library to be initialised (as described above in this thread), I left the Tangara alone for some time.
Today, I did a firmware update (v1.3.0) and had it initialise my library again. Unfortunately, the Tangara behaves identical to what I described above. After a few minutes, the initialising process seems to be done (the DB logo disappears) and it still recognises only a tiny fraction of the artist folders, within those folders recognised, it will only recognise one or two albums, and only a few songs of an album. Sometimes, it names the tunes but give a length of 0:00 seconds.
Hm, that's odd that only some are showing up. Are the tracks that aren't getting picked up by the database present in the file browser? If so, does playing these tracks from there work?
It sounds like some file or other issue might be causing the database indexer to fail early. To try narrow down where the issue is, you could try copy over a subset of your library at a time, or if you feel comfortable building and flashing the firmware yourself you could add some logging to the database (note: this might slow indexing down a bit) to see what files it's processing and when it stops. There's some docs on how to read the logs here: https://cooltech.zone/tangara/docs/developer/debugging/.
If the building and adding log statements to the firmware part sounds intimidating, but you'd still like the logs, I can build a debug .tra with the logging already enabled if you'd prefer.
Thanks for the quick response, ailurux! I am definitely not capable of building any firmware myself. If would be fantastic if you could help me out with this. If I understand it correctly, the added logging might be able to tell us were the initialising process goes wrong.
It admittedly is a very large library and there is a good chance that somewhere in there might be some 'illegal' files which corrupt the initialisation. It's impossible to check such a library by hand. And I don't know any software that could take over this work.
But hopefully, the log can give us clues. Do I need to PM you my email address?
Thanks again for your support.
Cheers,
Emsho
(2025-03-30, 10:23 PM)emsho Wrote: But hopefully, the log can give us clues. Do I need to PM you my email address?
No need, I'll add some logging to the firmware and put the .tra somewhere (it might also help others who are running into indexing issues) and reply here when I'm done.
Something I thought of whilst adding the logging though, just to check, are your tracks in a "Music/" directory at the root of the SD card (ie, the file path should start with "Music/...")? If not, this could also cause some tracks to not be indexed by the database.
(2025-03-31, 12:18 AM)ailurux Wrote: Something I thought of whilst adding the logging though, just to check, are your tracks in a "Music/" directory at the root of the SD card (ie, the file path should start with "Music/...")? If not, this could also cause some tracks to not be indexed by the database. Yes they are, one folder named 'Music', a second one being 'Podcasts'. Nothing else on the root level.
(2025-04-01, 08:13 AM)emsho Wrote: (2025-03-31, 12:18 AM)ailurux Wrote: Something I thought of whilst adding the logging though, just to check, are your tracks in a "Music/" directory at the root of the SD card (ie, the file path should start with "Music/...")? If not, this could also cause some tracks to not be indexed by the database. Yes they are, one folder named 'Music', a second one being 'Podcasts'. Nothing else on the root level.
Ok, cool, that shouldn't be an issue then. Will put together a database debug firmware sometime in the next couple of days (balancing assembly work at the moment as well).
2025-04-03, 01:16 AM
(Edited 2025-04-06, 10:23 PM by ailurux.)
Attached is a modified version of the current release (1.3.1) with logging added to each file processed by the database. This will slow down the database indexing by a bit (mine processed ~900 tracks in 3 minutes with this build), but the logs should hopefully help narrow down where the issue is. You'll also probably want to delete the database (`.tangara-db` folder on the sd card, you might need to show hidden files to delete it on your computer) before testing with this build to rule out any issues with it not processing tracks it's already done. It might be easiest to disable automatic database updating, and manually start it via the settings once you're monitoring the output to make sure you capture those logs as they happen. And here is the docs on how to read these logs (with the prebuilt firmware you only need to worry about reading the logs, not enabling them): https://cooltech.zone/tangara/docs/developer/debugging/
tangarafw-v1.3.1-database_debug.tra (Size: 2.08 MB / Downloads: 9)
Thank you for adding the logging to the firmware, ailurux!
Unfortunately, I'm not able to download your attachment. I keep getting "You don't have permission to access this page...". I tried with Brave (with 'shields down', as in: all cookies etc are permitted) and with Safari.
I'm sure it's me. (It pretty much always is...) But just to be sure: has anyone else managed to download the .tra file?
Thanks for your patience.
Cheers,
emsho
Same here:
You do not have permission to access this page. This could be because of one of the following reasons:
Your account has either been suspended or you have been banned from accessing this resource.
You do not have permission to access this page. Are you trying to access administrative pages or a resource that you shouldn't be? Check in the forum rules that you are allowed to perform this action.
Your account may still be awaiting activation or moderation. (Resend Activation Code)
You have accessed this page directly rather than using appropriate forms or link.
|
