msmcleod

@sjoens - the reason it takes you to the login page is because you're not logged in to BandLab, and it's trying to refresh your authorisation. I'm not sure why it's not allowing you to log in. The login works for me both on all of my Windows 10 machines, and my Windows 7 & Windows 11 machines. All machines are completely up to date with Windows updates though.

@Mark MoreThan-Shaw - just noticed that the clip is frozen in your screenshot... this isn't the same as rendering the region FX. All this does is create a temporary copy of the rendered region FX, but the region fx itself is still actually active. Did you actually render the region fx before freezing?

That is strange... I just tried the following: 1. Create two audio tracks with a clip on them 2. Added an arranger section covering the extent of both clips 3. Created a Melodyne Region FX on the 1st clip. 4. Attempted to move the section.... only the 2nd clip gets moved ( expected ) 5. Undo the move 6. Render the Region FX on the 1st clip 7. Move the section - both clips get moved as expected So for some reason, in your case, either Cakewalk thinks the region is still active, or there's something else in play. Can you zip up your project folder and PM it to me? I'll need to see it in action with the debugger attached. [Edit] - you could also try bounce to clip(s) on that clip to see if this helps

This is intentional - while a region fx is active the audio "owned" by the region fx plugin.

If you want everything saved, i.e. name, selected buses etc, all you need to do is add it as an export task.

@gmp - can you also try the project with the latest 2022.02 Update 1? (2022.02.39)

Maybe you hit nudge by accident?

We'll have something that addresses this in the next release.

We'll do something about this in the next release.

Me too... I had two... and only just managed to get my 3rd one from eBay after waiting about 3 years for one to turn up!

There's no PC in Sonar 8.5, and the OP is using Sonar 8.5 because of better compatibility with JAWS.

My PC was freezing twice a week - I spent AGES trying to work it out. The thing was, I've got a quad-boot: 2 x Win10, 1 x Win 7 64 bit, and 1 x Win 7 32bit. It would freeze in all four of them, and once it froze while doing a disk backup ( when it was running Linux booted from a CD ). On a hunch, I increased the CPU voltage in the BIOS very slightly... freeze problem solved. It's been around a month now with no issue. This was a complete computer freeze though, not just CbB. I've not seen CbB lock up in a long long time. I run a pretty clean machine though, and make sure no AV or cloud sync programs are looking at anything CbB might be.

Can you post a video of what is happening? Without seeing explicit steps and seeing what state the various options are in, it's hard to give any suggestions. ScreenToGif is useful for this.

I'm sure I've said this before, but the major three stumbling blocks for using Linux as an audio platform are: Lack of professional Audio Driver support Lack of native plugin support Lack of supported DAWs ( Reaper / MixBus being the main exceptions ) FWIW - I love Linux as a platform... just not as a DAW platform.

I can't seem to reproduce this - can you post a video of it happening? Also confirm whether you're using workspaces.

You absolutely have to switch to high performance mode to get any decent performance in audio applications. Software synths & effects are almost 100% reliant on CPU power.

Some of NI's instruments completely break the rules of MIDI, e.g. using CC#1 as a volume control is madness. CC#1 is defined as modulation, not volume... and CC#1's default value is zero. It's in the MIDI spec. So the question is, should Cakewalk start ignoring the MIDI spec just because NI does? There's probably some extra work we could do to be a bit more selective about which controllers get zero'd, but that's just a workaround. Given that NI have already made the decision to break the spec, the best thing to do is manually add a CC#1 to the beginning of your MIDI clips in the event list.

What version/edition of Melodyne?

ok - a few questions: 1. Are you opening the MIDI file, or dragging it into an existing project ? 2. Which track are you copying from? I tried a few clips, and the ones I tried had no issues. 3. Can you copy/paste (ALT + PrtScr) these two dialogs so I can see your paste settings? Paste Special Settings Editing Settings

No, there are no changes there... and I can't replicate the issue you're describing - copy/paste is working fine for me. Check your paste special settings - if it's set to "Paste as New Clips" it could just be the new clip is being placed on top of the original, so it's being hidden in the UI. Alternatively it could be you've got your paste settings to "Replace Old with New". If your paste special settings are set to Blend Old and New / Paste Into Existing Clips you shouldn't see this behaviour.

Personally I'd always go with a manufacturer that has experience in making quality mic pre-amps. Both Focusrite & Presonus have a history of making studio consoles (Focusrite with analog consoles / Presonus with digital consoles), so they have a wealth of experience designing quality mic pre's. Focusrite was founded by Rupert Neve, and is currently owned by the original founder of Soundcraft. I still use Focusrite in my office, and about 50% of the time in my studio ( the other 50% of the time, I use my RME which has only ADAT inputs... but is quite often "fed" by the output of my Focusrite Scarlett 18i20 when I'm not using other hardware pre's).

If all I'm doing is mixing, then using the onboard sound device in one of the WASAPI modes works fine for me on my laptop. I just plug my headphones directly into the laptop. Whether to use WASAPI Exclusive or WASAPI Shared is down to a number of factors: WASAPI Exclusive Low latency Cakewalk will completely take over the audio device, so you can't have other apps using audio. Checking "Suspend Audio Engine When Cakewalk Is Not in Focus" in Preferences->Audio->Playback and Recording can be used to mitigate this to an extent... but it can be annoying if you accidentally switch to some other application, and Cakewalk stops playing, so I tend to not have this option checked. Cakewalk normally has full control over sample rate/bit depth, assuming the onboard device fully supports exclusive mode. Not all on-board devices support this mode WASAPI Shared Higher latency Audio device is shared with all other applications You may need to manually change the sample rate/bit depth in Windows audio to match your Cakewalk project Supported by almost all on board audio devices

Alternatively, there is the "Toggle Track/Clip Gain in the Edit Filter" keyboard shortcut. This toggles between what the edit filter is currently set to, and Clip Gain Automation so you can quickly switch back and forth. I normally bind this to '\' as it's right next to SHIFT on a UK keyboard.

First check if there's a Cakewalk subfolder in your downloads folder - there should be a build 29 installer there named Cakewalk_by_BandLab_Update_Setup_28.02.0.029.exe Running this will rollback to the current release version. Alternatively, you can use the 2021.12 rollback installer in this thread, and then check for updates afterwards. You can then download the 2022.02 build 29 update: I can't think of anything in this update that would cause the problems you're describing though, so please let us know if this is something new, or if it's also an issue for you in the 2021.12 release.

I use Cakewalk on Windows 11 every day... it's works fine on Window 11. The issue your describing is to do with how you're using your audio device. It sounds like you've got another application taking exclusive control of your audio device. Alternatively, it could be that your audio drivers aren't compatible with Windows 11.