duplication ofset with multiple regions

[mtingle]

to understand what's happening try the following:

-turn snap to beats
-put a (longish) region starting on a beat
-turn snap off
-slice the region in a few random places not on the beat
-turn snap on

This is to simulate the kind of situations that happen relatively frequently for me. now:

-select all those sliced regions
-press the duplicate button

see how those regions that where 'on' the beat stay aligned while those sliced regions have not kept their relative positions.

I'm not saying this is a 'bug' but my suggestion would be that only the 1st region in a bunch of selected regions that where duplicated would align to the snapped value and all the other regions after would keep their relative positions to the 1st region.

Make sense?

[Rim]

This has been fixed for 1.09. The problem had to do with plugins. If you have any plugins in your project which have any latency, this latency was being added to the joined track in the form of silence at the start of the region (even if the plugins were not on that particular track).

Rim

[mtingle]

Hi Rim,

This is not to do with the join regions function, I did see that post referring to plugins not accounting for latency. This is to do with the duplicate function.

If you check out my example I think you'll see what I'm referring to.

Cheers,

Mike

[Rim]

Oops, sorry, I just re-read your post and I understand now. Yes, you're right. Your solution is a better one. I'll see if I can change this.

Thanks,
Rim