<div class="gmail_quote">Hi<br><br>2009/3/26 Adrian Knoth <span dir="ltr"><<a href="mailto:adi@drcomp.erfurt.thur.de">adi@drcomp.erfurt.thur.de</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Wed, Mar 25, 2009 at 09:05:32PM +0100, Grammostola Rosea wrote:<br>
<br>
> The problem is an realtime kernel and a proper configuration for music<br>
> production. Without that, you better stay away from music production<br>
<br>
</div>Not really. I absolutely have no problems with CONFIG_PREEMPT, dynticks,<br>
ondemand scheduler and all this fancy stuff in a vanilla 2.6.29 running<br>
on a dualcore amd64 laptop.<br>
<br>
It's an outdated myth that you need RT kernels for audio production,<br>
though it helps with very low latencies. (let's say buffer sizes below<br>
10ms and high CPU loads)<br>
<br>
</blockquote><div><br>maybe it is worthwhile to clarify where "audio production" begins and "audio fun" ends.<br>Recording 16 tracks + monitoring could be an impossible task with your !=RT kernel.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Nevertheless, for those with highest constraints or older hardware, a RT<br>
kernel is beneficial.<br>
<br>
<br>
HTH<br>
<font color="#888888"></font></blockquote><div><br>r <br></div></div><br>