I agree with Javahut 100%.
Just a very poor design. Never thinking we might save dozens of revisions to the same "Project" folder. The assumption was "One folder, one project file". And that assumption was just wrong.

There really isn't much of an argument here unless there's a parallel argument against multiple, versioned project files. Turn off versioning - problem solved. Simple as that.

Gobbler needs to scan these files, so there definitely is a point to them. If you delete them, Gobbler doesn't find your project. I also believe it makes sense from the way Gobbler works to have them in the same folder of the project file, though I suppose with some effort this might be changed.

I really don't see the problem to be honest. But I'm not the only Sonar user. Everyone is entitled to their opinion. Nonsensical as it may be :p
Seriously, just sort by type, they won't even be in the way anymore, Pick your battles seems the right advice to me.

I agree it could get messy with lots of project revisions in the same project folder, but if you set the folder to sort by file type at least it will bunch them all together and make it easier on the eyes. But yeah a separate assets folder would be ideal if possible.

I get that there are now a few uncessary files for those not using Gobbler, which currently includes me, but also that not seeing those extra files isn't exactly an effort.  And only when you actually need to see the folder contents at all.  It just seems so...   minor.   Comparitively speaking.

I had to look at my project folder with Windows Explorer to even notice these! I habitually open projects within SONAR, so they never show in the open dialog anyway...
 
 

It would be useful if it was useful...to everyone...no?
 
Soon we will have pictures of Cakewalk/Gibson Staff showing up in folders. JK guys but IMO its a waste of time having to go and figure out what they are and they cramp my space and style, even if there is a future use for it.
 
I get this sense of Sonar becoming full of bloatware as of late.

javahut
I would venture to say there are many more people who are NOT sharing projects than are. So putting them in the main Project folder because of a few that might share their project, while many people have absolutely no need to see them... but DO need to see the various main Project files... still makes no sense. If you know you want to share your file... then you either know or don't know that you also need to send the 'assets' file with it (along with all the audio files, which BTW are not in the same folder as the project, but have to sent). If you're sending someone your Project to work on... your already know you have to send your audio folder file. Why wouldn't it be just as easy to send an 'assets' folder with it?
 
Yes, it's not a huge deal... it's just a very inefficient waste of screen space, and extra files that have to be dealt with at some point... when they are, in fact, pointless to many , if not most, users. However, the Project files themselves are a main function of Sonar.
 
You don't have to do the right thing by giving them their own 'assets' folder. But it's damn sure not efficient, and is ugly and annoying to look at a new, additional, useless, 'assets' file for every single Project Save I do. Why not just stick all the audio and wave picture files in there to? That way they'll all be 'in one, easy to locate place'.
 
And on top of that... you're even saying that the files don't matter... a new one is created again every time you hit Save. If they don't matter, and we only need them for info, why even create them in the first place. If at some point they're needed by someone to share a project... just put an extra menu function to 'Save w/ Assets'.
 
Whomever thought this was a good design idea was... wrong.

Perhaps it's you that's really wrong here. You have a limited view of the issue because you don't know what Cakewalk has planned for the future.

Surly if you choose to use settings not recommended by MS because it suits you (view hidden files) then surely you are the one that has to deal with the consequences, in this case seeing hidden files that bother you.

In any case you've also said that because you use a different file explorer you can easily deal with the matter. Really think this is arguing for arguing's sake.

There is a setting in Preferences>Files at the last entry regarding asset files. Uncheck this and you should not be bothered by .asset files any longer.

My experiments with opening projects where these files existed, by using Save As new file name into a new project folder the file is saved with no .cwp.asset files added.

Hi Mike,
 
What version of Sonar are you using? I'm running X3b and that option isn't listed in Preferences. I wonder if the Bakers added that in c or d revisions.