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

If clock input is present, the Ext/BPM knob doesn't get saved/loaded correctly #60

Open
machty opened this issue Jun 27, 2021 · 2 comments

Comments

@machty
Copy link

machty commented Jun 27, 2021

I was learning this plugin and had the clock knob set to 120 BPM, but when i'd close and restart rack, the knob reverted back to Ext. I realized this was because I also had the clock input connected to another module, and of course I understand that it doesn't really make sense to leave the clock input connected if you're using the built-in clock, but it was pretty confusing behavior and probably not the correct desirable behavior.

@ValleyAudio
Copy link
Owner

ValleyAudio commented Aug 8, 2021

Hi @machty, so to clarify this issue, it’s when you restart Rack or reload your patch, it’s reverting to ext if you leave a patchcord in the clock input?

@machty
Copy link
Author

machty commented Aug 8, 2021

@ValleyAudio I had to actually try it out again to recall the exact behavior or source of confusion (I'm a bit less of a noob than I was so it's harder to imagine having this confusion), but yes, you stated it correctly. In short, uGraph's BPM knob is a knob that should retain its value between saves, even if its value is being disregarded because an external clock is plugged in.

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