[ardour-users] Fade creates new file and leaves the old

[Brett McCoy]

Matthew Polashek wrote:

> OK, this is very helpful.  I understand this, though I didn't have a chance to
> get through the manual yet.  Now, it seems to me that the layered "takes" (even
> though they aren't new takes when I am just making new fades) should move along
> with the top layer by default.  Does that make sense?

I don't think they do... each layer stays independent of the others. You 
can select multiple layers, I think, if they overlap and move them 
together. This layered concept is how punches are done -- when you do a 
punch in and out, it creates a region in a layer above the previous 
take, with the start and end of the punch region inside the ends of the 
lower region. If you take a look at the manual page I listed, it 
describes the difference between how "internal" fades are done as 
opposed to external ones (based on where the ends of the regions are).

> Matt
> 
> 
>>Message: 6
>>Date: Tue, 17 Jan 2006 15:40:13 -0500
>>From: Brett McCoy idragosani at chapelperilous.net>
>>Subject: Re: [ardour-users] Fade creates new file and leaves the old
>>	one?
>>To: ardour-users at lists.ardour.org
>>Message-ID: 43CD562D.6050001 at chapelperilous.net>
>>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>>Matthew Polashek wrote:
>>
>>>I end up with 10 files sitting in my track, as I tweak a fade, then when I move
>>>the soundbyte forward or back, I have to go and delete all the previous versions.
>>>Maybe I need to spend some time with the manual or something.
>>
>>I think you are confusing regions in the playlist with files (they 
>>aren't the same, you can have many regions that actualyl come from a 
>>single file). Each time you record something on a track, it becomes a 
>>region, and each subsequent one gets placed over top the previous, so 
>>you have layered 'takes' (if you have ever used the Gimp or Photoshop 
>>and used the layers tool, it is kinda like that). Only the topmost 
>>region is 'active' when you audition the track. When two regions 
>>overlap, a crossfade is automatically created between the two.
>>
>>More info here:
>>
>>http://www.ardour.org/manual/editing:crossfades
>>
>>
>>>Matthew Polashek
>>>matt at tinysongs.com
>>>www.tinysongs.com
>>>
>>>On Tue, 17 Jan 2006 15:25 , Paul Davis paul at linuxaudiosystems.com> sent:
>>>
>>>
>>>
>>>>On Tue, 2006-01-17 at 12:05 +0000, Matthew Polashek wrote:
>>>>
>>>>
>>>>>Hi!
>>>>>
>>>>>When I make a fade Ardour seems to create a new audio file and leave the old one
>>>>>beneath it.  I'm sure there's a simple setting or something I have to change to
>>>>>make this stop but I haven't figured it out yet.  Can anyone help me
>>>
>>>understand this?
>>>
>>>
>>>>it creates a new object called a Crossfade, which reads and mixes data
>>>
>>>>from the two regions involved in the fade. no new files are created.
>>>
>>>
>>>>why do you want to stop it? 
>>>>how do you imagine crossfades working differently?
>>>>
>>>>--p
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>_______________________________________________
>>>ardour-users mailing list
>>>ardour-users at lists.ardour.org
>>>http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org
>>
>>
>>-- 
>>------------------------------------
>>Programmer by day, Guitarist by Night
>>http://www.chapelperilous.net
>>http://www.alhazred.com
>>http://www.cassandrasyndrome.com
>>
>>
>>------------------------------
> 
> 
> 
> 
> _______________________________________________
> ardour-users mailing list
> ardour-users at lists.ardour.org
> http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org


-- 
------------------------------------
Programmer by day, Guitarist by Night
http://www.chapelperilous.net
http://www.alhazred.com
http://www.cassandrasyndrome.com