Hi. In testing OSC, Ive actually been able to reproduce some crashing
with Quartz Composer with a fairly simple Max patch.
creating a OSC Receiver with the following keys
/box/led
/box/led_row
/box/led_col
as sending within max/msp via the udpsend object
the messages /box/led <float> , /box/led_row <float> and /box/led
<col> I was able to reproduce crashing almost immediately.
Does the OSC implementation within Quartz Composer support
hierarchical namespace/keys ? IE
/this/is/some/hierarchy/of/OSC
/this/is/some/otherhierarchy/of/OSC
or is the namespace 'flat'?
/thisworks
/this/does/not ?
Id be surprised if OSC under Max/MSP was the culprit, as it is one of
the de-facto OSC 'munging' environments, and has worked with every
other OSC implementation ive seen. I would note that sending from
Quartz Composer to Max/MSP seemed to work. As a note, I used UDP port
7400, and used the local loopback 127.0.0.1 network. Is it appropriate
to send Crashlogs to the list?
Thank you.
Kevin, that's just the thing - I can see that it should be
generating a structure, but I only ever see 'Type:Structure' when I
mouseover the output from the OSC Receiver. Passing it through a
Structure Index Member > Image With String > Billboard gives me
nothing.
I'm attaching a Max/MSP patch that acts as a fake Monome for testing
purposes. You'll need the free Max/MSP runtime to use it.
<_40h_fake.mxb>
Surya
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
