Will.

But - Isn't asking questions the basic research? ? We first ask questions, before doing research. Soliloquy: Darnit! What is 1+1 again (asking the question) Let me check my text book (doing the research.) ??

The irony with this is: Only realizing now that, right after giving you advice - the samething happened to me. Definitely some Voodoo things going on here. ? Probably a bug.

Yet, another complaint from me with the 058 build (and I've doing this a lot with this build.) I believe it's the 4th time cakewalk just cuts out a Vsti. This is not the typical cutout during playback where it resumes after a quick double TAP on stop and play with the spacebar. You have to re-insert the Instrument and shift the midi file on the newly created insert for it to play again. This workaround isn't a big deal, but after a few times - frustration starts to kick in.

This is going to be tedious on another level. Delete your plugins one-by-one and save the project to check for any compatibilities issue with any third party Vst or VSTi. If it doesn't solve your dropouts, you can always attach a mini dump file here for management to check.

?? I had those too before. Had to delete that entire project. Fix something and then another problem occurs somewhere. I'm dealing with an issue at the moment. Not a big issue though. It comes and goes.

But then it would be triggered to play the entire measure of the problematic region. I'm not saying it isn't so - but, it would play the same melody as is through the other Vsti too and not just a "D" note. I run into this from time-to-time too. That's easily detectable and an easy fix.

Experience with this is telling me there's an underlying "D" underneath the original clip. Exit the PRV and locate the section where you hear the "D" note and zoom in on the clip in the track view state. Highlight the focused clip and temporarily delete it to check if the "D" note reveals itself. If there's nothing: Try to record that piece over on a new instance on a separate track and delete the old track. Do not copy and paste things over to this newly created track.

I agree with Gswitz.

Another bug in this builld. Previously: when I've set my LinkPFsendMute to "True" I couldn't hear the effects on a bus, if you mute or solo the routed/group Aux track - which have always been my preferred setting. In this build, it does not obey the selection on Mute with an Aux track. It obey's the selection on solo only. Meaning: When I solo the Group-Aux track - no effects are heard. When I mute the Group-Aux track you hear them.

When this happens again. Just enter the Task Manager from the Taskbar or by pressing Ctrl+Alt+Delete and close it there. I'm not gona go too deep in yo why this happen - just know it's commonly due to some third party plugins | OR | Cpu and Ram overloads and drivers not closing/releasing in-time upon closing the program. This will happen from time-to-time, so you need to make a mental note of this.

Glad I could help. Yeah. It needs some refine work. Though, once you're use to it - it works well. I normally bounce to dry by removing everything that is selected and just flip between MONO or Stereo. Another useful method for you might be to freeze the midi track. Just hit the Snow Flake button on the track in track view. If you don't like the extra empty tail it gives you - you can always right click on the track and go to "freeze option" and tweak according to your taste.

If it's still in a midi state - it's in Midi. To bounce the Midi to an AUDIO Waveform you need to go up to the "Track TAB" and click on "Bounce to track"

Plenty of times! Same result. An interface has absolutely NOTHING to do with your export - that's the work of your DAW's render[ing] encoder.

Some weird Voodoo is going on with windows and this 2021.06 build? So this is with only me? Headache!

What I normally do is - I load SPAN into the reverb buss and a gain plugin crack that up all the way to listen to how long the tail is after I put in my levels on the reverb. I hear what you say - but even with the KRKs at a steady calibrated level - some tails can't be heard without crancking the Reverb buss. Heres something to try: Render every track as stems and play it back in Windows. When you hear one locate the same track in CbB, with both effects bypassed on and off.

It does not. The only job of an audio interface is to let you get audio signals into the computer and out to your speakers or headphones. Whatever happens in mixing is entirely in the DAW. Perhaps a long tail from a reverb? I've uploaded a video on a bug where the groove clip feature does not cut of the notes by rounding the clip out - check that too. Oh-boy! I'm trying to think of possible causes - what about clips that has been bounced to a track | Or |freeze track fade out? Could be something thay is tailing into the silent part that gets cut of? Headache.

I always try to keep things as how it was send unless the client agree with me. People don't normally like it when you make changes to their work. This is why communication between you and the client need to be on point - really important. Like @pwalpwal said: Contact the client again and ask if it wont be an issue for him to resend every stem "clean" to you? The fact that he already said others dont normally find an issue with this - that's a barrier of causion if he was my client. It's easy to lose clients with this. I'm lucky enough not to ran into this issue. As I stated: I'm only there to clean/polish up the stems not to alter their work - unless it really is a problem in the mix itself. Though most of the time pushing it back or bringing to to the front by isolating it works everytime and maybe just widening it more, but i don't mess with their panning. Just my 2cents.

Don't know if this is a bug | OR | new enhancement to groove clips that doesn't show the indicators that it's ready to be looped (grooved) out. There's nothing on this in the UPDATE 3 overview. Honestly? I actually like it this way. Have to admit though: I dont normally use groove - I Ctrl+D everything. Dont know what made me use groove today. So, I'm just putting this out here, in case of it being a BUG. This will definitely confuse a lot of members who make use of this feature. Groove.mp4

Question: Are you doing this on an Audio Clip or Midi Clip. On midi clips - this is pretty much a no-zone. Also you need to have the "Smart tool" selected.

Can't seem to get this video smaller than the required upload size for videos on the forum - so I'm gona have to send screenshots. Edit: @Noel Borthwick @jsg Download the video here: https://file.re/2021/08/07/test-2/ Or you can edit your Track Control Order first, then custom save your workspace and select "APPLY TO PROJECT LOAD" and re-save your project | OR | saving it as a custom default template - like how it is in my case in the video.

It's working I'm already shortening the video.

Workspaces are not binded to a Template by Default. They're work independently from one another and project base - making this is a pain. I used to have a looooong list of custom templates - before sticking to only one custom empty default template. What ever I tweak in the Workspace and saving it in its own and the current profect it re-opens these setting next time I open that project. It's how to get you to save these settings.

https://discuss.cakewalk.com/index.php?/topic/31280-202106-feedback/&do=findComment&comment=260669 Important: https://discuss.cakewalk.com/index.php?/topic/31280-202106-feedback/&do=findComment&comment=260796

Let's focus on answers to solve the issue at hand with what the member have at his disposal, by being neutral. ☺ @Henrique Hespanhol Tozzi If you can. Dowload the "demo" version of FL Studio and use the "FL ASIO Drivers" within for better performance | OR | switch to the WASAPI EXCLUSIVE drivers within CbB for when you do your recordings. This should give you a constant decent recordings with your laptop or desktop hardware. ☺

Is that link correct? It takes us to a 2021 .04 thread.