Noel Borthwick

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?

You can upload the zipped dump to any sharing service like google drive and send a link.

Its in the bus compressor. Is this reproducible? If so please PM me the project file and steps.

Knowing patches is not possible because that is managed by the plugins preset management directly. Cbb doesnt know what patch is selected. Im not surprised that you corrupted the file haha. The data structures are quite complex and there are sizes stored for chunks so if you are not careful you can corrupt the data very easily. I had some rudimentary XML extraction built in a long time ago that could output a file that had the basic track properties but you wouldn't be able to get patch names. We can consider having some basic text extraction for the project for documenting whats in the project without having to open it.

If this same a bundle file make sure that you can open it successfully from the bundle. Any file can get corrupted on disk and since a bundle is a single file there is a risk of the entire file getting corrupted. Hence the recommendation you save both the bundle and the actually project file with it's audio.

A bundle file is a multi chunk RIFF wave file. The compacted audio data for all regions is stored first (per wave file format - stereo/mono/32 bit/24 bit, etc) followed by the CWP chunk. This is why if you rename it to wave it will play because media players ignore the subsequent chunks. As long as you download the file in entirety from google drive you can save as with the CWB extension and it will load fine. FWIW there is nothing wrong about saving as bundles. All known previous issues have been addressed a long time ago and yet people keep repeating the same incorrect info. You should always additionally save as CWP with external audio since its a lot more efficient to load and it provides a secondary backup. Bundles are convenient when you want to collaborate or simply store a single file.

I'm saying that the the user interface load (drawing clips, scrolling, etc) can also have an impact on streaming because it consumes CPU resources and in some cases can also affect DPC latency. Some applications have less going on in the user interface than Cakewalk and so performance can be affected because of that as well. Additionally plugins can have load that can impact different DAW's differently such as plugins that do OpenGL graphics. My point was without investigation you can't easily draw an assumption that the issue is directly related to the audio engine. There are many moving parts in a DAW besides the engine itself. We can investigate it further if you send us the sessions. As part of our ongoing efforts, we continue to try to improve performance in various areas of the DAW.

Let me know if it happens again in the next release. I’ve prevented the actual crash from happening.

@Andres Medina I tried to look for cases where this issue would occur and was not successful. Does this crash only occur with the Listento receiver and is it a reproducible problem? Also I see you are running a behringer audio interface. Did you notice any particularly odd behavior when loading templates with this plugin? We also tired making a template with the plugin and it does not crash. I've added code to prevent the crash itself but the cause is a mystery.

I'd be curious to take a look at the project files for both the Cbb and Ableton project. We're always trying to improve performance so if there are obvious issues we can investigate further. Its very difficult to compare two vastly different applications because there are millions of variables. Its not just the audio engine that gates performance, there are many factors such that can impact workload. User interface is one of the main areas that can cause glitches for example.

@Andres Medina Its a crash in our code where its doing something unexpected when loading a track template. I'll fix it for the new release. Thanks for sending this dump since it allows us to find and fix issues we would not know about otherwise. Although it happens when loading the Listento receiver the crash is not a plugin fault from what I can see.

In any discussion about usability you have to look at different user personas. Power users or experienced DAW users are always going to want more visible and newcomers who don’t necessarily have a lot of experience will get overwhelmed with showing all controls. Both types of users will get confused by different things so its not a simple solution. The general guidelines for modern UX is to show context specific or workflow specific controls to reduce visual overload. There is no perfect solution but our defaults try to provide a balance to allow people to get started quickly without getting overwhelmed. This is why workspaces were invented. If you are the sort of user who wants to see the kitchen sink its not for you. This is why our onboarding process asks you upfront to choose a workspace. I personally find keeping the interface focused on workflow more streamlined (tracking vs mixing particularly)

I can contact them and ask about it.

Out of curiosity what are the fields you would like to see if there were a text dump?