A 96/24 stereo track of about 5 minutes in length has taken ten minutes and it about 80% done.  This is a 4-core AMD PhenomII.  Dialog spinner is up, can't do anything else with program.  Using "Radius Mix".

That is far too long for a bounce and your system specs description is far too short.
 
List your:
CPU (including it's potential speed)
RAM
Interface (if you do not have one say so because that is very important)
Operating System (with bit version and which version of Sonar you have installed)
Hard Disk speed if available (if it is an SSD this doesn't matter)
 
Also...
 
What does your Edit > Preferences > Audio-Drivers section report as your Roundtrip Latency
 
You can check for performance issues by inserting the Perfomance Module into your Control Bar by cright clicking on the Control Bar and selecting "Performance" (it may take a couple tries until it replaces an existing module). This will show whether your CPU, RAM or hard disk are being maxed out.
 
Also...
 
Do you have a ton of effects and other gack on the track? If so turn or delete all that stuff when bouncing audiosnap renders so you aren't doing multiple resource draining functions all at once.
 
Cheers.

200bpm
 
Hope the result sounds good.

That varies with how much the file has to be modified. Depending on what I've asked AudioSnap to do, the results can range from so good you can't even notice a change happened all the way to unusable.

Beepster
That is far too long for a bounce and your system specs description is far too short.
 
List your:
CPU (including it's potential speed)
RAM
Interface (if you do not have one say so because that is very important)
Operating System (with bit version and which version of Sonar you have installed)
Hard Disk speed if available (if it is an SSD this doesn't matter)
 
Also...
 
What does your Edit > Preferences > Audio-Drivers section report as your Roundtrip Latency
 
You can check for performance issues by inserting the Perfomance Module into your Control Bar by cright clicking on the Control Bar and selecting "Performance" (it may take a couple tries until it replaces an existing module). This will show whether your CPU, RAM or hard disk are being maxed out.
 
Also...
 
Do you have a ton of effects and other gack on the track? If so turn or delete all that stuff when bouncing audiosnap renders so you aren't doing multiple resource draining functions all at once.
 
Cheers.

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.

Anderton

200bpm
 
Hope the result sounds good.

That varies with how much the file has to be modified. Depending on what I've asked AudioSnap to do, the results can range from so good you can't even notice a change happened all the way to unusable.

Just a question on the topic because I'm guessing you've tried this...
 
If you need to make a drastic change does doing it in increments help keep the sound from degrading? Like making minor modifications to get it closer, bounce, then repeating until it's where you want? Or will that just make things worse.
 
Haven't tried this yet but wondered.
 
Cheers.

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.

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.
 
If you are trying to do like a dozen tracks or more then yes... it can take a while to bounce. Still not a bug though. The computer just needs time to do the calculations.

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.

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.
 

BTW if you render something and it sounds wonky then you have options. You can try the different Offline rendering modes (very important you change the OFFLINE rendering... not the ONLINE one) or simply redo the bounce. Sometimes doing a second pass will garner better results. I used to have to do the latter frequently on my older underpowered system.

Track sounded fine.

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.

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.