[UberKitten]

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.

[jacqueline]

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.

[UberKitten]

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

[jacqueline]

Oh awesome, thank you! Will get this loaded up and see if we can repro your crashes.

[emsho]

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

[tofuvavohu]

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.

[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

[jacqueline]

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!

[emsho]

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... ?..

[redshift]

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

[emsho]

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.