[PD] MIDI input time resolution

[Alexandre Torres Porres]

> even if you use the [v*] family of objects,
> you don't get sample-accurate timing, right?

I used vline~ to convert [ctlin] to audio and it seems it only converter
one value for the whole block, so yeah

2015-07-13 4:25 GMT-03:00 IOhannes m zmoelnig <zmoelnig at iem.at>:

> 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?
>
> fgmasdr
> IOhannes
>
>
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management ->
> http://lists.puredata.info/listinfo/pd-list
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20150713/2ad80804/attachment-0001.html>