<br><br>On Tuesday, 2 August 2011, D. R. Newman <<a href="mailto:d.r.newman@e-consultation.org">d.r.newman@e-consultation.org</a>> wrote:<br><br>>> Using pulse audio I assume?<br>><br>> Yes I am using pulse audio under KDE.<br>
><br>>> A few options to get this pulse issue: use native Alsa. Use ALSA:pulse<br>>> driver (which is pulse's alsa emulation).<br>><br>> Does that mean putting ALSA:pulse into the MythTV configuration?<br>
<br>Yes<br><br>><br>>> If you do want to use native pulse driver for some reason, change the pulse<br>>> server sampling rate from 44.1kHz default to 48kHz.<br>><br>> Where do I change that? In /etc/pulse/daemon.conf? <br>
<br>Yes <br><br>> Or is it better to<br>> try the solution mentioned at<br>> <a href="https://wiki.archlinux.org/index.php/PulseAudio#Glitches.2C_skips_or_crackling">https://wiki.archlinux.org/index.php/PulseAudio#Glitches.2C_skips_or_crackling</a><br>
> (or even run PulseAudio on top of Jack)?<br><br>Sounds like an awfully ugly work around... Running two sound servers on top of another?<br><br>ALSA:pulse is the solution that gives the best solution if using pulse.<br>
Otherwise changing the resampling rate does the trick.<br>