• SONAR
  • CAUTION! - Bouncing Tracks (p.3)
2013/04/08 13:47:53
brconflict
Maybe I should have stated the OP a little more literal. The second post was an update, and a saving grace. When I said it cost me, at that time, I had assumed it would. Sometimes people say things in a sense of what's coming vs. what just happened. Like, "The car engine blew. That just cost me this entire trip". 
2013/04/08 14:38:12
FastBikerBoy
brconflict


FastBikerBoy


Just to clarify something. When you say "Bounce" do you mean "Export"? When you bounce tracks you specify a track where you want the bounced audio to end up but not a physical location on your system - that's one of the main differences between bounce and export.

You do specify a location when you export but that shouldn't remove the original track, but then neither should bounce to track. The only thing that removes originals is "Bounce to clips".

I'm not trying to be pedantic just understand what happened.

Karl, yes, "bounce to clips". In the Audio folder, I could see "bounced" filenames with a number (nnn). I did have many other bounced tracks in the Audio folder, but for some reason, these several didn't make it in there. 

I have mixed feelings about Cactus Music's response in that I agree with much of what he says, but it's easy to assume I'm not doing something right. I try to keep my process as simple and structured/clean as possible. This one threw me for en entire loop. If all my bounced clips made it correctly into the Audio folder as expected, then I'm scratching my head as to why some bounced clips didn't. Maybe it would help to know that I bounced many clips from the one session/project in Sonar, but only some of them made it into the Audio folder. I thought maybe, perhaps the number in parenthesis had somehow changed or been corrupted, but the audio simply wasn't there. This was after two manual backups, one locally, and one off-site of the same folder at different times after the bounces.

Anyway, back to Karl, what you mentioned is the reason I pledge caution: Bounced clips doesn't ask "where", they just do it as designed. 

I won't say I didn't do something wrong--that's still quite possible, but what could that have been for something so simple? I just found this really odd, and I was nearly out some cash to have the band to come back in to re-track what I'd lost. 

All is well now, though. I'm just preaching a little caution when backing up Audio or bouncing to clips. 

I'm probably going to appear a bit stupid here but I'm still trying to get a handle on exactly what you mean. If you select a clip or clips and then "Bounce to clip" (either from the right click menu or the clips menu in the TV) - the clip is bounced in situ and replaces the original(s). I'm a little confused as to what audio folder you are referring to. Do you mean you are trying to  manage the clips outside of Sonar? i.e. in your project or global audio folder? Or are you referring to a track folder within Sonar?
 
If it's the former that's definitely not a good idea (as you've found out) the only reliable way of using clips outside of Sonar is to export them with the export function when you do get to choose where to put them. If it's the latter I'm not sure what's happened as even if the bounce failed the original clips should be retained.
2013/04/08 15:03:10
Kalle Rantaaho
FBB, you're not alone. I don't understand anything of this.
2013/04/08 15:08:02
John
All I know is I am confused, still. 
2013/04/08 15:12:26
paulo
brconflict


Maybe I should have stated the OP a little more literal. The second post was an update, and a saving grace. When I said it cost me, at that time, I had assumed it would. Sometimes people say things in a sense of what's coming vs. what just happened. Like, "The car engine blew. That just cost me this entire trip". 


Alright, fair enough, but your update post said that you found them elsewhere on your off-site back up which still implied that the project file you were talking about had lost both the edited clips and also the original recordings, so to be clear, there was no audio at all for the tracks in question before you found your off-site back up ?
2013/04/08 15:20:14
stevec
All I know is I am confused, still.

 
I believe the OP used Bounce To Clip, and then found that specific audio files representing the bounced versions were not in the project audio folder along with all of the other bounced clips/wave files.
 
This is fresh in my mind since I've been copying specific bounced clips (split portions of longer tracks) into S1 for work with Melodyne.   I then take those bounced versions from S1's project folder and copy them back into my SONAR project audio folder, and import them into their respective tracks to replace the original versions.   So I have been working directly with bounced clips over the last few weeks on a fairly regular basis.    However... every clip has been in its expected location.
 
2013/04/08 15:56:58
brconflict
If this is terribly confusing, then let me start at the beginning by asking, because there is a definite answer to this, and because apparently I don't know: Where exactly does Sonar store "Bounce-to-Clip" audio, by default? From that answer, I can move forward to explain what I find odd and what possibly broke for me. Thanks! 

2013/04/08 18:16:42
jb101
I always "Use Per-project Audio Folders" as it makes keeping track of everything easier, including sharing projects and backing up.
 
When you do this the "Bounce to CLIPS" wavs are all saved in the project's audio folder.
2013/04/08 19:20:30
Danny Danzi
jb101


I always "Use Per-project Audio Folders" as it makes keeping track of everything easier, including sharing projects and backing up.
 
When you do this the "Bounce to CLIPS" wavs are all saved in the project's audio folder.

+1 and me also jb. I loved when Cakewalk implemented that per project audio folder thing.
 
br: If you're not doing things this way, definitely try them. For back-up stuff, once you do things this way, you can take the .cwp and the audio folder it created and send it to your back up drive, a flash drive or wherever. Any bounces or information for all the audio stuff is all in that folder. You could also save as a bundle file too and it will store the entire project in a single file.
 
-Danny  
2013/04/08 19:32:54
brconflict
jb101, yeah, that helps me think more clearly. Let's assume I don't use Per-project Audio Folders. In this case, if all my Projects/Session files are saved in the C:\Cakewalk\Cakewalk Projects folder (default folder, anyway), then, inside that folder is a folder called, "Audio" or "Audio Data" depending on the Sonar X version, I believe. In that Audio folder would be literally all of the clips from all the saved Projects in Sonar, including any Bounced clips from any of my projects/sessions.

My case is just that simple. In that Audio folder (C:\Cakewalk\Cakewalk Projects\Audio) were indeed many bounced clips, alongside all of the clips from all the projects/sessions I saved in the default Cakewalk Projects directory. Assuming I want to back up and restore all of my projects and audio, if I simply back up the folder, C:\Cakewalk\Cakewalk Projects, literally all of the projects and audio there should be backed up. 

Oddly, in my case, there were some bounced clips in two projects (all drum tracks in one Project and one backing vocal track in another project) must not have been saved in that Audio folder on my C drive, but elsewhere. I know I didn't specify a change in locations for those bounced clips, so I'm a little baffled that they would exist in another folder. I've not tried to export/import, or edit anything outside Sonar.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account