[PD] Re: arduino-help.me.please.pd [gadlletas]

[nomeparece]

thanks frank, christian, hans, IOhannes, martin...

nice to read all that about how to control a servo from pd.. i  
thought it was "easier" for me as entry level user to get to have a  
simple patch to move, withouth the need of exact prescition, a little  
servo..but what i see now is that things get to complex for me and  
that pd is still to far from my grasp..i cannot creatre a [comport~]  
or modifying stuff in the sample or rate timing..acordinng to all the  
replies, it looks like rocketeer science for me.

:(

again, merci
/a

On May 30, 2006, at 12:45 AM, pd-list-request at iem.at wrote:
>
>
>    5. Re: arduino-help.me.please.pd [gadlletas] (Hans-Christoph  
> Steiner)
>
>
> Hallo,
> Frank Barknecht hat gesagt: // Frank Barknecht wrote:
>
>
>> I guess (without looking), that somewhere in [comport] this
>> information is discarded.  Probably it shouldn't be discarded, if
>> you want a timing resolution better than 64 samples.
>>
>
> I now had a quick look at comport.c and it already is using clocks for
> reading from the comport, but just writes to the port whenever
> messages come in, which is quantized to one block. So you'll get
> jitter. I think, introducing an unquantized timing similar to how
> vline~ in d_ctl.c handles it (by using "x->x_referencetime =
> clock_getlogicaltime();" and then working with "timenow =
> clock_gettimesince(x->x_referencetime);") could get rid of the jitter.
> It wouldn't be necessary to make a signal object [comport~].
>
> At least that's what I believe: This clock stuff is quite confusing.
>
> Ciao
> -- 
>  Frank Barknecht                 _ ______footils.org_ __goto10.org__