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.

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

MIKMIDISequencer slower than audio #180

Closed
mlostekk opened this issue Feb 18, 2017 · 8 comments
Closed

MIKMIDISequencer slower than audio #180

mlostekk opened this issue Feb 18, 2017 · 8 comments
Assignees
Milestone

Comments

@mlostekk
Copy link
Contributor

Hello,

i am having very simple midi file that i am playing with the sequencer. I have also bounced that midi file to an audio file and playing both at the same time. What i observe is that both sources drift.

I am printing out both currentTimeStamps and seeing that the MIKMIDISequencer seems to be a bit slower than the audiotimestamp. I can also hear this effect if i attach an external midi device.

Is this a known issue? Is it maybe related to some internal rounding errors?

@mlostekk
Copy link
Contributor Author

I just found out that when applying this

midiSequencer.tempo = midiSequence.tempoEvents.firstObject.bpm * 1.0166;

It keeps nearly stable

@armadsen
Copy link
Member

Hi Martin,

How are you doing the bounce to audio? Any chance you can provide a sample project that reproduces the problem?

@mlostekk
Copy link
Contributor Author

okay. will upload a demo project by end of today!

@mlostekk
Copy link
Contributor Author

You can see the drifting difference in this project

https://github.com/mlostekk/MIKMIDIAudioVsMidi

The first counter is the timer in milliseconds. The lower right one is the difference. You can see it drifting. And you can can hear it.

@mlostekk
Copy link
Contributor Author

Ah, and by the way, i have directly bounced the wave file from ableton. But it does not matter, as you can see the timers shifting

@mlostekk
Copy link
Contributor Author

no update about that what i might do wrong?

@mlostekk
Copy link
Contributor Author

@armadsen armadsen self-assigned this Aug 27, 2017
@armadsen armadsen added this to the 1.6.2 milestone Aug 27, 2017
@armadsen
Copy link
Member

This appears to be a duplicate of #199, which was fixed by fe68908. Sorry it took so long to get it fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants