banging jit.matrix does nothing when bang is from udpreceive
So I narrowed my problem down a bit. When you send a bang to a jit.matrix it's supposed to send out the matrix (as a 'jit.matrix name') out its left outlet. When the bang (or any message) is received over udpreceive, and then the bang (or other message translated into a bang) is sent to the jit.matrix, the jit.matrix only outputs a matrix for the last bang received.
I have attached a small patch demonstrating this anomaly. Any work around would be greatly appreciated. I believe it is a bug of some sort, possibly in jit.matrix, possibly in udpsend/receive, but it's tough to know for certain.
Thanks in advance!
Here's a quick fix: put a jit.qfaker object between the receiver and
the jit.matrix object. This moves the bangs back into the scheduler
thread, from the queue.
jb
Am 26.05.2007 um 01:07 schrieb sayles:
> So I narrowed my problem down a bit. When you send a bang to a
> jit.matrix it's supposed to send out the matrix (as a 'jit.matrix
> name') out its left outlet. When the bang (or any message) is
> received over udpreceive, and then the bang (or other message
> translated into a bang) is sent to the jit.matrix, the jit.matrix
> only outputs a matrix for the last bang received.
>
> I have attached a small patch demonstrating this anomaly. Any work
> around would be greatly appreciated. I believe it is a bug of some
> sort, possibly in jit.matrix, possibly in udpsend/receive, but it's
> tough to know for certain.
>
> Thanks in advance!
It seems that I missed the reason you're using udpsend... but I
didn't miss Joshua's suggestion to use jit.net.send/recv objects for
sending real matrix data, and nice thing about them is that they can
send max messages too. You can't send a bang, but you can replace it
with some other word, like mybang:
hth,
nesa
Thanks! that seems to be exactly what i needed. placed a jit.qfaker right after the udpreceive and it all works.