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

Audacity Bugzilla



Bug 1620 - Clipfix process dialog counts up rather than down
Clipfix process dialog counts up rather than down
Status: RESOLVED QUICKFIXED
Product: Audacity
Classification: Unclassified
Component: Nyquist
unspecified
Per OS Linux
: P4 Repeatable
Assigned To: Steve Daulton
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-03-28 17:11 UTC by Steve Daulton
Modified: 2018-08-20 11:51 UTC (History)
5 users (show)

See Also:
Steps To Reproduce:
Release Note:
First Git SHA:
Group: ---
Workaround:
Closed: 2018-08-20 00:00:00
gale: Test‑OK‑Win+
gale: Test‑OK‑Mac+
gale: Test‑OK‑Lin+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Daulton 2017-03-28 17:11:11 UTC
When applying Clipfix to a medium to long selection, the 'Remaining time' is initially very low and gradually increases as the audio is processed.

There's a more general technical difficulty in displaying accurate times for Nyquist plug-ins, but in Clipfix it is MUCH worse than it should be.

Assigned to myself.
Comment 1 Steve Daulton 2017-03-30 19:51:18 UTC
https://github.com/audacity/audacity/commit/a9879bddf

Tested on Linux.
The progress dialog is not perfect, but I think this is as good as it gets. On par with other effects and MUCH better than before.
Comment 2 Gale Andrews 2017-04-12 22:34:55 UTC
Yes the progress dialogue displayed values are much improved and time remaining counts down. On Windows the disk I/O was very high while the progress bar shot immediately to     half way and time remaining continued to count up. As soon as time remaining counted down again, disk I/O dropped back to normal.
Comment 3 Gale Andrews 2017-04-12 23:14:33 UTC
(In reply to Gale Andrews from comment #2)
> On Windows the disk I/O was very high while the progress bar shot immediately
> to half way and time remaining continued to count up. As soon as time remaining 
> counted down again, disk I/O dropped back to normal.
This comment was about the 2.1.3 (unfixed) code, in case it wasn't clear. Disk I/O is steady and low in the fixed code.