I am working more with other engineers (using other DAWs), and have just started using Gobbler and would like to take full advantage of its collaboration potential.  I can envision a nice system where I have projects backed up in Gobbler and other engineers can grab the audio files as needed without me having to manually export the files and transfer them.  I add a new track, and it automatically is backed up and made available to collaborators.  Could be very simple and efficient.
 
The problem is that, as far as I can tell, Sonar will not write broadcast wave files (BWFs) within its projects. So if another engineer grabs the backed up audio the tracks and imports them into his/her DAW they won't line up in the right spots.  I know I can *export* BWFs, but is there a way to have Sonar write them by default?  
 
Thanks.

Well if you check in preferences->Files->Audio Datas   (may be different,I have it in french)
There's an option: "Export Broadcast Wave as default"

guigz2000
Well if you check in preferences->Files->Audio Datas   (may be different,I have it in french)
There's an option: "Export Broadcast Wave as default"

Yes, but the OP is not about exporting, but bouncing into a Broadcast Wav inside the project. Would that default setting include bouncing?
 
That Gobbler sounds interesting. Does it sort of break the project structure and make individual tracks available to others (not using SONAR) as if they were picked from the  Project Audio Folder (or MIDI from the Project Folder)?

guigz2000
Well if you check in preferences->Files->Audio Datas   (may be different,I have it in french)
There's an option: "Export Broadcast Wave as default"

Thanks, but that only seems to affect files which are exported, not how standard project files are written.  

The audio files in Sonar are not necessarily what you want to work on anyway. Sonar is a non destructive editor so the audio files don't necessarily contain all the data. The clip, edit and fx data is in the cwp file not in the audio file unless you render it. If you do that you might as well export all the audio files in one pass as BWFs.

In a way,it's just logical... Project soundfiles are just audio data pools. Since clips can reference parts of these files and set/change their positions, there's no use to store a position which in any case won't be used. It enables to copy clips without having to duplicate soundfiles 
 

mudgel
The audio files in Sonar are not necessarily what you want to work on anyway. Sonar is a non destructive editor so the audio files don't necessarily contain all the data. The clip, edit and fx data is in the cwp file not in the audio file unless you render it. If you do that you might as well export all the audio files in one pass as BWFs.

Thanks but I understand all of this.  There are still times it would be helpful to be able to quickly send unedited, dry broadcast wave files. One can do this with "export audio" and it is very helpful.  Being able to skip this step by writing BWFs directly that would automatically uploaded to Gobbler would be a nice addition.  

guigz2000
In a way,it's just logical... Project soundfiles are just audio data pools. Since clips can reference parts of these files and set/change their positions, there's no use to store a position which in any case won't be used. It enables to copy clips without having to duplicate soundfiles 
 

 
I understand, and this may be a reason that what I am looking for can't be done.  But given the potential benefits I am hoping there it way I can do this.