BUG: 1st knob parameter resets to index 0 upon returning from Tuner Mode, causing mismatch with UI

[hogejair]

Describe the bug

When returning from the Tuner mode, the parameter assigned to the 1st knob in the audio processing is forced to its 0th index (the state where the knob is turned all the way to the left), and it remains in this state until the physical knob is manually turned again.
However, the on-screen UI (the visual knob position and displayed parameter value) remains perfectly unchanged from before entering the Tuner mode. This causes a mismatch between what the user sees on the screen and what the audio function is actually processing.

I initially thought this was a bug in my custom pedal code, but I confirmed that this issue occurs consistently across other pedals made with Stomphacks.

Steps to Reproduce

1. Load a pedal created with Stomphacks.
2. Set the 1st knob to any position other than the leftmost one (i.e., an index of 1 or greater).
3. Enter Tuner mode on the device.
4. Exit Tuner mode and return to the pedal screen.
5. Observe that the 1st knob's parameter value in the audio processing drops to the value corresponding to index 0 and stays there.
6. Note that the on-screen UI (knob position and displayed value) still shows the state set in Step 2.

Expected behavior

The parameter states (selected index values) in the audio processing should perfectly sync with the UI and be preserved when returning from Tuner mode. The internal parameter should not be reset to the 0th index unless the physical knob is actually turned.