I moved to Max 6 recently in an effort to prevent my M4L/Ableton crashes (which didn’t abate so I just gave up on that for now).
It’s working fine for me. We’ll need more details.
To demonstrate "autowatch not working".
1. Load the patch below with watcher.js as attached:
autowatch = 1;
2. I see "loading 3" in the Max window.
3. Now change the post message in the JS file to "loading autowatch".
4. I see nothing new in the Max Window.
5. Clicking on the "compile" button, I see "loading autowatch" in the Max Window.
6. Sending the messages autowatch 1 or autowatch 0 into the patch has no effect.
In this setup, the compile button does work. In my more complex setup, the compile button does not appear to work. If needed, I can distill that down later into a more complete test.
----------begin_max5_patcher---------- 416.3ocuTtsaCBCCF9Z3oHJZWxp.FsEs61ywzTUJ3QCBRPIg1tU028QbnmVW OnI1twRw1w92e4vFeO5b4ZPSIOSdk34sw2yCcYc30u1iVyVmUwzXZTirnnBn AtPxVSEXLez.tZP4BCk7VeTQaMWzEG2YTuyFlIaAWTLSAYF2tRmNJLfjXMwg 6r6qRCSwpACnlAB17JrSgG5fSBmzBdNJU47xGmRst156aMA24LVCZMqX+PZf 0nPorVibkU9jGhtHANL9uKEFM+SLPT7nvehJwWgJoHUdxZSsamDkdDVt4nmP ORGhNDhQdQwYUCITxj0M7qbiXv3QLdAIAsi+E7HdX4g.V0U0yvQolfWQ.0nR 8.AknaAE20ioSN6syMgx3q.k9HZ1RHeVWxcMcFyXT74sF2mFd6YyEdlhwPvt CunznUbw2+1AGNq+SYtV1px1gM2K5.xgALGzFtfY3RwQ4jbRNK344f33uMx4 ZqDy2qwyN6uW0jbGpY7+lZh+CUi6fi0zrDT59RhBo6YQoTYWNI.WxEtkXEoJ XIeW9i8sUaq+WfJDABI -----------end_max5_patcher-----------
Here’s what I did.
- saved your js file to a folder on my desktop
- made a new patch with your code and saved it in to the same folder as the js.
- added a js object to the patch to load the js, verify that is loaded ok.
- opened the js in a text editor and changed the post arg
- saved the js file i the external editor and saw it updating in the Max window as expected.
This is how my workflow used to go before I got Max 6. Once I got Max 6, this workflow ceased to happen for me.
Sorry, this must be frustrating for you if you can’t repro.
Um. I can make you a quicktime screen movie showing me going through these steps, if that would help – it’d be a bit large but probably clear enough, I could put it on YouTube?
Could it be some setting in Max that I could re-initialize?
I’m loathe to restart the machine as I have a lot of work in process, but that could be done I suppose?
I have of course quit and restarted M4L a few times.
Oh, I should add that I do all my work, for both Max and Max for Live in ~/Library/Application Support/Ableton/Library/Presets/MIDI Effects/Max MIDI Effect, perhaps that’s somehow the issue?
All right. I made a screen movie which appears to demonstrate this bug from scratch, and also to show an anomalous error in the Max window that might well be related.
It’s uploading as we speak, it’ll take about 20 mins, and it’ll be here. I’ll update this post when it’s finished uploading.
And it’s up, 3 minutes and 11 seconds of thrills!
I click compile a few more times, and each time I get the error, and the message.
I close Max and restart it by double-clicking on the Max patch. Now everything’s OK. I demonstrate this by opening the Max editor and changing the JS – you can see the message print correctly in the Max window.
Now I fire up my external editor and change the file.
No new message appears in the Max window!
Then I open the JS file from inside Max, and it appears to have not changed…
I go through this procedure one more time to check, and that’s it.
Is your Max MIDI effect folder in your search path? If it is not then this looks right to me.
You save the js into that folder before you have saved the patch there, so the search path for the file does not exist.
I think the compile message forces a re-read, at which point the patch is in the search path and it works.
Yeah? Or maybe I’m missing something.
Max MIDI Effect was not in my search path. I put it in my search path and reran the experiment from scratch, and got exactly the same results.
So clearly somehow my system is different from yours. Under no circumstances does autowatch do anything for me, whether or not the .js and the .maxpat are in my search path, and it always seems to work for you.
How could our systems be different and cause this? I’m running 10.6, on a vanilla MacBook…. my Max 6 is a fairly fresh install and I’ve installed no other software…
Ah ok. Yeah seems like we aren’t doing very well with the newly created files from the js object.
Thanks for persevering with this and sorry for the trouble. We’ll have a look at it for sure.
Particularly, I don’t care about the initial errors. What I care about is autowatch not working. The other issue is irrelevant, really – it just came up during my demo…
In the meantime, I think you can workaround this by creating the js file before loading the js object. Autowatch should then work fine.
Debugging is hard — too hard.
Interesting idea, but I get the issue even when there are no syntax errors. :-(