I suspect that most Sonar users know by now that the first 2-3 weeks after release of the monthly update need to be left  to those who wish to take on the role of Post-release Beta Tester.   Some of us have learned this the hard way. 
 
It was a good idea for CW to clean up the code and remove any bloat in Sonar Pt.  However, this is often more fraught with danger than adding a new feature.
 
Cheers.

KIKO CUETO
Esto lo he comentado en otro hilo,pero creo que es bueno sumar opiniones, he tenido problemas al exportar.
Pues, despues de Mucho intentarlo y no queria Que Lo CONSEGUIR, Una PASE regresión una Jamaica, y la exportacion me ha funcionado a la primera, no se si que sera el Proyecto ESTABA En Esta actualizacion .....

Puede ser que sea un plugin específico que causa el problema. Es posible que desee pruebe a desactivar todos los plugins en el proyecto y luego exportar una pequeña parte de ella para audio. Si funciona, intente volver a habilitar los plugins uno por uno hasta que encuentre el que está causando el problema.

jpetersen
@icontakt:
Is it possible to revert to JS but still install the new drum replacer download that came with K?

 
I don't use DR (I've never installed it), but I've just rolled back to Jamaica Plain and see the DR on the Command Center saying "Latest version: 1.2.0.14" (which IS the latest version), so I think you can use the new DR in JP.
 
 

Doktor Avalanche
I really need a stable version of Sonar with no big issues to get in my way, and month after month I'm given a choice of what I should cope with or not, and yes I might be considering another DAW if the situation continues (not to be facetious or anything). Pity because I think Sonar is a great product. I certainly was pretty optimistic about the situation when Platinum came out but getting less so.
 
I appreciate I may be in the minority in these forums when it comes to vocalizing this opinion, but outside the Sonar forums I see a different story. A lot of people I notice are worried about making comments like this for fear of being shouted down, the reputation is that these are helpful forums until somebody says something which can be deemed or labelled as anti-sonar, even when they are not trying to be. 

 
I understand your concerns and points.

Duh. I meant JP, not JS. But OK, you understood that.
Thanks for the info.

DR often seems dependent on Sonar versions. You will see an error message if it is out of sync or it will crash (earlier versions) anyway. See how it goes... You will soon find out.

Doktor Avalanche

KPerry
What new features were there this release? This was all about optimisations, no?

Optimizations/performance improvements are enhancements not bug fixes and certainly would not happen during a feature freeze.

Well one is VST engine improvements handling mono. By the look of it this it may have broken some third party plugins which had previously worked around the issue, at least that's how I interpreted cakewalks post.

Regardless not complaining yet, cakewalk needs to be given a chance to put in a rapid regression fix or two, but it is Thanksgiving..

Now here's where I would disagree: I think that optimisations/performance improvements *are* bug fixes.  In extremis, something that is too slow actually makes a feature unusable, hence it is broken - improving its performance makes it usable, hence fixes a bug.  An obvious example would be a VST which used so much CPU because of inefficient programming that it couldn't run without overloading; a change to the relevant code makes it work.  Bug fix, surely?
 
The main reason, however, feature freezes/maintenance releases per se make little sense is as follows.  Suppose there are a mere 10 bugs in SONAR.  There is a maintenance release that addresses 9 of them, no new features.  That one bug is one that affects you* and a handful of other users, but the majority of use cases are unaffected.  The next release has new features because we've just had a maintenance release, so new features are presumably OK to add again.  But you will still be unhappy because one of your bugs isn't fixed, so you want another maintenance release before new features are added.  The logical conclusion is that nothing is enhanced/improved/added until all bugs are quashed, because there will always be some people who haven't had *their* bugbears addressed.
 
That would clearly never work commercially, nor would it likely be practical (especially given the huge variety of hardware, operating systems, plug-ins and combinations thereof in a DAW).
 
* This is a non-specific "you", by the way.
 
EDITED to remove not that changed the meaning of one sentence!

Doktor Avalanche

Doktor Avalanche
A lot of people I notice are worried about making comments like this for fear of being shouted down, the reputation is that these are helpful forums until somebody says something which can be deemed or labelled as anti-sonar, even when they are not trying to be.

backwoods
ALEX, i think u need a psychiatrist. You post about a thousand times how crap everything is and say thank god i read the forums, i'm rolling back to gloucester. i won't be updating this month.
 
then two minutes later. ok, i just updated to kingston. seems solid.
 
seriously, **** you weirdo!!!

^^^^
There you go... The sad thing is that comment will be allowed, and the thread will end up deteriating most likely...

maybe if you only commented in threads where you contribute something useful to the OP then you wouldn't wind people up so much? it's really ok, you don't have to comment on everything, you know?
 

KPerry
Now here's where I would disagree: I think that optimisations/performance improvements *are* bug fixes.  In extremis, something that is too slow actually makes a feature unusable, hence it is broken - improving its performance makes it usable, hence fixes a bug. 

From a developer and software development perspective it isn't though, they are categorised as enhancements. Performance improvements can always be made all the time, from the perspective you state one could argue that all non optimal code is 'buggy' (which would pretty much be most of the product, you can always make improvements).

If something does become so slow to become unusable it can be deemed a performance bug however, as you mention, I haven't seen that in Sonar for long while.

The whole point of a feature freeze is to surgically fix what can be fixed without doing any major code alterations, with the hope that it does not create major bugs. Even after this there is likelyhood of regression issue, so that has to be factored in as well.

In regards to your other comment I think you are basically trying to say there will always be bugs, that is a given, it is however a numbers game and everything should be done to minimalize that figure. If you don't get them first time around you try again next time round, all of it is a cycle. I agree priority is down to impact (ie number of people effected), but if you don't ever fix bugs that effect 'minorities' (nb 'minorities' can be quite large when selling thousands of copies) then what you can end up with is big backlog of irritations, which take away from the user experience. Eventually it can bite you in the back as it will eventually get noticed by everybody. Then you end up with a heck of a lot of complaints and a huge backlog of work to do.

Having said that (separate point) these performance enhancements seem pretty good.

backwoods
ALEX, i think u need a psychiatrist. You post about a thousand times how crap everything is and say thank god i read the forums, i'm rolling back to gloucester. i won't be updating this month.
 
then two minutes later. ok, i just updated to kingston. seems solid.
 
seriously, **** you weirdo!!!

This kind of post is in violation of the CoC. Please don't post this sort of thing in the future. If you have a problem with a member you can contact a host or CW and have them take care of the situation. Do not attack another member or call them names.  This is not permitted.  

I don't think he meant it to be abusive John...lets let this slip its been a ordeal for some people this release (Kingston)