Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Formant slider is invisible at first when opening a "Choir Pad Thing" factory patch #5581

Closed
xard-dev opened this issue Dec 6, 2021 · 12 comments
Labels
Bug Report Item submitted using the Bug Report template

Comments

@xard-dev
Copy link

xard-dev commented Dec 6, 2021

Bug Description:
Formant slider is invisible at first when opening a "Choir Pad Thing" factory patch.

Surge Version
Surge XT 0.99.main.007a427

  • Version:
  • Plugin Type: LV2 / VST3
  • Bitness: 64-bit

Reproduction Steps:
Steps to reproduce the behavior:

  1. Open factory patch "Choir Pad Thing".
  2. Look for the initial state of the Formant slider.

Expected Behavior:
The format slider is rendered.

Screenshots:
image

Computer Information (please complete the following information):

  • OS: Ubuntu 20.04 LTS
  • Host: Carla / Ardour 6 / Standalone
  • Version: 2.1.0 / 6.9

Additional Information:
This is not an issue in older Surge.

There is also something unexpected going on when clicking the S-LFO1 control to show the slider which might or might not have anything to do with the main issue:
image

@xard-dev xard-dev added the Bug Report Item submitted using the Bug Report template label Dec 6, 2021
@xard-dev
Copy link
Author

xard-dev commented Dec 6, 2021

I discovered this thing when manually testing and comparing all factory presets between the versions for audible differences. So far I've found none including fiddling macros, pitch bending and a quick modwheel testing.

@mkruselj
Copy link
Collaborator

mkruselj commented Dec 6, 2021

This is not a bug - that just means those filters are disabled (which is a right click menu option). In 1.9 we had to show this differently on Linux due to VSTGUI bugs on Linux, but with JUCE, we can show it transparent (as it was intended) across all platforms!

The other thing which you show about mod assign mode is simply the transparency between the green mod slider and regular orange slider blending together. That's just how it is.

@mkruselj mkruselj closed this as completed Dec 6, 2021
@xard-dev
Copy link
Author

xard-dev commented Dec 6, 2021

Okay, I tested the Format behavior and it was exactly as you said: On both versions it's disabled (though the patch shows a value of "-3075.00 %". I need to look up how the disabling actually works as I did not find a way disable it again after touching the control.

@xard-dev
Copy link
Author

xard-dev commented Dec 6, 2021

The Low Cut and High Cut have Activate and Deactivate context menu items and that works as expected.

However the Formant control does not have activation option at all. Also the sound changes after I touch it once in both versions and I can't get it back to way it was unless I'm reloading the patch. Could this be a separate issue?

@mkruselj
Copy link
Collaborator

mkruselj commented Dec 6, 2021

Ah so that would just be a patch versioning issue for Formant parameter. Corrupt value stored, or something. I vaguely remember stumbling upon it. That's a separate and unrelated issue, though.

@xard-dev
Copy link
Author

xard-dev commented Dec 6, 2021

Thank you for the clarification! If the value is corrupted then I guess it's "garbage in garbage out" situation in terms of the UI.

@mkruselj
Copy link
Collaborator

mkruselj commented Dec 6, 2021

Yeah... but apparently the engine still takes it and makes a plausible sound. Worst thing is - none of the "legal" values reproduce that sound. So we might just axe the patch from the library... but I would be curious to know if there are other factory patches that have Formant parameter borked like this.

This is a patch from streaming version 9 (if you open the .fxp you can find an XML entry <patch revision="9"> and we have 433 such patches...

@xard-dev
Copy link
Author

xard-dev commented Dec 6, 2021

I'll go through at least the factory presets and so far I've found problematic ones:

  • Choir Pad Thing
  • Pad 7

I'll open a ticket with full listing about this regression issue once I'm done with the factory presets.

@mkruselj
Copy link
Collaborator

mkruselj commented Dec 6, 2021

@xard-dev No need for a ticket, I've located the issue and one of next nightlies are going to have it fixed!

@mkruselj
Copy link
Collaborator

mkruselj commented Dec 6, 2021

Fixed at head now!

@xard-dev
Copy link
Author

xard-dev commented Dec 6, 2021

Oh, nice!
These were the direct findings on my testing until I realized that I forgot to check the B dual feature settings when present... oops.

The issue was related to Window type waveform.

Pads

  • Choir Pad Thing
  • Computers In Space
  • Hmm...
  • Pad 7
  • Primes (very minor difference after changing value)

Polysynths

  • Embarrass
  • Eyan
  • Fonk
  • Hombre
  • Jim
  • Japanese Space-ulation Wheel
  • Past tense
  • Quantization Choice

Sequences

  • Burial Ground

Oh, and I did not notice any audible difference between Surge and Surge XT Factory presets when comparing them with same midi notes and 75% panning (left older, right XT). Unfortunately the older VST3 version does not have audio inputs in Ardour so I could not test the vocoder and inputs against the older verion. However the LV2 XT sounded ok.

@baconpaul
Copy link
Collaborator

Awesome thank you
This bug has been there forever. You are correct that it wouldn't change the patch playback, but it would have made it uneditable.
Appreciate all the diligent testing today!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Report Item submitted using the Bug Report template
Projects
None yet
Development

No branches or pull requests

3 participants