[PD] MIDI input time resolution

IOhannes m zmoelnig zmoelnig at iem.at
Mon Jul 13 09:25:57 CEST 2015

On 2015-07-13 07:33, Alexandre Torres Porres wrote:
> Howdy, so I'm making some tests, and I see that my [notein] is sending
> notes at exact DSP cycles, which may make sense I guess, but is kind of a
> bummer. I'd like to know why is that anyway...
> And how about when you have several values coming from [ctlin] for example?
> Does only one of them get sent out in sync with DSP?

just to see whether i understand the question correctly:
so the problem is, that a message emitted by [ctlout] is nto properly
timestamped like a message emitted by (say) [metro]?
that is, even if you use the [v*] family of objects, you don't get
sample-accurate timing, right?

while i do believe that the above assumptions are right (i haven't
tested though), i wonder how you set up your tests: basic MIDI isn't
very good at timing at all, just relying that 31.25kBd are "fast
enough", which is a very bad metric.
so how do you generate you MIDI events to be properly alligned with some
sample clock?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20150713/46033808/attachment.sig>

More information about the Pd-list mailing list