Noel Borthwick

Did the same thing happen with EA2 or do you believe this to be new behavior?

There may be a misunderstanding. We investigated all Waves issues reported to us and they were are all crashes within the Waves plugins. I have passed on this information directly to Waves and they are actively investigating it. Please read this article on plugin compatibility. Just because a plugin doesn't crash in one DAW doesn't mean very much.

Please PM @msmcleod or @Jonathan Sasor with the project file that has this issue to allow us to investigate it.

This isn't an install related issue. It may be project specific. Since you are in touch with the company you can tell them that they can contact me if they need clarifications or assistance with anything.

Check your PM messages.

@Winstonhulley88 This is a plug-in crash so it would be something to report to the plugin vendor to fix. It looks like they are missing a pointer check in their code somewhere. The panic code sends a reset controllers sequence to the VST instruments. Perhaps this plugin is crashing on one of the CC resets. Unhandled exception at 0x000007FEB546B478 (Blade2.dll) in blade 2 test_10282020_183756.DMP: 0xC0000005: Access violation reading location 0x0000000000000008. This is the plugin info. If its a beta plugin you should obtain an updated version or contact the vendor about the crash and give them the same dump file. Blade2.dll *c:\beta test vst 64\Rob Papen\Blade2\Blade2.dll 1.00.0.0 10/26/2020 6:30 AM blade 2 test_10282020_183756.DMP EDIT: I just installed the trial version of Blade 2 and I don't get any crash when I press the panic button. So it may be specific to your project or the way you are using it. I suggest contacting the vendor.

@Winstonhulley88 please upload it to any file share like google drive or One drive etc and PM me the link. Also often zipping the file will make it much smaller.

Yes @Winstonhulley88 please send a link to the dump file that was created ASAP so we can take a look at it.

That is something you should take up with Waves support. They should be able to help you with this. Many issues with waves 12 are due to prior versions being installed at the same time which they do not support.

Please try the 2020.10 EA release since there are some optimizations that improve performance when there are many take lanes with muted clips. Also list the dropout code.

I don't see this issue. Can you reproduce in a new project? If so please post a video or some steps. Does it make a different if you are using a workspace or not?

I've fixed it thanks. Just some new code that was supposed to operate on notes, not checking the data type properly. We'll post an updated build tomorrow morning.

We can't edit the app since the user may have unsaved changes. So it prompts from the installer. We could prompt first from the app I suppose.

Realtek works fine with both Wasapi Shared and exclusive. In fact on Win10 you can get very decent latency with it - it goes down to about 4-5 msec with no issues. You shouldnt have issues overdubbing from the line in as long as you are running at low latency. Audio quality should be acceptable as long as you don't have any electrical noise coming in from the MOBO when recording. If you have a line level signal coming in from a mic into the line-in input you may be surprised. Obviously don't use the onboard mic lol.

You can get a free license for the Vienna Symphonic Library Big Bang Orchestra, which is powered by the Synchron Player here: https://www.vsl.co.at/en/BBO_Map/BBO They have an articulation map that you can download for it as well.

I'll investigate thanks.

@Cédric Lawde this behavior has been improved for the 2020.10 release. Simply adding a synth or loading a project shouldn't be triggering the creation of those files since they are only used during recording so that issue has been addressed. Some notes for others reading this topic later. With regard to the Allow Arm Changes topic please read the help for the Recording Options. In most cases you should always leave the two sub options "Only for Inputs in Project" and "Exclude Synth Inputs" checked because otherwise you can get a very large number of files created if you have many audio inputs available. This will make starting the transport sluggish. 3 files are created preemptively for every input on the system without those options checked. So if you have 16 hardware inputs and 10 synths in the project each with 8 recordable outputs, you will get a massive number of files created each time. 96*3 = 288 files! While these files are very small, file creation takes time and it will unnecessarily overload the system. By leaving "Only for Inputs in Project" checked this will greatly reduce the number of anticipated inputs and be much more efficient while still allowing you to arm on the fly. Another general performance tweak is to only select audio device inputs in preferences that you actually use and leave others unselected. This will also help reduce unnecessary inputs.

Its not Cakewalk crashing its the UAD driver crashing. Bluescreens can never be caused by user mode programs, only kernel mode drivers can bluescreen. This is not a question we can answer, only UA can debug and solve this issue so I suggest contacting their technical support with the recipe.

We need more information than that. What exactly are you selecting and copy pasting. Please post detailed steps or a video so we can evaluate.

@Sascha Denda thanks for sending your template. I was able to reproduce the glitch when step recording. The actual issue is not performance related. Its caused because the step recorder by default auto advances by the step size after every note. When advancing the time, it was interrupting the engine so you would hear a momentary pause in the audio that sounds like the note is being cut off. If you turn off "auto advance" you will see that the glitch stops. I've fixed the issue so that it no longer interrupts the engine while auto advance is on. Thanks for bringing it to our attention.

Hide related VST2 plugins has absolutely nothing to do with VST scanning. It just affects what is shown in Cakewalk's menus and plugin layouts. Its completely coincidental that your change appeared to affect your problem.

@Maestro We're not sure why you think its slower to work. In the PRV you essentially add the articulation to a row the same way. Our automation lanes are different and we didn't want to confuse them with MIDI articulations since its not the same thing as track automation. Can you make a video or explain what you are doing better?

Thanks, I've reverted to the previous value of showing muted clips by default to avoid confusion. The option is still there for those who prefer not to show muted clips.

There are no changes to this for the .10 release. Can you be more explicit about what why you think its faulty? How exactly are you doing the copy and paste.

Please pm me a link to the project template file.