Re: ardour export + jamin

On Wed, 2010-01-13 at 21:51 +0100, Kees van Veen wrote:
> Jack,
> 
> Can't get it to abort when the Jack period is 256. Tried it several 
> times without aborting. My .jackdrc then was: /usr/bin/jackd -R -dalsa 
> -dhw:0 -r44100 -p256 -n2
> 
> As soon as I changed my jack settings to 64 frames: /usr/bin/jackd -R 
> -dalsa -dhw:0 -r44100 -p64 -n4, Jamin aborted at the end of the first 
> export I tried.
> 
> I've attached the gdb.log with the content you asked. Kernel: Linux 
> 2.6.31-9-rt #152-Ubuntu SMP PREEMPT RT Thu Oct 15 05:01:14 UTC 2009 i686 
> GNU/Linux. All packages from the Ubuntu Karmic standard repos.
> 
> Changing the jack settings to 128 frames: /usr/bin/jackd -R -dalsa 
> -dhw:0 -r44100 -p128 -n2, did not show the abort either, tried it 
> several times in a row.
> 
> As soon as I changed it back to 64 as above, trouble started again.
> 
> I'm very curious about the magical 256/128 ...
> 

    There seems to be a lot of misunderstanding about when you need low
latency.  If you're not running live or trying to record new tracks
while using software monitoring you don't really need low latency.
JAMin wasn't designed for live work and it wasn't designed to be a
plugin for a single track.  It was designed for stereo audio mastering.
The amount of processing involved is significant so it probably won't be
able to keep up with small period sizes.  Just kick it up to 2048 and
relax ;-)


> If you need more info, or want me to try other things, let me know.
> 
> Regards,
> Kees
> 
> -------- Original Message --------
> Subject: Re: [Jamin] ardour export + jamin
> From: Jack O'Quin <[email protected]>
> To: Kees van Veen <[email protected]>
> Date: Wed Jan 13 2010 17:53:55 GMT+0100 (CET)
> > On Wed, Jan 13, 2010 at 10:32 AM, Jack O'Quin <[email protected]> wrote:
> >   
> >> On Wed, Jan 13, 2010 at 2:40 AM, Kees van Veen <[email protected]> wrote:
> >>     
> >
> >   
> >> If you can reproduce this error, please configure your system to take
> >> a core dump (ulimit -c unlimited), trigger the failure, then print the
> >> gdb stack traceback for all the jamin threads:
> >>
> >> gdb> thread all apply bt
> >>
> >> Then, please send the output to this list, along with your JACK
> >> parameters (period, etc) and any other interesting facts you can think
> >> of.
> >>     
> >
> > Kees,
> >
> > I just read the long thread about this from the Ardour site.  The
> > process thread aborts exactly where I expected from your description.
> > But, I'd still like to know where the other threads were at that time.
> >
> > Is your JACK period less than 256 frames?  What happens if you use a
> > larger frame size (at least 256)?  Does the problem go away then?
> >
> > Depending on what we discover, I may ask you to try some different patches.
> >
> > Regards,
> >   
> 
> 
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev 
> _______________________________________________ Jamin-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jamin-devel


------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev