SONAR 5.2 Free Update Now Available

[Alex Westner]

Is this an adapter issue? Just wondering as P5 has started messing up when looping, which I don't recall happening prior to updating Sonar...

Ya, I think it is.

[WillieJenkins]

I wouldn't worry about cakewalk "dropping the ball" guys, Lest we forget, they released an update patch for Sonar4 after Sonar5 had shipped. Very few DAW-based companies would provide this level of support.

http://forum.cakewalk.com/tm.asp?m=747870&mpage=5&key=

This thread above is rather amazing as well. Give them time, they will fix the problems

[Resonant Serpent]

I wouldn't worry about cakewalk "dropping the ball" guys, Lest we forget, they released an update patch for Sonar4 after Sonar5 had shipped. Very few DAW-based companies would provide this level of support.

http://forum.cakewalk.com/tm.asp?m=747870&mpage=5&key=

This thread above is rather amazing as well. Give them time, they will fix the problems

They've also decided to release Sonar 5 updates when Sonar 4 is still broken. It's bullshit. The prog has been out for a year and a half, and it still doesn't work right. The bug I speak of is the 'vst automation bug' where I can't automate more than one parameter per plug or the automation breaks.

I know that Alex gave me a response on this forum that the bug would be fixed after 5.2, but I'm sick of waiting. I'll have a new host soon. Why the f**k should I pay for an update when BOTH 3 and 4 are currently broken. Yes, I'm pissed off about it.

It should be par for the course that companies update a prog until it does what it claims to do.

Maybe Cakewalk will release a glorious update to 4 tomorrow, and I'll eat my words; but for right now, I'm not holding my breath.

[headquest]

In an ideal world I guess you are right, Resonant Serpent... but this is not utopia .

I switched to Sonar from a programme where version one had various bugs... then I paid to upgrade to version 2 and found the same bugs were still there and not fixed... plus some new ones had been added!! I was told that when the next paid for upgrade comes out *they* will maybe have fixed the issues that have been there since version 1 !

I have regretably had similar issues with some other software over the years.

To underline the point, it is a sad and inevitable reality that all software has bugs/issues from time to time. In terms of how well software developers relate to their users and work to solve issues some are certainly better than others. In my experience Cakewalk (and Ableton) are the best two mainstream music sequencer developers when it comes to bug-squishing and customer support. SO I think your points are rather unfair when you actually compare Cakewalk to some of the far-worse competition out there.

Of course, if you really do find some company providing better customer support, make sure that you let us all know!!

[Hunter]

My projects seem to loop okay and without dropouts; however, if I mute a track while it is playing back, it can result in dropouts even though my cpu is only showing around 30% usage.

I wish there was a way to prevent Sonar from turning the engine off...I'd much rather have a brief audio breakup than have the entire engine turn itself off for a brief cpu spike...

Yeah! You're right, I had a muted track, and it only seems to drop out when the track is muted, if I unmute it doesn't dropout.

Yup, that's a known issue that does have a workaround.

From the SONAR 5.2 Readme file:

"When looping a VST(i) alongside a DX(i), the VST(i) may sometimes playback earler after a loop boundary. The workaround for this issue is to insert an effect (even a bypassed effect) on the tracks which are sourcing the VST(i) output."

You can even turn on the built-in track EQ and bypass it and that should resolve the issue without any additional CPU overhead.

Hi ALex, I was meaning actual audio engine dropouts rather than timing issues, there are inserted effects on all the tracks, so I've not experienced the timing issue yet.

However it seems that xylyx and me have the same issues where having a muted track and looping leads very quickly to a audio engine dropout, red light at the bottom and all.

hope that helps narrow it downa bit.

[WillieJenkins]

I wouldn't worry about cakewalk "dropping the ball" guys, Lest we forget, they released an update patch for Sonar4 after Sonar5 had shipped. Very few DAW-based companies would provide this level of support.

http://forum.cakewalk.com/tm.asp?m=747870&mpage=5&key=

This thread above is rather amazing as well. Give them time, they will fix the problems

They've also decided to release Sonar 5 updates when Sonar 4 is still broken. It's bullshit. The prog has been out for a year and a half, and it still doesn't work right. The bug I speak of is the 'vst automation bug' where I can't automate more than one parameter per plug or the automation breaks.

I know that Alex gave me a response on this forum that the bug would be fixed after 5.2, but I'm sick of waiting. I'll have a new host soon. Why the f**k should I pay for an update when BOTH 3 and 4 are currently broken. Yes, I'm pissed off about it.

It should be par for the course that companies update a prog until it does what it claims to do.

Maybe Cakewalk will release a glorious update to 4 tomorrow, and I'll eat my words; but for right now, I'm not holding my breath.

which magical host w/o bugs are you moving to? every daw user would like to know