thanx for your thoughts on this guys. :-)
yeah - i'll just re-rip the offending track in FLAC.
and i agree with jeebers - this is the first of my thousands of tracks
encoded with GTuneb3 which exhibits this phenomenon. never seen it
before.
i suspect it has to do with extreme and sudden
hi all!
i love my SB3. matter of fact, i just got my 2nd one. ;-)
BUT i just discovered something rather unsettling and i would like to
see if anyone out there has noticed a similar effect.
i generally encode my CDs using SJeng's OggEncGTb3 tuned ogg-vorbis
encoder set to q6. i find this gives
would say it is entirely possible that the SB3 chokes on some high
quality encodes. And from your description of turning off anf on the
visualisations, i think thats whats happening.
dcote;228434 Wrote:
i generally encode my CDs using SJeng's OggEncGTb3 tuned ogg-vorbis
encoder set to q6. i
Try the official encoder, we tested some tracks at q10 with the official
encoder and they playback fine. q6 shouldn't produce files with such a
large bitrate.
But yes, Ogg decoding is a cpu-intensive process so what you describe
is definitely a cpu problem. I'm sure there is room for
hi funktstar,
actually i have. when i ripped the file, i did not realize how complex
it was and that vorbis bitrates would soar like that. i normally avoid
FLAC, because it is too big for me and i find vorbis @q6 to be
indistinguishable from FLAC.
so far, i see many workarounds, none which are
FWIW I have several thousand tracks encoded at Q8 using the standard
encoder, and have never encountered a problem like this. :-)
--
jeebers
jeebers's Profile: http://forums.slimdevices.com/member.php?userid=10290
View
