Noel Borthwick

Hi @Peter - IK Multimedia we've received a few crash dump files from users that confirm that the crash site is within the Modo Drum plugin. If you don't have a dump file contact me and I can send it to your developers. The problem also occurs in all prior versions of SONAR and is not specific to CbB.

Revoice Pro and VocALign now support ARA 2 and work seamlessly in CbB through our partnership with Synchro Arts. To celebrate their latest update, together with Synchro Arts we’re giving Cakewalk by BandLab users the opportunity to win Revoice Pro and VocALign Project! These powerful industry standard tools for vocal production now work even better in CbB as a result of our ARA 2 integration.

Revoice Pro and VocALign now support ARA 2 and work seamlessly in CbB through our partnership with Synchro Arts. To celebrate their latest update, together with Synchro Arts we’re giving Cakewalk by BandLab users the opportunity to win Revoice Pro and VocALign Project! These powerful industry standard tools for vocal production now work even better in CbB as a result of our ARA 2 integration.

Perhaps the behavior of prefader sends being fully independent is too advanced for be a default behavior? The problem is if we change it some projects may sound different and unexpected for someone who actually has set up for headphone mixes. We could try and expose UI to select the pre fader send behavior...

Thanks for the video @Gswitz The behaviour you demonstrate is expected. At 3:25 in the video the main reason why the export doesn't include the doubled reverb from the pre fader send is because you SELECTED track 2. When you do that the bounce is omitting track 1 completely from the mix as if it didn't exist. (Behind the scenes bounce actually makes a copy of just the elements of the project that are selected) If you did the export with all tracks selected you would get identical behavior to playback. The reasoning behind prefader sends working independently even when a track is muted (in this case as a result of another track being soloed) is rooted in use cases such as setting up headphone mixes. Suppose the engineer has set up prefader sends for headphone mixes to the musicians. i.e. In this scenario you don't want the act of soloing or muting another track in the control room to cut out the sound from the headphones. IOW the engineers mix needs to be independent from the cue mix. The ability to select elements for export is powerful but can be confusing if you don't follow the underlying routing.

Bruce I really doubt this is a bug. Please send me an example project so we can see the routing in the project. There is no difference in this regard from any prior SONAR version.If you are hearing other buses when picking Master there is somehow something from those buses being routed to the master via a send or aux track or something.

Hi @HappyRon Hill in the next update, it will now additionally set the playback position to where you click based on the Click setting. Note that if you want the rewind to start of clip behavior you will still need to shift click.

@Bruce Searl and @Gswitz selecting a bus for export will include all other buses that send to that bus. This is by design and is not a bug. If you choose the Master bus in the export you are telling it to export everything that goes to the master including other buses that route to it such as the metronome or your reverb bus etc. The only way to exclude those is to mute them manually. In your example your phones bus will not get included in the mix unless you are also routing it to the master bus. To avoid this, route the phones bus to a hardware out rather than the master. The Export UI could be improved, but that would add more complexity to that already advanced dialog. >>I think i know what you are describing. In cakewalk, if you solo a track, other tracks mute but their sends do not. This only happens with pre fader sends and is because pre fader sends are computed before mute is applied. There is an ini setting that controls this called LinkPFSendMute in aud.ini. I suppose we can change the default behavior since some users find it unexpected.

What if we never modified the project while playing from within a playlist? Would this solve the issue for you?

Hi @Rogério Dec this would be a limitation of the Microsoft Media foundation video framework that we use so it could be tricky to address from our side. We haven't looked at video in a long time but we'll schedule some time to investigate again in the future. Thanks for your understanding. The root issue is that MP4 compressed requires prior keyframes to be decoded before the video engine can start streaming. In general most compressed formats including MP3 work that way and are not designed for editing. Some video apps decode to an intermediate format for this reason.

Thanks, its not a problem - I understand now. You want to be able to isolate the clip AND set the playback position at the same time. When I made the change originally (which was much before the addition of the new click option) I had moved the behavior to rewind to the clip start to require the CTRL modifier. However now that we have a click option it seems logical to allow it to also seek to the mouse position additionally, since it can be disabled via the click option. I'll make the change for the next release.

As I said the shift click is for the "rewind to start of clip" behavior. Its not intended to seek to the click position itself. If you want to seek to the click position in a lane, click on the top half of the clip. That allows you to set the position while playing (if set during playback is enabled)

Not exactly. Previously it would play from the start of the clip not the now position. Completely different function. In comp nose clicking the lower half is supposed to isolate not additionally rewind the now time by default that's why we decoupled the two. And made it require a shift gesture. There is no change in behavior from the past in that regard except that it isn't the default.

First import an audio loop or a wave file from the browser and make sure you can hear it. If the can then audio output is working. For MIDI inert a soft synth (try TTS1) and you should be able to hear yourself playing when the synth track had focus.

@Jim Roseberry have you filed a feedback hub report? @Pete Brown may be able to follow up.

Hi Pete, The default ui hasn't been updated in a long time since it's rare that a plugin doesn't have a ui these days. Well look into improving it at some point.

Thanks @Helene KolpakovaKolpakova glad it's working well for you. That is the idea - to make it work so that you don't notice it and can concentrate on your music! Let us know if you encounter any other workflow issues.

It would be more useful if you took the time to explain what you don't like The smart tool works exactly like it did before by default. There are no changes to ripple edit in this release.

There are no changes to audio processing in the July release that could have impacted anything like this. Also Cakewalk never sets the audio buffer size directly except through the control panel so its not even possible to change. Its coincidental that your problem occured at the same time. Did you do any Windows updates? What is possible is that the driver is changing the buffer size based on the project sample rate. If its switching to 192K when loading CbB its because your default sample rate in CbB is set to 192K or you are loading a project already saved at that setting. Its completely normal for CbB to switch sample rates in that scenario.

What exactly is different from what you were used before? The smart tool by default performs the same actions. If anything copy and paste is a lot more predictable and tons of bugs were fixed. Have you read the notes we released yesterday?

This would happen in any application that enumerates drivers like Cakewalk. I could probably write a test app that triggers the same result. Bottom line is that drivers shouldn't try and install software!

A detailed 2019.07 Feature Overview has been posted with lots of screen captures and explanations of the new comp workflow.

An easy way to troubleshoot it when it's hanging is to open task manager and see what process is being launched when cbb starts up. That will lead you to the errant application

@Tay Zonday that is not our installer! We have no such message in Cakewalk. As scook mentioned above some driver is being loaded as part of Cakewalk initialization and is trying to install some software. You will have to track it down and remove it or properly installd it. Do you happen to have the Yamaha driver mentioned?

Does it persist if you close and open Cakewalk?