Might be a bit of a curly question this one.<br><br>Currently, most of my templates for LS and RG are setup with alsamidi.<br>I&#39;ve started converting the LS ones to jackmidi, and i&#39;m starting to use it more and more.<br>
<br>My question is:<br><br>With alsa 1.0.19, i have hpet timing. (and i don&#39;t know enough about this, to know if it&#39;s been there for a version or two.)<br><br>Nearly all my linux experience has been with the RTC timer, for better or worse, and frankly, i have little idea which is better, save the conversations we&#39;ve had here from time to time.<br>
<br>So, what does Jack use?<br><br>I understand alsa sits in my kernel, and communicates with my hardware. Given that, it&#39;s using hpet as the timer, and i assume here, that means it&#39;s timing midi for me as well.<br>
There&#39;s also some sort of rtc emulation in this version (from the little info i&#39;ve been able to glean.)<br><br>Is there a benefit, timing and stability wise, in using jackmidi for as much as possible, with the a2jmidid bridge to capture older apps using alsa, given the rapid development we&#39;ve seen over the past 12 months in many corners of our little niche community.<br>
<br>Is it time to consider this, as a serious alternative to alsa midi, and what sorts of pros and cons do we face?<br><br>I&#39;m using a lot of ports, and driven fairly serious chunks of midi data, for my orchestral nonsense, so this is quite important looking ahead. (imho)<br>
<br>Some insight into this would be appreciated.<br><br>Alex.<br>-- <br>Parchment Studios (It started as a joke...)<br>