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.

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.

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.

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.

Ok - my bad.... looks like both clips & tracks source categories ARE affected by those checkboxes, even though they're disabled. I guess the easiest way to get around this is to make them always available - just confirming with the team.

AFAIK the Melda Free bundle isn't restricted in any way - the only thing paying for it does is remove the reminder notice that it's the free bundle. I guess this is mainly geared towards people not wanting their clients to know they're using free plugins. The deals you get on the plugins really are excellent and they all add up to further discounts on bundles in the future. I'd bought quite a few Melda plugins before I got an offer I couldn't refuse - the complete bundle for only 10% of the cost. Lifetime upgrades, unlimited installs on all my computers, and I automatically get new plugins as soon as they become available. You really can't get any better than that.

When source category is set to clips, the track & bus settings are disabled because they are irrelevant. For clips export, the audio is essentially tapped after the clip fx/automation - i.e. before it reaches the track, and therefore any buses. A similar thing happens with the "Tracks" source category, where the audio is captured after the track fx/automation, before it hits any buses - so the bus settings are disabled. [EDIT] - Both Clips / Tracks source categories go through the tracks / buses. The controls should not be disabled - this is a bug. We added the "Tracks Through Entire Mix" category so that you can capture individual tracks as they are heard through the main outputs (i.e. in this case, it goes through all of the buses). This is done by soloing and exporting each track in turn. The last expanded state of each of the dialog sections, along with the dialog size and position is stored in the registry as a global state, so if you close the dialog with the Mix and Render section expanded, it'll stay expanded for all projects until you collapse it again.

The only time I've seen this is when CbB was using the Realtek ASIO driver. I've also heard reports of this happening when HDMI audio is enabled. Is this happening with small projects, or only larger ones?

With tracks, I use the FX Bin for sound design, and the Pro Channel for mixing. In other words, I'll use whatever effects I need to get each track sounding how I want it in isolation (i.e. with the pro channel off), then only use the Pro Channel for mixing. This basically emulates what I used to do in the analog world - i.e. record the source as I want to hear it, then use the mixer to balance / EQ things to fit things in. For buses though, I'll just use the Pro Channel / Fix Bins as if they were one big FX chain. Sends from tracks to buses/aux tracks are either Pre Fader (but post any FX), or Post Fader. If I need pre-fx sends, I'll either clone the track with no FX, or go via an aux track. As a general rule, I use aux tracks for fx sends (e.g. reverbs from more than one track), and buses for collections of tracks (e.g. drums, vocals, bass, guitars, solo guitar, keys, backing vocals ) to make mix automation easier. If I can keep the number of "mix down" buses to less than 8, I can ride the faders via the MCU during mixdown.