Bug 2154 – selected audio: timeline and track show different selected time range

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

Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla

Bug 2154 - selected audio: timeline and track show different selected time range


Summary:	selected audio: timeline and track show different selected time range

Status:	RESOLVED QUICKFIXED

Product:	Audacity
Classification:	Unclassified
Component:	User Interface
Version:	2.3.3
Hardware:	Per OS Windows 10

Importance:	P4 MoonPhase
Assigned To:	Default Assignee for New Bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2019-07-15 06:03 UTC by David Bailes
Modified:	2019-07-17 05:01 UTC (History)
CC List:	7 users (show)

See Also:
Steps To Reproduce:	1. create several audio tracks, for example 8. 2. select some audio is a track using the mouse. 3. Repeat this several times. 4. Observe: Occasionally, the selected time ranges shown in the track and the Timeline are not the same (the Timeline is correct.)
Release Note:
First Git SHA:
Group:	---
Workaround:
Closed:	2019-07-17 00:00:00

Attachments
timeline and track show different selected time range (4.64 KB, image/png) 2019-07-15 06:03 UTC, David Bailes	Details
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 David Bailes 2019-07-15 06:03:33 UTC

Created attachment 837 [details]
timeline and track show different selected time range

Comment 1 David Bailes 2019-07-15 06:18:19 UTC

(In reply to David Bailes from comment #0)
> Created attachment 837 [details]
> timeline and track show different selected time range

the start and end of selection are the same as those shown in the track.

Comment 2 Peter Sampson 2019-07-15 08:49:35 UTC

Testing on W10 with audacity-2.3.3-alpha-286-582d8afdcb54aa921d29310368d854ec308e65ae

I cannot get this to happen no matter how hard I try

Comment 3 David Bailes 2019-07-15 09:41:22 UTC

(In reply to Peter Sampson from comment #2)
> Testing on W10 with
> audacity-2.3.3-alpha-286-582d8afdcb54aa921d29310368d854ec308e65ae
> 
> I cannot get this to happen no matter how hard I try

I suspect you need a slower cpu to see this bug.

Comment 4 Peter Sampson 2019-07-15 10:54:02 UTC

(In reply to David Bailes from comment #3)
>I suspect you need a slower cpu to see this bug.

This is my slower CPU in Zurich - my old Tosh Satellite with spinning metal disk

It's an i5 2,5GHz 6GB RAM   -  is that too fast still ?

Comment 5 David Bailes 2019-07-16 06:16:31 UTC

(In reply to Peter Sampson from comment #4)
> (In reply to David Bailes from comment #3)
> >I suspect you need a slower cpu to see this bug.
> 
> This is my slower CPU in Zurich - my old Tosh Satellite with spinning metal
> disk
> 
> It's an i5 2,5GHz 6GB RAM   -  is that too fast still ?

I don't know. I've got an AMD cpu, and you can't just compare clock speeds between intel and amd cpus. In addition I've got an ancient onboard graphics chip.
If I run the debug version the problem occurs more frequently.

Comment 6 David Bailes 2019-07-17 04:35:09 UTC

This has been fixed by Paul's commit:
https://github.com/audacity/audacity/commit/a07b165307cf3bc3050e78be0d37a19bf4caf253