From Audacity Wiki
|Proposal pages help us get from feature requests into actual plans. This proposal page is about making the play at speed slider real-time and stretchy.|
Proposal pages are used on an ongoing basis by the Audacity development team and are open to edits from visitors to the wiki. They are a good way to get community feedback on a proposal.
- Note: Proposals for Google Summer of Code projects are significantly different in structure, are submitted via Google's web app and may or may not have a corresponding proposal page.
bug 133 is an enhancement request for this and has more details.
- Play at speed only plays at the speed set when play at speed was started.
- It is difficult to precisely set a play speed.
- Integrate play at speed with the scrubbing code, so that the slider can control the play speed in real time.
- Make the play at speed control resizable (like meter toolbars) so that greater precision in setting the speed is easy/possible.
- What is the purpose of the feature? - More controllable play-at-speed
- What are the relative importances of the different features in it? (this is used to justify having a large button, a small button or just a menu item, for example) - The feature uses the same real estate and/or gives the user the option of giving the slider more/less real estate that they previously could not do.
- Does the feature have modes, and if so how easy are the modes to get out of? (stuck in a mode) - No.
- Does the feature have invalid states that can be greyed out? - No change from previous play at speed.
- What is the factorisation of the feature? (e.g. pin/unpin can operate on its own, independent of scrub/seek). - Resizing and real time are separate factors.
- What are the justifications for 'novelty' in the design? (e.g. RSI free operation, lack-of-precision in conventional sliders). - Resizability gives greater precision
- Is VI use integral? (e.g. labels added a label editor dialog, essential for VI, useful for non ). - VI users will probably use the numerical controls.
- James Crook
- We should consider having an easy click-stop at x1, x2 and x3.