Max4Live patchers Save doesn't work
Has anyone run into this? Save As and Save don't work at all. I can click the menu items, however, nothing happens. The patchers are very simple, basically a test JS file and basic stuff. I've run into this behavior often. When I close the patch, it asks if I want to save the patch. However, that doesn't work either. The only alternative is to close and hit Don't Save and not save your work. In regular Max, I can save as expected, however I need an amxd file inside Live.
On another note, I'm so confused with how shotty everything seems to be with Max4Live, it's unworkably buggy most of the time. Now, I try to reduce things to a single Javascript file. I know for a fact I can open, save, modify text files and target the API. Working with M4L is kind of a nightmare though and I avoid it! Is anyone else seeing huge problems like I am?
BTW, I'm on a Macbook Air High Sierra. Ohh and I just got this message just now when I tried to save the patch as a Max Audio Effect instead:
It may be a folder permission issue.
I experienced the same problem on a Win10 laptop. It's a laptop I use at work and its default home folder is set to a coroprate fileshare with some "smart" mirroring functionality for offline usage I guess. Problem is that this folder is used as default for some local files, e.g. "User Library".
Going through all folder assignments in Live's preferences and making sure all pointed to local folders on the C: drive fixed the problem.
Thank you Peter, there might be something to permissions getting corrupted or something? I'm not sure what was going on.. but after restarting computer, opening an empty set, opening a blank Max patch, I could get things workable there, and then eventually things got fixed in the old project? ...strange. Yesterday I found that I couldn't change record quantization on a project or rename clips.. also weird behavior! There's some funky stuff going around
I've also experience this several times, and other related (I think) issues.
I reported it and it seems Cycling has now understood what's happening, so hopefully we'll see a fix soon.