Noel Borthwick

We worked closely with softube on integration and support all the necessary back end to integrate with the console one.

Did Cakewalk show the same midi device names in preferences and in one same order as the other daws when you had the problem?

We don't have those to verify. Is this something you can reproduce consistently? If so PM me and I can send you something to test. the main issue addressed had to do with vst3 but there is a secondary fix that may or may not affect it. Are you sure this isn't a problem with the plugins themselves considering they are old? Often auth issues can also lead to similar symptoms.

Over several years we have had a few sporadic reports from users regarding plug-in settings being lost when loading projects. We take any kind of data loss very seriously and many people have tried very hard to reproduce this problem over the last five years with no success. I'm happy to report that we believe this issue has finally been solved thanks to the assistance of several testers and end users. I'd like to call out @scook, @Max Arwood, Justin Mitchell, @msmcleod and the other users who contributed to this search for their invaluable assistance and troubleshooting, and for testing various iterations of the fix over the last few months. Max and Justin in particular spent many hours with me allowing me access to remote troubleshooting sessions on their DAW to try and isolate the issue. This ultimately led to isolating some of the issues with Waves and FabFilter plugins. Some background for those interested in this saga: While the actual problems appeared to be related to plugins from certain manufacturers, this is not caused by bugs in the plugins themselves. Rather, it was an unexpected interaction between specific VST3 features and the order in which plugins are loaded in the host. (This specific issue has preexisted since SONAR X3 when VST3 was introduced). The source of the issue with settings lost when loading a project, was a somewhat confusing part of the VST3 spec that allows plug-ins to send parameter changes to the host for delegation back to the plugin. The issue here was that certain VST's rely on this "parameter feedback loop" from the host to update their internal processor's when loading the project, even though the plugin state has been fully initialized by the host when loading the project. CbB/SONAR did not do this parameter reflection step when loading from projects. Without this step, occasionally a few of these plugins would reset their state to their default parameters even though they state has been fully loaded by the DAW. Whats even more confounding is that the reset behavior was not consistent - it would happen randomly, which makes it very hard to pinpoint the root cause. Why this confusing and error prone behavior was built into the VST3 spec is a subject for another debate I will be reporting this to Steinberg since the specification doesn't call out hosts to support this explicitly, and their unit tester doesn't even flag this as an error which should be an easy thing to do. The second problem had to do with loading fxchain presets and prochannel state. There was an isolated bug where Cakewalk's internal state for the plugins parameters could get out of sync with the actual loaded parameter state when copying or moving plugins around. This issue was also addressed. We have sent out test builds to several customers who reported these intermittent issues and they have all reported it as resolved in use over several weeks. The good news is that as a result of this work we've also optimized our internal parameter management for plugins which speeds up loading projects and various operations like cloning tracks and copying plugins. We're very happy to to put this one to rest finally and make CbB even more stable and failsafe! Stay tuned to see these fixes in our next public release. PS: Please note that settings being lost doesn't necessarily imply that its a problem in the DAW. This symptom can be caused by multiple reasons including authorization problems, demo mode or other plugin installation issues.

I've fixed the crash that @spiffo reported to me. Thanks for your assistance and diligence in getting me a project. There was a potential race condition that could cause a crash when a sidechain was created under certain routing conditions. This is why it was so intermittent and only affected some people. In his project he had a synth track sidechaining to a compressor in another track. It also seemed more likely to happen if there were multiple synth tracks sourced by the same synth output. The take away from this is for problems like this its very important to try and get a repro and send us a dump/project. Its only because of spiffo's project that I was able to fix this issue. There are so many environmental permutations that it can be very hard for us to replicate or notice some of these problems.

Ah I see - I missspoke. What its doing is when lanes are open it treats a browser double click the same as a drag and drop to the master track for the lane. This results in the drop occuring to the FIRST lane not the current lane. I suppose we can consider trying to special case the browser and make it always append lanes if you double click.

I wouldnt worry too much about that toast. All it means is that the system was busy enough that the time to process a single audio buffer exceeded the threshold and caused the engine to stop. The reason it drops out even when not playing is likely because you have synths in your projects or you have "always stream audio through FX" enabled. So its telling you that realtime playback has been stopped. I'm sure there is room for improvement, but it can happen with some more intensive edit operations.

@winkpainThe file menu issue will be fixed. The other behavior of double clicking files in browser when lanes are open is that it will insert to the active lane. I think that is expected today. Its also how it works with tracks - it will insert into the current track. When lanes are closed there is no active lane so it appends...

I can decipher it if you send me the dump file.

Haha no that's fine I just don't receive those directly so asked you to PM me to expedite it. Thanks to the help of @spiffo and @M.O.S.T. Music I got dump files and finally now have a project file that can reproduce a crash with sidechaining. We should be able to address this once I figure out whats going on.

Who did you send it to? Can you forward the project file and minidump to me? PM me.

I was able to reproduce it in the NFR they sent us so it happens in the latest plugin I had in July. I'm not sure if its fixed since then. Both @Jonathan Sasor and I were able to reproduce it.

I was referring to double clicking in the clips view within the lane to select it. I was able to repro your issue. We didn't test importing from the file menu so missed that case. It will be fixed in the next update.

Esc is used for other operations as well such as cancelling a mixdown, so it may be unexpected to make it cancel a selection...

Seems pretty unlikely that this would be related to the driver unless some dependency for that plugin got removed somehow. Does the plugin itself scan ok? What if you switch to the onboard audio device (WASAPI) and try loading the plugin - does it work?

@Christian Jones I think there may be a disconnect. Can you please notify the rep you are speaking to that I sent them very detailed technical information about this problem with BIAS FX 2. Yes it also happens in the new version. The information was sent on July 24 to Joe Kuo from support there and he acknowledged receipt and said it would be forwarded to their engineers.

Reminder - last few days to apply for the Cakewalk and Synchro Arts competition! Winner will be announced around Sep 1.

@RobertWS make sure that num lock is OFF before doing that. Its the "gray" num-5 key that unselects. I use it all the time.

Dragging from the browser respects the drop location and will insert clips contiguously on lanes. If you drop on a lane that has data it will autocrop it like this. If you drag to to the main comp track it will drop starting from the first lane and crop any data that lives there. This is by design. If you want to insert new lanes just drop to the last lane or insert a new lane and drop there. EXAMPLE: Dragging MIDI and audio clips from Browser to add take lanes EDIT: I see you mentioned the import audio menu. Make sure that the target lane you want to import to is selected by double clicking the lane. I'll check if the import audio menu respects the selected lane position.

Thanks! Please also send the minidump for the crash.

Do you still have the project that crashes? If so please send it to me.

Yes you can turn off the click behavior not the selection handles. See the feature overview topic. Regarding unselecting there are hotkeys to do that. Num-5 or CTRL-Shift-A will deselect.

@Cosmo Kramer which behavior are you referring to? If its the click to set now time that is already configurable..

It is indeed a melodyne issue and happens in all ara2 hosts. I reported this while we were working on ara2. I imagine celemony will fix it in a subsequent melodyne update. It's just a minor ui issue since closing and opening the view fixes it. Feel free to report it directly to celemony as well.

Lol I just ran into this Ironic that I come to our forum to find the solution.