![]() I find it unlikely that placing all the songs in the root would be a good idea. Fortunately though most of the collection is on CD so I just need to devote some time to rip all to FLAC files since the 340 obviously boasts a much better HK system than my STI. I have a pretty extensive music catalog, but unfortunately most are in mp3 format. So you guys are saying that you only have to place the songs on the root of the drive and it will play however many are on the USB drive (i.e., not limited to a specific amount of songs)? No matter how many songs I load up on a USB, the car only plays the first 255 songs. ![]() I have the exact same problem with my STI's USB port. I will report any findings once I have them.įor the record, the car is a 2014 F30, with MN-003.001.002 / TN-003.001.002 (which appears to be the latest version as of today).Įven if I'm right and there is indeed an indexer limit, I wonder why such a limit prevents simple folder browsing, as such activity requires no index. I am going to repeat this experiment with half of the collection removed (16 bits, 65536 songs). I wonder if any other people noticed a similar behavior with larger collections. I couldn't seem to find any consistent "pattern" to which folders remained and which disappeared. I could only see some of the Genres, some of the Artists under them and some of the Albums under each (visible) artist. I saw all the Genres/Artists/Album, etc.īUT, once the indexer finished (took a few minutes there.) several folders disappeared. ![]() And I was able to browse the ENTIRE tree and play it. I connected the drive with the test data and something very interesting happened: for the first few minutes, while the indexer was active, I couldn't browse by artist/album, etc. Total: 17 bits, 131,072 songs, occupying, as expected, about 120GB on the drive.Įach song has a unique file name and a corresponding ID3 tag specifying its "location." A file would look like "10.3" I picked a 1Mb song and replicated it under a carefully-designed folder structure, which proves, likely, that the BMW song indexer has a 16 bit limit (65,536 songs). Wiped the drive clean and filled it with "fake" music. ![]() The behavior was not consistent so I decided to test more methodically. BUT: I did encounter a strange behavior with folders "randomly disappearing." The hardware worked well, got recognized, played music, etc. Encouraged by several, successful "big" reports by other members, I decided to go a bit bigger: 480GB SSD Drive, with about 320Gb content on it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |