Noel Borthwick

@Steven de Jong Thanks for your report. Its likely sub optimal UI in Omnisphere. Many plugins do very inefficient drawing and depending on the video drivers this can lead to glitches in audio. This is why in my original message I mentioned UI performance. Ableton has a vastly different architecture for its application UI (a cross platform framework) so its not surprising that some problems you see here may not appear in that app. We have observed very similar behavior in another application we are developing. Unfortunately Windows is a crapshoot when it comes to balancing realtime workloads with a busy user interface, esp with all the variances in graphics API's and drivers. So if you remove Omnisphere (or close the UI) does the problem get significantly better?

I've posted a build that has a fix for this and a handful of other issues. Can you all of you affected please try this and report back? Please also verify that punch in recording and loop recording behaves as expected and that audio is aligned. @DeeringAmps @Base 57 @giovannibuchelli

Hi guys, thanks for reporting this. I've identified the change that caused this and will fix it. Its caused because the latency offset is actually being applied twice in this case because of some obfuscated code that was doing this unexpectedly! I'll post a fix for you to test shortly.

@giovannibuchelli & @Patrick Bray I suspect this is a side effect of a different bug fix I did to solve an issue with virtual ports and aux track recording where punch in recording would be late. Can you confirm whether you are doing either punch in recording or loop recording, or if in your test it was just simple recording.

We’ll try and reproduce it thanks. BTW hardware MIDI ports dont have a unique signature in Windows so shuffling devices around lead to tracks getting assigned to different devices. They are just indexed hence its difficult to identify when devices are added and removed. There is really no easy way to get around this. We’ll look into your specific case and see if something can be done with templates. Also if you haven’t changed anything with your configuration the ports shouldn’t change.

@giovannibuchelli can you try rolling back to the prior release and check if this problem still occurs? You can easily reinstall or rollback. See this thread.

Hmm I stand corrected, I was confusing software inputs like patch points. We could consider allowing hardware input monitoring to be pre input gain but it could be tricky. Recorded audio should always be at the source level so it would sound different post record if we did that.

Possibly related to your windows display settings if something changed there.

I don’t see why you shouldn’t be able to mix live inputs rather than recording. (Not being able to hear your mix through headphones in a live room is a different physical problem of course) While track volume affects the post FX gain, Input gain will affect the pre FX gain. If I understand what you want, you should be able to set the input gain levels to mix all your live input levels to what you want. Alternatively if you want to mix post FX use track volume. @David Baay Input gain does affect live inputs since its applied immediately after the inputs and pre fix bin. Take a look at the signal flowchart.

Which version of Cakewalk are you running?

I replied in the EA thread with the explanation as well.

You can try and install the latest early access release from here and see if it helps.

We made a couple of fixes to work around the worst issues with the RealTek ASIO driver. It reports sample rate of zero Please check if it works better with the latest early access release of Cakewalk.

Start screen is going to go away and be replaced by something much better in the future, So no further work is planned for Start Screen itself until then.

If it isn’t working in WASAPI chances are it wont work in windows and other windows apps either. Ensure that you set the sample rate to 16 bit 44.1, or 16 bit 48K. Pretty much all headsets work at those.

Use WASAPI shared mode which is the preferred format for USB headsets.

That is correct

WASAPI Shared mode can run at different sample rates from other applications because Windows internally sample rate converts and mixes the output from all client applications. Even in ASIO mode some drivers can internally handle this by sample rate converting. If youtube is failing its typically because Cakewalk is in ASIO mode and the driver doesn’t handle multi client use well.

Its crashing in the plugin not Cakewalk so this isn't something we can investigate. Please contact the vendor and give them the dump file. Unhandled exception at 0x00007FFB4786E5DE (VD-DEEP.dll) in Orme_April_2021_2_04222021_192142.dmp: 0xC0000005: Access violation reading location 0x0000000000000018.

Make sure you set the driver mode in preferences to WASAPI shared mode. And plug in the headset

Thanks for the feedback. They can make it easier to view the dynamics, and yes it looks cool too.

Hi everyone, We just dropped an early access release that has a lot of new exciting new features including deep BandLab integration via a brand new library view. Not only can this feature be used to publish to BandLab and collaborate with other musicians, you can also use it to save stem mixes of your project and play them anywhere, which can be very useful when testing mixes or trying to get opinions from other folks on your mixes such as in the songs forum. This is much more powerful than posting a stereo mix to your song, because if you additionally provide stems others can offer more constructive advice feedback on your mixes. (there are options to provide a full mix in addition to individual track/bus stems) Please try out this feature and let us know your thoughts in the early access thread.

Actually bundles are not so susceptible because the bulk of the data is the wave data which is at the start of the file. Any small corruption there wouldn’t prevent the bundle loading typically. The CWP is tagged on at the end. That’s the dangerous bit.

Do you hear the distortion even when you freeze or render the track? Looking at the rendered wave may give you some clues. Also check if the gain is clipping in your signal flow.

Your status bar says “Saving file”. Were you saving the project or do you have auto save enabled?