msmcleod

@Kevin Roberts - I'm not sure if this will help or not, but I've got Firefox set as my default browser on Windows 7. This is one of the few browsers which is still receiving security updates. When I went to re-activate, it fired up Firefox for me to login to my BandLab account, and once logged in, CbB re-authorised.

I've not looked into this in any detail, but in theory, you should be able to use this to use Atmos in CbB: https://fiedler-audio.com/ You may even be able to use CbB's surround panner (assuming the software presents itself as a hardware audio device), but I suspect you'll be limited to using WASAPI Shared or WDM to facilitate this.

It did occur to me that this might be the underlying cause of the issue, especially seeing as it's an older project with (most likely) and older version of Omnisphere. The symptoms of the issue would be that anything after Omnisphere in the synth rack would have it's outputs knocked off by one. Has anyone seeing this issue happen with a newer project?

Append Instrument Track only works if: 1. The synth has multiple audio outputs; and 2. The existing tracks are set to unique MIDI channel outputs/ Synth Audio inputs. If you've inserted the instrument as a "Per-Output Instrument Track", this is done automatically for you. If you've not, you need to go through all tracks using that synth making sure they have a unique MIDI output channel, and an audio input from unique audio synth output. Ideally, these should be in order, e.g.: Midi Channel 1 / Synth Audio Output 1 Midi Channel 2 / Synth Audio Output 2 etc.. Don't forget you also have to set up the routing within the VSTi itself, ensuring MIDI Channel 1 goes to Audio 1, MIDI Channel 2 goes to Audio 2 etc. Simple Instrument Tracks have a MIDI output channel of "none" (meaning all), so at the very least you'll need to change this to Channel 1.

While workspaces / screensets can work to a certain extent, they're a bit of a heavy handed approach. The Track Manager ( "H" is the keyboard shortcut ) can store/recall presets, so you can have as many sets of hidden / shown tracks or buses as you want. The new Sonar actually has a new button in the top left corner of both the tracks and console views, so you can quickly apply any preset you want without opening any dialogs.

When the name is highlighted, it means it's the Active Track or Bus. When the track number or bus is highlighted, it means the track or bus is selected. Any commands you run act on the track and/or bus selection - in other words, the selection is the source for commands. The Active Track can be seen as a target for certain commands - for example, if you've copied some tracks or clips, pasting will start on the Active Track. While the focused track is almost always the Active Track, being active doesn't mean it's actually focussed in the true sense ( i.e. a control on a different view or even a separate program could have focus).

The new setup file is a "bootstrap" installer - i.e. it automatically detects the latest version available, downloads it, and installs it. You should be able to safely run the 2023.09 update from any previous version of CbB, although if you're installing on Windows 7, it is technically not supported. None of your existing settings will be altered.

IIRC the last time this happened to me was due to a default algorithm not being set within Melodyne. I can't remember if I had to open Melodyne as a standalone and pick it there, or create a region FX on an audio file to pick it. Once the default had been set, everything was fine. I only had to do this in Melodyne 4 however. AFAIK if you're using Melodyne 5, Cakewalk will prompt you as to which algorithm to use.

I had no issues updating / installing / authenticating CbB 2023.09 on Windows 7, although I did get the usual "not supported" warning dialog when installing the update. My Windows 7 install has the all the latest Windows 7 updates. I didn't experience any issues running CbB 2023.09 on Windows 7 either, although to be fair it was a very quick smoke-test. The new Sonar will NOT install on Windows 7 or Windows 8/8.1. The new High Dpi / scalable UI support relies on features only available in Windows 10 and above.

To a certain extent, I'm in the same boat. I have a lot of older software (mainly hardware synth patch editors) that have 16-bit components, so I have to run them on Windows 7 32 bit; I also have some software that only works on Windows 7 64 bit. The way I got around this was to have a dual (actually quad) boot. On the same machine, I've got: SSD #1: Windows 10 64 bit - DAW boot, Windows 7 64 bit, Data partition SSD #2: Windows 10 64 bit - Development boot SSD #3: Windows 7 32 bit SSD #4: Projects When I start my PC, I get a boot menu to choose which operating system to boot with. My Data Partition holds any sample libraries that things VST's like Kontakt use. The drive letter is the same for all of my OS's, so there's only one copy of the samples that is used by all OS's. So the easiest way to solve your issue is to install Windows 10 on a new drive, leave your Windows 7 drive as is, and edit your boot menu so you can choose between them when you boot up. The only downside to this approach is licensing. Some plugins may see your different boots as separate machines, so you'll be using an additional license for them; others are clever enough to realise you're actually using the same machine.

It sounds like you've not got both the MIDI inputs and outputs checked for those. If this isn't the case, also check your Control Surface preferences to verify it's not "stolen" one of them because your MIDI device order has changed.

There are also options within Kontakt to tell it how many of the samples to load - i.e. all of them, or only to load "n" Mb, then the rest on demand. If Kontakt is configured to load all of the samples, it'll not only take an age to load a project, it'll take forever to shut down too as it frees up GB's of memory. What I tend to do is set it to load everything on demand, then play the project through once. This ensures it's only loaded the samples for the notes / velocities it's actually using.

If you've got "Non-destructive MIDI Editing" checked (which is the default), when a MIDI clip is split, a copy of the entire clip is made. All you need to do is drag the end of the clips out (i.e. a reverse trim) to reveal the copy of those events. If however, you're going to use cut or delete, the best thing to do is: 1. Select the event range as normal 2. Go to "Select by Filter", then uncheck the CC events you want to keep 3. Do your cut or delete If you've already done the cut, just copy one of the split clips you've left untouched to another track and drag the ends of the clip out - your original events should all be there.

