jweb limitations / behavior in M4L
Using jweb in a Max for Live device behaves different when its running in the device chain or in the Max Editor, depending on the features one uses.
I try to use PixiJS, which works as long as I am in the Max editor, but it stops working, when I close the editor and let it run in device chain inside Live.
In the attached M4L device there are several simple examples, that use different approaches and techniques, but none of them work in Live's device chain - but all of them in the Max editor and I don't know why.
Are there know limitations using jweb inside Max for Live that I've missed?
Using TwoJS e.g. works, but its not that versatile and as PixiJS uses WebGL (or WebGPU), it should have a great performance, but maybe this is also the cause of the trouble.
Although, if you load PixiJS's website via an url message into jweb (inside the device chain - see the "browse PixiJS" button), its seems to work, but the animation seems to be slower, which might be a hint that WebGL (and WebGPU) isn't fully supported or that some fallback is used.
Any ideas?
What versions of everything are you using? What OS? Your device appears to work for me in Max 9.0.3 and Ableton Live 12.1.5.
I'd recommend submitting a Support Ticket here:
https://cycling74.com/support/contact
Thanks @Ben Bracken for giving it a try.
I work on MacOS 14.6.1, Ableton Live 12.1.5 and its bundled Max version, which is 8.6.5 - and I got a dedicated Max 8 License as well, but currently no Max 9.
As you are also running Live 12.1.5, I wonder if you use a regular version and just setup Live to use the separate Max version 9 via Live's preferences (for others who might wonder how its done : https://help.ableton.com/hc/en-us/articles/209070309-Using-a-separate-Max-for-Live-installation ), or do you use a beta or developer version of Live from your colleague over at Ableton?
But anyways, I will submit a support ticket.