[Ardour-Dev] Fwd: Re: "Click of deaf" bug

Natanael Olaiz nolaiz at gmail.com
Fri Jul 16 06:26:24 PDT 2010


> -------- Original Message --------
> Subject: 	Re: [Ardour-Dev] "Click of deaf" bug
> Date: 	Fri, 16 Jul 2010 14:38:43 +0200
> From: 	Christian Zollner <osterchrisi at gmx.at>
> To: 	Natanael Olaiz <nolaiz at gmail.com>
>
>
>
> Same happened to me a few times lately...
> I wasn't able to reproduce it in any way but I had the feeling it
> happens whenever you split a region, move the second one to another
> track without applying any changes to it and later putting it back to
> its original position.
>
>    

BTW, I remember now: in my case the regions was two different audio 
files, not splitted...


> When I have more time next week I could try to reproduce it...
>
> Best,
> chrisi
>
>
>
>
> Am Freitag, den 16.07.2010, 10:55 +0200 schrieb Natanael Olaiz:
> >  Hi,
> >
> >  We found a strange and harmful bug in Ardour, and unfortunately, it
> >  looks difficult to reproduce.
> >
> >  Description: two regions are one just after the other (so, no crossfade)
> >  makes a several hundred dBs click when the playhead pass over the
> >  intersection:http://imagebin.ca/view/LSvEnz.html
> >
> >  Some observations:
> >       - It happens even without any plugin or automation on the track
> >       - If the gain of the track is 0, it doesn't happens. If it's
> >  greater, the bug happens and it looks proportional to the track gain.
> >       - Related to the previous?: when there is a plugin applied, the
> >  gain bug is happening after the plugin process (1 mono track with 22
> >  outputs without plugin: all peaks fall -after several seconds- all
> >  together, meanwhile 1 mono track with 22 outputs with a spacialization
> >  plugin applied: the peaks fall differently because the process)
> >       - It looks to happen only when the starting region have the fade-in
> >  deactivated (no matter the state of the previous ending fade-out).
> >       - When reloading the session, it doesn't happen. But if you move
> >  the second region some times, and put it again snapped to the first one,
> >  it usually happens again each time you pass over the region intersection
> >  until you close the session again.
> >
> >  We tried to simplify the session removing all the tracks but the
> >  problematic one, and still happens. Then we tried to remove clean the
> >  unused sources and move the regions to the begining, and we could not
> >  reproduce it again...
> >
> >
> >  Any hint to debug it? Maybe a NaN in the fade-in algorithm?
> >
> >
> >  Thanks in advance.
> >
> >  Best regards,
> >  Natanael.
> >
> >  _______________________________________________
> >  ardour-dev mailing list
> >  ardour-dev at lists.ardour.org
> >  http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org
>
> _______________________________
>
> http://www.zaunerelektronik.net
> _______________________________
>
>
>    

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ardour.org/pipermail/ardour-dev-ardour.org/attachments/20100716/2915b76a/attachment-0002.htm>


More information about the Ardour-Dev mailing list