or Connect
Head-Fi.org › Forums › Equipment Forums › Portable Source Gear › The Fiio X5 Thread
New Posts  All Forums:Forum Nav:

The Fiio X5 Thread - Page 435

post #6511 of 19490
Quote:
Originally Posted by maeschba View Post


I once removed several folders on my X3 to investigate a freeze and found out that there seems to be a problem with long filenames. The file with the long name got loaded but it was not recognized by the player.


Thanks, I tried re-tagging longer albums files and renaming the folder, the library update still freezes :( Now I try formatting the card

post #6512 of 19490
Quote:
Originally Posted by thericochet View Post
 

"Why else would you put 2 memory card slots then?"

 

2 64GB cards full of FLACs even at 16/44 (let alone the intended HD quality) is nowhere near 5800 songs.

Whether you can hit 5800 songs even with 2 128GB cards of FLAC 16/44 is going to depend enormously on what you are putting on there.

I'm tired of justifying my collection.

 

5800 is a very low limit. Whether it affects you or not, smaller/older/less capable players can index much more than that stock. 

post #6513 of 19490
Quote:
Originally Posted by addsfsds View Post
 


Thanks, I tried re-tagging longer albums files and renaming the folder, the library update still freezes :( Now I try formatting the card


It was not the tags, but the filenames in my case. Btw. internal memory (X3) and card are both formatted to FAT32.

 

What kind of files do you have that cause the freezes?

post #6514 of 19490

edit: regarding 5800gate

 

I admit entirely that it's not ideal but apart from exceptional cases it wouldn't actually affect FLAC listeners, i.e. the player's very specifically targeted market. Why not move on and find something that unlike this is actually designed for large numbers of lossy files?

post #6515 of 19490
Quote:
Originally Posted by thericochet View Post

edit: regarding 5800gate



 



I admit entirely that it's not ideal but apart from exceptional cases it wouldn't actually affect FLAC listeners, i.e. the player's very specifically targeted market. Why not move on and find something that unlike this is actually designed for large numbers of lossy files?


 



GAAAAAAAAAAAAAAHHHHHHHHHHHHH!!!!!!!!!!!!!!!

BECAUSE WE HAVE MORE THAN 5800 LOSSLESS SONGS, THE X5 SO-SAY HAS EVER EXPANDABLE MEMORY (256 microSD currently being worked on - so X5 could potentially hold 512, and more if microSD continues to expand in storage space), AND WE OTHERWISE THINK THE X5 IS PROBABLY A GREAT PLAYER AND INCREDIBLE VALUE FOR MONEY!!!!!!!!!!!!!!!!


Sorry, I don't mean to shout at you specifically (although I AM shouting), but it really, really, really shouldn't be this difficult to get people to understand!
post #6516 of 19490
Quote:
Originally Posted by thericochet View Post
 

edit: regarding 5800gate

 

I admit entirely that it's not ideal but apart from exceptional cases it wouldn't actually affect FLAC listeners, i.e. the player's very specifically targeted market. Why not move on and find something that unlike this is actually designed for large numbers of lossy files?

 

I have lossless FLACs that are on average 20-30MBs for each song. That takes about 170GB to reach 5800 songs. The X5 supports 256GB so even if you filled it with lossless FLACs you would reach that limit quite easy.

 

 

FYI: I have no DSD files and none of my songs are available as DSD. But I would never tell ppl who want native DSD playback to look for something else that is "designed" for native DSD playback.

post #6517 of 19490

I too have more than 5800 songs. I have about 25,000 lossless songs at FLAC 16/44 (lowest/basic lossless). That's not the issue.

 

In practice, far fewer than 5800 of them will actually fit onto 2 64GB cards, and somewhere around 5800 of them (depending on what you want to put on there) will fit onto 2 128GB cards. If you're using higher quality files you can fit far fewer than 5800 of them on there. Hence fine for stated purpose given current card availability.

 

Hopefully in the long run the limit will be lifted somehow, even if this involves storing the library files on the cards themselves.

 

I admit it will be a problem for some but there are issues that will be a problem for almost all still to look at, and the player will still work in folder view no matter how many files you've got.


Edited by thericochet - 4/9/14 at 7:24am
post #6518 of 19490
Quote:
Originally Posted by thericochet View Post

I too have more than 5800 songs. I have about 25,000 lossless songs at FLAC 16/44 (lowest/basic lossless). That's not the issue.



 



In practice, far fewer than 5800 of them will actually fit onto 2 64GB cards, and somewhere around 5800 of them will fit onto 2 128GB cards. If you're using higher quality files you can fit far fewer than 5800 of them on there. Hence fine for stated purpose given current card availability.



 



Hopefully in the long run the limit will be lifted somehow, even if this involves storing the library files on the cards themselves.


 



Fine.

But what happens when 256gb cards are the norm?

And then 512gb?

And then 1tb?

That's a LOT of pointless and wasted space if you're still restricted to 5800 files.
post #6519 of 19490

Then that is later on and the file scan/indexing/storage of library files has plenty of time to be reviewed in the meantime.

I'm entirely with you in eventually wanting 2 512MB cards holding 25,000 FLACs on there.

post #6520 of 19490
Quote:
Originally Posted by thericochet View Post

Then that is later on and the file scan/indexing/storage of library files has plenty of time to be reviewed in the meantime.



I'm entirely with you in eventually wanting 2 512MB cards holding 25,000 FLACs on there.


 



But, correct me if I am wrong or have misunderstood, it sounds like the problem is a hardware issue that cannot (or will not) be resolved.

So, basically, the X5 will never be able to get round this problem.
post #6521 of 19490

Position well stated.........

post #6522 of 19490
Quote:
Originally Posted by maeschba View Post
 


It was not the tags, but the filenames in my case. Btw. internal memory (X3) and card are both formatted to FAT32.

 

What kind of files do you have that cause the freezes?

I was thinking about some 24 bit 88.1 khz as some people pointed out they were having problems playing them. After deleting those files and trying to short some files names, problems are still there. My sd is NTFS but i'm trying to format it from the X5 now.

post #6523 of 19490

"But, correct me if I am wrong or have misunderstood, it sounds like the problem is a hardware issue that cannot (or will not) be resolved."
 

I very much doubt this is genuinely the case. Even very weak hardware can index far more songs than that when it's running Rockbox. There is myriad evidence that pretty much any modern PMP hardware can do it. So I'd be amazed if it wasn't a software/implementation issue, regardless of what has been said here by (iirc) JamesFiio, and if it's just library file storage, as it appears to be, that can just be moved to the cards themselves.

post #6524 of 19490

Are we still on this issue? It is already getting too old 3 days ago.

 

 

Quote:
Originally Posted by ptravel View Post
 

Here's a thought:

 

Internal memory limitations are responsible for the 5800 track restriction.  Why not keep track indices for each SD card on the card itself?  That what eliminate the necessity of scanning each card whenever one is changed (after the initial scan, of course).

 

It might seem easy on paper -

 

Say you design the database generation based on a simple dynamic read / write function based on how many RAM you have. At first it seems to run well enough so you keep it simple as it is. Now 5 (or any number of line the X5 has) thousands line of code and 6 (or any amount of time it took) months later, you realize that you are running out of RAM and your database is limited to 5800 tracks. So what do you do? You went back and try to redo your dynamic read / write function and make it to dump all the files it scans on to the SD card instead of RAM, which is a more complex operation. But the problem is you are not just limited to one line of code - somewhat in that 5 thousands line of code, you probably use the same read / write function for other purposes, and they might need to be changed as well. So are all the other feature that access the old database which now required to point to the newly designed database. At the end, it is not just one line of code anymore but several weeks or months worth of code that needed to be carefully rewrite to avoid creating new bug.... now alone come some smart guys telling you that you should have done this and that, only it is 6 months too late.

 

The idea might be simple, but the execution is anything but.


Edited by ClieOS - 4/9/14 at 7:50am
post #6525 of 19490
Quote:
Originally Posted by thericochet View Post

"But, correct me if I am wrong or have misunderstood, it sounds like the problem is a hardware issue that cannot (or will not) be resolved."

 



I very much doubt this is genuinely the case. Even very weak hardware can index far more songs than that when it's running Rockbox. There is myriad evidence that pretty much any modern PMP hardware can do it. So I'd be amazed if it wasn't a software/implementation issue, regardless of what has been said here by (iirc) JamesFiio, and if it's just library file storage, as it appears to be, that can just be moved to the cards themselves.


 



Well that's what I thought RE Rockbox - if memory serves, the iAudio X5 had the same file limit issue, which was resolved only by Rockbox. But when I mentioned RB as a possible solution someone else (not James) earlier in this thread said that RB would NOT resolve the problem, because of the (Fiio) X5's lack of onboard memory (whereas the iAudio X5 had an internal hard drive, of course).

So what is the reality?
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Portable Source Gear
Head-Fi.org › Forums › Equipment Forums › Portable Source Gear › The Fiio X5 Thread