Noel Borthwick

Pm me your user ID and we can look at your account. Ideally you should contact support with account questions.

Send a dump file and we can see what's crashing

Yeah, there are subtle bugs that can go unnoticed for years, decades even. I've fixed bugs that have been there since 2005 or earlier. And then some user comes along and sees the bug immediately due to something very specific in their workflow and says - this app has not been tested, <insert expletive here> 🙂 I actually just fixed one like that - a crash with no audio devices present that was introduced in 2013. Anyway, thanks for reporting this so clearly. It was a pretty important one to fix.

No worries I was just concerned that there was an issue with their activation.

We are planning for a degree of customization and considering json file based approaches too.

Hi @Jan I investigated this problem and was able to reproduce it with Sylenth1. It is indeed a bug and exactly as you suspected that the tempo was being used as an integer. In October last year I heavily optimized time reporting for VST plugins to reduce CPU use and we now cache tempo to avoid expensive calculations. However, I had a typo in my code that was returning an integer instead of the fractional tempo. This issue was not caught since most people tend to use integer tempos. The bug is now fixed and will be in the next update that we release soon. Thanks for bringing this to our attention. I'll send you a build that you can verify. PS: I PM'ed you a link to a build with a fix. Please report back.

It will expire independent of being signed in or offline for that matter. Sign in doesnt have anything to do with activation other than identifying the user to the server.

I think you are getting confused with their UI. As I mentioned its auto activated inside Sonar and Next. The UI of the plugin is whatever general UI Overloud has for an external license. The key here is that you should be able to stream audio and use the plugin with no limitations. If you try running that plugin in another DAW or even CbB you will get this dialog and can only use it as a demo.

This has been addressed for the next update.

The Internet connection message has been fixed for the next update. It was unintentional.

There is no auth code required. TH-U will auto activate inside Sonar and Next. You cannot use it in cbb or another DAW if that's what you are trying to do.

Its most likely that the save is so fast that you dont see the progress display. A second save is likely faster due to caching.

Not a bug. Its intentional that clicking the title bar dismisses quick start. Most users try and interact with the menu or close the app when the quick start is open so we facilitate this by dismissing it.

New prochannel modules are being considered but we don't have anything to announce just yet.

There is no good reason to uninstall unless you desperately need the space. If you uninstall fully you might lose some plugins no longer distributed is the one thing you might consider. Otherwise if you are never going to need to check something there you can uninstall.

Cheers for getting Premium, you wont be disappointed esp with whats coming later. Regarding the perf meters, they don’t measure UI load by default but rather audio processing load unless you change the metering options to show global system load. Some spikyness there is not abnormal, since its impossible to perfectly balance load on your CPU in a real world project since you may have varying processing or plugin loads on tracks and buses. Turning on Plugin load balancing will help smooth the load if you have many plugins on each track and arent running at super low latency. If you have a recipe for the language change issue, please send me a PM.

@Bristol_Jonesey are you signing out after activating? Irrespective of whether you actually stay online or not activation will be retained for the lease period as long as you stay signed in to Sonar. (Sign in is not the same as being online) >>I'd rather not have to go online every time I open Sonar. >>Is there a fix for this? Being online is definitely not a requirement. Will need to troubleshoot this with you as to why this is happening. Send me a PM.

Is not that Sonar is incompatible. It's just that we don't do any significant testing on it. We have limited staff and resources are spent on testing current software. I was just trying to rule out a system level issue.

There is nothing to fix lol. Turn on show strip colors in preferences.

Please read the FAQ about the free tier. This has been rehashed many times. The free tier only includes the Core features of Sonar, not all features you could find in now discontinued. cbb. Many of those older features have been greatly improved in Sonar. If you want the full Premium Tier feature set of Sonar you will need to purchase a BandLab membership Our free tier is very generous compared to other free DAW offerings but it won't include the entire Sonar feature set now or in the future, as new features are added. Again just core features.

A forced update is not related to activation. It's when there are certain bugs or backend changes that mandate everyone switching over to the new version for consistency. We do this periodically but relatively infrequently to sync the user base with the latest version. In this case we're working out some issues in the system in preparation for future changes and this required the update. Additionally we corrected some copy that was leading to unnecessary confusion about the new free tier.

Sonar initializes and still uses DirectShow for the purpose of dx plugins. If something got messed up with dhow this would explain why the problem only manifested in sonar and not your other DAW's. It doesn't necessarily mean it's a bug in Sonar itself.

Yes as I said the "gap" was intentional to fix a problem. You might not have seen it bit it could happen intermittently which is why I had to make that change. I'll look into it next week and see if there is an alternate way to address that problem.

Well look into this next week and see if we can repro it.

Regarding the external insert issue, we looked at the code and indeed in Sonar there is a change to how bypass works. However its completely intentional and doesnt have anything to do with engine stability. Its exactly the opposite in fact. In Cbb there were numerous bugs with EI and when bypassing and unbypassing rapidly you could crash or hang the system because the external insert has very complex routing internally and it led to a race condition. To solve that I made it do a proper "hard bypass". In fact bypassing from the fx rack is always a hard bypass as opposed to an internal plugin bypass. In the case of the EI the old code wasn't handling it in a threadsafe way. The New EI has extended functionality and doing this was the only safe way to handle it. That said I'll consider implementing a soft bypass mode for the EI - this will have to be done from the plugin UI's bypass button. This isn't available today for the EI. In any case the TLDR is that this is not a bug but expected behavior today. Much better to be safe than crash.