dropfile problem (bug?)
I encounter a weird problem with [dropfile].
Sometimes it will not only output the name of the file/folder that is dropped into the dropzone, but it will first output:
"Macintosh HD:/Applications/Max5/MaxMSP.app/Contents/MacOS/"
It is possible to filter this out of course, but it should not be doing that.
Does anybody else experience this?
(I'm on a mac (osx10.5.6, intel) using v5.0.7)
I get the same thing over here. The faulty path is the same every time, and it happens irregularly, about once every 6 times on average when i drag files to the [dropfile] (by hand).
The amount of stress the CPU is under doesn't seem to matter, I get the same results with all my metros off. Patch size doesn't matter either, it happens using this patch as well (and nothing else):
Using 5.0.7 on an Intel Mac also.
Oh, I tried reproducing this in Max 4.6.3 as well, I was unable to.
Hi folks,
I can't reproduce here with Max 5.0.7 release. Does it still happen after you trash your Max 5 preferences folder?
-Ben
Yep, can reproduce it here, also after thrashing prefs; just keep dropping for a minute, with changing and multiple selections. Maybe it's a Dutch thing. Could it be that max starts to become erratic at or below sea level...
print: read Nox:/Users/jvkr/Library/Preferences/Max 4.6 Preferences Folder/
print: read Nox:/Users/jvkr/Library/Preferences/Max 4 Preferences Folder/
print: read Nox:/Users/jvkr/Library/Preferences/Mase Preferences Folder/
print: read Nox:/Users/jvkr/Library/Preferences/Max 4 Preferences Folder/
print: read Nox:/Users/jvkr/Library/Preferences/Mase Preferences Folder/
print: read Nox:/Applications/prog/Max5/MaxMSP.app/Contents/MacOS/
print: read Nox:/Users/jvkr/Library/Preferences/Max 5 Preferences Folder/
print: read Nox:/Users/jvkr/Library/Preferences/MCP Preferences Folder/
print: read Nox:/Users/jvkr/Library/Preferences/Max 4.6 Preferences Folder/
_
johan
Duplicatable here, as well.
print: Dome:/Applications/Max5/MaxMSP.app/Contents/MacOS/
print: Dome:/linky.html
print: Dome:/linky.rtf
print: Dome:/Applications/Max5/MaxMSP.app/Contents/MacOS/
print: Dome:/linky.txt
print: Dome:/Pounder2.wav
print: Dome:/Pounder3.wav
print: Dome:/Rose clip.mp3
print: Dome:/Applications/Max5/MaxMSP.app/Contents/MacOS/
print: Dome:/shooting stars lyrics.rtf
I'd actually noticed this a while ago (before 5.0.7 it seemed like it was every single time, and it would happen in a standalone regularly as well) but it didn't seem to be causing any problems with my patch at all (aside from an error message saying 'buffer~: can't read' every time it'd load anything, but still reading the correct file)
Note that I can't replicate in the standalone anymore, it seems to not occur in runtime, now.
OSX 10.5.6, MaxMSP/Runtime 5.0.7 (38325), Mac Pro 8 core.
for those who have this problem, here is a little workaround
(please save and reload for the loadbang to work)
`