Peter Sampson

> and fails when used at intermediate points in the track [anything other than the final portion with empty field] showing an error due to insufficient space to paste on...

This does _**NOT**_ appear to be a regression - the same occurs in all earlier 3.x releases. I cannot test with Audacity 2.4.2 as Audacity crashes when running the Macro,

@Paul-Licameli hahaha > The exceptional two-pass nature of the Noise Reduction effect, Indeedy > Macros. The macro system. The entire miserable ill-considered extension of the Chains feature. Yebbut my use...

A Forum report of this today: https://forum.audacityteam.org/viewtopic.php?f=46&t=129397&p=464419

At even bigger track sizes I can get **-8dB** labelled in the left channel and **_inconsistently_** **-9dB** in the right channel 

And note that we have a similar Vertical Scale labelling inconsistency when using **Spectogram** view at default stereo track size. And note that this is a regression on 3.0.5 and...

The Default **Linear**, now **Linear (amp)**, appears to be nicely consistent in this regard - and has always been so.

Testing on W10 this remains the case in: a) 3.3.0 Beta: audacity-win-3.3.0-beta-20230405+caeb58e-x64-msvc2022 b) 3.4.0 alpha: audacity-win-3.4.0-alpha-20230405+934774c-x64-msvc2022

@LWinterberg @dozzzzer Testing on W10 with 3.5.0 recent release - this still occurs. This issue appears to arise because the left channel waveform is slightly smaller than the right channel...

@LWinterberg This is still the case in 3.5.0 It could be ameliorated by replacing "Built-in Effect ..." with "**Built-in EGAT**" - or just "**Built-in**" _as most users will have no...