Bug 1489 – Stray ticks in Timeline after stopping Scrub Mode with Scrub Bar open

••• Introduction •••
••• Keywords •••

Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla

Bug 1489 - Stray ticks in Timeline after stopping Scrub Mode with Scrub Bar open


Summary:	Stray ticks in Timeline after stopping Scrub Mode with Scrub Bar open

Status:	CLOSED WORKSFORME

Product:	Audacity
Classification:	Unclassified
Component:	Audio IO
Version:	2.1.3
Hardware:	Per OS All

Importance:	P5 RepeatableAll
Assigned To:	Default Assignee for New Bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-08-20 13:42 UTC by Gale Andrews
Modified:	2019-06-08 11:31 UTC (History)
CC List:	3 users (show)

See Also:
Steps To Reproduce:	A1 Launch Audacity without audacity.cfg present A2 Without adding audio, click in Scrub Bar then ESC or otherwise stop playback. A tick appears in the timeline where the playhead was. A3 Drag in the Scrub Bar then ESC. New ticks appear in the Timeline at the start and end of the drag. They disappear when the Timeline is refreshed. B1 Launch Audacity without audacity.cfg present B2 Add some audio and start scrub or seek by any method and stop Scrub Mode by any method. A tick appears subliminally in the Timeline before disappearing. Does not seem to happen if Scrub Bar is off.
Release Note:
First Git SHA:
Group:	---
Workaround:
Closed:	2019-06-08 00:00:00

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Gale Andrews 2016-08-20 13:42:28 UTC

Did not happen until recently, I believe. Observed on Windows 10 and El Capitan (HEAD at time of reporting) and Ubuntu (built 18Aug16, "8b90a8f").  

Not observed at "b27504e" 04Aug16 on Windows 10.

Comment 1 James Crook 2017-08-16 11:48:25 UTC

A1-A3 work for me fine, since playback does not start.

B1-B2, About half the time I do get two little marks just above where the play cursor was, either side of where it was, for a moment, when playback stops.

Comment 2 Peter Sampson 2019-06-08 11:31:02 UTC

I cannot reproduce thus behavior at all on 2.3.3 alpha on W10 or on macOS 10.14.5