In Reply to: RE: cPlay's FLAC decoder posted by J.Mac on January 9, 2010 at 04:45:47:
But if you use Flac files with this player you risk suffering dropouts.I've never had a dropout playing flac-format files with cPlay, cMP or both together in nearly two years of using them on a range of platforms. If you got them when you tried the programs (I take it you have tried them . . . ), your computer was under-specified, your OS was wrongly configured or both. As has been pointed out on this list time and again, decoding flac is not processor intensive.
EDIT: I have just spotted that Tony has earlier made essentially the same points - only rather better. Sorry for the repetition.
'Primitive' was being generous.
Perhaps it was but it doesn't help me to understand why cPlay's flac decoding is "primitive". Could I persuade you to be generous with your time as well as your judgement and explain?
No, it requires _less_ RAM to buffer the Flac than it does the corresponding WAV.
Well, it would at that except that, by design and as explained in the documents, cPlay decompresses flac files into wav format before it buffers them.
My music library includes several RBCD music tracks well over an hour long. If I were to upsample one of them off-line to, say, 192 KHz before playing it (as many recommend), how much RAM might I need using the technique you suggest?
This post is made possible by the generous support of people like you and our sponsors:
Follow Ups
- RE: cPlay's FLAC decoder - Ryelands 01/9/1008:36:07 01/9/10 (2)
- RE: cPlay's FLAC decoder - J.Mac 19:12:46 01/10/10 (1)
- RE: cPlay's FLAC decoder - Ryelands 02:32:40 01/11/10 (0)