As someone who uses a screen reader with Audacity and all other
computer apps, I appreciate making Audacity more keyboard-command
friendly. I like your idea of being able to slow down and speed up
audio playback. Especially if this could be integrated with ability
to set start and end markers using the keyboard. And made so that
those markers cannot be disturbed except with _deliberate_
reassignment of the marker positions.
On Wed, 15 Dec 2004, Shane Mueller wrote:
> One thing that often happens when you are transcribing recorded sound is
> that it never plays at the speed you want it to. It is either too fast
> (i.e., dictated speech), or too slow (searching for a single quote in a
> 50-min lecture).
> I have added a slider and a button to the transcription toolbar on CVS
> head that allows you to playback at a set speed. This is still
> experimental, and I encourage people to make any changes they wish and
> figure out ways to improve it. I don't know if having a separate
> 'play-at-speed' play button is the best idea; maybe it should route
> through the normal play button. This just speeds up playback, like if
> you were slowing down/speeding up a cassette tape. It is not really
> hooked in to the whole control toolbar logic right now, and so may cause
> problems in various ways, and may not work perfectly with
> It works by making an invisible time track whose values get set by the
> slider. It gets passed into the whole audioIO machinery that deals with
> timetrack shifting. Currently, the start/stop times are correct, but
> the cursor doesn't get warped correctly--I would have to make the time
> track accessible to the trackpanel in some way for this to work out.
> Here are some of the notes on the changes:
> * ASliders can now take on the different lwslider forms (new
> constructor), and there is a new slider style: SPEED_SLIDER, which goes
> from 0 to 5 continuously.
> * I #ifdef'ed out that pragma warning in Track.h that was causing a
> thousand warning messages during compile time on linux. #pragma is
> supposed to be compiler-specific, so it should probably be our practice
> to make sure they only get used by the compiler they are intended for.
> But, they were not documented, so I'm not sure why they were in there or
> what they were for.
> * The MakeButton function in ToolBar overlayed an image onto a button,
> with a specified offset adjustment. For boring but necessary reasons, I
> changed the logic so that it automatically centers the icon on the
> button, and then adjusts from there using the old offset parameters,
> which can get set to 0 (or +/- 1 if you want to monkey with things). I
> think I fixed everything that was affected, but things may look strange
> on the Mac or something, and could need tweaking.
> * It would be nice for sliders to have a manual value entry dialog
> available via double-click or ctrl-click or something.
> * It would also be cool to have a log-scale slider.
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> Audacity-devel mailing list