0000654: Loop/punch range vs. range selection

ID	Project	Category	View Status	Date Submitted	Last Update

0000654	ardour	features	public	2004-07-29 18:02	2013-03-17 15:40

Reporter	kme	Assigned To
Priority	urgent	Severity	feature	Reproducibility	N/A
Status	closed	Resolution	no change required

Summary	0000654: Loop/punch range vs. range selection
Description	beta18.4 (PlanetCCRMA) With the recent addition of loop/punch ranges (very, very nice!), I'm wondering why ordinary range selection (as with the "Range" cursor) doesn't work the same way...using the same code? IMHO range selection should be across all tracks by default anyway, allowing users to CTL-select/de-select tracks as desired. In fact, why differentiate range types at all (with the mini-submenu which appears for "loop/punch", or otherwise)? Why does ardour need to know/care what the user plans to do with the range selection? - if loop play is toggled, the range loops - if "punch-in" or record is armed, the range is recorded/punched into - and if desired, the user can delete, copy, create chunks, or simply play the selected range (sans looping!), etc. Range markers can still appear but would simply have more generic labels (range1, range2, etc).
Tags	No tags attached.

Date Modified	Username	Field	Change
2004-07-29 18:02	kme	New Issue
2013-03-17 15:40	naptastic	Note Added: 0014741
2013-03-17 15:40	naptastic	Status	new => closed
2013-03-17 15:40	naptastic	Resolution	open => no change required

naptastic 2013-03-17 15:40 reporter ~0014741	The current setup accommodates the widest number of use cases. For example, if you want to repeatedly record a range and have pre-roll, you would set a separate loop and punch range. Range selection is orthogonal to track selection.