I think I get it: the last controller value to be stored in "pack" (thru the
rightmost inlet) was not beeing triggered by anything hitting the leftmost
inlet... as a result, I could never get the extreme values. Typical Pd
programming mistake! I corrected this and now, it works fine.
Thanks for your help.
D.S
From: David Schaffer
Sent: Saturday, October 10, 2009 4:56 PM
To: pd list
Subject: [PD] "pack" object resolution issue
Hello there,
something strange happens to me when routing ctlin signals thru a pack
object and then unpacking the result afterwards: my midi values seem less
precise. I noticed it when using extreme values (either 0 or 127): it gets me
somewhere between 0 and 18 or between 118 and 127. As a consequence, similar
midi fader positions give me slightly different values, which is annoying
(ctlin's direct output works fine and always gives me the same results). Has
someone else been thru this before? Thank you!
D.S
http://www.flickr.com/photos/schafferdavid/
http://audioblog.arteradio.com/David_Schaffer/
--------------------------------------------------------------------------------
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
