Remembering save paths
I don’t know if I’m just being dense, but whenever I go to save a patch I’ve been working on (using command-s), Max fails to remember the previous save path, even if I’ve saved the same patch multiple times in the same session. It always goes back to ‘Documents’. I then have to navigate back to the correct folder, and select ‘overwrite’. This means saving for me takes about 30 seconds, instead of being a mindless task that I don’t even have to think about. Anyone else having this?
yes, I am experiencing this as well. Same when loading samples and open files.
Max5.02, MBP2.33, OS10.4.11
In my setup Max remembers the path, but always asks me if I want to overwrite, as if I were doing a "save as" instead of "save".
Yeah, I should have said.
Max 5.0.2, OS X 10.5.3, Mac Pro Quad 2.66
same here voxish. it’s not too annoying though and cycling im sure will fix it in an update eventually. i have problems with my file preferences. if i create a folder and indicate in my file preferences to look for patches in it, it’ll sometimes work and sometimes not. i’ve ended up just putting everything in the cycling 74 patches folder, which isn’t too troublesome, but all the same, i’d like to be able to create my own folder for patches.
Actually, I’ve always found file prefs in Max to be troublesome. I was hoping it would get better in v. 5 and not worse. It’s early days, though, and the file system seems to be a priority right now, so…
I never had any problems with 4.6, so I guess this is just teething problems. I’m loving the rest of 5 though, although it does slow down after it’s been open a while as mentioned in another thread.
What i understand from the initial post is that when you go to save a previously saved patch, you get a save dialog instead of just automatically saving, correct?
I can’t reproduce this here with Max 5.0.2. Drop a note to support at cycling74 dot com and we can take a closer look if you are still having this problem.
Cycling ’74 Support
I was also suffering from the same problem and was hoping the upgrade to 5.0.3 would help. It didn’t. But with a little experimentation…
If you have left your UNIX file path in the dust and you are silly enough, like I was to use slashes (/) in directory names in any part of the file path, you will get a Save As dialog for Save, rather than just a quiet saving experience. Once I changed the name of my projects folder from "MAX/MSP/Jitter projects" to Max-MSP-Jitter projects, my Save worries were behind me–I hope you find the same relief.
Is this a bug? Or should we all just know better.
Ben, I’d be curious to have you try that out to see if putting slashes in directory names causes the problem to crop up for you as well.
Sorry if this was discovered earlier–I just stopped at this post.
OS 10.4.11, Max/MSP/Jitter 5.0.3, Mac Pro
I can reproduce this. Not sure if it just is this way now or will be fixed, but i’ll log it.
Path separator characters in filenames or folder names will always be problematic in software that permits the specification of full pathnames. At the UNIX level, for example, slashes are illegal characters for filenames. Somehow the Mac works around this in a non-UNIX friendly way. For example, if I add /x to a filename, and I do an ls in the terminal, the name appears with a :x at the end. : was an illegal character in the old Mac OS filesystem. Perhaps it’s some kind of inside joke.
If you create a file called foo/bar.maxpat and you were to try to refer to its full pathname, Max would interpret "Macintosh HD:/foo/bar.maxpat" as a file called bar.maxpat in the foo directory. That is, roughly, the source of problems one might experience with the use of slashes in filenames. We might be able to work around this problem in a limited number of cases such as re-saving a file, but it’s not a priority.
Ha, yup, as I said, we should all know better. And in general, I abide by legal UNIX path names. My Max/MSP/Jitter directory was named by me on a purely subconscious level, having ALWAYS seen it referred to that way (by Cycling ’74 and by all who mention it).
Just wanted to provide an answer to the original poster, if that was indeed the problem.