You can have multiple articulations playing at the same time if you've set the articulation maps up properly. Articulations that are mutually exclusive (i.e. they cancel each other out) should be in the same group. If you have an articulation that can be played at the same time as another, it should be in a separate group. Different groups appear on separate articulation lanes.

Why not use Articulation Maps? They'll do the key switching for you, and are far easier to use in the PRV. Once your articulation maps are defined, you can even extract your existing key switches from your MIDI track it'll create the articulations for you. CreativeSauce does a great tutorial here:

It's also worth mentioning that Track Templates are in the drop down on the Media tab in the browser. You can simply drag/drop from there into your project - a massive time saver.

MF = Media Foundation

Take a look at shielded CAT 6 network cable - it's way cheaper than audio cable, and performs just as well if not better ( it has to cope with far higher frequencies with zero interference). If you share a ground, you can pass 4 balanced signals through a CAT 6 cable at a fraction of the price of audio cable. Sooner or later the industry will catch on to this and hike up the price accordingly!

Just to give some perspective here. The highest frequency a human can hear is around 20Khz if you're 21 or younger. As you get older, this continues to drop. I suspect the majority of users on this forum will struggle to hear anything over 15Khz. 44.1Hkz can reproduce frequencies up to 22Khz (so beyond human hearing). 16bit audio has a dynamic range of 96db across all of its frequencies. Compare this to tape: a maximum dynamic range 55db - with it's optimal frequency reproduction between 120Hz and 800Khz (it starts to drop off either end of these frequencies). Vinyl has a maximum dynamic range of 60db; frequency range is around 7hz to 50Khz (so better than a 96Khz sample rate). However as far as dynamic range is concerned, vinyl and tape aren't even a match for 12 bit audio (72db), which a bunch of budget synths/samplers used in the 80's/90's. Given that most tracks are of a single instrument, it's likely that the required dynamic range recorded on a single track is way less than 96db. Where things start to go wrong is when you mix in 16 bit - then you're dynamic range is significantly reduced. However NO modern DAW mixes in 16 bit. They all use at least 32 bit float or 64 bit float for mixing; only going back to 16bit at the stereo master bus. The advantage of recording in 24bit is you can record really quiet signals with no loss of dynamic range, and no perceived increase in noise. However, as long as you're recording signals at a decent level, there should be no issues using 44.1Khz/16bit for recording.... I mean, it's absolutely fine on CD. Comparing 32 bit to 24 bit is problematic - 24 bit is an integer format; 32 bit / 64 bit are floating point formats. Although you can store higher numbers in floating point (which is why it's great for mixing), you do lose precision at the extremes. For a mixed down song, a 24 bit integer file and a 32 bit floating point file are equivalent in quality.

I can repro this issue, but unfortunately the ship has sailed for CbB, so it'll have to be fixed in Sonar. In the meantime, make sure both the track and bus are solo'd.

I tried installing / activating CbB 2023.09 on my Windows 7 boot, and had no issues. I'm using Firefox as my main browser (it's the only one that still receives updates). There should be no problems with Windows 7 activation as long as it's got all the latest Windows updates.

There are two things I can think of that could cause this: 1. Select Sections with Time Ruler is checked 2. Ripple Edit All is on.

They do need to be registered as COM objects in the registry though. The CbB installer does this automatically. Manual registration has to be done with regsvr32.

There are several ways to do this: Method 1 - I find this is the easiest and gives consistently good audio quality: 1. Ensure the Time Format for each audio clip is M:B:T - this will ensure the start times move automatically with tempo. 2. Take a note of the end times (in M:B:T) of each audio track before you change tempo. 3. Change the project tempo 4. Hold down CTRL + SHIFT and stretch the audio track end times to the same M:B:T's you wrote down in step 2. 5. Bounce to clip(s) on each clip to render in higher quality. Method 2 - very quick & easy, although audio quality may vary depending on material*: 1. Select all of your audio clips, then go to the Groove Clip tab in the clip properties and check "Stretch to Tempo" while holding down CTRL. 2. Ensure "Original Tempo" matches the current project tempo 3. Change the project tempo - the audio clips will automatically stretch. 4. Bounce to clip(s) on each clip to render in higher quality. *I can't be 100% sure, but if you've correctly identified the transients beforehand, the quality may improve Method 3 - Audio Snap There are plenty of YouTube videos on how to use this. This is arguably the best quality, but depending on transient/tempo detection can either be very quick or a painfully manual process. If you have many audio tracks however, it may be favourable to Method 1.

By default, Cakewalk will assign the outputs as you've described to better support extenders without further configuration. If you want to override this: 1. Open the Mackie Control surface dialog from the Utilities menu. 2. Click the "Configure Layout" button 3. Within TouchDAW, turn the v-pot on the first channel so that the display shows channels 1-8. 4. Click the "Press Again When Done" button on the Mackie Control surface dialog 5. Save your configuration as a preset within the Mackie Control surface dialog, and close the dialog. However, the MackieControl wasn't really designed to work this way - you may get the two surfaces fighting each other. If you do have issues, consider downloading/installing my version of the Mackie Control software: https://msmcleod.co.uk/cakewalk/MMcLMackieControlSetup.zip Once installed, restart Cakewalk and use "MMcL Mackie Control #1" for TouchDAW, leaving the SSL on Cakewalk's Mackie Control. Currently, my version of the Mackie Control is identical to Cakewalk's but is registered using its own unique id, so it's seen as separate from the Cakewalk one. This allows the two surfaces to operate independently, but still follow the same channels.