[amk]

Been trying to get my library onto the tangara for a few days now. I'm running firmware 1.2 (but tried 1.0, 1.1.2) but I've been running into issues when it tries to index the library. 

What usually happens is it starts scanning and then gives up after a while and lets me browse the database (but not scroll as it freezes) and shows that only a few artists have been indexed. If i check the database settings page it shows that it is 0.0kb

I've tried a couple of things, my library is fairly large (30000 songs) so that may also be part of the problem

• my library by default is in mp3s and FLAC (around 600gb), indexing this fails database says its 0kb
  

• transcoding all the flac to opus had no effect
  
• copying over small parts of the music library (All artists beginning with C for example, or a couple of artists) works okay, but adding further music sometimes corrupts the database and it goes back to 0kb
  
• Using a 64gb sandisk sd card works fine, just cant contain the whole library, it also works with the storage mode over USB (the 1tb card does not work over usb and results in a no SD card inserted error when turning off the usb storage mode)
  
• changing to FAT32 from exfat had no effect
  
• Including only opus files also fails, tried this in case some old mp3 or flac was corrupted, but all opus is freshly transcoded
  

Maybe its an SD card issue, I'm using a 1tb Sandisk card, but I cant test others with my whole library as I dont have another big enough and with the 64gig ones they seem to work okay

I can zip up one of the 0kb databases if it'd help debugging

[taivlam]

Been trying to get my library onto the tangara for a few days now. I'm running firmware 1.2 (but tried 1.0, 1.1.2) but I've been running into issues when it tries to index the library. 

What usually happens is it starts scanning and then gives up after a while and lets me browse the database (but not scroll as it freezes) and shows that only a few artists have been indexed. If i check the database settings page it shows that it is 0.0kb

...

Have you tried first saving all of your music onto your (micro)SD card, next connecting the (micro)SD card, and lastly reflashing your Tangara?  That is how I was able to make my microSD card readable on my new Tangara, as I described in another thread.

(In my issue, I never even saw my Tangara showing a loading message that the database was being created.)

[PetitDebardeurRose]

Also echoing OP's comments here...have the latest firmware and flashed it once without anything on my SD card and then put maybe 50gigs worth of music which it later seemed to index fine after being on all night. Since then I added more to my card and my current total is 331gbs and now it never indexes everything. Have done a re-flash once and used the update feature in the Database tab, but I still also get the 0kb index that OP stated happened. Also, trying to navigate tracks is painfully slow in this state when scrolling and even at max speed scrolling, it will chug and it can take a minute to even be able to scroll up to exit from the tracks field.

[amk]

I think this is SD card compatibility issue, I picked up a SanDisk 256 GB card and scanning seems to be working fine/not giving up -- generally things seem to be working as expected, though i'm waiting for a full scan to finish, however a quarter of my library seemed to scan and work okay.
-----
Finished a full scan, seems to have worked fine on the 250gb card, so seems fairly certain to be an SD compat issue

[PetitDebardeurRose]

I think this is SD card compatibility issue, I picked up a SanDisk 256 GB card and scanning seems to be working fine/not giving up -- generally things seem to be working as expected, though i'm waiting for a full scan to finish, however a quarter of my library seemed to scan and work okay.
-----
Finished a full scan, seems to have worked fine on the 250gb card, so seems fairly certain to be an SD compat issue

working with a new SanDisk Ultra 1.5TB micro-SD myself (along with SanDisk adapter)

that 256gb one you got, is it the big fat kind? did you fill it all the way up and have it work? right now i'm testing what the limits are for my card...about to see if it will index 76.1gbs as the last full index it worked with was 49.6gbs

[amk]

Its just a regular microsd sized one, its one of the "extreme" ones that are gold and red. The transcoded opus version of my music library fits in with 40~ gb to spare but everything (30k tracks) seemed to index okay, itd be nice to add an Artists/Albums/Tracks total to the database page to make sure as i can compare to other things then

[PetitDebardeurRose]

Its just a regular microsd sized one, its one of the "extreme" ones that are gold and red. The transcoded opus version of my music library fits in with 40~ gb to spare but everything (30k tracks) seemed to index okay, itd be nice to add an Artists/Albums/Tracks total to the database page to make sure as i can compare to other things then

gotcha

so far the only thing thats worked for me is when adding music, to manually delete everything on the microSD that isn't the music folder, then flash the firmware without the card in it, and then after that is done to turn off, insert the memory card, reboot and at that point it seems to index fine.

thus far i've got it to index to about 80gigs fine, so if I keep doing this I might eventually find where it starts to really struggle, but at the moment i'm making due with just a smaller collection

[jacqueline]

The specific SD card definitely seems to be a huge factor in these issues AFAICT. Hopefully we can get our hands on some cards with similar performance characteristics soon!

