


There is a disparity between frame rate used by vst's internal sync and how the PPS-100 calculates Midi clocks from SMPTE frame rate, and this means the converted Midi Clocks begin transmission at Cue Start(punch in) with a varying frame offset that is required to lock with the bpm of the DAW. Ok, I received the PPS-100 today and after some testing, I can see there is an unavoidable issue with variable frame offsets. Audio-based sync, in conjunction with rock-solidly timed external Midi devices, seems the only logical choice.
CONVERT MIDI NOTE NUMBER TO CLOCK PC
If you're wondering why the interest in SMPTE, it's mostly because I want to eliminate jitter in having my PC act as the primary sync source for several external gear items that either use Midi clock or convert Midi clock to pulse clocks or Sync24. If anyone can testify to either of the above two as being reliable or can suggest something else, I'd be very grateful. Seems like the biggest issues faced if it works would be Start position on the correct bar/measure/beat and any additional latencies produced by conversion. The JL Cooper PPS 100, which does actually quite a number of different sync conversions, but they were made in the early 90's and are getting scarce.The pay version of JJOS for the Akai MPC's, which would require additional SMPTE to MTC conversion, if you wanted to start from audio-tracked sync.I am well aware of the difference between time-based and tempo-based sync.
CONVERT MIDI NOTE NUMBER TO CLOCK CODE
Wondering how people go about taking a SMPTE stripe or Midi Time Code and converting it to Midi Clock, especially those who do not use a DAW.
