msmcleod

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.

The clip index is calculated by its position in time relative to the other clips on the same lane, so the first is named 001, the second 002 etc. However, this number only increases on the same lane/track. In other words, if you've got only one clip per track, they'll all have an index of 001. I tend to use the following to get everything in sequence: {tracknumber}-{laneindex}-{clipindex} This ensures you get a unique name for each track, sorted by track, then by lane, then by clip sequence in time.

looks like you might be using an older theme?

The subtlety here is the difference in the type of selection. When you lasso select, you're selecting the nodes ( which are a UI representation of the underlying envelope shapes in the envelope stream ), whereas when you do a time range selection, it's selecting a time range selection of the clip envelope streams themselves. The envelope code treats the two selections in a completely different way. I suspect this will not be an easy one to fix, but worth looking into.

Interesting... I have seen this with Presonus FatChannel, so I always make sure Presonus Hub is running when I do a scan, so CbB sees it as fully authorised. Given that the auth for Waves works completely differently, I can't see this being the issue with CR8 tho.

Other users have reported this, although I've not experienced this myself. Cakewalk is definitely not moving the file - maybe your AV software? Please post what AV software you are using.

It's normal for that file to be recreated. I'd assumed it might have been corrupted, which is why I suggested deleting it so it would be recreated. The only other thing is to check your template path within CbB, as this is where the template list is built from. Check the folder path is correct, and that there are project templates inside:

Yes, it was the VST3 version.

Mouse cursor issues can sometimes be caused by custom mouse software - I know I had a bunch of issues when using the Kensington Works application that was shipped with my trackball. All my issues went away when I uninstalled it.

Exit Cakewalk, then delete this file: %APPDATA%\Cakewalk\Cakewalk Core\Offline.html The start screen should be fine when you restart Cakewalk.

Just tried it here, and it's working fine for me. Uninstalled V12 Plugins Installed V13 Plugins VST Scan from CbB Preferences Added CR8 as an Simple Instrument Track, and dragged a wav file into it Saved the project Closed & Re-opened CbB Re-opened the project - everything is as expected Closed & Restarted CbB - new project Searched for CR8 in the browser, and found it No problem adding a new instance

@marled - The track volume can be ignored by unchecking the "Track Automation" checkbox. Just switch category to Entire Mix, uncheck it (probably along with Track FX etc), and switch back to clips. We'll be releasing a fix soon.