[Ardour-Users] Ardour 4.0 rc3

[Paul Davis]

Yes, most-recently-touched actually can't work because of a very simple
example: 1 long region, with 1 short region placed on top of it. Now trim
the long region. It should NOT be placed above the short region.

On Sat, Apr 11, 2015 at 11:28 AM, Niko Efthymiou <nefthy at nefthy.de> wrote:

> On 11.04.2015 16:52, Paul Davis wrote:
>
>> On Sat, Apr 11, 2015 at 10:45 AM, Paul Davis <paul at linuxaudiosystems.com>
>> wrote:
>>
>> I just checked this. As I thought, things have not changed since
>> Ardour 3.5.403, but clearly we need a more nuanced model here. Some
>> combination of most-recently-touched and later-is-higher.
>>
>
>
> I dislike the idea of changing the layering order without explicit user
> action like move layer to top/bottom/up/down, as would be the case with
> most-recently-touched. Accidentally messing up the layering can cause
> havoc, especially with overdub/punch-in scenarios, with many similar layers
> laying on top of each other.
>
> A command to restore the default order for a track would be nice thing
> though.
>
> Niko
>
> _______________________________________________
> Ardour-Users mailing list
> ardour-users at lists.ardour.org
> To unsubscribe  or change your mailing preferences please visit:
> http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ardour.org/pipermail/ardour-users-ardour.org/attachments/20150411/88f4e7e9/attachment-0001.htm>