Noel Borthwick

MIDInco firstly thank you for voicing your concerns respectfully to the community. Let me just say this - the Cakewalk team is comprised of dedicated and passionate people who believe in making creative tools for musicians. You may not know it, but most DAW teams are very small. Building DAW's is not a high profit margin industry in case you haven't noticed. To help catch you up - we've achieved a lot in the last six and a half years with BandLab... A lot more than we did under Gibson or even Roland. You can achieve a lot with small teams. Not only have we breathed new life into Sonar but we also built a new cross platform DAW - Cakewalk Next. which is very centered on music creation rather than production. For Sonar we've been laser focused on stability and the features we've added are very workflow centric. Our list of bug fixes since we started exceeds 4000 just looking at our ticket counts. I'll let you refer to the change log and make up your own mind as to the value we've brought. Here is the Sonar Change Log and here is the Cakewalk change log As far as the team goes there are a several senior members, some of which even go all the way back to the 90's. I personally started using Cakewalk in '92 and joined as a developer in 1997 on Cakewalk Pro Audio and I've worked on every single version of Sonar since. And my shoe size varies depending on the vendor I buy it from ?

The video exposes a single stereo audio track to the Media foundation audio decoder which is what we're using to extract MP4 audio. So im afraid there isn't much we can do in this case. Sonar is not a video editing application so if you have more complex video formats you will have to externally extract the audio. I also tried this in a different DAW sand had the same results as Sonar.

You cannot since it has expired. This forum is for Sonar not Cbb by the way.

Im sorry there are no changes in the "latest version" that would account for what you are seeing. We know the exact set of changes that went in and nothing impacts latency. The issue the OP is reporting is not the same as what you are referring to so if you have a different issue make a fresh thread and provide a repro. The OP's issue isn't directly latency compensation related either. I should also add that if you have a problem with Sonar contact support and work with them. Staff don't actually do technical support in this forum - its a peer to peer user forum.

We tried the project you sent in to support and I don't see any timing issues playing it here. Notes a properly silenced when the MIDI gate is active and I only hear quarter notes. I even stacked 10 instances of Fabfilter Pro L2 which has high delay on track one and the output was perfectly synced. I don't think the problem is what you think it is. The issue you are seeing may be something else since with the recipe you provided we cannot reproduce it. I'll send you a PM and we can troubleshoot further. Are you running Sonar? We're not updating Cbb for remote issues like this in any case.

There is no need to add envelopes or activate all synth parameters ahead of time and it's intentionally not done because it consumes memory and processing for no good reason. Instead sonar creates parameters only after you change the value of a parameter in the instrument. If you really want all parameters go into learn mode in the synth UI and then choose a preset in the synth or reset the patch. This will trigger creation of the parameters and you will get a warning message if there are a large number is parameters. Many instruments expose thousands of parameters and exposing them all at once will consume unnecessary resources.

Autopitch isn't integrated into Next yet, but it shares a lot of the same features.

Its not so much the DAW as in what the video codec is reporting back when its transcoded to WAV, which is what happens. If you send a link to the MP4 I can take a look and see why its coming in as stereo. I assume that you have checked the import as mono box in the import video dialog?

The sidechaining routing detects feedback and eliminates routing possibilities that would result in feedback. This is the most likely reason it's not shown.

I'd sell you one if I had it

We've always had the ability to upsample at higher than 2x for ages, but its not in the UX. Read the help - the upsampling settings are in aud.ini https://legacy.cakewalk.com/Documentation?product=CakewalkSonar&language=3&help=Mixing.25.html The {Plug-in CLSID}.SampleRate= variable specifies the per plug-in upsampling rate. It defaults to a value of 0 (zero), which means “resample at twice the project sample rate”. The max sample rate is 384000 Hz. This variable is not stored in the Aud.ini file by default, so it must be manually added if you want to change a plug-in’s upsample rate (Tip: copy the CLSID from the corresponding EnableFlags= variable).

Turn off your AV. its not a virus its the VST scanner.

VstScan.zip You can download and try this Vst scanner. Unzip and copy it to C:\Program Files\Cakewalk\Shared Utilities, and then rescan the plugin. We'd planned to drop this update but it didn't make it into the CbB codebase. For clarity, were not making any bug fixes to CbB since the last year and a half. Only a small amount of critical maintenance fixes will go into CbB. If you want regular fixes like this one (which was released to Sonar users in Feb) you have to purchase Sonar membership.

You are posting in a thread for an issue that was resolved ages ago. If you have a new issue you need to provide a way for others to reproduce it as provide a simple project file. Most such problems can be very project specific so we typically need a project file to reproduce it. Also if this issue is important to you I suggest you download Sonar and try it since there have been many improvements to sidechaining. Even running it as a demo you should be able to test it. CbB is only receiving maintenance updates since a year and a half now. All active work is on Sonar.

Have you sent a crash dump?

This directory issue was fixed awhile back in Sonar. Maybe even in CbB I don't remember...

Need more information before we can offer a solution. Most obvious is are you running Sonar or Cbb? What is the specific issue -crash or other problem. If it's a crash send a dump file.

Nice catch @Spectrum424

The dropout reason codes are all documented in the help. https://legacy.cakewalk.com/Documentation?product=CakewalkSonar&language=3&help=AudioPerformance.24.html code 1: Audio processing took longer than the buffers allotted time slice. Increase the Buffer Size value in Edit > Preferences > Audio - Driver Settings. The recommended action just a general suggestion. It would appear from your symptoms that the synth is taking a huge amount of time to process the string tremolos. If it takes longer than the quantum of time determined by the audio buffer size for N consecutive buffers the engine will trigger a dropout and stop playback. You could bounce that section to avoid this issue. Have you tried running the same project on a different machine if you have one? Its also possible that there is something else that leads to the problem, eg a fragmented disk. Perhaps the synth is trying to do disk I/O and its simply too slow to keep up. If you can send a trimmed down project with just the section in question that drops out I could take a look and see if there is anything else that jumps out. PS: depending on the number of cores you have enabling plug-in load balancing may also help with this. I would also contact the plug-in vendor to ask why the processing is so expensive and if it can be optimized.

That's just sheer coincidence or it's a driver related issue. There is no way opening a project in another version can affect the outcome of opening in a prior version.

There are no functional changes other than a few of maintenance updates. You should post a video. The new project dialog has certainly not changed in many years. Re asio it looks like something has affected your driver. Does it work in other programs? Posting a video may be more informative.

What is the dropout error code shown? I added those specifically to aid in diagnosing drop outs. To rule out something at the point of failure, try starting playback a measure or two before that point. If it plays past that and drops out elsewhere later then the problem is cumulative. The error code is the best way to diagnose further in that case.

If you have a reproducible case send the project file and also capture a dump file from task manager while it appears hung. That may show what operation is taking long.

If you are running the latest version of sonar released today open quick start and you should see thu as an add on under product updates.

You can get a scan log today if you are that interested in whats being scanned. Look in Preferences VST.