View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007261||ardour||features||public||2017-03-04 10:04||2017-03-05 09:00|
|Summary||0007261: Unable to find "Follow Edits"|
|Description||Up to version 5.6 there was the button "Follow Edits" in the main toolbar. Now, on it's place is the button "Follow Range". |
Where can I find a button, shortcut or setting to bring back the very, very usefull feature "Follow Edits"?
|Tags||No tags attached.|
The Follow Edits function was changed slightly and renamed to Follow Range in commit 628c99d55 and was part of the 5.6 release.
Can you please explain your workflow and what parts of the Follow Edits functionality you find useful. Perhaps an alternate method can be suggested or something else can be done.
before the change that you mentioned, the playhead was moved to a point a few seconds in front of a region:
- by clicking on a region
- by moving a region
- by trimming a region
all these playhead moves are performed automatically an the user hasn't manually place the playhaed to play for controlling the edits. It avoids the clicks and "moving arround" the playhaed and saves a lot of time in production environment, for example editing a speech record or a interview.
For me, it was an very important feature, that I've not found in other DAWs...
Without thinking about this too much, it seems like you almost need a "Follow Selection" mode where the playhead also locates on object/region selection changes so that it works with all types of selections and not just range selection. I'm not sure that will help with region trimming but after playing with Follow Edits in 5.5 the behaviour seems strange to me (perhaps I hit bugs) and the playhead is moved after the region sometimes rather than to before the trim so you can hear it.
A mode where the loop range follows the selection might also be interesting.
I haven't had any problems with "Follow Edits" up to version 5.5. I don't understand, why this was dropped! In comparison to other DAWs, IMHO, this behavior was a good argument to use Ardour. Now: :-(
||I was not involved in the decision to change/redesign the functionality, I'm sorry but you will have to wait for further feedback.|
|2017-03-04 10:04||aPilger||New Issue|
|2017-03-04 10:38||timbyr||Note Added: 0019469|
|2017-03-04 10:38||timbyr||Status||new => feedback|
|2017-03-04 11:19||aPilger||Note Added: 0019471|
|2017-03-04 11:19||aPilger||Status||feedback => new|
|2017-03-04 11:21||aPilger||Note Edited: 0019471|
|2017-03-04 12:04||timbyr||Note Added: 0019473|
|2017-03-04 16:55||aPilger||Note Added: 0019477|
|2017-03-05 00:02||timbyr||Note Added: 0019479|
|2017-03-05 09:00||aPilger||Note Edited: 0019477|