Hello Andy. Any chance their might be an increase in the 12,000 title limit in the future? I know a lot of folks use only lossless titles which do eat up more space and it would seem that 12000 titles would be more than enough(I have 13770 files on a 128GB card and still have 8 GB remaining) But I am sure their are a good amount of folks that want to use this device with mp3s as well, and we could fit more files than that on a 256 card down the road. I would definitively be willing to wait a little longer for the database to process, if that were a side affect. You might be able to grab more customers who have larger libraries and to whom the limit might be deal-breaker when deciding whether or not to buy this device. Just my thoughts and my hope to add this to my firmware wishlist.
Here's what Andy Kong from Cayin said specifically in regards to this issue, you can find his original post at the bottom of page 146 of this thread:
"The N3 has a maximum index limit of 12,000 titles. This limit does not affect folder browsing or playlist operation, but it will affect the features under the Category menu. Upgrade to v1.2 firmware will not change maximum index limit.
We though 12,000 titles should be enough for 1 TF card (upto 256GB), now that we know some of our customers will go beyond that. I have no idea whether we can extend the limit further because this will increase the processing loading and will take up more internal memory, the system resource is indeed a bit tight with N3, we have to be very calculative in order to offer this level of digital audio capability and sound quality at the entry level budget."
Thanks nplateau for helping out by quoting my previous respond on the maximum file limit on Music Category function. I have submitted an optimization request to my team last Wednesday, literally immediately before I get on my plan to US (well, the plan was delayed for 6 hours, so I have some extra time to handle that promptly). From what I was told today, we can increase the title limit to 20,000, this is technically feasible and probably hitting the limit of N3 hardware (CPU processing power and RAM available for processing). The final availability will depend on actual testing after implementation. We cannot 100% guarantee that the feature will roll out in next firmware upgrade, we'll implement the feature but the final result will depends on actually testing, we do not want to downgrade our user experience and UI smoothness because of this feature.
For the meantime, you can access to all music files of your TF card by using the Music Library function of N3. By the way, may I ask if you are coming from an ipod/itunes background? I must say N3 is significantly behind the iTunes in terms of music management. The iTunes is a much larger project then N3 and embrace a comprehensive database library concepts. N3 is an index-based library when compare to iTunes. The current Music Category feature of N3 is fairly primitive when compare to iTunes, we can and we shall improve the Music Category feature of N3 down the road, but I don't want to create a false hope that we can compare with iTunes later on. We won't have that resource nor N3 has the appropriate architecture for something like that. There were some very high quality discussion about migration issues (and mentality) from iPod/iTunes users to N3 or similar DAP about a month back, unfortunately I don't have my reading notes with me while I am traveling, if someone can recall that, please post the reference again.
So is he saying I could create a playlist with all 13700 of my files and it would still play all of them at once? If so, would i need to create a playlist externally (m3u)? Thanks again for your help.
I mean you can access the undetected file from Music Library and Playlist, I was emphasis on the accessibility at that post. N3 cannot handle a playlist with 13700 music files. In fact, N3 has a maximum playlist entries limit of 1000 titles only, significantly below the maximum file number of Music Category function. The processing power required to handle playlist is enormous because this feature is not supported by the X1000 CPU directly and we need to implement this feature by our firmware coding, imagine the playlist is just a text based file, we need to load the metadata of the files in the playlist in advance otherwise we cannot allow users to scroll up and down the playlist smoothly, that's why we need to set a limit to the maximum number of playlist entries.
PS. By the way, I'll resume duty at Hong Kong on 12 June, will chime in again as soon as I get back on track, but until then the forum is supported by the Cayinsupport account, she is our new CS and is still in training period, I hope she is still in one piece when I get back to office.