msmcleod

It's partly because Windows 7 is no longer supported by Microsoft, partly down to us not having the resources to test unsupported OS's, but mostly down to future development being potentially held back due to older operating systems.

Yes, it's available in the early access release:

Although not officially supported, the latest version of Cakewalk should work fine with Windows 7. Download the latest version of BandLab Assistant, then go to the Apps tab to update: https://www.bandlab.com/products/cakewalk

Go to Preferences->Customization->Editing and un-check "Split MIDI Notes".

Isn't what you're both describing exactly what clip gain automation is? I don't get it - you want two types of clip automation?

One thing I would say, is that everyone I know who's gone for a 4K monitor says they'd never go back to 1080P... so I would take my original comments as a purely personal stance. I actually used to use a 2 monitor setup with CbB, but switched to a single 1080P setup so that I'd feel comfortable switching between my laptop & my studio setup. Screensets in CbB are the perfect solution for me. The other reason is my eyes aren't great nowadays. I've been very slightly long-sighted for the past 30 years, so for the most part my eye sight is fine, but I do struggle sometimes with small text close up. I try to avoid using glasses unless I'm straining to see (which is usually when I'm tired or the lighting is bad), but I don't want to build up a reliance on them. For me 27" 1080P monitor at 1m away is very comfortable. A 23" monitor is fine at around 75cm, but I do need to use glasses with a 15" laptop screen. When my optician says I need to wear the glasses pretty much full-time, I'll no doubt opt for a 4K at that point!

Doing a google search for: lurssen mastering console CPU usage ... brings up a post from just about every main DAW's forum complaining about the same issue. FL Studio, Cakewalk, Pro Tools, Studio One... they're all there. So I suspect it's an issue specific to LMC. I get similarly high Audio Processing / Engine Load values to you, and see the same behaviour when making the GUI small. In saying that, I'm running at 64 samples and not getting any dropouts or crackles. That's running LMC v1.03 on an i5 3570 @ 3.4Ghz [4 cores ], 16Gb RAM, 2TB SSD, Scarlett 6i6 1st gen. Interestingly, changing the buffer size and/or using x2 up-sampling doesn't seem to make much of a difference at all to the CPU load, which leads me to suspect the CPU load isn't in the LMC's audio processing side. I've got v1.10 on my laptop running in WASAPI mode, and it's pretty much the same - pretty high load, but not enough to cause crackles or dropouts. [Edit] - Here's what I'm seeing using 2 x oversampling with a buffer size of 64:

This will be available in the next 2020.05 release.

@Frank DeFede - if you're happy with your mixes, and they're not clipping, just export the stereo wav files and check them in one of the many audio checking apps out there. For example: Loudness Penalty Analyzer: https://www.loudnesspenalty.com/ Expose by Mastering the Mix: https://www.masteringthemix.com/products/expose The most you should need to do is lower the level of your stereo files. You shouldn't need to remix from scratch.

@Tommy Byrnes - the main change since the March update is the arranger feature, which uses DirectDraw under the hood for the UI. So the issue you're seeing could be caused by an issue with your DirectX drivers. You could try running dxdiag to see if there's any issues with your driver config: https://www.howtogeek.com/258485/how-to-use-the-directx-diagnostic-in-windows/

There is a quicker way by just keeping the filter in Clip Automation Gain, then select at the bottom half and adjust from the top half. No modifiers involved - just left click:

It's unclear what you're trying to do... are you trying to move the section without the data? Or are you saying that you're trying to move the section WITH the data, but the data is getting deleted?

Duplicate Clips with Ripple on is fixed in the 2020.05 EA release, however it became clear when fixing this that ripple edit isn't fully supported for all cases in the PRV. I suspect that this might explain some of the oddities people are seeing. The best advice I can give for the meantime, is to make sure you do any ripple edits in the track view. Position locked clips are exactly that - their position is locked, so they don't move. I think you're expecting the lock to act more like an "anchor" rather than a lock... which Cakewalk doesn't currently do.

I used to use a 23" 1080P monitor in my studio which is the smallest screen I could cope with for my ageing eyes. The 4K equivalent would be 4 x that, so a 46" monitor (not sure you can get one in that size). But anyhow, I tried sitting 3' away from a 40" TV and there was no way I could cope with being so close to such a large screen. I've since upgraded to a 27" 1080P monitor in the studio and it's perfect for me. I'd love to have another one next to it, but unfortunately I've not got the room

One of the other ways I translate my "old skool" ways to working in the box... I try to make a distinction between tracking, mixing and mastering. IMO it's far too easy/convenient to blur these when working with a DAW, when in fact I actually find it makes things more complicated as you move further along the process. If I've tracked an instrument by going straight through the DI, I'll then spend some time using a channel strip, compressor, EQ etc to get the sound I want for that instrument. This I always do in solo because at this point I'm essentially doing sound design. In the old days, I'd have done this before it went to tape (i.e. though preamps/console/outboard)... but now I can do it after I've recorded it by adding the "tracking" console emulation afterwards. Once the sound is what I want, I'll bounce it so all I've got is a clean track. I'll do that with all my tracks, so I've got a clean slate to work from for mixing. If I didn't do this, there would be possible confusion between which plugins are sound-design, and which plugins are for mixing - not to mention the extra CPU load. Then I mix... Once I've done my mix, I bounce to a stereo track and master ONLY on that stereo track.

Occasionally Windows updates don't update properly. I found this with the most recent update, which was causing my system to occasionally BSOD on reboot. What I normally do is run a cmd window as admin and run a system file check: More info on what this does : https://answers.microsoft.com/en-us/windows/forum/windows_10-update/system-file-check-sfc-scan-and-repair-system-files/bc609315-da1f-4775-812c-695b60477a93

Re-installing CbB should be pretty painless - it doesn't alter any user settings. I quite often do it several times a day. The easiest way to do this would be to run the rollback installer, then install 2020.04 again via BandLab assistant. A link to the rollback installer is in this post:

Thinking about it, I can see why MAutoAlign would have issues with overheads. Even if you'd measured your mic positions so it was equal distance from the snare, the snare would be the ONLY instrument that would be in time with both mics. Every other drum/cymbal would reach the mics at different times. Any auto-alignment tool would struggle with that if they're all playing together. If it was say something like a bass amp mic + DI signal then MAutoAlign would work fine.

There should be absolutely no reason to run ASIO4ALL with the 18i20. ASIO4ALL is a "fake" ASIO driver for use with audio interfaces that don't have a native ASIO driver. The 18i20 has it's own ASIO driver specifically written for it. My recomendations: 1. Uninstall ASIO4ALL completely 2. Install the latest Focusrite Control 3.5.0 3. Switch to ASIO mode in Cakewalk

You need to upload animated gifs to an external website, and then use Insert other media->Insert Image from URL.

I think you're best approach is to keep trying with Focusrite. I'm surprised at your comment that they're not recommending using ASIO - was this directly from Focusrite themselves? They did have quite a few BSOD issues with their driver, which they fixed in a beta version ( you can see the beta releases at http://beta.focusrite.com ) . For the 1st gen at least, they combined the latest firmware, MixControl and 4.64.15 USB driver in that beta. The official release for the 1st gen includes the previous version (4.63.24.564) of the USB driver. However installing the official 1st gen 2i2 ASIO USB driver brings it up to the latest - so essentially the same as the beta. For the 3rd gen though, the drivers are different. You said in an earlier post, you're using the v2.14 driver- the latest for the 3rd gen should be Focusrite Control v3.5.0: https://customer.focusrite.com/en/support/downloads?brand=Focusrite&product_by_range=1359&download_type=software I'd recommend giving the v3.5.0 a go, and if this doesn't solve your issue use WASAPI in the meantime.

@Laszlo Mayer - what revision of the 18i20 are you using? I'm still on the 1st gen.

I've got to admit, I'm pretty old-school in my approach. When tracking, I try to record the sound exactly as I want it to be heard, which means recording it with compression + EQ etc already applied. The only exception to this is guitar, where I record both the dry and the effected signal. Vocals also tend to be recorded dry. With mixing, any edits are destructive. If I'm getting rid of bleed or rumbles in silence, I'll permanently remove it. Same with any pitch or timing correction. My reasoning being that if it sounded bad enough to need to be edited, then there's no way I'd want to keep the original... though if it's someone else's performance, I'll just keep a backup of the original files. In saying that, I'm much more likely to re-record a bad take than resort to editing. The end result is a much simpler session to work with, less plugins/automation, and much less strain on my CPU. With Cakewalk though, you can effectively do both by archiving / hiding the original tracks and work with copies.

The envelope issue has been fixed for the next release. The PRV issue will need further investigation.

If you can't use ASIO use WASAPI. You'll get terrible latency with MME - this should only be used as a last resort. Then go into Preferences -> Audio -> Devices and make sure "Show Mono Outputs" is checked. Out of interest, what version of the ASIO driver are you using? I'm using v4.64.15 without issue.