Noel Borthwick

How many plugins do you have installed? Some users had slowdowns loading the plugin inventory from the registry. It it happens when simply starting the program without a project this is definitely the issue. I've improved start time for loading plugins very significantly for the next release. This is obviously in Cakewalk by BandLab. SONAR is no longer a supported product.

Thanks I'll take a look. I think at minimum it should be preloading the next project ahead of time irrespective of the wait for keypress option.

If you send a link to a crash dump I can verify that the crash is actually in rapture. However we are not shipping rapture presently so I can't give you a timeline for plugin related fixes.

Thanks we'll look into it. You shouldn't need to restart cbb however. What happens if you just press play the again? Do the notes not get reset?

The default record mode is Comping. You can change it to Overwrite or Sound on Sound if you prefer the more classic record modes. By default in comping mode only the most recent take is audible and others are muted. There is no need to switch to the mute tool to unmute because everything can be done via the default smart tool by clicking or dragging in the bottom half of the clip to isolate the areas you want. Pay attention to the help module tips when you hover over clips and it will show you more information about the tools and zones. You can read more about Comping here.

This has been resolved for the next release. There is a new read only mode for the playlist.

@Chris Boshuizen This issue has been fixed for our next update. Its actually something that was broken in one of the SONAR releases itself. The next update has major improvements and optimizations for plugin time sync and looping so many old issues have been resolved.

@marled I was able to repro the issue where if you had it set to "On stop rewind to now" multiple clicks during playback would jump to the begin of the loop or start of the project. There was some code that was added many years ago to try and detect multiple rewinds and jump back. I've taken it out since it seems unexpected and was behaving inconsistently which is why you thought it was a bug. However I cannot reproduce playback getting stuck like you describe. Did that only happen with "On stop rewind to now"? If you can repro even otherwise please see if you can get a recipe since I would like to fix that issue. I tried many times but do not see that problem.

I heard about that Cortana bug. A big CPU spike from a background process like that could certainly cause dropouts. I'm not sure what you mean by grayed out PRV keys however. A dropout shouldn't cause keys to get grayed out. Is this reproducible and can you take a screenshot? Regarding the burst of sound after resuming a dropout, that can happen. If the engine has been stopped the synth still has unplayed buffers or tails that it will spit out once playback is resumed. VST doesn't provide a way to reset internal synth buffers.

@Colin Nicholls No I was referring to the setting in CbB itself under Preferences | Playback and recording, to "Suspend audio engine when Cakewalk is not in focus" Please also try the DropoutMsec setting mentioned above.

Nothing has changed of any significance in 07 that would impact this area. Though Echo made great products, you are running a discontinued 15 year old device that doesn't have officially supported Windows 10 drivers. It's not surprising that it might behave sub-optimally in Windows 10. I suspect something environmental in your system is affecting driver performance leading to the dropout rather than CbB. In ASIO mode all audio is driven by the ASIO driver's thread rather than managed by Cakewalk. If the ASIO thread is starved for some reason it will cause a dropout. Most modern ASIO drivers take extreme precautions to guarantee real time performance of the driver, setting their thread priorities to realtime and other kernel tricks. Regarding why your dropouts seem more likely to happen when idle, its hard to say since there are many variables. PCI devices especially legacy ones, are prone to interference from other devices on the system and can require tuning. Some things you can try: Do you have MMCSS enabled in preferences? If enabled Cakewalk will try and change the driver thread priority to the MMCSS pro audio priority. Check whether toggling that flag makes any difference. Try playing with the DropoutMsec variable in Aud.ini. This allows adjusting the tolerance for the drop out. Do you have share audio devices enabled? Try toggling that off to let CbB exclusively use the driver.

You are using asio or wasapi? What latency are you running at by default? If you are getting dropouts that frequently when running at moderate latency something is interrupting your audio driver. Cakewalk has a fuse to detect if audio processing was unable to complete within the allocated timeslot and pops that message. Unless you have a synth or plugin in the streaming path that is costly normally your shouldn't see dropouts esp when playback is not happening. Does this also happen when playing your project or only when idle?

