Customing project folder structure

[outofhand]

Is it possible to change the default project folder structure in DP?

I like to save project versions with datestamps. Further, I save datestamped VI/rewired app versions along with the project version.
But I want "master" folders for audio files, analysis files, plug-in data etc that are *not* datestamped.

Here's the problem: DP seems to always make folders for audio files, analysis files, plug-in data that sit *right next* to the project files.

I can't see any way to tell DP I want these folders for the project to sit in another location.
I've tried setting a new "take folder" in the Audio Monitor window, but it makes no difference - DP still makes an Audio Files folder next to the project file.

To put it more simply:

Here's the folder/filestructure I want:

> Project folder/
>> 20110503/
>>> 20110503 DP Project File
>>> 20110503 VI Drumkit Version
>>> 20110503 Rewired App Version
>> 20110505/
>>> 20110505 DP Project File
>>> 20110505 VI Drumkit Version
>>> 20110505 Rewired App Version
>> Audio Files Folder/
>> Analysis Files Folder/
>> Plug-in Data Folder/


And here's what DP is actually giving me:

> Project folder/
>> 20110503/
>>> 20110503 DP Project File
>>> 20110503 VI Drumkit Version
>>> 20110503 Rewired App Version
>>> Audio Files Folder/
>>> Analysis Files Folder/
>>> Plug-in Data Folder/
>> 20110505/
>>> 20110505 DP Project File
>>> 20110505 VI Drumkit Version
>>> 20110505 Rewired App Version
>>> Audio Files Folder/
>>> Analysis Files Folder/
>>> Plug-in Data Folder/
>> Audio Files Folder/
>> Analysis Files Folder/
>> Plug-in Data Folder/


Make sense?

Can DP actually support the custom folder structure I'm trying to get here?

[MIDI Life Crisis]

No on both counts. Makes no sense to me and DP cannot do whatever it is you're trying to do. The folder structure is the folder structure. You can create sub folders in the BTD process, but soundbites need to be where they are supposed to be.

I would suggest a file name convention and a system of personal folders you create to save the data as you want to see it. But DP wants the audio in the audio folder.

Unless someone else has a better idea...

[Tim]

You can have multiple project/sequence files that share a common audio files (and the rest) folder by doing a save-as to the same folder, and choosing to NOT duplicate audio files.

[MIDI Life Crisis]

Tim understands the question! Is that it? One folder to rule them all? Won't that make things rather "difficult" after a time? I am not grasping the value of what the o/p is trying to do here. Clearly, my ignorance, but I'd love to know. Well, I'd like to know. I love ice cream...

[Tim]

Actually, looking at the o/p again, I don't think I got it. It looks like he/she already has multiple projects sharing a common audio folder.

[MIDI Life Crisis]

It would appear to be a somewhat convoluted method that doesn't make sense to me, but again, if I understood the logic behind it I could make a better argument against it...

[Shooshie]

I'm also unsure of what he's asking, but if I'm reading the little >>> thingies correctly, then it appears that Tim got it right. He has saved complete copies of the project (including audio) inside the project folder, when all he really had to do was just save-as without choosing to duplicate audio.

That is… assuming I guessed it right.

Shooshie

[zaratero]

I also think Tim got it right. Why not simply use save as without copying soundbites and loose the folders? That´s how I do it. In your case:

> Project folder/
>> 20110503 DP Project File
>> 20110503 VI Drumkit Version
>> 20110503 Rewired App Version
>> 20110505 DP Project File
>> 20110505 VI Drumkit Version
>> 20110505 Rewired App Version
>> Audio Files Folder/
>> Analysis Files Folder/
>> Plug-in Data Folder/

[FMiguelez]

.

Part of his post I think I understand, but not the motives behind it. Perhaps if the OP tells us exactly what he wishes to do, we could offer ideas.

Now, he mentioned trying to change the Take Files location when recording.
They DO work and make a difference... you can tell DP where you want your NEW to-be-recorded audio to be placed (it can be anywhere in your computer, but the folder will still be called Audio).

What is not clear, is if all he wants to do is a file/project naming scheme.
If so, I've tried many. The one that works best for me is:
Short project file titles that reflect any major changes or stages I'm currently working on, preceded by a ordering number. For instance, I will have:

01 First Sketches------------- (Manual Save As...)
-----01 First Sketches 2
---- 01 First sketches 3....1000000000 (if I'm not inspired)------ (these are the automatic or manual saves)

02 Composition
-----02 Composition 2
-----02 Composition 3
...

03 Orchestration
-----03 Orchestration 2
-----03 Orchestration with stupid changes by client
...

04 Preliminar MIDI Mix
------04 Preliminar MIDI Mix 2
------04 Preliminar MIDI Mix Brass added

......etc.

That shows me the files in a writing PROCESS order. If I need dates, I just press ⌘I, or do a good Spotlight search.

Of course, if I misunderstood the question then I'll look like an arse... it wouldn't be the first time either

MY ADVISE: Just leave the DP files alone the way MOTU intended.
If you need further organization, try using Aliases as if they were SBs (pointers) instead.

[outofhand]

You've pretty much got it.... I'm trying to maintain versions/history where a project is defined not just in DP, but across multiple applications. I use MaxMSP via ReWire, NI Battery and a few other things. If I make a change in MaxMSP I want to be able to save that, but also save the relevant DP host file that it related to, and the version of the Battery kit that was in use at the time etc etc.

I am not duplicating audio files when saving. The Audio Files folders inside the datestamped folders are empty. But DP makes them, seemingly when I save.

The only folder that actually has audio in it is the master Audio Files one at the root level of the project. The audio files all go into the one folder because all the project versions refer to them... and they're not application files so never really get looked at directly.

Why not simply use save as without copying soundbites and loose the folders? That´s how I do it. In your case:

> Project folder/
>> 20110503 DP Project File
>> 20110503 VI Drumkit Version
>> 20110503 Rewired App Version
>> 20110505 DP Project File
>> 20110505 VI Drumkit Version
>> 20110505 Rewired App Version
>> Audio Files Folder/
>> Analysis Files Folder/
>> Plug-in Data Folder/

Yes, this appears to be the only way to go. I'm just trying to be a bit cleaner.... I can get into hundreds of project versions.

Why use datestamped folders instead of v01, v02 etc... ? Cos you never run out of numbers and never have to worry if you've zero-padded enough

[zaratero]

Yes, this appears to be the only way to go. I'm just trying to be a bit cleaner.... I can get into hundreds of project versions.

As someone suggested I´d go the alias route instead of messing that folder. Default is a good thing for consistency IMMO. I create a "temp bounces" folder, "deliveries" folder and "finals" folder in the project folder and create aliases in there to the audio files in the audio folder .