Audacity Bug Summary
••• Introduction •••
••• Keywords •••
    Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla



Bug 1392 - With cut preview, playhead can be seen running over the TQP & Scrub buttons
With cut preview, playhead can be seen running over the TQP & Scrub buttons
Status: RESOLVED FIXED
Product: Audacity
Classification: Unclassified
Component: Audio IO
2.1.3
Per OS All
: P4 RepeatableAll
Assigned To: Default Assignee for New Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-05-18 05:19 UTC by Peter Sampson
Modified: 2018-08-20 11:45 UTC (History)
6 users (show)

See Also:
Steps To Reproduce:
1) Creat 2.5 seconds of audio 2) zoom to fit 3) select from 0.5 to 1.0 seconds 4) Play cut preview ( Ctrl/Cmd + Play) 5) Playhead runs over TQP/Scrub buttons and play line runs over the Track Control Panel (see attachment)
Release Note:
First Git SHA:
Group: ---
Workaround:
Closed: 2018-08-20 00:00:00
petersampsonaudacity: Regression+
petersampsonaudacity: Test‑OK‑Win+
petersampsonaudacity: Test‑OK‑Mac+


Attachments
Playhead on buttons and playline on TCP (31.80 KB, image/png)
2016-05-18 05:19 UTC, Peter Sampson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Sampson 2016-05-18 05:19:34 UTC
Created attachment 671 [details]
Playhead on buttons and playline on TCP

With cut preview  playhead can be seen running over the TQP & Scrub buttons and the dark green playline that runs over the waveform also now can run over the Track Control Panel (see attached screenshot).

This is marked as a regression because although we did not have the new buttons these would not appear to be the cause.  In 2.1.2 the green playhead and playline do not appear until time=o, so no green line running over the TCP and no playhead displayed in the part of the timeline above the TCP.

This could probably be more properly viewed as a fault with Play Cut Preview, rather than a display issue as described, because clearly in my steps to reproduce there is only half a second of audio before the potential Cut.  But "Cut Preview>Preview before cut region" is the default 2 seconds - so Audacity is trying to play 1.5 seconds of non-existent audio before getting to where the audio really starts.

Same behavior on W10 and Mac El Capitan
Comment 2 Peter Sampson 2016-05-19 10:57:09 UTC
Testin on Mac El Capitan 19May16 nightly 6acbOf9

Audacity still plays the null audio - but the playhead and playline do not run over the Track Control panel - but only appear once just past there.

Looks ok on Mac
Comment 3 Paul L 2016-05-20 13:36:51 UTC
Playing null audio -- that is not the regression from 2.1.2 I think.
Comment 4 Gale Andrews 2016-05-20 19:21:17 UTC
Tests OK for me on Windows 10 and Ubuntu 14.04 with Quick-Play Cut Preview and Play-at-Speed Cut Preview as well as Play Cut Preview. 

The one question I have is when scroll left of zero is enabled and Cut Preview plays visible audio behind zero. In recent builds before this fix, such play before zero displayed the standard green line in the waveform with playhead in the Timeline. To me this was an improvement over 2.1.2 release where we showed a headless green line when playing before zero. 

But now, there is no waveform or Timeline indication of playing visible audio behind zero. Should that not be re-enabled while still fixing this bug?
Comment 5 Paul L 2016-05-20 19:34:35 UTC
I suggest Gale reopen this as a P4 to correct that.
Comment 6 Gale Andrews 2016-05-21 14:01:48 UTC
(In reply to Paul L from comment #5)
reopened as suggested. 

Fix is suboptimal because when scroll left of zero is enabled and Cut Preview plays visible audio behind zero, there is no waveform or Timeline indication of playback.
Comment 7 Peter Sampson 2018-01-25 13:15:22 UTC
I cannot reproduce the Steps behaviors in the latest 2.2.2 alphas on W10 or on macOS 10.13.2

Behaviors look totally as expected (and as documented in the Manual) both without the enable scroll left of zero.

I do not observe Gale's "sub-optimal" behaviors.

Accordingly I shall close this bug as resolved