Re: ToneShiftEQ v0.3.0 — First public relea se

Am 03.07.26 um 19:32 schrieb Robin Gareus:
> On 2026-07-03 1:51 PM, Hermann Meyer wrote:
>>
>>
>> Regarding the phase response: the plugin uses minimum-phase impulse=20
>> responses processed through a partitioned convolution engine. The=20
>> Ardour spectrum analyzer confirms linear-phase behavior in the output,
>
>
> That is not what I see here.
>
> Running Toneshift EQ v0.3.0-6-g51e2224 LV2 version. I set the plugin=20
> mid-band to be -12dB at 1kHz, peaking/bell curve, and all other=20
> settings are default. The plugin reports 128 samples latency. For good=
=20
> measure I fed it with pink noise.
>
> Ardour's built-in analyzer clearly shows a phase shift, and the=20
> attenuation at 1kHz is only 10.4dB deep (not 12dB).
>
Okay, I'll remove the linear phase phrase from the descriptions. Still.=20
I've seen a couple of EQ's were we could talk about phase twisting=20
instead linear response. To the attenuation, when you set the smooth=20
parameter to zero you'll get the -12 dB ( default is 0.3). When you=20
compare with what the GUI shows in it' filter curve, you'll see the=20
exact same as what the Ardour build in analyzer show.


> https://robin.linuxaudio.org/tmp/toneshift-eq12.png
>
> Small buglette: The enable control is the wrong way around. It behaves=
=20
> like a bypass (1: bypassed), and isn't mapped to LV2 (and doesn't have=
=20
> lv2:designation lv2:enabled;)
>
That's intentional. It isn't meant as bypass like in other plugs, so,=20
the gain control and the analyzer still been active. It is meant as a=20
A/B switch to compare original signal with processed one.


> I do like the UI though, and the small inline display is also nice! I=20
> hope you can address these issues. While I tend to avoid linear phase=20
> EQs due to pre-ringing, artifacts it'll still be a nice addition to=20
> the ecosystem.
>
>
Nice to hear at least one thing good about my work.=C2=A0 Thanks for that.

hermann


> --=20
> robin