Sonar Platinum Errors

Numerous Sonar Platinum errors. Cakewalk Tech support helped me solve one of them. I have been a cakewalk customer since 1998. There have been some problems over the years but always solved, until 2016. I now have to purchase Cubase, or FL Studio or some similar DAW.
 
2-21-16 - Omnisphere and Absynth are not playing last saved patches (ignore this one, it might now be fixed. cakewalk tech said to uncheck
"maintain midi numbers at stop: In PREFERENCES)
3-21-16 - metronome stops working in playback and record. i can't enable it at all. Solved: TURN MASTER FX OFF THEN BACK ON. waves one knob filter automation not working. it worked in part 1 (the previous sequence.)
3.25.16 - east-west red frog sample causes brief signal interruption in any other audible track east-west red frog sample does not bounce properly to new track, either with bus bounce or entire mix bounce (Both Solved: All SD3 pathes assigned to different PLAY tracks. All PLAY tracks "bounce to tracks in Sonar. Archive PLAY)
4.19.16 - Double click on Synth icon in track on edit screen, no results - Pro Channel not working. no audible changes on any module _ Soft synth plays wrong notes until i click on the midi clip itself, then it goes back to the right notes. it happens often.
4.22.16 _ Master bounce to tracks causes rendered file to make changes to some synth sounds _ Breverb on Vocal Sub does not bounce properly. Sounds like automation increasing reverb is fine, but after bounce to tracks,
reverb cuts in abruptly
4.28.16 - false midi trigger at 35 seconds. when i move the clip, the false trigger stays at 35 seconds and falsely triggers a different
midi note now at that timecode
4.29.16 - One Crash - False midi notes. Multiple midi notes where only one was written. - dropout in one midi section. deleting and reinstalling the track and copying midi data over solved the problem for about 10
minutes. dropouts resumed.

It sounds as though most of the OP's problems are solved.
 
The remaining ones do not sound like bugs as nobody else has reported the same or similar problems.
 
Could be a configuration or computer problem but we don't know ANYTHING about his setup.
 
blg1, in order to progress this please list your full system spec including interface, driver, driver mode etc.

I posted an alert a few days ago about numerous malfunctions in Sonar Platinum. The malfunctions are listed below.
 
1. I was told my computer might have a virus. I did check just now using McAfee Antivirus Plus and am showing no infections.
 
2. I was told by a Cakewalk Tech Support Rep that there would be a report created at Cakewalk to address one of the malfunctions: CWBRN-46239. This report was created on 2.15.16. As of 5.3.16, nothing has been done to address this or most other malfunctions. I purchased a PreSonus DAW because I need to keep working and Sonar Platinum is not working as advertised. I am done using Cakewalk products because Cakewalk was done with me months ago.
 
2-16-16 Entire Mix Bounce currputs one or more tracks/causes synths to play wrong patches/reqreites midid data i think. Sonar wesite and phone tech support dont understand why CONTROL CLICK Edit Filter does not change ALL selected tracks.
2-21-16 - Omnisphere and Absynth are not playing last saved patches (ignore this one, it might now be fixed. cakewalk tech said to uncheck "maintain midi numbers at stop: In PREFERENCES)
3-21-16 - metronome stops working in playback and record. i can't enable it at all. Solved: TURN MASTER FX OFF THEN BACK ON. waves one knob filter automation not working. it worked in part 1 (the previous sequence.)
3.25.16 - east-west red frog sample causes brief signal interruption in any other audible track east-west red frog sample does not bounce properly to new track, either with bus bounce or entire mix bounce (Both Solved: All SD3 pathes assigned to different PLAY tracks. All PLAY tracks "bounce to tracks in Sonar. Archive PLAY)
4.19.16 - Double click on Synth icon in track on edit screen, no results - Pro Channel not working. no audible changes on any module _ Soft synth plays wrong notes until i click on the midi clip itself, then it goes back to the right notes. it happens often.
4.22.16 _ Master bounce to tracks causes rendered file to make changes to some synth sounds _ Breverb on Vocal Sub does not bounce properly. Sounds like automation increasing reverb is fine, but after bounce to tracks, reverb cuts in abruptly
4.28.16 - false midi trigger at 35 seconds. when i move the clip, the false trigger stays at 35 seconds and falsely triggers a different midi note now at that timecode
4.29.16 - One Crash - False midi notes. Multiple midi notes where only one was written. - dropout in one midi section. deleting and reinstalling the track and copying midi data over solved the problem for about 10 minutes. dropouts resumed.
4.30.16 - crash upon melodyne 4 "create region fx"
5.1.16 - master bounce to tracks does not match original tracks - individual sub bounces to to tracks do not match individual tracks - no bus bounces at all

No, that has nothing to do with malware. But may be it worse to do intensive memory and hard disk checks. Some mentioned problems sound like something is happening on its own, randomly.
Otherwise it looks more like a combination of:
* MIDI settings (the buffer, controllers reset), may be in combination with CC lookback bug
* audio settings (buffer, sound card + driver), may be some bit and bitrate conversions.
* bounce settings, combined with particular plug-ins, mentioned MIDI potential problems, may be combined with not understanding that some Synth are producing different sounds every time they play (in fact most of them do, I was also surprised...)
* some "operator errors", probably combined with focusing bugs in Sonar
 
But in case Sonar will generate MIDI notes on its own, will not be able to bounce correctly anything and ProChannel will not work at all, I guess OP will not be alone with such complains.
 
Sure, from time to time everyone has strange observations with Sonar. But not on such level...

again, might not work for you, but i've been where you are , so frustrated I could throw the computer out the window and down a bottle of vodka...LOL  after waisting several days , then finally re installing windows 
 

You have to troubleshoot each issue to completion separately. Only then can you know what's due to:
 
1. An actual bug
2. User error or incorrect expectation
3. Preference setting
4. Project configuration
5. 3rd-party plugin defect or interoperability issue with SONAR
6. Corrupted project or session
7. Hardware or O/S problem
8. Other
 
DAWs are complex beasts. A lot can go wrong that has nothing to do with defects in the DAW software. Laundry lists of briefly summarized issues are of little value to anyone.

stratman70
Sorry but I really do not think the OP is interested in any help - That obviously was not the point of his Post. IMHO

 
True...he said he's going to purchase another DAW. However if he checks any of the support forums for any other DAWs that still maintain support forums, he'll find them populated with people who claim to have found bugs, some real and some imagined. 
 
If the problem is pilot error but someone assumes software is the problem, then the "problem" will never be fixed. For example...
 

4.19.16 - Double click on Synth icon in track on edit screen, no results

 
He's probably clicking on the icon below the track header; that icon is there for identification. The icon to click to open the synth GUI is the little one in the track header. This is logical. The little icon will always be visible, even if the track is minimized. 
 

Pro Channel not working. no audible changes on any module

 
Logic would dictate that if this was indeed a bug, the forum would be up in arms. The only other time I remember this being identified as a "bug" was by William Copper, because he didn't realize there was a ProChannel global FX bypass button. That's probably what's happening in this case. This functionality is also logical, so you can bypass the entire ProChannel with one click rather than having to disable each module independently.
 
Anyway, the reality is that today's DAWs are complex. It's not surprising that some people don't have the desire or discipline to study a DAW with the same intensity that's required to master any musical instrument. For these people, I believe - and I say this without any condescension, because I've heard some truly great music created on all-in-one studios - that something like a digital Portastudio is a better choice.
 
 

+100 Wookiee's comment on McAfee - for the sake of whatever DAW the OP intends to use -  strongly recommend he uninstall it and exile it forever from his DAW. Highly recommend using the "McAfee Consumer Products Removal Tool" (MCPR, available on Bleepingcomputer.com) after a complete normal uninstall, then system restart. Before you uninstall, check your CPU and Memory levels (while running your DAW) in windows Task Manager, then again after completely uninstalling it. That'll help to dissuade you against reinstalling it should you want to use the remainder of your AV subscription.
 
 

bgl1
I purchased a PreSonus DAW 

 

bgl1
If cakewalk rep said I was going to receive information from a troubleshooting report and never did (info above) I think y'all need to understand that cakewalk does NOT support its customers. That's why I purchased a different DAW.

 
I really hope PreSonus customer support has improved from a couple of years ago. Back then, a couple of inquiry emails I sent to them were completely ignored.
 

icontakt
I really hope PreSonus customer support has improved from a couple of years ago. Back then, a couple of inquiry emails I sent to them were completely ignored.

Best support I got at PreSonus was from folks that are also members here! :)

Anderton

jpetersen
From experience I can say it's impossible to know when or even whether a bug will be fixed. 

Bugs introduced in a new version are typically fixed within a month, sometimes less. However bugs involving old code are a crap shoot as to when they'll be fixed, depending on how deep they are in the code, and what else is going on. For example if CW is concentrating on automation or changing it, they'll try to fix automation-related bugs at that time; otherwise the automation bugs will wait until it's their turn.

that does make it sound like bugs "involving old code" won't really ever get fixed?

Slightly off topic... I remember there was a possibility to look at problem report by number (I mean CWBRN). Does someone remember where? Rather hard to find.
 
For reports... I have created 2 so far. Neither was confirmed/commented. In general I agree with Craig, in case you report about new bug, there is a big chance it is going to be fixed. Otherwise the code is "old" and it will not be fixed in any predictable future. Bugs introduced more then 10 years ago will probably stay forever

We'd better get reporting then, before they get old.
 
The audio engine improvements had a bug,
The drum replacer has an issue,
The new LP plugs have issues (just reported)
Let's think - what has recently been introduced?

For whatever the worth - I had sent a malfunctioning Presonus AudioBox 1818VSL audio interface back to Presonus for $145 worth of repairs.  Two weeks later, it came back.  I pulled it from the box and immediately hooked it up, and it STILL had the same exact issues, even though the repair ticket indicated that they apparently replaced 2 different circuit boards in it.
 
They did generate a prepaid shipping label for me to send it back, and I am guessing they will replace whatever is left in it, so I am sure it will work out fine.
 
The point is that all of this stuff can go South at times, whether Cakewalk or Presonus or any of the music stuff.  Issues exist with virtually EVERY single DAW company's offerings.  When you get to a point where you have deadlines and time-sensitive deliveries and such, it's time to invest in creating and maintaining protocols for handling issues when they arise, such as:
 
1) Creating a system restore point prior to applying a major software update or configuration change.
2) Creating and implementing a workable backup/recovery process, consider additionally having an offsite copy of things - Someone just had their entire studio cleaned out overnight, and lost something like 10 YEARS of projects, because there was no offsite backup.  That is a not likely scenario, but it DOES happen.  (fire/flood/robbery/hardware are all possibilities too)
3) Learning to separate issues, to be able to work them independently and efficiently.
4) Understanding how to roll back a Sonar update, in case one introduces a show stopper bug to your flow
5) Understanding the likelihood that a given error is local to your setup/configuration versus global to the community of users.  (example, ProChannel not working would have been quite prominent in the forums if that were some global issue - that it is NOT being complained about by folks in general would point ME to consider that it is something I might have accidentally done to myself)
6) Being willing to engage with whatever combination of forum folks and Cakewalk support it takes to get an individual issue has a workaround or was resolved - whether the issue was operator error, some configuration change needed, or a bug.
 
To the OP - if you ARE willing to engage in the process, I will do my best to work with you on figuring out how to get you past your issues - so please let me know if you wish to do so, and I'll invest the time into trying to help.  (I believe others in the forum would do so, as well) :)
 
We might not be able to resolve all of your issues, but if they can be resolved through anything short of a maintenance fix by Cakewalk, these forums are a good shot for getting most things squared away.
 
Bob Bone
 

Well, it wasn't just one or two other bugs, and they were 15+ years old. Here's what Noel said (I just found this post in the thread I pointed to):
 

Noel Borthwick [Cakewalk]
There were some other 15+ year bugs fixed with MIDI CC rendering. Pedal events could be rendered from the cropped out area of the clip which could lead to unexpected behavior. Controller searchback would also see stuff it shouldn't have.
There are lots of MIDI editing and rendering fixes and improvements in this version - a lot more than we've done in a long time.

 
So, very old bugs get fixed too!