I got two problems, possibly related, but not sure:

1. Some recorded takes are corrupted. This happens independent of project size, buffer size and CPU load. I could not find a reason/repetitive pattern yet. When it happens, all further recordings are also corrupted until Sonar is restarted, then it works fine, until ... it happens again ... next hour, next day ??? (last time it happened in a 2 track project recording MIDI and audio from an external piano)
2. On playback I get occasional audio glitches/crackles (independent of buffer sizes). In most projects it happens rarely (short crackles), but I found one project that repeatedly does it (at what appears random times i.e. about once in a 3 min playback, but at different times in each playback); here it is more like a buzzing noise of 0.5 - 2 sec.

 I did a number of tests:

• My first idea was HDD issues / pending HDD failure so I did some bechmarks tests. HDD bechmarks show read/write speed at about 110-120 MB/s; not spectacular but sufficient as the trouble making project lists about 15 MB/s in the task manager at peak reading times (some 40 tracks @ 96 kHz, 24 bit). So disk throughput does not seem to an issue. Additionally, I found enough space on the somewhat faster system drive to move the project there for a test. Same audio glitching issues.
• When the record corruption happens, it is not audible while direct monitoring via the interface (i.e. no problem at the A/D conversion, perfect audio quality there), only at playback it shows the corruption (sometimes totally garbled, sometimes a number of crackles), like it gets corrupted in the USB transfer or in Sonar (??)
• Malwarebytes found 0 detections. CCleaner nothing really relevant (but I let it clean anyway). This is what I expected as it is a dedicated DAW, which is online only for DAW software updates.
• LatencyMon reports a supersmooth system if run over extended times. Nothing recorded there, even when run with the troublemaking project until there is an audio glitch.
• Sonar itself is (probably) not to blame (?) - at least it happens with 2016.08, 2016.09, 2016.10
• Interestingly, playback glitching does not happen with an older audio interface (Roland Octa-Capture), but it also did not happen with the new (MOTU 1248 AVB) when I extensively tested it 2 months ago. I tried MOTU drivers from 2 months ago, but same story.
• I swapped USB cables, USB ports, same situation.
• BTW, win10 Pro, all updates applied.

 
I have the feeling that some component is on it's way out (but I can't fully exclude Sonar from the list). I will do more tests, but that requires cabling up different hardware ...
 
Any suggestions welcome.
 
 
 

A few years ago I had somewhat similar problems with USB audio interface and onboard LAN card, the difference is that crackles in playback were always present (several crackles per minute). Disabling LAN in Device Manager fixed everything (I had to change motherboard later to fix this permanently).
 
Also I would check video card/drivers, maybe would try rolling them back. Those updates aimed for gaming performance in rare cases can downgrade performance with tasks other than games.

Outside chance Rob but for point 2, in the project that has random noise, you don't have a plugin that has reverted to demo mode by any chance? I can't recall which plugin it was but I had a similar issue with a project/plugin after a windows update.

AndreyB
A few years ago I had somewhat similar problems with USB audio interface and onboard LAN card, the difference is that crackles in playback were always present (several crackles per minute). Disabling LAN in Device Manager fixed everything (I had to change motherboard later to fix this permanently).
 
Also I would check video card/drivers, maybe would try rolling them back. Those updates aimed for gaming performance in rare cases can downgrade performance with tasks other than games.

 
thanks. I'll add that to the check list (now where the heck did I put that thing??) ... not aware of any graphic card driver updates (none done manually), but these auto-update days you never know ...

tenfoot
Outside chance Rob but for point 2, in the project that has random noise, you don't have a plugin that has reverted to demo mode by any chance? I can't recall which plugin it was but I had a similar issue with a project/plugin after a windows update.

that crossed my mind as well ... it's a finalized mix, so there are plenty of FX plugs (no VSTs), but I will definitely check on this. will kick them out for a test as global FX disable (which I had tried) may not be enough to rule that out (BTW, there are known issues of global FX not turning everything off)
 
using random noise when in demo mode is the cheesiest way of license protection. this is so lo-fi
 

I did have an issue when I updated the CA2A on my Studio rig.
As it is not connected to the internet the "new" CA2A was indeed in DEMO mode.
"Cheesy" is right, but easy to fix.
Click the down arrow on the upper right hand corner of the plug and authorize.
Of course if you haven't updated the CA2A or are connected to the internet disregard this message.
And of course, this a$$umes you have a CA2A inserted in the project.
 
T

Rob[atSound-Rehab]
using random noise when in demo mode is the cheesiest way of license protection. this is so lo-fi

I couldn't agree more. I also believe it is counterproductive to achieving sales. It is very hard to be impressed by anything when your first encounter with it is scarred by vexatious bursts of horrible noise!

DeeringAmps
I did have an issue when I updated the CA2A on my Studio rig.
As it is not connected to the internet the "new" CA2A was indeed in DEMO mode.
"Cheesy" is right, but easy to fix.
Click the down arrow on the upper right hand corner of the plug and authorize.
Of course if you haven't updated the CA2A or are connected to the internet disregard this message.
And of course, this a$$umes you have a CA2A inserted in the project.
 
T

does ca-2a still "phone home" even after activation? that could explain a bunch of the other "ca-2a/vst scan failing" posts, if ca-2a is receiving an unexpected response from a server... just a thought

Rob[atSound-Rehab]
 

• When the record corruption happens, it is not audible while direct monitoring via the interface (i.e. no problem at the A/D conversion, perfect audio quality there), only at playback it shows the corruption (sometimes totally garbled, sometimes a number of crackles), like it gets corrupted in the USB transfer or in Sonar (??)

If you have "Remove DC Offset" enabled in Preferences>Audio>Playback and Recording, disable it and test again.
 

"does ca-2a still "phone home" even after activation?"
I don't think so, its fine on the Studio rig after I did the "offline" authorization.
T

quick update of my additional, so far not successful tests:

• can't simply play project on mobile DAW, even at largest buffer (project too heavy for system?), without FX yes but not with FX which is strange because ...
• actually there are not that many FX plugs, it's mostly ProChannel ... apart from that a single instance of WAVES J37, WAVES PuigChild 67, BOZ The Wall, Guitar Rig (3x), WAVES Kings Microphones, WAVES IR, FabFilter Timeless 2 ... BTW, nothing that has noise as "license protection" AFAIK
• however, it is 35 tracks @ 96 khZ, recorded takes @24bit, rendered ones at 32 bit
• checking/unchecking 64 bit engine does not make any difference (I wonder if that should makes a difference at all as OS, Sonar and all plugs are 64 bit)
• it's definitely not LAN (even if deactivated in BIOS problem persists)