zarby

i want to if it's possible to create special folder in a project, other than data other media ...

hi,
i want to if it's possible to create special folder in a project, other than data other media ...

how-to-create-a-special-folder-in-a-project

Basically, I have a sub-folder hierarchy that I would like to maintain (e.g., audio files in sections) in the media folder, but it seems that Max either flattens the structure (consolidate), sometimes placing audio files in the wrong areas (other folder), or doesn't see the files if I don't place them at the root media folder level. Is there anything we can do about this? I'm sure it's something simple that I'm missing...

Basically, I have a sub-folder hierarchy that I would like to maintain (e.g., audio files in sections) in the media folder, but it seems that Max either flattens the structure (consolidate), sometimes placing audio files in the wrong areas (other folder), or doesn't see the files if I don't place them at the root media folder level.  Is there anything we can do about this?  I'm sure it's something simple that I'm missing...

Seems that this is not currently possible, which makes it difficult to port existing projects to the Project format. Sub-folders are a must, to keep projects organized. Hopefully we'll see that feature in an upcoming release.

Seems that this is not currently possible, which makes it difficult to port existing projects to the Project format.  Sub-folders are a must, to keep projects organized.  Hopefully we'll see that feature in an upcoming release.


I would like to organise my numerous audiofiles in my 'project' 'media folder' in order to : 

- share a clean organisation with co-developpers and users

I would like to organise my numerous audiofiles in my 'project' 'media folder' in order to : 
- classify audiofiles by categories 
- autopopulate audiofile menus
- update easily with new files
- share a clean organisation with co-developpers and users

when i am not mistaken there is one thing about "projects" where they do not differ from other locations; you can always work with paths to files and folders 

 by making use of "path" to [thispatcher].

having all media files in the media folder is like having files 

in the search path and this is not disturbed by knowing where they are using another method.

when i am not mistaken there is one thing about "projects" where they do not differ from other locations; you can always work with paths to files and folders relative to a patcher-on-disk by making use of "path" to [thispatcher].

having all media files in the media folder is like having files somewhere in the search path and this is not disturbed by knowing where they are using another method.

But if using a "path" to [thispatcher] method, the hole advantage of the project, which is to find dependencies everywhere is lost. 

Because when using the project on another machine or repertory, the original path will then be lost, unless reconstructing a custom path character chain, local to the project, which is complex in max and subject to bugs.

I have tried to create folders in the Media folder of the max project and move an audio file into it, but then, the audio file can't be found anymore.

But if using a "path" to [thispatcher] method, the hole advantage of the project, which is to find dependencies everywhere is lost. 
Because when using the project on another machine or repertory, the original path will then  be lost, unless reconstructing a custom path character chain, local to the project, which is complex in max and subject to bugs. 

I have tried to create folders in the Media folder of the max project and move an audio file into it, but then, the audio file can't be found anymore.


working with full paths is a PITA - but can´t you avoid using full paths? 

portability is basically the idea of relative paths and to my knowledge the only thing you can do when your files are outside the max search path.

(it might be that i misunderstand something about 

working with full paths is a PITA - but can´t you avoid using full paths? 
portability is basically the idea of relative paths and to my knowledge the only thing you can do when your files are outside the max search path.

(it might be that i misunderstand something about projects)


If I'm not mistaken, "projects" have one characteristic in common with other places: you can always work with paths to files and folders relative to a patcher-on-disk by using "path" to [thispatcher]. The search path is equivalent to having files somewhere if all media files are in the media folder, therefore knowing where the files are using another way won't interfere with this

If I'm not mistaken, "projects" have one characteristic in common with other places: you can always work with paths to files and folders relative to a patcher-on-disk by using "path" to [thispatcher]. The search path is equivalent to having files somewhere if all media files are in the media folder, therefore knowing where the files are using another way won't interfere with this. 

how to create a special folder in a project?