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.

Sign up for GitHub

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

Jump to bottom

MIKMIDIClock should be thread safe #93

Closed
kris2point0 opened this issue Jun 9, 2015 · 0 comments
Closed

MIKMIDIClock should be thread safe #93

kris2point0 opened this issue Jun 9, 2015 · 0 comments
Assignees
@kris2point0
Labels
enhancement
Milestone
1.5

Comments

@kris2point0
Copy link
Contributor

A single MIKMIDIClock instance has the potential to be used across multiple threads (main, CoreAudio, MIKMIDISequencer's processingQueue, etc.) that are all interested in the same tempo and timing information, and should probably be thread safe.
@kris2point0 kris2point0 self-assigned this Jun 9, 2015
@kris2point0 kris2point0 added this to the 1.1 milestone Jun 9, 2015
kris2point0 added a commit that referenced this issue Jun 9, 2015
@kris2point0
Issue #93: MIKMIDIClock is now thread-safe
dade71b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kris2point0 kris2point0

Labels
enhancement
Projects
None yet
Milestone
1.5
Development

No branches or pull requests
1 participant
@kris2point0