-
Notifications
You must be signed in to change notification settings - Fork 65
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
Question about sequencer example #93
Comments
It's not exactly expected, but I wouldn't classify it as a bug. It is probably a result of two factors: 1) the Windows MM backend is synchroneous, i.e. when you use |
It's not a big problem, I can just add a pause at the end of every song. And as you say, it's probably specific to Windows. But it's off by much more than a few milliseconds. The last few notes get cut off without the pause at the end. Maybe it's the way MIDI data is buffered in Windows? |
One problem with the sequencer example is that events can be left in the pending queue after
to this:
With this fix, it's no longer necessary to artificially sleep at the end of the sequence, and line 249 (the following) can be deleted:
|
The ability to stop a sequence when it is not finished is a feature, IMO. Maybe there should be a flag PRs welcome. |
Hi!
This is the first time I've tried using python-rtmidi. I tried to run the sequence example (sequencer.py), but the last three notes didn't play. On a hunch, I added a pause in the 'finally' block and that took care of the problem. Is this expected behaviour or a bug?
I'm running under Python 3.8 and Windows 10.
Thanks.
The text was updated successfully, but these errors were encountered: