Also... are you using a hard disk or a solid state drive? If it is a hard disk what is the speed of the drive? If it is a slow drive then that will add to the render time because the info needs to be read and written when rendering.
 
Are you on a laptop? What is your OS? Does the bit version match your version of Sonar (ie 64 bit version installed on a 64 bit copy of WIndows).
 

> Unless a cause can be identified, it is a bug.

This is definitely Teal, identical mannerisms .

Beepster

200bpm

Beepster

200bpm
 
Round trip latency 3.4ms.  RME interface, 8G Corsair 1600. computer at 3.6G.
 
It took over ten minutes to render a 5minute track.  No effects or VSTis, this was a simple isolated test.  Didnt think to check performance specs til it was over but I dont think it was using more than one core, but still.  Seems like a bug, at least it never said "not responding" and did not crash.
 
Sounded decent for a moderate change in bpm.

One stereo track.
By "track" I'm assuming you mean a single track or a stereo wave. If so... no that is not a bug. Something else is wrong.

 
Unless a cause can be identified, it is a bug.  System is stable long-term daw, optimized, and with one of best interfaces you can buy.  Other features working great, latency is really low, sonar responds well to large plugin count.
 
Tech support found that the AudioSnap features I was trying to use were not properly documented, and honestly, I would not have figured out all the various undocumented selections I needed to make to get it working.  Its very possible this is caused by a software setting.  If behavior is undocumented and impossible to address without tech support, its a bug, imo.
 

You did not answer my question in regards to how many tracks you were bouncing and no it is not a "bug". A bug is a reproduceable error that happens across multiple systems that can be traced to the program. Many people bounce with Sonar regularly and if it were a "bug" the forum would be flooded with complaints.
 
A render taking a long time is usually a system setting/underpowered system (which by your specs yours is not) or you are throwing an arseload of info at the program which requires a while for it to process.
 
So how many tracks were you rendering at once? Please provide a direct answer to the question.
 
Thank you.

One stereo track.
Win 7 64 bit, 64bitSONAR.  7200rpm spinpoint, system has two of them.  Tower format.
 
The reason I'm not going through this whole game of "listing system specs" is because they are not responsible for this. 
 
Tech support told me AS can corrupt projects, and it took a bunch of undocumented option tweaks to get it to do something which the manual says is easy.  This problem is more likely that an option was tweaked within program that is causing the slow render, or related to prior use of audiosnap within the project, which again cakewalk told me was buggy.

Sorry. I see what you did. You could have have simply corrected me instead of reposting the whole thing. If it was indeed a single stereo wave then something else is going on and it is likely system specific so we've troubleshooted the problem down to, what I'm going to say is probably a slow hard drive and/or a bunch of wares messing around in the background (often happens with preloaded laptops) or a system (which you say is a dedicated DAW that has been in use for a while) which may have been optimized incorrectly for Sonar (there are specific settings those optimization guides recommended that do not play well with Sonar so contact support for the proper set up).
 
A slow render time is NOT a bug with the software. Your definition of a "bug" is incorrect. If it were then I should be able to load X3 on my ancient P3 XP system and call the resulting failure of epic proportions a "bug then blame Cakewalk for it.
 
Anything else?

And as I typed that you actually posted something. The AS corruption issue has nothing to do with your slow render times. They are not related. The not being able to save projects with open AS clips COULD be considered a bug. I have encountered it and it is annoying. When that happens however the project becomes unuseable. You can obviously still use this project because you have successfully rendered a track.
 
They are two separate issues and it is likely a system issue... which is why your system specs ARE relevant. Just because you SAY they aren't does not make it so.
 

Also Audiosnap is a notoriously cumbersome and problematic feature. It is due for an update. I already said that upthread. In the meantime I recommend you consider investing in Reaper or use the freeware version whenever you need to do extensive time stretching.
 
Sonar does still have some flaws. If you are going to comb through every single feature in the manual you will encounter them (I did the same thing). However you are going to experience this in most DAWs and computer programs in general. We can offer you confirmation of known bugs, limitations and their solutions or workarounds as needed. You are not going to get anywhere though if you blame the Bakers at every possible turn, not provide essential info when asked or generally behave arrogantly.
 
