I had a few PM's with Koz about this. I think he will accept a majority decision.
I think there are three plans on the table. All of the plans could also include configurable threshold below 0 dB for the given number of samples. I think that is un-necessary complication but I don't object if we want it.
Plan A) has Show Clipping trigger threshold as now, one sample at 0 dB, unconfigurable. Meter also clips (and holds) at one sample at 0 dB (removing discrepancy between meters and Show Clipping), but user can change that to x samples before it clips and y samples before it holds. Non-holds will fade away.
That's a fairly big change for playback meters - it may make loudness war files show as more dangerous than they are (but Steve would say that is a good thing).
So Plan B) lets the meter clip default stay at 4 samples at 0 dB (and x and y can still be customised). To maintain consistency with Show Clipping, the latter does not show red lines until 4 samples are clipped. But because consensus says it must show every clipped sample by default, we show runs of 3 or less clipped samples differently (lighter red, dashes or whatever).
Plan C) makes both Show Clipping and Meters thresholds configurable. Both default to trigger on 1 clipped sample. Because we have a pair of matched settings they have to go in Prefs. I don't favour C. It makes the settings less accessible and makes the display of Show Clipping more complex if user chooses a threshold more > 1.
I would choose A) for consistency and no change to Show Clipping, though B) is a good fallback if consensus thinks meter should continue not to clip until four samples.
I would also say with B), Find Clipping default thresholds should change from 3 to 4 samples.
Is this a way of moving forward? I hope so
Gale