<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
Gentlemen,<br><br>Here is the shortest snippet I could write to generate the issue:<br><br><i>adc => LiSa looper => dac;<br>1::minute => looper.duration;<br>1 => looper.record;<br>100::ms => now;<br>0 => looper.record;<br>1::minute => looper.duration;</i><br><br>I get no errors specifically from ChucK (even if I put an infinite while loop in there to advance time)... ChucK will just hang out for as long as I'll let it.<br><br>However, here is the response from Jack:<br><br><i>subgraph starting at qjackctl timed out (subgraph_wait_fd=17, status = 0, state = Running, pollret = 0 revents = 0x0)<br>bad status (1) for client ChucK handling event (type = 8)<br>**** alsa_pcm: xrun of at least 0.143 msecs</i><br><br>So, it looks like an xrun. The laptop I'm using is pretty dang old... is it possible that the low amount of RAM and slower processor could be causing this?<br><br>-Matt<br><br><div><div id="SkyDrivePlaceholder"></div>> Date: Wed, 25 Apr 2012 16:11:12 +0200<br>> From: signal.automatique@gmail.com<br>> To: chuck-users@lists.cs.princeton.edu<br>> Subject: Re: [chuck-users] LiSa looping issue<br>> <br>> On Wed, Apr 25, 2012 at 09:10:59AM -0400, Matt Bard wrote:<br>> > Kas,<br>> > <br>> > Thank you for clarifying a few things. There was a definite fallacy in my<br>> > loopRec understanding. Your response cleared that up.<br>> <br>> It happens, I had something quite similar last week where I talked<br>> about "loop" in the sense of "iterate over.." and my discussion<br>> partner assumed there was some signal feedback. Such oddities in<br>> natural languages can easily throw us for a loop ;-)<br>> <br>> > <br>> > That comment made me scratch my head too after looking at it. I just botched<br>> > my comment. Everything is working just as expected there except my commenting<br>> > ability.<br>> <br>> No problem, I was just making sure because misunderstandings are easy<br>> to have.<br>> <br>> > <br>> > So, it appears that I do understand what is going on. My issue then is simply<br>> > that I cannot call .clear() appropriately (.duration was my backup which also<br>> > failed). Hopefully that will get fixed at some point, or maybe I can write a<br>> > function to clear things out myself to see<br>> > if that works. Thanks again for all your insight.<br>> <br>> Well, the easiest way of manually clearing would be to write a loop<br>> that would write a 0.0 to each valueAt() location. However, that<br>> would, as Dan pointed out, be doing *exactly* what .clear() does in<br>> LiSa's source. That doesn't seem like a solution to me, especially not<br>> as a loop in ChucK will never be as fast as one in the C++ source.<br>> <br>> It's also odd to me that you'd get a error from Jack and not ChucK. A<br>> ChucK error could happen if there would be a typo in the source, Jack<br>> only gets involved once there is a generated signal (from LiSa in this<br>> case) that made it through the UGen graph, to the output and to the<br>> sound system.<br>> <br>> Could you send the most simple example possible that will create this<br>> error for you, as well as the exact error? It may also be relevant<br>> to know whether you are using Jackd1 or Jackd2 (check in your package<br>> manager, probably Synaptic). I'd also be interested in knowing whether<br>> you are using some exceptionally small buffer size. Oh, and the exact<br>> error you get when calling .duration() as well, please. Contrary to<br>> Dan I am on Linux so I could try to reproduce this and we can<br>> -hopefully- make some guesses about what is going wrong.<br>> <br>> Yours,<br>> Kas.<br>> _______________________________________________<br>> chuck-users mailing list<br>> chuck-users@lists.cs.princeton.edu<br>> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users<br></div> </div></body>
</html>