At Fri, 4 Sep 2009 11:14:22 +0200, Giovanni Maruzzelli wrote: > > On Fri, Sep 4, 2009 at 9:57 AM, Giovanni > Maruzzelli<gmaruzz.lists@xxxxxxxxx> wrote: > > > > I'll do it and report > > Follow is the run results with your patch. > > It is possible that the "go to zero" you have seen before, is because > the application pause sending audio between small snippets (words or > phrases). This is not a problem with the other drivers, but it DO > generates XRUNs (at least with other kind of ALSA channel drivers > [yes, I have made another one, that works flawlessly, that uses cm108 > to interface GSM phones]). > > I tried to activate the XRUN debug, as for your instructions, but does > not give me output. Maybe it uses the DEBUG printk, that I saw does > not generates output on this centos box (I probably would have to > setup syslogd to print DEBUG messages). I had to modify your printks > and delete the KERN_DEBUG from it to have messages to appear in > /var/log/messages. If it's XRUN, the stream has to be stopped once, so you must have STOP log there. > So, this time for not having false positives I send you the result of > a continuous play of music, without pauses in it (maybe a pause at the > beginning): Hrm, is this the output from one stream? > Sep 4 11:04:04 localhost kernel: *** STOP > Sep 4 11:04:25 localhost kernel: *** START: buffer=4096, period=2048, > rate=16000 > Sep 4 11:04:25 localhost kernel: xxx delta=2, pos=32000(32), rest=2016000(2016) > Sep 4 11:04:25 localhost kernel: xxx delta=3, pos=80000(80), rest=1968000(1968) > Sep 4 11:04:25 localhost kernel: *** START: buffer=4096, period=2048, > rate=16000 Here you have the second start without stopping. Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
