[ardour-dev] export problems - testers requested

David Mulcahy eseol at tiscali.co.uk
Sat Apr 30 13:56:38 PDT 2005

On Saturday 30 April 2005 18:54, Paul Davis wrote:
> Problems with export are one of just two remaining items preventing
> the release of ardour 0.99. Reports to the mailing list/mantis/#ardour
> seem inconclusive at present. One user who was having crashes every
> time he tried to downsample from 48kHz -> 44.1kHz reports that
> updating his system fixed the problem. Other reports are confusing, or
> anecdotal.
> I would really appreciate it if as many as people as possible could
> try exports on sessions longer than, say, 5 minutes, with and without
> down and upsampling. These tests should be run with JACK in realtime
> and non-realtime mode, and you should note which version of JACK you
> are using. Also report which version of glibc you have, like this:

Firstly it only happens at samplerate conversion for me 44.1 -> 48 (eg I 
record at 44.1 and resample to 48 - both 16 bit)
and at a low period size 128 (2048 is fine).  The following error poped up but 
not always
*** glibc detected *** free(): invalid pointer: 0xb3727128 ***
in fact pretty sure ardour pops up something about glibc in its error window 
before it shutsdown)
I will give you more details later but i think it is pretty easily to 
reproduce once you now how - and it pretty much brings down jack and ardour.

I reported this earlier (on the jacck list) - my system has changed a lot 
(different libc and jack) but i can still reproduce it.


More information about the Ardour-Dev mailing list