Posts: 33-48 of 99

It looks that currently schism sends one midi clock message (F8) every eigth row and it should send 6 midi clock messages on every row.

I think that the easiest way to test it would be to connect an external sequencer and check if it stays in sync.

ok, sending one clock message every eighth row is definitely wrong. the midi spec says that 24 clock messages should be sent per quarter note, so six messages per row is perfect if you're assuming that four rows correspond to one quarter note. which is reasonable.

edit: i said a bunch of stuff here before about how sending one clock event per tick would probably be easiest, but it looks like that's not the case. more info to come.

Great work! I finally had a chance to test it and now it syncs well.I noticed though that it is maybe shifted a few ticks. Is it possible that it sends additional clock messages at the beginning with the midi start message?

if it's shifted a few ticks, is it possible that the midi timestamps (that schism is sending) are wrong or that there's a latency issue?

the start message and the clock messages are handled by completely different parts of the code, so i don't think there's any causal relationship there. the number of clock messages sent is directly tied to the number of samples that the mixer outputs, so i don't think there should be a problem there either, but i'm investigating further.

edit: also, what software/hardware are you syncing to it? we'd like to collect that sort of info in case something goes wrong in the future.

that looks like the build that scannerboy linked earlier, which doesn't include the dylib. (past "official" releases of schismtracker have included the dylib, and we plan to do so with ours as well). also, scannerboy's builds are from storlek's hg repo, which is now several bugfixes behind our git one :Þ

we don't have anyone with a mac to do builds for our new versions, so any osx user who feels capable of running some build scripts every now and then, hit us up

scannerboy wrote:

Great work! I finally had a chance to test it and now it syncs well.I noticed though that it is maybe shifted a few ticks. Is it possible that it sends additional clock messages at the beginning with the midi start message?

i'm assuming this is because the latency of your audio device != the latency of your midi device

e.g. if you think your midi sequencer is playing 100ms ahead of schism, clock_offset=4410 to delay the midi clock by 4410 samples. it'll be a bit of trial and error but hopefully once you've found the right number you can "set and forget" it

Also if anyone has problems with sending MIDI clock I also managed to make it work

this OSX build doesn't work for me unfortunately I'm on 10.11.4 and I got this message:

"Check with the developer to make sure Schism_Tracker works with this version of OS X. You may need to reinstall the application. Be sure to install any available updates for the application and OS X."