[bug] Circular knob display + calculation errors.

[jayrope]

Bug here on plugdata-fx VST3 0.93
macos 15.7.4
Reaper 7.55

Demo patch
circular-knob-bug.txt

Double clicking a circular knob should reset it to it's initital absolute value.
This works in linear mode here.

Yet it does not work both in logaritmical and exponential mode. There a double-click resets the dial to the linear position, while respectively calculating the linear dial position through logaritmical / exponential mode.

Please also note, that upon initial patch load/initialisation of the objects the dial positions are correctly displayed, yet when the knobs are double-clicked they all reset to the linear mode position, regardless of which mode was actually set in the inspector.

You can simulate this behaviour by choosing the whole group of objects, copy it to clipboard, then re-insert someplace else. These newly created objects show the correct dial positions again, just like directly after a patch load.

I hope I made it clear, and see demo patch above - rename from .txt to .pd - Github didn't allow me to upload .pd
Cheers! @timothyschoen

[dromer]

Ah, I thought I had created a ticket for this already, but only reported it on Discord.

Thnx, can indeed confirm that the position is incorrect.

[edit: hmm, on latest nightly it actually goes to 0 on double-click for me. in all modes. and in log mode it starts at 0 too.]

[timothyschoen]

Ah, I thought I had created a ticket for this already, but only reported it on Discord.

Thnx, can indeed confirm that the position is incorrect.

[edit: hmm, on latest nightly it actually goes to 0 on double-click for me. in all modes. and in log mode it starts at 0 too.]

Yes, it's already fixed on nightly! The "arc start" parameter decides the reset value

[jayrope]

Yes, it's already fixed on nightly!

@timothyschoen Lovely, I'll check it out.
@dromer Not using Discord, and I suppose we have the git for reports anyway. Anything else in my opinion just creates too many support lines to attend. No pun intended.

[dromer]

The "arc start" parameter decides the reset value

Huh, that should be the Initial value setting no? Now it seems that these two options are at odds ..

This is quite unintuitive imo.

[timothyschoen]

The "arc start" parameter decides the reset value

Huh, that should be the Initial value setting no? Now it seems that these two options are at odds ..

This is quite unintuitive imo.

That's up to @porres, not me

[jayrope]

The "arc start" parameter decides the reset value

Huh, that should be the Initial value setting no? Now it seems that these two options are at odds ..

This is quite unintuitive imo.

+1

[jayrope]

The "arc start" parameter decides the reset value

Huh, that should be the Initial value setting no? Now it seems that these two options are at odds ..
This is quite unintuitive imo.

That's up to @porres, not me

The arc start value as a an initial value is now, what's been taken as the intial value. I agree that this is counter-intuitive.
Keeping this like that will just produce more support threads. The intitial value should be the one, that being produced when double clicking a know.
The arc value also produces a weird effect on the arc itself. If it is set higher then the minimum value, then the difference greys out. I don't even understand what that means, to be honest. @porres you have a comment there? Thank you in advance!

[porres]

@porres you have a comment there

yes, the object is quite outdated :) I changed this way long ago, in RC9, sometime between may (RC8) and september of 2023 (RC9)...

from the RC9 changelog: "[knob] 'init' message removed, now you have 'load' (a bit similar)... and now this value is not the 'arc start' anymore.", by the way, knob was added in RC8!

[dromer]

@porres and should Knob reset to this "load" value after double-click, so that the same value is used for both functions?

Then "arc start" is only used for drawing (as expected) and this load value for init+reset behavior.

[jayrope]

@porres So how can these issues be fixed? Are you on it youself eventually?

[porres]

should Knob reset to this "load" value after double-click, so that the same value is used for both functions?

double click restores to arc start state (same as 'reset' message)

alt/option+click reloads ( that is: restores to 'load' value / same as 'reload' message )

it's all in the help file ;)

how can these issues be fixed? Are you on it yourself eventually?

no :) I don't do the porting

[porres]

why is this issue closed? :) you should open a new one I guess

[timothyschoen]

The arc start value as a an initial value is now, what's been taken as the intial value.

I think this comment has lead to confusion: the init value and double-click values are separate things in ELSE's knob, and plugdata correctly implements this. Whether this behaviour is good or not is debatable, but there is no difference between plugdata's else/knob and pd-vanilla's else/knob.

This has nothing to do with plugdata's knob being outdated, I updated to the latest ELSE updates on February 2026, and it will get updated to the latest ELSE again very soon.