Audacity Forum

waxcylinder wrote:Good catch Steve Brown

Logged on our Bug-tracker as P3 Bug #1790: http://bugzilla.audacityteam.org/show_bug.cgi?id=1790

This is a recent bug that crept into 2.2.0 (was ok in 2.1.3 and earlier). Luckily you caught this just in time for us to hopefully squeeze a fix for it into the upcoming 2.2.1 release

Thanks for that,

Peter

You're welcome. It may be too much to ask, but I'd like to be able to see a readout of the coordinates of a point drawn on the Equalizer graph, in the upcoming release of Audacity. That would make it easier for me to combine two equalization curves into one, instead of having the Equalization effect do two passes on the same file, one for each curve. I figure the fewer passes, the better it is for the audio.

Regards,

Steve Brown

P.S. I'm using Windows 10 Home and Audacity 2.2.0.

Steve Brown wrote:It may be too much to ask

Asking is fine If it's not available now, we can log it as a feature request.
Feature requests are best posted on this board: viewforum.php?f=20 where they remain visible for longer, so more likely to attract discussion and possibly support from others. The 'votes' for the feature are then logged on the Audacity wiki and the forum topic is archived.

Steve Brown wrote:I'd like to be able to see a readout of the coordinates of a point drawn on the Equalizer graph

That is not going to happen in the next release, as that is due out early December (not enough time).
The Equalization effect is well overdue for a rewrite. I've added your 'vote' for this feature.

Steve Brown wrote:I figure the fewer passes, the better it is for the audio.

Provided that the track is 32-bit float format (default), it actually makes no difference. 32-bit float is so accurate that you can apply an effect thousands of times without degrading the sound quality.