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

Audacity Bugzilla



Bug 454 - Contrast tool may analyse wrong track
Contrast tool may analyse wrong track
Status: RESOLVED FIXED
Product: Audacity
Classification: Unclassified
Component: Built-in FX
unspecified
PC All
: P4 Repeatable
Assigned To: Default Assignee for New Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-11-18 06:41 UTC by Steve Daulton
Modified: 2018-08-20 11:45 UTC (History)
5 users (show)

See Also:
Steps To Reproduce:
Release Note:
First Git SHA:
Group: ---
Workaround:
Closed: 2018-08-20 00:00:00
stevethefiddle: Accessibility+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Daulton 2011-11-18 06:41:30 UTC
If there is more than one audio track in a project, the Contrast tool always analyses the bottom track regardless of which track is selected.
Comment 1 Martyn Shaw 2012-01-10 19:47:55 UTC
(In reply to comment #0)

OK, I fixed that to measure only one selected track, otherwise to show an error.

HTH
Martyn
Comment 2 Steve Daulton 2012-01-13 08:58:59 UTC
(In reply to comment #1)
Tested successfully on Linux.
Comment 3 Gale Andrews 2012-01-13 14:09:42 UTC
I'm seeing two possible problems on Win XP:

1) We now cannot analyze an unsplit stereo track, so the description in the Manual "Contrast Analysis is designed to analyze a single mono or stereo speech track" is now wrong. It was (a little) misleading anyway because analysing a stereo track was only actually measuring the bottom (right) channel, but shouldn't the error for a stereo pair say you have to split the track and measure one channel? Or should we live with the issue where we have a single selected stereo pair, not throw an error and document that it will only measure the right channel? That seems more useful/less irritating? 

Going forward, "should" we sometime be able to average a measurement on multiple channels or tracks? 

 
2) Any time you press Reset, even if you had measured some foreground and/or background, you get the new message "Nothing to measure. Please select a section of a track." twice.  

I noticed a problem (not documented before?) that if you have a longer track below a shorter track and select valid audio in the longer track after the end of the track above, you get "Times are not reasonable!". New bug, or is it not fixable?
Comment 4 Steve Daulton 2012-01-13 18:54:24 UTC
(In reply to comment #3)
As I'm not very familiar with this tool my comment "Tested successfully on Linux" refers only to the specific issue that measurement is made when one track only is selected, and an error is thrown if more than one track is selected.

The issues raised by Gale in comment 3 also apply on Linux.

Also the "Directions for non-mouse, keyboard users" (http://www.eramp.com/WCAG_2_audio_contrast_tool_help.htm) do not work because the selection does not respond to the times set in the interface, but I presume that is a different issue altogether.

On Linux it is not possible to tab past the first measurement result.
Comment 5 Gale Andrews 2012-01-14 12:19:29 UTC
(In reply to comment #4)
> the "Directions for non-mouse, keyboard users"
> (http://www.eramp.com/WCAG_2_audio_contrast_tool_help.htm) do not work 
> because the selection does not respond to the times set in the interface
Thanks, I let David know that, Cc to Martyn.

> On Linux it is not possible to tab past the first measurement result.
Confirmed. You could raise a P5 for it, though because of bug 57 it's pretty irrelevant.
Comment 6 Gale Andrews 2012-05-27 17:49:36 UTC
RESOLVED - FIXED for this bug, as it is fixed per the subject, but new bugs opened (thanks, Steve). 

* Bug 511 "Contrast tool gives incorrect error message for stereo            tracks instead of analyzing". 

* Bug 512 "Contrast tool gives incorrect error message on Reset" 

* Bug 513 "Contrast tool fails if selection is beyond the end of a previous track"