Ted Felix <t...@tedfelix.com> writes: > PREEMPT_DYNAMIC is something new. It doesn't guarantee you are > running a preemptible kernel. It allows for turning on PREEMPT via the > kernel command line parameters (preempt=full). > > This post seems helpful: > > https://cm-mail.stanford.edu/pipermail/planetccrma/2021-November/018882.html > it is helpful though i'm not sure what is happening at my end.
running timidity.service play something on rg i get crackles and pops (more for some items than others) so i put preempt=full at bottom of /etc/defaults/grub do sudo grub-mkconfig -o /boot/grub/grub.cfg reboot sudo dmesg | grep -i preempt Dynamic Preempt: full play things on rg - perfectly! no issues with timidity running. then i comment out the preempt=full line do sudo grub-mkconfig -o /boot/grub/grub.cfg reboot sudo dmesg | grep -i preempt Dynamic Preempt: full huh?! shouldn't commenting it out give me something other than "full"? BUT when i play, i get the same crackles and pops, so no lowlatency? so i don't understand what i'm actually running from the dmesg, but it seems clear that when i have the preempt=full (in /etc/defaults/grub things work perfectly even with timidity, so presumably lowlatency is actually on. i'm going to be using yoshimi anyway instead of timidity and things worked perfectly with it (without the preempt=full line). however, i'm glad i followed these instructions to activate the lowlatency, though it seems to me that dmesg is thinking preempt=full even when i comment it out and the crackles and pops suggest that i'm not running lowlatency. i would like to know what the point of the dmesg "full" is, but for practical purposes i do seem to have control over the quality. in any case, thx for your help ted. -- In friendship, prad _______________________________________________ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
