I knew this would double post.

scook
There is no limit to the number of cwp files in a folder. I use per-project audio folders and almost always have several active cwp files (and older versions too) in the folder above the audio folder. The only time I make a copy of a project is to make a backup or use the "Save As" to another folder for the final cleanup. I can copy the other cwp's from the original folder if I need them.

I wholly agree.
 
Using Per Project Folders gives you MUCH more flexibility when troubleshooting, and you can be assured that all of the relevant audio files are located within the project sub-folder.
 
The Global audio folder was designed to be used when creating new projects using ctrl + N (because it has nowhere else to store the audio)
 
In my opinion, you are needlessly complicating your entire folder structure.
 
A simple test - say you want to completely delete and entire project including all its audio?
Using global, audio, you would have to to hunt down every audio clip/track associated with the project and hope they were all named correctly when you delete them. This can be complicated if at some point during the project's life cycle you change the project name. Sonar will NOT go back and rename all of the older clips with the old name.
 
Using PPF's, all you need do is delete the entire folder from Windows.

weird requirement to make a template setting work, per project audio folders... I wonder why that is?

Bristol_Jonesey
 
In my opinion, you are needlessly complicating your entire folder structure.
 
 

I'm not sure it is for others to criticize the way people organise their work.  I'm sure it's possible to design a file structure, and stick to it, that would have advantages in certain circumstances.
 
To me, this issue presented by pdarg looks like a bug.  And if it isn't, I'd like to hear the logic behind it.

I did say it was only in MY opinion.
 
If opinions are now being treated as criticism then the days of forum interaction are sadly numbered

Bristol_Jonesey
I did say it was only in MY opinion.
 
If opinions are now being treated as criticism then the days of forum interaction are sadly numbered

I'm not fighting you, just describing a situation that often comes up, much to the thread creator's chagrin.  "Needlessly complicating" is a value judgement in my eyes.  We have no idea  how pdarg works, and it's not up to us to judge the validity of his methods.
 

But his problem would be solved IF he were to adopt a slightly different workflow - and a workflow which is endorsed and recommended, not only by the vast majority of users, but also by Cakewalk.
 
I will say no more on the subject.

In my opinion, it sounds to me like he is needlessly complicating his life too.  Per project folders  make hard drive cleanup a lot simpler. he obviously feels differently, but I am having trouble understanding his stance. Perhaps i am missing something.

For me, perhaps the most important aspect is that per-project folders offer the means to get the desired behavior today, rather in a future version if and when CW were to change it.   You gotta do something between now and then!