<br><br>On Sunday, 18 March 2012, Ross Boylan <<a href="mailto:RossBoylan@stanfordalumni.org">RossBoylan@stanfordalumni.org</a>> wrote:<br><br>><br>> I'm pretty sure I used the same recording each time. So why is it now<br>
> trying for 320 when before is was 192? Does the code try progressively<br>> larger buffer sizes til it gets where it wants to go? If so, what is<br>> the final size I should use?<br>><br><br>The way that figure is reported/calculated is as follow.<br>
Myth asks alsa for 500ms audio. Say it only gets 250ms.<br>Myth looks at the size of the existing alsa kernel buffer, and sees that it's set to 64kB<br>As myth only got half the time it wanted, it assumes the audio buffer should have been 128kB instead.<br>
<br>So myth could have guessed that you needed 192kB buffer, but alsa continues to return a different buffer than what we ask. So the value reported changes.<br><br>I wouldn't worry about it unless you do get buffer underruns. The message is harmless, but does help finding the cause of buffer underruns when they do happen.<br>
<br>> Also, not being able to reset the sound without disabling other sound<br>> seems like a problem if different recordings have different<br>> requirements, which I gather they do.<br>><br><br>You can only modify the card if it's not in use elsewhere.<br>
<br>> mythtv 0.24-2.<br>> linux kernel 2.6.26-2-686<br>> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High<br>> Definition Audio Controller (rev 01) on motherboard.<br><br>Try upgrading your alsa drivers.