it was the touch outlet from route, not touchbyvox which works this way, perfect, thanks!On 11 Aug 2021, at 02:38, Daniel Iglesia <daniel.iglesia@gmail.com> wrote:Hi1) The multitouch widget sends out 4 different streams of data, each sorted a different way, for different desired usage. In your case, if you listen on "touchesByVox", the first element is the voice number, so a [route 1 2 3 4 5] should separate it into a stream per voice. Is that what you get? (it's been a while since I looked at it)
fair enough, should work for me too!2) There is not a single official format for saving, but you can read and write text files to/from disk with the vanilla objects, and come up with your own state-saving pattern. Rather than come up with a universal format, I assumed every user would have their own custom needs and would prefer their own mechanism.
On Tue, Aug 10, 2021 at 2:41 PM Simon Iten <itensimon@gmail.com> wrote:For MobMuPlat devs or users…
what is the preferred way to receive data from a multitouch GUI object? i.e. send out a bunch of MIDI CC messages according to 3 or 4 fingers x/y position. (two CC messages per finger)
i looked at the documentation and i can see the values, but i am stuck at extracting x and y independently for each finger “voice”. i don’t get the magic with [list prepend set] into [list trim], or how i can get a numeric stream (one value per outlet) from it.
thanks, and sorry if this question is obvious
also, is there a mechanism to save states like in pdparty? saving to a .sav file and recalling later?
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list