attached is a patch that i have been working on for a little while.
it basically makes a matrix (a monome, if you have one) into an editor for clips.
it does what it is supposed to do….but it sure does bring out some strange behavior from Live. crashes mostly.
if anyone can spot anything that i am doing to cause the crashes, i would greatly appreciate the feedback.
It just crashed on me in the OSCbonjour code.
Seems like as good a place to start as any.
Let us know if you find anything reproducible which points to us
ok, thank you. (and i fixed an oversight of thanking you in the patch, didn’t know if you and pukunui were one and the same)
ugh. it had to be the code i didn’t write.
ok, i took out that abstraction and i am still getting an unidentifiable c++ exception. i reported a bug. if it any help, the exception gets thrown in live’s max window
I see warnings like that every now and then with complex API js scripts. Is it actually affecting the way the device works? Do you still see the errors if the device is running in Live?
The difficulty with the device in this thread is the js quite involved. Hopefully if you are able to see it not working in some way then you will be able to point us to where the problem is.
ok, sweet. the crashing has been tamed by removing oscbonjour. if that unidentifiable exception stuff is not my doing i can breathe a sigh of relief and move on.
the device runs well now, so thank you. i will definitely let you know if something seem awry.
I revive this topic to ask:
What is oscbonjour and how does it apply to M4L?
thx in advance, :)
oscbonjour is an external that added some networking functionality (Bonjour setup and OSC if I remember correctly.)
IS there a problem you are trying to solve involving OSC or bonjour?
Log in to reply
C74 IN YOUR INBOX
C74 RSS Feed | © Copyright Cycling '74 | Terms & Conditions
Let us tell you about notable Max projects, obscure facts, and creative media artists of all kinds.