<br><br><div><span class="gmail_quote">On 3/23/07, <b class="gmail_sendername">Lee Revell</b> <<a href="mailto:rlrevell@joe-job.com">rlrevell@joe-job.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 3/23/07, michael noble <<a href="mailto:looplog@gmail.com">looplog@gmail.com</a>> wrote:<br>> I know that Studio to Go 2 beta allows you to do this at the expense of<br>> processor overhead. I haven't tried this as far as timing issues are
<br>> concerned, but it certainly is possible and with a nice GUI based<br>> configuration wizard.<br>><br><br></blockquote></div><br>that was also my assumption at first but I'll quote Chris Cannam on this one
<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">The multiple card support needs some qualification. It is really intended for attaching stereo I/O (and limited quality) consumer-type soundcards as occasional-use JACK inputs or outputs; it isn't appropriate for multiple large I/O clock-synchronised cards, for which a specialised ALSA multi-card device still has to be set up...
</blockquote><div><br>So it may or may not be what the original poster wanted. Just thought I'd share, is all... <br></div><br><br>-- <br>networking practice for sound environments :: <a href="http://nowhere.iamnobody.net">
http://nowhere.iamnobody.net</a>