-
Notifications
You must be signed in to change notification settings - Fork 45
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
Different behavior on shared methods (SynthEvent/SampleEvent) #146
Comments
Noticed now that after using synthEvent.setEventStart(posInSamples) they will play at the right position one time, then settling at the nearest full step before. This means I can get around this by updating positions every time the sequencer is at 0. Still strange and as I said it works fine on SampleEvents so I don't think I'm using it the wrong way. |
Hi @vustav thanks for pointing this out, looks like a bug in the synthesis routine and has indeed to do with first time playback. Will address this shortly. |
This has been addressed in f592455 Can you verify whether this addresses the issue in the context of your application ? If all is correct, you no longer need to update the event positions whenever the sequencer reaches the zero offset any longer. Additionally, if you were using |
Works perfect now! |
Excellent! Thanks so much for pointing out the issue. |
event.positionEvent(pos) works as intended on SampleEvents but on SynthEvents they play at full steps, ex. a SynthEvent set to play at 3 1/4 will play at 3 etc.
The text was updated successfully, but these errors were encountered: