Re: Maolan 0.0.3

Robin Gareus <[email protected]> Thu, 19 Mar 2026 16:41:30 +0100

Newsgroups	gmane.linux.audio.users
Message-ID	<[email protected]>

On 2026-03-19 4:08 PM, Goran Mekić wrote:
> On 3/19/26 1:10 PM, Fons Adriaensen wrote:
>> On Thu, Mar 19, 2026 at 09:32:24PM +1100, Roger wrote:
>>
>>>> I've never heard of this before, I'll have to think about it, but it
>>>> definitely sounds like a good idea.
>> I've wanted this once, when mxing the sound for a 90 min video
>> documentary. It consisted of hundreds of short regions, and most
>> of them needed some specific processing. Managed it by separating
>> them over multiple tracks, each one requiring more or less the
>> same effect(s), and combining this with automation.
> 
> I see how it can be useful, but I have a question how merging of clips 
> should be handled? Clip split can just keep the same FX on splitted 
> clips, but merge can be between clips with some or none FX that are 
> common, and even if there are common FX the settings is probably 
> different. I see multiple ways to handle it:
> 
> - forbid merging if one of the clips has FX
> - use the FX of the first clip
> - put FX of all clips into a series (or parallel)


In Ardour "merging" is called "combining" (and we call "clips" regions).

A region compound is just meta-data containing two or more regions. Each 
retain their FX (and you can later un-combine as well). One can also 
nest compounds.

However, if you apply region FX to a compound region, they are lost when 
uncombining.

Alternatively one can bounce regions or a timeline range to a new 
region, hard applying the FX.

--
robin

OpenPGP_signature.asc (application/pgp-signature, 840 B)