search for: 35kbs

I've just finished a little encoding set and the following happened: 22Khz resampled, q-0.4 encode = ~38kbs = one error at the beginning only. 22Khz resampled, q-0.5 encode = ~37kbs = 6 to 7 sleep errors in the first second or so, nothing after that. 22Khz resampled, q-0.6 encode = ~35kbs = 14 to 15 sleep errors then nothing. 22Khz resampled, q-0.8 encode = ~33kbs = Many sleep errors. --- Geoff Shang <gshang@uq.net.au> wrote: > hmmmm. so is there a difference between the one > that works and the one > that doesn't? Bitrate, maybe? > Geoff. ________________...

...ding set and the > following happened: > > 22Khz resampled, q-0.4 encode = ~38kbs = one error at > the beginning only. > > 22Khz resampled, q-0.5 encode = ~37kbs = 6 to 7 sleep > errors in the first second or so, nothing after that. > > 22Khz resampled, q-0.6 encode = ~35kbs = 14 to 15 > sleep errors then nothing. > > 22Khz resampled, q-0.8 encode = ~33kbs = Many sleep > errors. Will you try something to get you going. In the ices/src/input.c file goto line 92, you should see if(sleep > 1000) { LOG_WARN1("Extended sleep requested...

Thanks for offering to help, Karl. Config - I thought my email was long even without the config files so I didn't include them! They are normal random playlist configs. What aspects are you looking for? CPU - vmstat 1 gives consistant CPU readings of around 2,1,97 for us,sy,id respectively when no one is listening to the streams. There's hardly any change when a client starts listening.