[Ardour-Users] IMPORTANT cross-fade changes in Ardour 3 svn

Dragan Noveski perodog at gmx.net
Mon Apr 16 10:45:13 PDT 2012

On 16.04.2012 19:41, Jörn Nettingsmeier wrote:
> On 04/16/2012 07:24 PM, Paul Davis wrote:
>> On Mon, Apr 16, 2012 at 1:20 PM, Dragan Noveski<perodog at gmx.net>  wrote:
>>> yes, the same here. i also spoke to harrison, but i still do not get 
>>> the
>>> point what might be better now. perhaps it is gonna be documented 
>>> somewhere
>>> or there is  a cool youtube video of how to handle x-fades now.
>> it doesn't offer new functionality. instead it:
>>     (a) reduces by 1 the number of different things that can
>> potentially affect the gain applied to a sample
>>     (b) removes a huge chunk of complex code from the code base
>> we view these both as improvements. there may be some issues to work
>> out with respect to the ability to do really arbitrary fades, but they
>> will get worked out over time, and without the complexity that the
>> former Crossfade object added to the code.
> hmmm. if i let two regions overlap, i would expect them to crossfade 
> at constant loudness. the crossfade object seemed to do that. now if 
> the region fade-ins and fade-outs are used instead, will they be 
> adjusted automatically, so that just overlapping two regions will give 
> a meaningful result? that's quite important.
> at the same time, will i be able to edit them? crossfade edits again 
> should maintain constant loudness and only deviate from this ideal at 
> the explicit request of the user, if at all.
> i don't quite understand if the new approach can do that...
> yay for reducing code complexity, but boo hiss for having to manually 
> tweak two independent fades for each edit and probably getting them 
> wrong.
that is how i see it working atm.


More information about the Ardour-Users mailing list