msmcleod

I've gotta go with @Jeremy Oakes recommendation. I've got two ASUS ROG gaming laptops that I use for both development and DAW use. Both of them are excellent and have given me zero problems. I use WASAPI when using the on-board sound device, and ASIO when using them with my Focusrite Scarlett 2i2. The only downside to them is the battery life - I'll get around 45 - 60 mins max, which is kind of understandable given that they're powerful machines eating up CPU usage. The lower priced ones have less powerful graphics cards, which is fine - you should be focusing on CPU speed / cores rather than how good the GPU is. I recommend getting at least 16GB RAM. Most come with an SSD for the OS drive, and a Hybrid ( HHSD ) drive for storing games. If you can, get one with a 512GB SSD for the OS drive - 256GB will work, but it'll get full quickly. Use the second drive for samples (including plugin sample libraries) and projects. You can partition the 2nd drive to separate your projects from the samples. If possible, consider replacing the 2nd drive with a large SSD. This was possible with my older laptop, but not with my newer one as it's a sealed unit ( and the newer one belongs to BandLab, so I'm not gonna open it anyhow! ).

32 bit and 64 bit are floating point. 16 bit and 24 bit are integer. Dithering only makes sense when switching to an integer bit depth.

I've just tried my Win 7 boot, and it's working fine with the latest Cakewalk. I went to Refresh Activation, it launched The Edge browser - I logged in, and it successfully refreshed my activation. As long as Win 7 has all of the latest updates, and the TLS fix, it should work fine. That being said, you can always download BandLab Assistant and authorise using that.

@billp - I was getting these quite frequently - not just in Cakewalk - I was getting the same error with certain plugins in Reaper and Studio One. A few days ago, I installed the latest 2022-01 Cumulative Update for Windows 10 Version 21H2 (KB5009543). After installing the update, all of the crashes went away. I'm not saying this will fix your issue, but worth checking out.

@petemus - This is a known issue when saving track templates with nested folders with a particular structure. It has been fixed for the next release.

This page covers what the update does: https://support.microsoft.com/en-gb/topic/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-winhttp-in-windows-c4bd73d2-31d7-761e-0178-11268bb10392 As you scroll down the page, it details what it changes in the registry, and what the various registry entries mean. I guess you could check your existing registry entries against what is on this page.

I do get what you're saying. In the past I've used a Roland D110 guitar sound, which was obviously a synthesised guitar, but gave an interesting quality - especially when I then repeated the phrase immediately afterwards with a real guitar. The contrast worked really well. For me though, there are very few situations where the AAS Strum does it for me - unless it's pretty far back in the mix. Where it does hold its own is the mode where you hold a chord down in one hand, and trigger the individual strings in another. This is really useful for coming up with picking patterns I wouldn't normally have come up with on a real guitar (mainly down to habit). For me it's a useful writing tool, but for a sound source, not so much.

Ah - this is probably due to the lack of TLS 1.1 / TLS 1.2 support in Win 7. It needs a Windows Update, then needs to be enabled as default ( FYI TLS is the latest version of SSL for secure https connections). details are here: https://support.microsoft.com/en-us/topic/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-winhttp-in-windows-c4bd73d2-31d7-761e-0178-11268bb10392 All modern websites use the latest TLS 1.2 protocol, so installing this is really a must if you need internet on Windows 7.

Melda, TH3 ( which I then upgraded to TH-U ) & Melodyne (upgraded to Editor for polyphonic editing). I did upgrade AAS Strum to the full version too, but don't use it that much. To my ears it doesn't sound realistic enough to use as a guitar, and sounds too realistic to pass off as anything but something trying to sound like a guitar!

Yes - if you're using VirtualBox, make sure you've installed the extension pack, and configured the network in the virtual machine's settings. Instructions on installing the extension pack can be found here: https://forums.virtualbox.org/viewtopic.php?f=25&t=99355 For the network settings, either a bridged or NAT connection will work, depending on your requirements.

No, a dual boot means restarting the machine and choosing the relevant OS on bootup.

That might indicate a sample rate mismatch.

No.

You could check the meters within the Console View. Make sure you expand the Hardware outs at the far right too. If it's working, you should see all three meters light up as you play. If you're getting a signal at the hardware device ( the right most meter ), then the sound is getting to your hardware device - anything beyond that, is beyond Cakewalk's control.

Ok - there's your issue. The Master bus is set to None. Set it to your audio device.

Sorry, can you turn off the Pro Channel as well... I need to see this:

Can you show the whole screen? I can't tell from that screenshot what your master bus is routed to.

This message just means that your audio device doesn't support the Sample Rate / Bit Rate you specified within Cakewalk.

Ok, then you've selected the correct sound device. Next thing to check is that the Sample Rate / Bit depth within Cakewalk matches Windows, e.g: Should match: You can get to this properties dialog, by: 1. Right click on the speaker tray icon 2. Select "Open Sound Settings" 3. Click "Device Properties" 4. Click "Additional Device Properties"

Yes, it could be just a volume issue. Make sure it's turned up within Windows. If this doesn't work, it could be you've selected the wrong audio device. Typically on-board sound devices have two options: an analog output (Speakers), and a digital (SPDIF) output. You probably need to select the analog output. The V49 is not an audio device, it's a MIDI device, so it won't be listed under the Audio devices.

Ok, so you're using an on-board device. So... 1. Start Cakewalk 2. Go to Preferences, and set the driver mode to WASAPI Shared within Audio->Playback and Recording 3. Go to Audio->Devices and make sure your audio device is listed and checked in both the inputs & outputs. 4. Go to Audio->Device Settings and set your Primary Timing Master / Recording Timing Master to your audio device. If your device isn't listed, go back to step 2 and change the driver mode to WDM. [Edit] - Forgot to mention... you also need to make sure your Sample Rate / Bit Rate in Cakewalk matches what you've set within Windows. So, if you want to record in 44100Khz / 16 bit, you need to go to the audio device properties within Windows settings and set it to be the same as Cakewalk.

Ok, let's step back a bit. Can you answer the following: 1. What version of Windows are you running? 2. What sound card are you using with Audacity? 3. Are you trying to run Audacity at the same time as Cakewalk?

The Alesis V49 is a MIDI keyboard. What are you using as an audio device? If you're using the on-board audio device, then set your driver mode to WASAPI Shared within Preferences-> Audio -> Playback and Recording

The most common reason for this message is that either you've forgotten to switch on your audio interface, or your USB settings has caused it to go to sleep. Typically, what is going on here: You've got your driver mode set to ASIO You start Cakewalk without your audio interface plugged in Cakewalk tries to find an ASIO device, but can't find one - so you get the message If you intended to start Cakewalk without your audio interface plugged in ( i.e. you're using a laptop and you just want to use the onboard audio device ), just go into Audio -> Playback and Recording within preferences, and set the driver mode to WASAPI Shared. Just remember to set it back to ASIO when you do have your audio device plugged in.

A re-install normally leaves any user settings intact. You should do a full re-install though, as it looks like it wasn't actually installed properly at all - i.e. you may have transferred the files, but it didn't go through the proper install mechanism.