search for: im_jack

Displaying 4 results from an estimated 4 matches for "im_jack".

2004 Oct 31
2
Re: ices-kh dropping jack ports unexpectedly
...t; I've been testing this some more and the ices logs are showing a > ringbuffer full error at the time the port drops. I looked through the > source and the 'sleep time' parameter seems to have something to do with > setting the ring buffer size. I've tried recompiling the im_jack module > with the line: > > rb_size=(size_t)((s->sleep / 2000.0 ) * ...... > > changed to ... s->sleep / 1000.0 > > I'm running another test at the moment, but it would be good to know > whether this is actually likely to help, and if it's going to have any...
2004 Oct 31
0
Re: ices-kh dropping jack ports unexpectedly
...ngs up this way. I've been testing this some more and the ices logs are showing a ringbuffer full error at the time the port drops. I looked through the source and the 'sleep time' parameter seems to have something to do with setting the ring buffer size. I've tried recompiling the im_jack module with the line: rb_size=(size_t)((s->sleep / 2000.0 ) * ...... changed to ... s->sleep / 1000.0 I'm running another test at the moment, but it would be good to know whether this is actually likely to help, and if it's going to have any other effects on the way ices works (apa...
2004 Nov 01
0
Re: ices-kh dropping jack ports unexpectedly
...ices jack client which ports it should > connect to on startup, and then have it > reconnect itself when it makes the new port? If you have any idea why ices > is more sensitive to xruns than the other jack programs I'm using, that > would be a help as well. If you have updated the im_jack file as I said privately (from svn) then a sizing bug is fixed. Whether that will resolve the problem is hard to say as I've had little feedback. >From the sound of it the problem is either this sizing bug (may be it's above a maximum tolerance for you) or a scheduling one. > I'...
2004 Oct 18
9
ices-kh dropping jack ports unexpectedly
I've been having a problem where ices-kh (the jack'ified version) disconnects from its jack input source unexpectedly. This happens mainly while other jack clients are being started/stopped, or connected/disconnected, but also at other times (e.g. switching between different X sessions). I'm planning to do a bit more work on tuning up the jack setup to see if I can get rid of the