Noel Borthwick

Can you post a screenshot? That error is not related to the in app updates done from the help menu. Make sure you are signed in to your BandLab account for activation to work.

In app updates should be working now.

Tip for using it live. Turn off dropout detection. This will let the app keep running even if it runs into a potential dropout condition. Much better than stopping playback! Set this to TRUE in preferences | configuration file.

This is how to set it up. After a bounce I get this As you can see it respected the track lengths. As mark said "Tracks through entire mix" does not respect the track length. We'll try and make that work the same way as well.

Yes its hard to find since it depended on the order in which the sends from the patch point were created. The bug has been there since the creation of aux tracks so its good to get this fixed.

@Maxim Vasilyev thanks for sending the project that exhibited the problem. I was able to track down the cause and fix it for the next release. The main issue was that the internal patchpoint bus associated with the aux track was somehow sending twice to the aux track. As a result the gain was boosted. I'm not sure what led to the sends being duplicated but I've made the code that handles this more robust and it wont allow that to happen now. Also at load time it automatically gets fixed so that it routes only once to the aux. Did these projects originate in an earlier release of SONAR by any chance?

This looks like one of the plugins is corrupting the heap. Sometimes even the higher severity setting wont catch it. Not much I can do to fix that if its plugin related.

This has absolutely nothing to do with the .11 release. The only changes in this release are some bug fixes and improvements for solo functionality

We looked at TDR Nova and couldn’t quite figure out how that plugin works. You may want to contact the developer if there is an issue.

You could always do this. Select source category tracks. Make sure that you have nothing selected and export the full project. It should automatically size the export of the tracks based on their length. Fully described in the release notes as well. A note about selection and the Tracks export category: When the source category is Tracks, the project selection has a special meaning: Having a project selection means there is also a time selection. So if you have tracks selected in your project selection, then all the tracks chosen in your audio source will be exported at exactly the length of the selection. In other words, the length of each tracks’ audio file will be the same. If you have nothing selected in your project, then no specific export time range has been set, and the length of each tracks’ audio file will be the length of each individual track.

Do you get an error message when you do that? If not set the exception handling severity to 7, then restart the app and try and reproduce the problem. This is most probably the plugins corrupting the heap. If you get a crash dialog attach the dump file reported.

Glad you could figure it out. All the scanner is doing when not actually scanning a plugin is enumerating files on the system and checking timestamps and reading from the registry. That should be very fast unless something external blocks those accesses (as AV's typically do with any executable files and the registry). When scanning plugins the plugin is loaded and queried for various parameters. This can also be blocked and made very slow if the AV needs to check for viruses. This is the main reason we don't recommend running AV's on DAW's. That said I've never had issues with Windows defender slowing down the DAW. Your mileage may vary with other AV's since some are very aggressive.

As far as delay compensation goes playback and monitoring is identical. Delay is queried at the time of inserting the plugin as well as when playback starts. And also if the plugin notifies the DAW that delay has changed. The latter is more deterministic in VST3. Re 3 it really sounds like you are monitoring something using direct monitoring. If you are listening to the band AND the backing track monitoring through the DAW's outputs it should be in sync. Of course if you are listening to acoustic sound it wont be in sync. Many people use this scenario in Cakewalk so there is most likely a simple explanation for this.

Singapore time is about 6 months behind us ?

I've fixed all known issues with solo. So if you are still seeing a problem after updating to the latest EA build (27.11.0.010) please send a simple project bundle file that shows the problem. We're planning on releasing this soon so please try this ASAP.

If the scan appears to be slow even though its not actually scanning any new plugins (no toast notifications showing it scanning plugins) then there are some possibilities. Registry access is slow (degraded or something like an AV is blocking). Or something is slowing down access to the disk where the plugins are. Again could be AV related. If this was fast earlier these are the first areas I would look at. The scan log may show something as well.

No need to uninstall Cakewalk. Run the latest web installer and choose to install SI instruments from there.

Its hard to tell without looking at your project. In your picture you have the send track soloed. Also which version of CbB are you running? There were some routing scenarios where soling sidechain sends wouldn't activate the signal flow. These have been addressed in the latest early access build. Please check out that build and post in that thread if its not working. If you unsolo everything does it work?

Thanks, I think this fix was in the original build as well.

@Apeirofobia please try the new build 10 that I posted.

Build has been updated to 27.11.0.010 This contains the following additional improvements: Soloing a bus now includes any sidechain sends to plugins in tracks/buses Improvements to plugin silence flushing

Yes

I understand your use case perfectly. Its just very tricky to handle the routing to solo it... I have implemented some logic that seems to be working but it would require some regression testing. I can send you a build to try later. As for attaching a project, the easiest way is to save a small bundle file and attach it. Otherwise you will have to zip the entire project folder.

Double click the reg file after saving them to your desktop. One enables and one disables.

While this might look simple on the surface, its not that surprising that this scenario doesn't work. The dependency graph logic for bus solo is extremely complex and corner cases have to be specifically programmed esp in more complicated routing scenarios. I'll try and explain. There are two independent solo "groups" for Buses and tracks that can be independently manipulated. When you solo a bus it figures out all of its upstream and downstream circuit dependencies and makes these audible in the signal flow. Similarly when you solo tracks or aux tracks. However these solo groups are independent. In your scenario since you soloed the kick and bass buses, it figured out that it should make the corresponding aux tracks audible as well as their dependencies which are the bass and kick tracks. However the sidechain is an internal send from the kick aux track to the bass track aux. Since you only soloed buses and nothing is soloed in the track solo group, the intra track send is not evaluated and therefore the send is silenced. If you solo the kick aux track containing the compressor this will work. Also, if you worked exclusively with aux tracks it would also work. I'll have a look and see if if I can make the bus solo dependency figure out the intra track sends. Without breaking anything else! I suggest attaching a simple project for the issue since the routing can be very specific and there are thousands of permutations.