I think it depends on what kind of audio work you are facing to.<br><br>5.3 ms latency is not good if you do monitoring from software, so for non-prof use almost everyone can live with 5.3ms latency.<br><br>But recording a vocal track could be a little drama, because latencies > 5ms are really audible and from the headphones/monitor it sounds like singing within an empty barrel of oil.<br>
<br>cheers<br>r<br><br><br><br><div class="gmail_quote">2009/1/27 Peder Hedlund <span dir="ltr"><<a href="mailto:peder@musikhuset.org">peder@musikhuset.org</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;">
Quoting Ken Restivo <<a href="mailto:ken@restivo.org">ken@restivo.org</a>>:<br>
<br>
> And here is the next installment in the saga of trying to get Ingo<br>
> RT going on my Asus EEE.<br>
><br>
> I successfully built and ran the 2.6.26.8-rt12 with the alsa_seq<br>
> patch. It ran.<br>
><br>
> The problem is that neither the Ethernet (atl1e) or wireless<br>
> (rt2860sta) work. So I pretty much had to reboot back out of it<br>
> immediately.<br>
<br>
I've been running the standard kernel from openSUSE 11.0 on my Athlon<br>
2000+ and can get down to at least 5.3ms latency on an Audiophile 2496<br>
using the limits.conf "trick".<br>
<br>
Do people really need lower latencies for music purposes or are we<br>
just thinking "well, I needed the RT patch three years ago; I ain't<br>
stopping now" ?<br>
<br>
- Peder</blockquote></div><br>