Alex Montgomery wrote:
I think this kind of tools is a good candidate to be developed as
an "in server" JACK client. With the dbus based dynamic access of
available "in server" clients installed on a machine, it will be
quite easy to load/unload this kind of tool when needed (Netjack2
uses this model of "in server" clients).
Ok, so Nedko and I got a release out that supports goto/locate MMC
messages and command-line parameters. We're going to switch it over to
using JACK midi instead of ALSA midi next. Should we start thinking
about making this an "in server" client now? Could someone familiar
with this stuff comment on this?
Thanks,
-- Alex
I'm not familiar with MMC and I'm less familiar with Linux MIDI, because
of to much troubles, but I know that I need to sync an Atari ST with
Linux MIDI by MTC and this isn't possible for all applications. It would
be good if JACK transport can be master and slave for song position
pointer and also timing clock. ALSA MIDI is more important than JACK MIDI.
Cheers,
Ralf