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

[Bug]: Four Osc Synth Clicks while in Mono Mode #207

Open
1 task done
LiamGallagherBC opened this issue May 28, 2024 · 5 comments
Open
1 task done

[Bug]: Four Osc Synth Clicks while in Mono Mode #207

LiamGallagherBC opened this issue May 28, 2024 · 5 comments

Comments

@LiamGallagherBC
Copy link

LiamGallagherBC commented May 28, 2024

Detailed steps on how to reproduce the bug

  • Open up wave form.
  • Add Four Osc to a track.
  • Switch Four Osc to Mono mode in the Global settings area.
  • Play any rhythmically staggered vertical structure, chords or triads or whatever.
  • Hear clicking when the synth transitions from one note to the next.
2024-05-28.10-47-27.mp4

What is the expected behaviour?

The synth should transition smoothly between notes.

Unit test to reproduce the error?

NA

Operating systems

Windows

What versions of the operating systems?

10

Architectures

x86_64

Stacktrace

NA

Plug-in formats (if applicable)

No response

Plug-in host applications (DAWs) (if applicable)

Waveform.

Testing on the develop branch

The bug is present on the develop branch

Code of Conduct

  • I agree to follow the Code of Conduct
@FigBug
Copy link
Contributor

FigBug commented May 30, 2024

FourOscPlugin uses juce::MPESynthesiser internally which has terrible voice stealing algorithm. I'll try and find a way to work around it.

@FigBug
Copy link
Contributor

FigBug commented May 31, 2024

Actually, I did implement a somewhat better voice stealing algorithm. Can you find this line

            isQuickStop ? std::min (0.01f, paramValue (synth.ampRelease))
                        : paramValue (synth.ampRelease)`

And try increasing 0.01f, does that reduce the click?

@LiamGallagherBC
Copy link
Author

That certainly helps, but doesn't resolve it entirely. Do you have a suggestion for a good value to use?

@FigBug
Copy link
Contributor

FigBug commented Jun 6, 2024

It's a bad design I think I just need to rework how the voice handling works.

@LiamGallagherBC
Copy link
Author

Fair enough! If I can help you out at all please let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants