You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, typically when releasing multiple keys on the connected synthesizer at the same moment, SwiftUI's .onChange(of:) is called on the same frame – resulting in one of those calls not being executed. This results in a note's visualization to get "stuck on" even though the key is no longer being pressed and the note is no longer being played.
The "I'm going to ignore this" fix in place is the stuck key will be released on a subsequent release of that same key.
The text was updated successfully, but these errors were encountered:
Sometimes, typically when releasing multiple keys on the connected synthesizer at the same moment, SwiftUI's .onChange(of:) is called on the same frame – resulting in one of those calls not being executed. This results in a note's visualization to get "stuck on" even though the key is no longer being pressed and the note is no longer being played.
The "I'm going to ignore this" fix in place is the stuck key will be released on a subsequent release of that same key.
The text was updated successfully, but these errors were encountered: