> >- is there an api function, that tells jack not to kick the > >application > > absolutely not. if you miss RT deadlines for your process() callback > (or more precisely, if JACK believes you did) it has no choice but to > evict you from the graph. if you are left in the graph, the chances > are that you will just do it again. the only except is if the user > specified on the command line that they did not want this behaviour > (e.g. for live work where an xrun is better than a client being > kicked). but its definitely not up to the client. hm ... the application is basically not rt-safe at all ... fixing this should be possible, but that's a more general problem ...
> >or a callback that tells the application that it has been kicked out? > register a shutdown callback, and you'll find out about it. thanks ... i'll try this ... > >- is it possible to query the time out so that i can adapt the > >callback that it finished before this time out? > > you know how many frames you have to process and you know the sample > rate. but you have no idea how many other clients are running, so you > don't know how much time *you* actually have. you just have to adhere > to the basic rule: > > number of cycles = (A * number of frames) + C > > where A and C are constant. i see ... i'll do this manually ... thanks a lot ... tim -- mailto:[EMAIL PROTECTED] ICQ: 96771783 http://www.mokabar.tk latest mp3: kMW.mp3 http://mattin.org/mp3.html latest cd: Goh Lee Kwang & Tim Blechmann: Drone http://www.geocities.com/gohleekwangtimblechmannduo/ After one look at this planet any visitor from outer space would say "I want to see the manager." William S. Burroughs
