search for: pcm_initialise_module

...:45:50] INFO ices-core/main libshout version 2.0-kh22 [2003-11-25 10:45:50] INFO ices-core/main realtime scheduling has been enabled [2003-11-25 10:45:50] DBUG stream/start_runners starting runner [2003-11-25 10:45:50] INFO stream/ices_runner Runner 1 ready [2003-11-25 10:45:51] INFO input-pcm/pcm_initialise_module Initialising PCM input module [2003-11-25 10:45:51] DBUG input-pcm/pcm_initialise_module Module PCM using buffers of 4096 samples [2003-11-25 10:45:51] DBUG input/initialise_input_modules Module 1 (pcm) has 20 buffers [2003-11-25 10:45:51] DBUG input/open_next_input_module checking module 1 [200...

Hello, I will take your last version, but I have fresher news about the bug that occurs every mornings in fact... I think this is ntpdate which is causing the problem, as the time of the machine change for more than one second. Here is all the info: 09:46:17 up 1 day, 1:22, 2 users, load average: 0.60, 0.71, 0.68 86 processes: 84 sleeping, 2 running, 0 zombie, 0 stopped CPU states: 10.4%

...0:00:04] INFO ices-core/main libshout version 2.0-kh22 [2003-11-26 00:00:04] INFO ices-core/main realtime scheduling has been enabled [2003-11-26 00:00:04] DBUG stream/start_runners starting runner [2003-11-26 00:00:04] INFO stream/ices_runner Runner 1 ready [2003-11-26 00:00:04] INFO input-pcm/pcm_initialise_module Initialising PCM input module [2003-11-26 00:00:04] DBUG input-pcm/pcm_initialise_module Module PCM using buffers of 4096 samples [2003-11-26 00:00:04] DBUG input/initialise_input_modules Module 1 (pcm) has 20 buffers [2003-11-26 00:00:04] DBUG input/open_next_input_module checking module 1 [200...