Re: [LAD] Announcing PHASEX-0.14.96

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Johannes Kroll <jkroll@...>
Cc: <linux-audio-dev@...>
Date: Monday, January 21, 2013 - 10:27 pm

> ----- Original Message -----

> On Thu, 10 Jan 2013 22:26:15 -0500

Great!

> But I'm pretty sure that syncing Phasex to an external MIDI clock

Are there any specific sync/timing issues that you're trying to solve
by sending MIDI Clock messages?

MIDI Clock messages are currently ignored.  The original MIDI enabled
version of phasex had this, but it ended up adding too much jitter to
the LFO frequencies and caused more problems than it solved.  The
internal MIDI clock in phasex is used for timestamping incoming events
and assigning frame position.  (Future plans include a more robust
tempo clock that can be used with MIDI Clock, MTC, MIDI triggers, tap
tempo, JACK Transport, etc.)

For now, the best options for keeping in sync with tempo changes are
JACK Transport Tempo sync or automating the BPM parameter.  Not ideal,
I know... but this is better than nothing and should hold up until I
can get the tempo clock designed.

Cheers,
--ww
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

This is the only confirmed message in this thread.
Possibly related messages: