Noel Borthwick

fixed sorry

You misunderstood my statement about asio4all. Cakewalk want does NOT require a pro audio interface for rendering accurately. It never has. I was referring asio4all itself having a lot of compatibility issues because off the nature in which it operates. I'll have a better answer about the real source of your problems once we test and reproduce the issue.

Yes we used to have a test project we used several years ago. But I’m more interested in real world feedback of whether there is a perceptible improvement with fewer glitches in this version.

It bears repeating, if you are having crashes and don’t report them with dump files to allow us to analyze them there is a low chance of the issues being fixed because the chances of us guessing are next to zero. If you have an issue that is system specific or intermittent then capture the crash dump and submit it.

This is impossible. Cbb and BA have no connection to prior versions of Cakewalk.

If its crashing once per session I can almost guarantee you that its a plugin related problem. Have you submitted crash dumps so we can verify the cause?

Right the reason DAW’s dont provide it is because its not the traditional use of stems. Stems by definition are in isolation. You basically want the equivalent of a track solo and bounce macro. As far as your audio setup goes we don’t actively test or support ASIO4All. It is not a native ASIO driver and is simply wrapping WDM. I suggest getting a pro audio interface with good ASIO drivers. There are many inexpensive interfaces available such as those from Focusrite.

Hi we’re working on a major revamp to the BandLab integration for a future version that will make this more intuitive and flexible.

>>Therefore, if I may ask, will it be possible to just represent something to differentiate between the individual MIDI clips. Don't want the other MIDI clips to disappear. Just a means to understand the boundaries of each MIDI clip. It will be great for drum programming, or anything that has a "loop" nature. We’ll look into it for the future as well a mode to filter to selected data. CbB’s PRV is already very powerful to filter appropriate data if you show the pane on the right. >>My Cakewalk buffer size is 512 Samples (10.7msec). It does change from that value <Under driver settings> >>Number of Buffers 64 <Under playback and recording> >>Driver Mode = ASIO Number of buffers can’t be 64. For ASIO mode there is always a fixed number of 2. Can you post some screenshots of your audio settings in preferences? We’ll look at your project file. Regarding your export requirements, you basically want a macro to export single tracks but through their destinations. In general automating this gets more complicated since tracks can route through many tracks via aux tracks and correspondingly tracks can be sourced by other tracks as well as sidechains. So its not as simple it may seem on the surface to provide this functionality. I’m curious why this is such a common requirement for your workflow - i.e. to export individual tracks through buses?

Hi @eric chevrier, Is this an 8 physical core 16 virtual core PC? Can you provide some more detail on what you saw before this update? Are there fewer missed buffers at lower latencies? Also try with plugin load balancing off and on. @Blades, @Glenn Stanton do you see any difference in this release?

Which automation problem are you referring to? Can you provide a project file or a step by step recipe?

@AdK Studios thanks for the feedback. Some of the automation issues reported were bugs already fixed in the latest 2021.01 release. ESP the freeze issue. The plugin automation issue with pitch riser is also the identical issue. The bug was that in 2020.11 freeze or bounce could cause envelopes to get orphaned. If you had hovered over the envelope he would have noticed that it showed a tooltip saying “orphaned”. When automation doesn’t render this is the issue 99% of the time. Regarding clip based workflow our piano roll is currently not particularly tailored for that but well consider allowing a mode to show only selected clips. Its not something that most of our users have requested in the past. Regarding automation accuracy, its not clear what your buffer size is. You are running a VST2 plugin and in VST2 automation is only accurate to the buffer size, unlike VST3 which is sample accurate. If you want sample accurate automation you should only use VST3 plugins or run at a very low latency. This could also be something specific with the plugin since I have not encountered this specific issue. If you share a simple project file with a repro we can look into it. This is inaccurate. Its by design that bus effects are not applied and has been this way in every version of Cakewalk going back all the way to 2003. As far as stems go its intentional that source category tracks does NOT include bus automation since this is the typical use of track stems. If you want bus stems you should export with source category buses and make specific buses for the stems that you wish to deliver. Alternatively you can simply solo tracks you want and export with source category set to buses to get the results you want. I do agree that when source category is set to tracks, we need to gray out the bus options. That’s just a UI oversight.

Only Waves 12 has that component AFIK.

If you are running Waves V12 plugins, please read before installing the 2021.1 Update. There is a bug in a Waves V12 program called WavesLocalServer that locks a component used by Cakewalk and prevents the installer from updating it. If you receive the Code 5 error trying to replace sndfile.dll from our installer, the current workarounds are, either: 1. Reboot your PC before upgrading; or 2. End the WavesLocalServer process from within task manager, and click Try again Waves has been notified of this problem and will address it. NOTE; This issue only affects the installer and doesn’t cause problems with the normal execution of Cakewalk.

Reboot your pc and retry the install.

Yes we delayed to address some API changes for the BandLab back end. It should go out today. Preparing rockets to launch. 10..9..8..7..6..5..4..3..2..1....

Steinberg has fixed this but have not released the patch to elicenser. They sent me a patch over a month ago. If you need it PM me and I can forward the link.

Thanks for all the incredible feedback and participation folks. We plan on releasing the final update publicly this afternoon in a few hours. Keep an eye out for a notification in Cakewalk.

Try rebooting your PC and retry. Also for updates you don't need to use BandLab assistant anymore. Its all done inside Cakewalk by using Help | Check for updates.

Could any of you folks running high core count PC’s please try the latest hot fix? ESP those running AMD Ryzen systems. There are some optimizations and fixes for MMCSS that might improve performance. If nothing I just want to make sure that it doesn’t cause any issues.

The idea of posting early access is for users to test them early and report back if there is a regression. So its in your best interest to install it early, considering how easy it is to roll back if necessary. All these changes are going into the final release which will go out shortly.

This is resolved in the EX hotfix posted yesterday. Please verify

Build 93 has been posted. Thanks for your support testing this hotfix. In particular, please test ASIO with MMCSS enabled (and disabled) since there are some specific optimizations to the audio engine in this area that should make it more efficient. You will need to reboot your PC after installing this update to test this properly. The following new fixes are in this build. Ripple edit delete using section overlaps crops the clip at the end of the left sections MMCSS threads not properly unregistered on engine termination MMCSS threads could exceed quota with repeated changes to preferences CbB no longer attempts to set ASIO thread priority when MMCSS is not enabled Plugin Load balancing threads were not being released Remove unexpected dropout message when creating or loading new projects Unexpected sample rate conversion message when bouncing audio Add Instrument Track not putting audio track in folder / unable to remove from folder

Indeed, good catch! You shouldn't be seeing a sample rate conversion message unless actual sample rate conversion is occurring. The reason its showing it is the export process uses the same component to do bit depth and format conversions and this is triggering the faulty message. Its not actually doing any SRC. I'll fix it for the upcoming hotfix.

No just a few hours We had a few builds today.