FiiO X7 | DXD | DSD | 384K/64B | ESS9018+ Android | WiFi | Bluetooth | 4 AMP modules | Balanced Out |

[Sarcasmo]

Issue: Scanning failure when large number of files exist on card. Reordering directories matter.
 
Setup:
FiiO X7 FW 3.1.7
Sandisk 200GB microSD FAT32 (consistency checks run - reformat performed in case of filesystem issues)
 
File details:
I have 2 main directories on my card:
FLAC
MP3        <-- (don't judge...)
 
I have around 1200 flac files in the FLAC folder and around 22000 mp3 files in the MP3 folder.
Occationally I clean the FiiO music database and rescan ONLY the FLAC folder. The flac files within generally do not contain enbedded album art (only a folder.jpg) and so scan completely.
 
Problem details:
I happened to rename the FLAC folder to MUSIC so I was then left with two folders (please note the flacs are now contained in a folder alphabetically later then the 22000 mp3 files folder):
MP3
MUSIC
 
After cleaning the database and rescanning ONLY the MUSIC folder for flacs, it stalled at 0 scanned for 5 minutes and then failed to scan any files (empty database).
I repeated the scan several times with the same result (with device reboots to be sure).
I reformatted the card and copied the files back into the MP3 and MUSIC folders. The scan failed again.
I renamed the MUSIC folder back to FLAC, and the scan was successful.
 
Question:
@FiiO : Is the FiiO music app having an issue with the alphabetical ordering and number of files on the card?  It seems that it is performing some sort of filesystem tree parse and can't cope with skipping the 22000 mp3 files, failing before it gets to the flac files.  Renaming the flac folder to be alphabetically before the mp3 folder allows it to scan successfully.
 
I've seen this behaviour before in the workplace when a code module tries to grab the entire filesystem tree to analyse what's there and runs out of memory if there are too many files present.

 

[Paulo Abreu]

  Issue: Scanning failure when large number of files exist on card. Reordering directories matter.
 
Setup:
FiiO X7 FW 3.1.7
Sandisk 200GB microSD FAT32 (consistency checks run - reformat performed in case of filesystem issues)
 
File details:
I have 2 main directories on my card:
FLAC
MP3        <-- (don't judge...)
 
I have around 1200 flac files in the FLAC folder and around 22000 mp3 files in the MP3 folder.
Occationally I clean the FiiO music database and rescan ONLY the FLAC folder. The flac files within generally do not contain enbedded album art (only a folder.jpg) and so scan completely.
 
Problem details:
I happened to rename the FLAC folder to MUSIC so I was then left with two folders (please note the flacs are now contained in a folder alphabetically later then the 22000 mp3 files folder):
MP3
MUSIC
 
After cleaning the database and rescanning ONLY the MUSIC folder for flacs, it stalled at 0 scanned for 5 minutes and then failed to scan any files (empty database).
I repeated the scan several times with the same result (with device reboots to be sure).
I reformatted the card and copied the files back into the MP3 and MUSIC folders. The scan failed again.
I renamed the MUSIC folder back to FLAC, and the scan was successful.
 
Question:
@FiiO : Is the FiiO music app having an issue with the alphabetical ordering and number of files on the card?  It seems that it is performing some sort of filesystem tree parse and can't cope with skipping the 22000 mp3 files, failing before it gets to the flac files.  Renaming the flac folder to be alphabetically before the mp3 folder allows it to scan successfully.
 
I've seen this behaviour before in the workplace when a code module tries to grab the entire filesystem tree to analyse what's there and runs out of memory if there are too many files present.

 
That is interesting. After reseting database did you delete the FiiOMusic and Imageloader folders before scanning again?
If you are pointing a specific folder to scan music, it shouldn't look elsewhere, I guess - but an interesting find indeed.

 

[Sarcasmo]

   
That is interesting. After reseting database did you delete the FiiOMusic and Imageloader folders before scanning again?
If you are pointing a specific folder to scan music, it shouldn't look elsewhere, I guess - but an interesting find indeed.

 
Just tried deleting the 2 folders from the internal storage and now it's scanning properly... false alarm I'm guessing...
 
Thanks for spotting that Paulo.
 
On a side note, I scanned a 'test' mp3 album that had 500x500 embedded album art in jpg format (~40kb file size) and it would NOT scan. Removing the album art and replacing with a fresh 500x500 jpg from the internet solved the problem.  I've read pretty much all of this forum, but may have missed an issue identified with types (not just size) of jpg embedded album art?  Or could this too be related to those cache folders in the internal memory?

 

[Paulo Abreu]

   
Just tried deleting the 2 folders from the internal storage and now it's scanning properly... false alarm I'm guessing...
 
Thanks for spotting that Paulo.
 
On a side note, I scanned a 'test' mp3 album that had 500x500 embedded album art in jpg format (~40kb file size) and it would NOT scan. Removing the album art and replacing with a fresh 500x500 jpg from the internet solved the problem.  I've read pretty much all of this forum, but may have missed an issue identified with types (not just size) of jpg embedded album art?  Or could this too be related to those cache folders in the internal memory?

 
I don't think there is a final answer to that issue but FiiO stated is working to fix all problems with scanning.
One thing that seems to work for everyone (who's willing to accept that...) is to remove all the embeded art and have it externally as a JPG file (Cover.jpg) - that worked for me and have no issues with 2 x 200Gb + 1x 125Gb cards.
 
Regards

 

[Sarcasmo]

   
I don't think there is a final answer to that issue but FiiO stated is working to fix all problems with scanning.
One thing that seems to work for everyone (who's willing to accept that...) is to remove all the embeded art and have it externally as a JPG file (Cover.jpg) - that worked for me and have no issues with 2 x 200Gb + 1x 125Gb cards.
 
Regards

 
Yeh, that seems to be that case and is the approach I've been using with portable media players for a while now - just a shame - embedded seems tidier some how, but it is what it is...

 

[Paulo Abreu]

I couldn't figure yet when and how but pulsar light goes OFF while X7 is on and playing music (with some browsing and pauses in between). This only happened to me in this latest 3.1.7 FW.
 
I go to settings, Display, Pulsar light and it says "lit" under "working" (as I have it set), switch off/Lit again and its back again. Its a minor issue but can induce one in mistake thinking X7 its off when its actually in pause or something and waisting battery unnecessarly.
 
My 2 cents

 

[peter1480]

This from the x5iii tread I guess also applies here.
 

Statements regarding the music scanning problem on X5 3rd gen

 

Dear customers,

 

We have recently received feedback from some customers saying that X5 3^rd gen could not scan all the songs on it.

 
After receiving the feedback, our software team had run some tests on this problem and found that: the using habits of our Chinese users and the song file types they use are quite different from that in other regions. Most of the song files owned by our Chinese users only have external album art, while the customers in other regions are mostly playing the song files with embedded album art. When the X5 3^rd gen scans the songs and update library, it will extract the embedded album art image from the song files and store them into a single folder. Since the quantity and size of files under one folder is limited on Android, the player will stop scanning when it reaches the limit. Therefore, when scanning a large music library, some songs might be omitted.
 

So far we've already planned to change the scanning mechanism, but it will require quite some work to finish. And the first beta test is not that satisfactory yet.

 

Before we solve this scanning problem, we recommend you follow the below methods to play your music.

a) View and play songs through the Folder view menu in FiiO Music;

b) Use a third-party app to play music. There is no SRC on the X5 3^rd gen, so the sound quality from a third-party app is also guaranteed;

c) First scan for all the songs in FiiO Music then exit the app. After that open the ES file manager, delete the "album" folder under the directory "Internal_sd/FiiOMusic". Then reopen FiiO Music and scan for all songs again. (some of the album arts will not be displayed if using this method)

 

We couldn't give you an estimated time when we could fix this problem so far, and we think that it's not appropriate to make an irresponsible promise here. But we will try our best and fix this issue as soon as we can.

 

And we sincerely apologize for any inconvenience this might bring to you.

 

Best regards,

FiiO Electronics Technology Co, Ltd.

 

[TheEldestBoy]

How often does Fiio typically release generational updates to their DAPs?
 
I'm just wondering when we might reasonably expect to see the release of X7 2nd generation?
 
My primary headphones are the HD600.
I like what I'm reading about the X5 3rd gen, but am worried that it's not powerful enough to bring out the best in my HD600.
The X7 with the AM5 amp module (or the AM3 balanced) is probably the best match for the HD600, but I feel like I want to wait until the 2nd generation of the X7 (so that they can implement everything they've learned from the success of the X5 3rd gen: dual SD slots, an arguably better UI, etc).
 
What do you guys think?

 

[FiiO]

   
Just tried deleting the 2 folders from the internal storage and now it's scanning properly... false alarm I'm guessing...
 
Thanks for spotting that Paulo.
 
On a side note, I scanned a 'test' mp3 album that had 500x500 embedded album art in jpg format (~40kb file size) and it would NOT scan. Removing the album art and replacing with a fresh 500x500 jpg from the internet solved the problem.  I've read pretty much all of this forum, but may have missed an issue identified with types (not just size) of jpg embedded album art?  Or could this too be related to those cache folders in the internal memory?

Dear Sarcasmo,
 
Thank you for the feedback. It seems that the issue happens still because of the embedded album art. 
Removing the album art and replacing with a fresh 500x500 jpg from the internet solved the problem. 
The fresh 500x500 jpg you mentioned is embedded one or external one? What about the file size?
 

So far we've already planned to change the scanning mechanism, but it will require quite some work to finish. And the first beta test is not that satisfactory yet.
 

We will try our best to slove this issue as soon as we can. Please accept our sincere apology for  bringing inconvenience to you.
 

Best regards

 

[Sarcasmo]

  Dear Sarcasmo,
 
Thank you for the feedback. It seems that the issue happens still because of the embedded album art. 
Removing the album art and replacing with a fresh 500x500 jpg from the internet solved the problem. 
The fresh 500x500 jpg you mentioned is embedded one or external one? What about the file size?
 

So far we've already planned to change the scanning mechanism, but it will require quite some work to finish. And the first beta test is not that satisfactory yet.
 

We will try our best to slove this issue as soon as we can. Please accept our sincere apology for  bringing inconvenience to you.
 

Best regards

 
@FiiO  : Thanks for your reply.
To answer your question, the fresh 500x500 jpg was NOT embedded when it scanned correctly.  It was about 40kb in size.

 

[Paulo Abreu]

  This from the x5iii tread I guess also applies here.
 

Statements regarding the music scanning problem on X5 3rd gen

 

Dear customers,

 

We have recently received feedback from some customers saying that X5 3^rd gen could not scan all the songs on it.

 
After receiving the feedback, ...

 
I am happy FiiO listened to the new X5 3rd community... "After receiving the feedback" sounds as a new subject, but let us not mix things, X7 is one thing, X5 is another.
 

 

 

[spetrushin]

Yeah, that sounds so funny. Because I remember that scanning issues was raised many-many times. So, that can means that all our feedback is here just local talks, nothing is goes to the FiiO bugtracker (of course, if they have it). 

 

[Paulo Abreu]

  Yeah, that sounds so funny. Because I remember that scanning issues was raised many-many times. So, that can means that all our feedback is here just local talks, nothing is goes to the FiiO bugtracker (of course, if they have it). 

 
Yeah. Although I understand the difference between the "obligation to give a response" to a problem related with an "official" firmware (X5) and the "feedback from a Beta" in "development". Its a different responsability and X5 owners are legitimate to complain. But the same could be said from X7 official FW2.x - a few things still today on the advertising material are yet to build.
 
But Hey, I am a happy X7 owner, FW developments have been great so far and no issues for me with the usage I give it. Keep on the good work @FiiO !!!
 
My 2 cents

 

[spetrushin]

   
Yeah. Although I understand the difference between the "obligation to give a response" to a problem related with an "official" firmware (X5) and the "feedback from a Beta" in "development". Its a different responsability and X5 owners are legitimate to complain. But the same could be said from X7 official FW2.x - a few things still today on the advertising material are yet to build.
 
But Hey, I am a happy X7 owner, FW developments have been great so far and no issues for me with the usage I give it. Keep on the good work @FiiO !!!
 
My 2 cents

 
Guess FiiO should say us thanks since we are looking and reporting bugs for free, because we are loving our devices and trying to do improvements. Such relations in the long term period are turning into product dissatisfaction and brand de-trust.
 
Better to release new products, and count money. But that strategy isn't working in the long term period.
 
But who cares  
 
I have very good idea: since X7 and X5III firmwares are identical we can report same info in the X5III thread.. Who knows, may be that way can push things forward.

 

[peter1480]

   
Yeah. Although I understand the difference between the "obligation to give a response" to a problem related with an "official" firmware (X5) and the "feedback from a Beta" in "development". Its a different responsability and X5 owners are legitimate to complain. But the same could be said from X7 official FW2.x - a few things still today on the advertising material are yet to build.
 
But Hey, I am a happy X7 owner, FW developments have been great so far and no issues for me with the usage I give it. Keep on the good work @FiiO !!!
 
My 2 cents

 

   
Guess FiiO should say us thanks since we are looking and reporting bugs for free, because we are loving our devices and trying to do improvements. Such relations in the long term period are turning into product dissatisfaction and brand de-trust.
 
Better to release new products, and count money. But that strategy isn't working in the long term period.
 
But who cares  
 
I have very good idea: since X7 and X5III firmwares are identical we can report same info in the X5III thread.. Who knows, may be that way can push things forward.

 

  Yeah, that sounds so funny. Because I remember that scanning issues was raised many-many times. So, that can means that all our feedback is here just local talks, nothing is goes to the FiiO bugtracker (of course, if they have it). 

I'm a happy owner of both the x7 and the x5iii and yes Fiio listen to their uses on the threads and by personnal message unlike some other DAP makers. I'm sure they will get there and having had a look at the Fiio player on both in detail they are almost identical bar a few lines of code mosly relating to the buttons on each device. So now the efforts are doubled