-
-
Notifications
You must be signed in to change notification settings - Fork 214
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
BPM gets reset after saving present #181
Comments
Hi Igor,
I cannot reproduce this. These are my steps to reproduce:
Download market build of Audiokit Synth One on iPhone 13 Pro Max
Choose Preset “Arp/Seq Octavio”
Navigate to Main Page.
Set BPM to 120
Save Preset
Set BPM to 60
Save As new preset
Recall 120 preset
Recall 60 preset
Note tempo is updated when recalling presets
There is an Easter egg menu (“About” -> “AudioKit Synth One"…have you been adjusting settings there?
“Lock arp rate” will ignore BPM captured in Presets
… On Jul 20, 2022, at 5:14 PM, Igor Pellegrini ***@***.***> wrote:
Hello guys,
I've made a sound with the sequencer active and I wanted to reduce the tempo of its playback.
But after trying to change BPM and then saving the preset, the tempo gets immediately reset to 120 bpm.
Reloading the preset doesn't restore the bpm that I tried to save; it restores the sound but with 120bpm.
Is this intended or is a bug to report?
—
Reply to this email directly, view it on GitHub <#181>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD5L5X4ADHFCIGVINMTABMLVVCI7RANCNFSM54FTSE3Q>.
You are receiving this because you are subscribed to this thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello guys,
I've made a sound with the sequencer active and I wanted to reduce the tempo of its playback.
But after trying to change BPM and then saving the preset, the tempo gets immediately reset to 120 bpm.
Reloading the preset doesn't restore the bpm that I tried to save; it restores the sound but with 120bpm.
Is this intended or is a bug to report?
The text was updated successfully, but these errors were encountered: