• SONAR
  • Saving a new project works differently
2017/02/26 01:23:11
Kev999
When I create a new project, hit Save and start typing a title, it used to automatically create a folder for the project, assigning it the same name as the project name. It doesn't seem to work that way anymore. It now saves the project at top level within the project drive (along with an new Audio folder there), unless I manually change the filepath myself by typing in a new folder name.
[Version 22.11.0.111]
2017/02/26 07:26:32
robert_e_bone
Hi - I wrote up a post that explains the different choices and results for creating new projects in Sonar, some time back.
 
Here is that content - and it will hopefully help you understand each of the choices:
 
Deciphering Sonar’s New Project Options
 
There are several different ways to create a new project in SONAR, but they don’t all place
audio files in the same location. Here’s how each option affects audio file storage.
 
  • Start Screen “New Project.” The project created from the Start Screen’s New Project option does not default to using Per Project Audio, and saves audio to the folder C:\Cakewalk Projects\Audio. Doing a Save As presents the audio path for manual modification, but any audio created prior to modifying that goes to the path listed above. If you want to use Per-Project Audio, avoid this option.
  • File > New. Creating a project using File > New behaves differently, and does present the path for the audio to be stored in an audio sub-folder because the default for SONAR has Per-Project Audio enabled. The path for the audio sub-folder is populated automatically to create a folder called Audio within the project folder, so as you type the name of the project, the path for the Audio sub-folder is modified to include whatever you are naming the project as the parent folder for the Audio subfolder (because Per-Project Audio is on by default). This option is fine for creating projects with Per-Project Audio automatically on.
  • Start Screen “New from Template.” Creating a new project via this method also presents the path for creating an Audio sub-folder within the project folder, and Page | 70 automatically adds the project folder name to the path to the Audio sub-folder (just like File > New does). This option is fine for creating projects with Per-Project Audio enabled.
  • Alt+F then N. This works the same way that File > New works, resulting in an Audio subfolder within the project folder, and the path is automatically populated as you type in the project name. This option works for creating projects with Per-Project Audio enabled.
  • Ctrl+N. This does not work like File > New, and does not create an Audio sub-folder. It will default to saving audio in the global Cakewalk Projects\Audio folder, though you can change that path during Save As. Audio clips created prior to a path modification to its default will be stored in the global Cakewalk Projects\Audio folder. If you want to use Per-Project Audio, this option isn’t recommended.
Consider starting new projects using the Start Screen “New from Template” option. Aside from the benefit that a template provides (you don’t have to start a project from scratch), as a result of the default Per-Project Audio option you’ll always end up with an automatically created Audio sub-folder, within the main project folder, and all of the audio clips stored properly within the Audio sub-folder.
 
Bob Bone
 
2017/02/26 08:38:54
The Maillard Reaction

2017/02/26 10:58:41
Anderton
Caa2
About 15 years ago I made a simple feature request: Please design the "New Project" dialog window to be resizable so that users can see the entire path to their project and audio folders.
 
It is a feature that will be very helpful to anyone who frequently works with a variety of projects and wants to place them in a variety of specific locations. 

 
I'm not understanding why this matters. It seems to me the only time you use the New Project window is upon creating a project, and you use the Browse button to the right of the Location field to locate the folder where you want to save it. I don't understand why you need to see where you just were; you know you were there because you specifically went there. Then after you choose the folder, you don't see the New Project window again.
 
If you're in the middle of doing a project and can't remember where something is, there's always "Save As" to see the complete file tree.
 
 
Every time I create new project I consider how this obvious convenience has been over looked while a seemingly endless supply of bloat has been rolled out year after year.

 
Probably the reason why this has never been implemented is because a) no one else has ever requested this, and/or b) the devs don't understand why this would be useful. Although you may consider features like Aux Tracks, Mix Recall, Upsampling, bug fixes, VocalSync, MIDI note chase, plug-in load balancing, Tempo Detection, etc. as "endless bloat," I think most users would prioritize those over changing the New Project window size. But, they may simply be in my position and not understand why you consider this crucial, so perhaps you could explain the use case a little better. If others agree this provides a much-needed functionality, then it's not just one person wanting something, which would increase its importance to the devs.
2017/02/26 11:14:07
pwalpwal
to be fair, resizable dialogs are standard in windows these days
2017/02/26 11:53:35
ralf
Essentially, there are only two options to create a new project:
1. Start Screen “New from Template.” / File > New: This creates a new project from a template.
2. Start Screen “New Project.” / Ctrl+N: This creates a new project from the default template.

In the first case, you get a dialog field where you can specify some project settings like tempo and sampling rate. And you can set the project name, project folder, and per project audio folder. When you use File > New, this dialog also includes the list of templates, while the Start Screen shows this list directly. In both template lists, you can set the default template to be used for the second case.

If you don't specify a project name - either by using the second option or by not entering a name in the first option - the project doesn't use a per project audio folder, except if you save it with the "copy audio files" check box active. (I think there is no longer a way to get rid of the per project audio folder, once you decided to use one.)
2017/02/27 20:36:13
Kev999
ralf
...I think there is no longer a way to get rid of the per project audio folder...

 
Yes, apparently. The "Use Per-Project Audio Folders" option is no longer present. Obviously it's redundant, since there are no other options.
2017/02/27 20:42:06
Kev999
robert_e_bone
  • Start Screen “New Project.” The project created from the Start Screen’s New Project option does not default to using Per Project Audio, and saves audio to the folder C:\Cakewalk Projects\Audio. Doing a Save As presents the audio path for manual modification, but any audio created prior to modifying that goes to the path listed above. If you want to use Per-Project Audio, avoid this option.

 
Thanks. I'll avoid this method in future. I've been caught out a few times recently when I've suddenly been asked to record something and needed to get started quickly.
2017/02/27 20:56:26
Anderton
pwalpwal
to be fair, resizable dialogs are standard in windows these days



The question I had was why that mattered in this particular case. If it doesn't matter, it seems counter-productive to have Cakewalk go back and change something that doesn't matter. If it does matter, then we should push for it.
2017/02/28 08:48:19
The Maillard Reaction

12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account