[PetitDebardeurRose]

tested a bunch today and my final conclusion is that if anyone else bought a 1.5tb SanDisk Ultra microsd, don't put more than 80gbs on it or the indexing will fail.

[PetitDebardeurRose]

tested a bunch today and my final conclusion is that if anyone else bought a 1.5tb SanDisk Ultra microsd, don't put more than 80gbs on it or the indexing will fail.

got in a brand new SanDisk 256gb full size SD card yesterday and put 43.7gbs on it...result is same as the former microsd as it won't play anything after the indexing happens, be it through the system or the file browser. *shrug*

[ailurux]

tested a bunch today and my final conclusion is that if anyone else bought a 1.5tb SanDisk Ultra microsd, don't put more than 80gbs on it or the indexing will fail.

got in a brand new SanDisk 256gb full size SD card yesterday and put 43.7gbs on it...result is same as the former microsd as it won't play anything after the indexing happens, be it through the system or the file browser. *shrug*

That sounds like it's more than an indexing issue if you can't play back through the file browser either. Is there any more info you can give me about what the behaviour is when you try to play a track, if possible with the serial output in case there's any errors that might shed some light on this issue? And could you share any info about what codecs your music is encoded with. Sorry you're having these issues!

[PetitDebardeurRose]

tested a bunch today and my final conclusion is that if anyone else bought a 1.5tb SanDisk Ultra microsd, don't put more than 80gbs on it or the indexing will fail.

got in a brand new SanDisk 256gb full size SD card yesterday and put 43.7gbs on it...result is same as the former microsd as it won't play anything after the indexing happens, be it through the system or the file browser. *shrug*

That sounds like it's more than an indexing issue if you can't play back through the file browser either. Is there any more info you can give me about what the behaviour is when you try to play a track, if possible with the serial output in case there's any errors that might shed some light on this issue? And could you share any info about what codecs your music is encoded with. Sorry you're having these issues!

The behaviour when playing a track, by which i'm usually going to a genre, most recently Electronic and playing the first of all the 87 songs. When I press play it shows it counting up to all the 87 tracks and then nothing. Have tried this with other methods, so just scrolling to a random song and hitting play and nothing happens and the cursor never progresses the song, not even pausing and then unpausing.

Weird thing is that the week or so of having the Tangara it seemed like I could get it up to at least 76ish gigs and playing fine, so i'm not sure what the cause could be?

How could I assist in sending more data that could be helpful to solving what might be going on? i'm using windows but have a linux box as well

[ailurux]

The behaviour when playing a track, by which i'm usually going to a genre, most recently Electronic and playing the first of all the 87 songs. When I press play it shows it counting up to all the 87 tracks and then nothing. Have tried this with other methods, so just scrolling to a random song and hitting play and nothing happens and the cursor never progresses the song, not even pausing and then unpausing.

Weird thing is that the week or so of having the Tangara it seemed like I could get it up to at least 76ish gigs and playing fine, so i'm not sure what the cause could be?

How could I assist in sending more data that could be helpful to solving what might be going on? i'm using windows but have a linux box as well

That is an odd issue. It seems like indexing is fine if you can see the tracks by genre, so that's good at least, but it sounds like there might be an issue with reading/writing to the queue file, or that there's an error in playing these tracks.

If you could connect the Tangara to a computer to read the serial output whilst attempting to play these tracks, there might be some errors logged that could help narrow down the cause. On Windows I believe you can use PuTTY, or on a linux machine you can use `screen`. The baud or speed should be 115200, otherwise you might get garbled output.

As another thing to check, the queue is stored internally in a queue playlist. It should be located at the root of the SD card, and be named `.queue.playlist`. You might need to show hidden files to see it. This is what Tangara looks at when it attempts to play the tracks in the queue. If the queue hasn't been cleared, this file should contain a list of all the tracks in the queue. When there's an error opening or playing a track, it'll go to the next one in this file, which sounds like it's happening for every track if it's just cycling through all of them very quickly and not playing them. You could check that the tracks listed in this file are pointing to the right filepaths.

[Construc_]

i seem to have a similar but not identical issue- mine seems to index a bit, and then give up, but it shows its got some database size (not 0).

I can navigate the SD card itself fine, and play things off that at least for a few minutes before it gives up and reboots.

the Albums By Artist screen shows some artists, but not all (it'll show Africa Hitech, Chevelle, and edIT), but if I go into the SD card itself i can see the rest (Asura, Carbon Based Lifeforms, Carpenter Brut, etc..) have not been indexed.

the Database shows "Size on disk: 1127.2KiB", with "Auto update" enabled, Schema version 8.

Putting the SD Card into my PC and deleting the tangara database folder and the two metadata files does not fix the issue.

I am using a 512GB Samsung EVO Plus MicroSD card, with a 117GB music collection