How to enable midi slave?

[EclectickMedia]

Hey there! After being recommended by FalkTX to use this package as a method of syncing to BPM, I've been running into some issues.

I was excited to see the "midi_clock_slave" option available in the Readme, but now find that that feature seemingly doesn't exist. Is there something I'm missing? I've been fiddling with it on and off for the last few weeks, but I just can't seem to get it too work.

Version v0.10.6-391-gf3ecdda

[falkTX]

how are you controlling mod-host?
on the command-line, you just need transport_sync midi, then you need to feed the MIDI data into the global mod-host midi-in port

[EclectickMedia]

Interactively, via the command line. Just tried transport_sync midi as a command line argument, and it seems to have been enabled in mod-host. Is transport_sync documented anywhere in the project? I see no mention of it in the man pages...

That being said. Even though mod-host seems to be running with transport_sync enabled and my clock-source is running through the mod-host port, JACK's transport seems unaffected. Perhaps I'm not quite understanding the purpose of this feature. Does it modify the JACK transport BPM, or just mod-hosts own internal bpm?

[falkTX]

mod-host does not have an internal transport state, it uses jack transport directly.
clock position is not supported yet, but syncing pulses to get BPM and play/stop is.
this is MMC, not MTC (I think...). mod-host only supports one of them.

[EclectickMedia]

MMC handles play/stop/seek transport commands. Midi clock only sends pulses to sync BPM, not play position or start/stop state. BPM is what I'm trying to sync, I don't need to worry about jack's timeline position.

Hmmm... are you able to confirm support for MTC in the package? I'm not versed in C types so it would be pointless for me to investigate myself.

[falkTX]

I always get confused by the 2, anyway, mod-host specifically handles bytes 0xF8 (MIDI clock pulse) and then 0xFA, 0xFB and 0xFC for start, continue and stop respectively.
Anything else, transport-wise, is unsupported.

[EclectickMedia]

0xF8 (MIDI clock pulse) should be the message I'm sending. Time for some further debug of my setup. Either its a config error on my side, or I'm not sending a compatible MIDI message.