I’ve searched the archives and find several instances of folks using FreeRip to make FLAC files and then the FUZE player even with newest firmware (I have v.1 firmware) sees the FLAC files fine but then rapidly scans through them ‘searching’ for something but won’t play them.
The forums here suggest it is not an encoding setting problem as whether you use compression 1 or 5 or 8 it doesn’t matter. The best I can learn is that it is ‘something’ about FreeRip settings, perhaps with the way the files are ‘tagged’. No one seems to be able to come up with a consistent solution.
Some just re-ripped from CD using a different program. I really can’t bear the thought of that as it was would be weeks of work again.
Has FreeRip ever researched this and suggested a ‘why is this happening and how to fix it’ reply?
Is there a way to in a batch format ‘fix’ the tag problem? Is the problem that FreeRip puts ID3 tags on and they need Vorbis tags or something on that order? Others suggested they don’t have tags? I don’t understand as the majority of my FLAC collection had the info autopopulated by freedb database which I assume would have the correct info in the correct field!
Can someone from SanDisk look into this to see if maybe a easy firmware fix would allow these FLAC files produced by FreeRip to be read? FreeRip is popular, easy to use, adds track info, and their FLAC files read everywhere else except on the FUZE. I can send a sample file to the board or to a tech supporter if required.
Some have used FLAC frontend to ‘add tags’ (I thought mine have tags already?) and then have done something else to add info to the tags (MP3edit or something?)