Yes, the "play position" icon would always indicate the "play position".Gale Andrews wrote:I quite like the idea of the extra downward pointing grey "play from" position though we would want that also when there is no selection region.
In the long term I would hope that we make much more use of right click context menus, to the extent that it becomes normal to right click on things.Gale Andrews wrote:How does user enable the play speed slider and how do we make that discoverable?
In the short term there could be one of those little downward pointing triangles like we have in the Meter Toolbars.
You misunderstand my meaning.Gale Andrews wrote:It's useful though, and it would be a feature that we never had before, given 2.1.0 could only "lock the static cursor position as a play region".steve wrote:Conceptually I think it makes no sense to "lock" the "current play position" because it is transient by its nature.
It makes little sense to "lock" as in "lock up / prevent from moving / disable.
We will never agree about that. There are just too many contradictions for my poor little head to get round.Gale Andrews wrote:The case is clear to me in 2.1.0. "Lock the static cursor position as a play region" then ...
That's a neat idea that nicely works around one of the main problems in the idea.Gale Andrews wrote:One advantage of a separate Play button for Transcription Toolbar is the ease of switching between standard 1x and an already determined "transcription speed". In Steve's mockup:
I could envisage the black "1.0" being a separate Play button for that indicated speed and that the main Play button still always plays at 1x.
It looks wrong to me. If I lock a region, then it plays the locked play region, but if I make an overdub it plays a different region. What's the logic?Gale Andrews wrote:Disagree that the selection should never have anything to do with the length of the recording. The current "solution" works for me where overdub ties the recording to the selection but recording always starts from the cursor position even if overdub is off.
I'm saying that when you start the transport, it always starts from the current play position, and if there is a "play region" defined then the cursor always traverses the play region. I think that would be far preferable than having different behaviours for play, record, loop and overdub (as we have now).Gale Andrews wrote:I am not sure if you are saying that we should require setting the playback start/region or recording start/region when we simply want to play or record as we do now, but I would like the locked recording start/region to an additional but not mandatory feature.