Displaying 4 results from an estimated 4 matches for "log_warn1".
2004 Aug 06
0
IceS 2.0a - Extended sleep requested
...t; 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 (%ld ms), sleeping for one
second",
sleep);
timing_sleep(1000);
}
change to the following
if(sleep > 5000) {
LOG_WARN1("Extended sleep requested (%ld ms), sleeping for 5
seconds",
slee...
2004 Aug 06
2
IceS 2.0a - Extended sleep requested
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.
---
2004 Aug 06
1
ices: Metadata for im_stdinpcm
...while(*md)
+ free(*md++);
+ free(s->metadata);
+ }
+
+ s->metadata = (char **)param;
+ s->newtrack = 1;
+ thread_mutex_unlock(&s->metadatalock);
+ break;
default:
LOG_WARN1("Unhandled event %d", ev);
return -1;
@@ -58,6 +89,24 @@
return 0;
}
+static void metadata_update(void *self, vorbis_comment *vc)
+{
+ stdinpcm_state *s = self;
+ char **md;
+
+ thread_mutex_lock(&s->metadatalock);
+
+ md = s->metadata;
+
+ if...
2004 Aug 06
1
Freedomaudio player
Karl Heyes wrote:
> Well assuming a pure clock change, a change of 10 secs could cause an
> extended sleep period in which icecast could drop the connection. In
> this case increasing the source-timeout is not the right solution as
> a 10 second gap in audio streaming is really bad! A simple log message
> could help track those type of problems. If the
> sleep is over say 2