The easiest way is to use Ripple Editing to accomplish this. Here is a video.

Selected but not announced publicly until they all respond via email.

Could you check what audio driver mode you were using when you had the issue, and what driver was selected?

Glad to hear that @Sidney Earl Goodroe Did this fix the VST2 versions of these plugins or VST3?

Entire Mix will sum everything coming out of ALL hardware outputs. If you have multiple outs used for headphones or are have some special routing it is probably not what you would want. Bottom line is there is no one size fits all solution. You have to pick what outputs you want to render.

As mentioned "Master" is just the name of one of the buses in the default template and has no special meaning. One thing we could consider doing is only select the DEFAULT bus.

Hi Dan, The thing is that there is internally nothing special about the bus called Master. The routing is flexible and its really up to the user which bus represents the entire mix. In fact there is no requirement for there to even be a master bus since all buses get mixed down to the target hardware outs. If you look at the signal flowchart you will see that.

Waves - lost perimeters. Now that would make a great album title 🤣

If you were referring to my post about program change numbers you may have misunderstood what I was saying. I was referring to the VST3's special program change PARAMETER. This has no notion of banks. Rather its a parameter who's values represent all preset's exposed by the plugin. AFIK there is no way to separate them into banks using that mechanism. Its a linear range of all presets that the plugin exposes. You will see the preset's in the preset picker in CbB's effects window toolbar, assuming the plugin exposes it. All Waves plugin's expose presets if you want to see it in action. Generally the only reason to access presets from the DAW directly would be to program a preset change somewhere during playback. So bank's don't necessarily buy you any functionality assuming that all the presets in the plugin can be set.

This thread has strayed far from the topic of plugin settings loss Losing automation envelope state is a completely different thing since it is host related rather than plugin related. Same with the program change issue which is related to the VST3 spec implementation. If you have a reproducible issue with that PM me a link to the project and we can look into it. As I mentioned earlier sending program changes will only work if the plugin exposes program's to the host. i.e. you MUST see presets listed in CbB's preset picker in the effects window. If not no dice. TH3 doesn't support VST3 presets. I don't have THU to test but I imagine its the same.

@craig The main issue with program changes is that MIDI defines a program change as a value from 0 to 127 and banks similarly. VST3 doesn't actually support MIDI as raw MIDI data but messages like CC's and Program changes internally handled as a special plugin parameter with a floating point range from 0-1. VST3 plugins can expose a count of supported "programs" and in fact if they do CbB will enumerate and show these programs in the preset picker on the toolbar at the top of the plugin window. If that is shown then by setting the flag in plugin manager to "Translate Bank/Program Changes", MIDI program changes in the project will get mapped to the appropriate value of the special program change parameter. Keep in mind that there aren't many VST3 plugin that properly expose their programs this way. Waves instruments are an exception and do support it. So you would in theory be able to send program changes to the VST3 this way. However it doesn't make too much sense since the range of 128 programs would be mapped over however many programs the plugin offers. So you would have to guess what program change number corresponded to the actual program! Not very user friendly. Alternatively a better approach would be for us to directly expose the program change parameter to the user as a plug-in automation parameter. I tested this and in theory this would allow you to dynamically assign a program change via track automation. As long as the plugin exposes the program change parameter this would show up as an assignable envelope for automation. As long as the plugin exposes the programs properly, the parameter values would show the correct program names in CbB. This is not supported yet but I can consider adding this in for a future release.

@martsave martin s can you provide some more information on the steps you you do to run into this issue?

Hi @JoseC, we looked at VCV. This is a completely different issue and its caused because the plugin is a minimal wrapper that doesn't handle chunked data saving. It also doesnt support a default vst program so our code is not saving any state for it. We'll try and handle this corner case where the plugin has no programs and no chunks. This is really an outlier case though. I haven't seen any plugs like this before