jon2211

normally I would think (read ../MIDI File Folder/Midi File)

would be the relative path from the EXE to the MIDI file. Doesn't seem to work. What's up with that?

normally I would think (read ../MIDI File Folder/Midi File)
would be the relative path from the EXE to the MIDI file.  Doesn't seem to work.  What's up with that?

relative-paths-2

On 30 oct. 08, at 16:12, Jon Grant wrote:

> normally I would think (read ../MIDI File Folder/Midi File)

> would be the relative path from the EXE to the MIDI file. Doesn't 

You can construct absolute path. For that you will need to get the 

location of your application by using the max sendapppath message, and 

generate the proper file path using sprintf or combine.

> So I have this:
>
> C: Drive
> |
> |-------Max APPLICATION FOLDER
> |          -EXE dlls etc
> |
> |-------MIDI FIle Folder
>           -MIDI FIle
>
> normally I would think (read ../MIDI File Folder/Midi File)
> would be the relative path from the EXE to the MIDI file.  Doesn't  
> seem to work.  What's up with that?

You can construct absolute path. For that you will need to get the  
location of your application by using the max sendapppath message, and  
generate the proper file path using sprintf or combine.

Also, I'd be curious if it worked if you first put a single dot before the two dots like this:

Hmm...doesn't work for me. Relative paths (with or without a "./") work for me on OS X, but not on Windows (Windows Server, XP, or Vista). This severely affects the portability of patches, especially when sending to Microshaft-based machines. Any ideas?

Hmm...doesn't work for me.  Relative paths (with or without a "./") work for me on OS X, but not on Windows (Windows Server, XP, or Vista).  This severely affects the portability of patches, especially when sending to Microshaft-based machines.  Any ideas?

Perhaps you can post a specific example of what didn't work?

Relative Paths