Rickddd

^^^^^ what he said.

That may be for some, but that's not the case with mine. I have one master directory for all my projects, and within that, are the folders for each project. But even if what you say is true, then having a long path that cuts out all or part of the actual file name isn't very useful either. I do remember many years ago when this worked flawlessly. I'd much rather see the file names. Keep in mind that some people, and me for sure, backup with sequential names, for example I'm working on a song called "Wayback". So I will periodically "save as": wayback1 wayback2 wayback3 wayback4...... etc. At the end of the day it's just an annoyance. But it would be a nice touch forward if it were fixed.

If I am coming back to a project, I open by clicking on open, selecting the project folder, then selecting the last saved file which is at the top of the list because I have sorted by reverse modification date. If I am in the middle of a project and close it for whatever reason and want to come back to it quickly , I will use the recently opened files list. (The one that I posted at the start of this thread). I do not use recently opened files for opening a project say the next day or beyond, because recently opened files list is not updated if there has been a crash in sonar. So to be on the safe side, I start in that scenario by the 1st method I listed. (It would be wonderful if they could mod it so that if sonar crashes, the true recently opened file is listed.) I have never manually typed in a name. Truth of the matter is I have for a long time I tried to realize if there is a pattern of what does what. I'm normally pretty good at picking up such patterns. But have never made rhyme or reason out of this one. Note that YEARS ago, in the before times, it didn't do this . But at some point in the last few years it started. It's not a huge deal, just annoying. And should be a fixable thing if the devs put their mind to it. (I was a programer for years....)

I have a question. And it's certainly no big deal. And it's been an issue for years. (it wasn't alays like this ('talking Cake I keep all my projects in the same parent directory: c:\cwtempC Yet when I look at my most recent files, some show the full path, and some not. Am I doing anything wrong? Rick

Just want to chime in and say I still see this kind of thing once in a while and it is super annoying.

Please view this topic concerning sonar autosave feature:

I hear ya. I've done the same thing... frequent CTRL-S plus my songs can have a couple of hundred sequential files, e.g., songname1.cwp, songname2.cwp etc. Still, even though I'm VERY diligent about quick manual saves, statistically, there have been times when my mind was "in the zone" and Murphy's law took effect. There's almost nothing I hate as much as having to redo work I painsakingly just did minutes ago. The good news is this: @msmcleod's suggestion in his post above works beautifully. I set mine at 5 minutes and zero events. I still do my manual saves, but msmcleods method provides a 2nd safety net to catch me. CAKEWALK: This autosave issue has been around for years. Time to fix. There has to be thousands of users that struggle with this not knowing WTF is going on.

In preferences, file > advanced you can specify an auto-save like: auto-save every [x] minutes or [y] changes. Here's my question. When I use this feature I see sonar auto-save maybe every 30 seconds (just appx, never really measured it) no matter what I put in those blocks. For example, I recently tried: auto-save every 21 minutes or 89 changes. And it kicks into auto-save every few actions that I perform. As I have to fast system that saves to a SSD so I live with it, but it is annoying. Real annoying. And keep in mind saving to a SSD wears it. It's not free. This is not an issue just with cakewalk sonar, its been this way in previous versions. Am I doing something wrong or interpreting teh auto-save settings wrong?

I don't mean to hurt any feelings of the cake bakers, but I've thought since day 1 of the the new sonar that the Bandlab free version was WAY easier on the eyes. Yeah, its a little boxy, but my eyes went "ah....." as I worked with it. The new sonar, as much as I like a lot about it, my eyes goes "yikes..." I've seen so many updates that listed "improved colors" and maybe they were, but they were improvements to color schemes and visual design (to my eyes) that fundamentally fell short of what cakewalk bandlab had achieved from the git-go. I get it - the bakers needed to distinguish it from the free version, but at what cost? I'd PAY to have my cake and eat it too... And as someone mentioned here above, the small check-marks and symbols don't help matters any. Again, let me state that I'm a fan of CW... been using it since Cakewalk Studio a dozen years ago. But the current visual design.... sucks. New colors alone are not going to make it as easy on the eyes as the prior version. And just to be clear..., and maybe its just me, every time I open it up I think "ah... I miss the good old days". I feel giving those of us that feel this way an option to revert visually to what once as would strengthen product loyalty. Just my 2 cents.

When I went back to the previous day, all was well. When I looked at the 5 or so files from the same project of the current day, they were all buggered the same way (even though on screen things looked fine at the time of "save-as"). Those 5 or so files were the result of various "save as" actions. I hadn't opened any of them when I did the "save as", which I did for protection. Note that the "auto saves" during the current day were also buggered. Thankfully, I have now manually put humphy-dumpty together again, and it seems to be holding. Thanks for asking.

I tried to send two of them, but they (even singly) exceed the boards limit of 4.88 mb. I tried zipping.. but not enough. I asked Jonathan for help on what to do.

I will send it. Note that I did not open the file in any older sonar version. Rick

This happened a couple times to me a year or two ago when I changed over from Bandlab to Sonar by Bandlab. I happily had not seen it again until now. What happens is this... all of a sudden, after a "save as", the next time I open that up, all the individual tracks hop out of their assigned track folders (e.g., guitar, keyboards, vocals...). The track folders that were once used are still there, but are now emptied. See image attached. Note: The top two tracks "Verse" and "Chorus" were never in track folders. The rest of teh tracks were spread in the track folders you see in the image. Now they are in just teh guitar folder. Also, this is a new project which was started in Sonar in the last week or two. If I'm somehow doing this by accident.. I doubt it but who knows... visual studio (programming software) has a cool feature to protect from accidentally moving a bunch of files into a folder... it detects if there is an excessive amount of relocations into a folder and pauses to warn the user "are you sure?". I know when I posted about this a year or two ago no one else experienced this. Maybe the same this time. ??? I install all the updates to Sonar as they are released. I am on Win pro, 32GB, I-9700. Any thoughts?

Thank you for weighing in because I was able to install .06 that way. There's still a follow-on issue - the 11MB prochannel won't install. No error message, just never installs. I did try to install it as well from the CPC. But I got that new .06 version and that is great. THANKS!

I tried to upgrade my 2025.05 to the new .06. The error message I immediately get is "Requires Cakewalk Sonar Version 2025.05". But that is the one I have. On thing that may have initiated this is I saw a 11MB prochannel update that I installed first. Maybe that screwed things up. Help.