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.

Sign up for GitHub

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

Jump to bottom

Proposal: change "Fine Tune" from OSC B to affecting OSC A (in reverse polarity) #211

Open
image-et-son opened this issue Dec 5, 2022 · 2 comments
Open

Proposal: change "Fine Tune" from OSC B to affecting OSC A (in reverse polarity) #211

image-et-son opened this issue Dec 5, 2022 · 2 comments
Assignees
@image-et-son
Labels
change request Changed behaviour of existing function

Comments

@image-et-son
Copy link
Owner

For creating well tuned patches it is mus more useful to move OSC B in octaves and to detune OSC A against it. In particular for heavy poly-mod patches, the fine tuning happens on OSC A (not B). At this stage this is just an idea.
@image-et-son image-et-son added the change request Changed behaviour of existing function label Dec 5, 2022
@image-et-son image-et-son self-assigned this Dec 5, 2022
@matrix12x
Copy link

Could you explain how this would work conceptually? Would this be the fine tune by OSC B, instead controlling OSC A?

Would it only be in specific circumstances and would it be a menu option?
I think in concept, for poly-mod patches, its a good idea. It's better than me slightly nudging OSC A pitch.

@matrix12x
Copy link

maybe it only "switches" to VCO A when the polymod FREQ A Switch is switched

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@image-et-son image-et-son

Labels
change request Changed behaviour of existing function
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@matrix12x @image-et-son