View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0007714ardourbugspublic2018-12-26 21:292021-12-15 11:34
Reporterunfa Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
PlatformPCOSLinux MintOS Version18.3 KDE5
Product Version5.12 
Summary0007714: Ripple Edit Mode doesn't consider track groups
DescriptionI'd expect the Ripple Edit Mode to shift around all regions on all tracks together, or at least do so with respect to the Track Groups - unfortunately that's not the case.

It'll work great, but only in the scope of a single track - so as soon I have regions on multiple tracks - any editing done in the Ripple Edit Mode will break their relative sync, so it's not making anything easier, like I'd hoped it would.

Or maybe I'm just missing something?
TagsNo tags attached.

Activities

bachstudies

2020-12-23 19:25

reporter   ~0025349

I think grouped ripple editing only works if the starts of regions are exactly aligned i.e. immediately after import or after making a cut. I would really appreciate a multi-track ripple edit mode as in Samplitude and Reaper with any markers automatically moved along with the regions.

Blindekinder

2021-12-15 11:34

reporter   ~0026275

It could be critical for some use. For example:
Editing a piece with >30 people speaking, one track for each. We are working with hundredths of regions since the interventions are all mixed. When we want to insert a region, we have to Select All after edit point (ctrl+shft+E), and move all together. If by accident one moves a fade or resize a region without unselecting, ALL regions will be affected.

Moving all region in all tracks after edit point in ripple mode edit is more secure and no need to make selection before moving.

Issue History

Date Modified Username Field Change
2018-12-26 21:29 unfa New Issue
2020-12-23 19:25 bachstudies Note Added: 0025349
2021-12-15 11:34 Blindekinder Note Added: 0026275