Cheers.
 

Beepster
  The AS corruption issue has nothing to do with your slow render times. They are not related.  

OK, I did another test, I created a new project, imported the same audio file and immediately bounced to clip.  This time it took about 20s to finish the bounce and probably another 5s to draw the wav.
 
The only thing different this time is that I did not do anything with AudioSnap.  System configuration did not change, nothing else different.  Also remember that the prior audiosnap test was done from a new project with Cake support on the line.  I thanked him and we ended call when I realized the bounce would take a long time.
 
The project is set to 24/96 and the wav I'm importing is 16/44, so at the beginning of both projects, there was sample rate conversion which took about ten seconds.  That is the only other thing done by this project.
 
 
 
Previously I was having ANOTHER bug where after selecting the preferences, it would take 11s to finish the dialog and it would appear to reinitialize my interface.  I found that it was project specific- when I opened up another light project with just some midi tracks and EZD2 and would select preferences, it would only take about 4s to close out.  And furthermore, if I didn't make any changes and just clicked out, it would just close the dialog instead of going through the 11s routine.
 
I was using audiosnap in my other test projects as that is one of the most important features to me, so its very likely that Audiosnap is the common denominator in both projects taking considerable time to perform simple ops.
 
Furthermore, the Cakewalk rep said that Audiosnap has been known to corrupt projects, so my theory at this point is that these are BUGS related to something done with AS within a project.  Period.
 
Having read some older posts, there appears to have been a problem with bugs for X3a-d, so I attribute the resistance I'm getting to the loyalists being gun shy; they would rather dismiss a new user's problem than entertain that there is a bug that will impact his use of the product.
 
Not particularly happy about the bug(s), even less happy with the communities response to it.

200bpm
The reason I'm not going through this whole game of "listing system specs" is because they are not responsible for this.

Wow it's just like Teal from the dead...
 

200bpm
 
Having read some older posts, there appears to have been a problem with bugs for X3a-d, so I attribute the resistance I'm getting to the loyalists being gun shy; they would rather dismiss a new user's problem than entertain that there is a bug that will impact his use of the product.

 
Oh really..
 

Beepster
The not being able to save projects with open AS clips COULD be considered a bug. I have encountered it and it is annoying. When that happens however the project becomes unuseable.

 
Hmm not heard of this one... Possible to have steps to repro?
I couldn't find Open as clips here. Then again I rarely use AudioSnap.
 
I tried: 
New Project.
Drag a Wav into Sonar to create a new track.
View -> Audiosnap palette.
File -> Save As
 
Cheers Beep.
 
(BTW None of Teal's, sorry 200bpm's issues, are reproducible at my end, nor would I class most of them as bugs).

CakeAlexS
 
(BTW None of Teal's, sorry 200bpm's issues, are reproducible at my end, nor would I class most of them as bugs).

 
How do you know how to reproduce them?   Cake support took me through a long list of options/settings that are not documented in the audiosnap part of the manual.
 
So dismissive.
 
Woman to police officer:  "I've been raped."
Police Officer: "Where are you going in such a hurry."
Woman: "To the police station to file a report!."
Police Officer: "I need to see your title and registration."
Woman: "I was raped, please help me!"
Police Officer (to dispatch):  "Perp is hostile."
Police Officer:  "Get out of the car! Hands on the hood."
(police officer frisks woman)
Woman:  "I need to file a report, I was raped."
Police Officer: "How do you know it was rape?  So many rape allegations are false. Was it your husband?  Your boyfriend?  Have you been drinking?  I need to see some documentation to prove your citizenship. "
Police to Dispatch: "Perp is hostile, requesting backup, may be drugs involved."
 
 

200bpm 
How do you know how to reproduce them?   Cake support took me through a long list of options/settings that are not documented in the audiosnap part of the manual.

Then provide steps to repro then like I attempted in my last post (assuming it is an actual bug)..... Or look at the link I gave you above which contains a links to a number of confirmed bugs. Here is a good example when we talk about steps to repro.

If we can reproduce it then we might start taking you seriously, but as you won't even give us your configuration when asked I suspect you won't bother.
 
Ta...