Re: Jamin issue?
Steve Harris <[email protected]>
| Newsgroups | gmane.comp.audio.jamin.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Nov 17, 2005 at 04:14:17PM -0500, Jesse Chappell wrote: > On 11/17/05, Sampo Savolainen <[email protected]> wrote: > > Hi > > > > Today I finished a mix and mastered the session with Jamin. Jamin was > > used as an insert in ardours' master bus. > > > > After exporting I noticed that there was a strange anomaly in the > > exported audio. I restarted ardour & jamin and started investigating. It > > seems that about 10-20% of the time the anomaly happened and the rest of > > the time it sounded fine. > > Sampo told me on IRC the periodsize he used was 128 here. OK, thats probably the problem, Jamin has to use a worker thread when the period size is below 256 samples (IIRC), if theres a lot of RT pressure then it will miss deadlines. I guess we could add a option to bypass the thread, but its liklt to cause xruns. > I've been meaning to post here because I believe Jamin is broken when > freewheeling using the separate DSP thread mode of operation. I > haven't scoured the code yet, but other people have run into the issue > during ardour exports through Jamin. The glitches don't occur at > large period sizes when jamin does the DSP in the audio thread. > > JACK freewheeling state is a special case which clients should > recognize and alter their behavior if necessary. Of course most > clients don't need to, but tricky ones like jamin just might. Yes, I guess jamin's 2nd thread doesn't get to run. - Steve ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click