msmcleod

First, make sure you've got "Show Mono Outputs" enabled: Then the channels are assigned like this: For drums, I guess you'll probably for the most part be using the mono inputs.

I've currently got Editor, and I'm seriously considering upgrading to Studio. The main reason being that the new Chord analysis feature works across multiple tracks, and takes all of the tracks into account when figuring out what the chords are.

I think the only thing you can do is use your ART as the timing/playback master, and live with the fact that your Shure might be a few milliseconds out. It should be easy enough to nudge the recorded clip once recorded if its timing is slightly out. In reality though, I don't think you'll notice any audible difference in timing. Personally I always advise people against getting USB mics, unless they're ONLY doing podcasts. Most decent mics (and your Shure, being a Shure, probably is a decent mic) have non-USB equivalents, and I'll steer people towards them instead. There's two reasons for this: 1. The ASIO "one driver at a time issue" you've encountered; and 2. With a standard XLR mic, you've got a choice of preamps and interfaces. When you upgrade your preamp/interface, you can still use your mic. With a USB mic, it's also the preamp and the interface, and you've not choice at all. [Edit] - You could use ASIO4ALL or ASIOLink as an alternative way of combining these interfaces. ASIO4ALL will use the WDM mode of both interfaces, and present it to Cakewalk as ASIO. ASIOLink can use ASIO mode for the ART, and WDM for the Shure - presenting them both to Cakewalk as ASIO. The configuration of both can be a bit of a hassle though - ASIOLink especially so.

A CAL script would probably do it... but it would be fairly complicated tho. The split notes to tracks script is probably the place to start, but the logic will be different. The way I would approach it would be to give it a max number of tracks, then go through and individually move the top notes to the 1st track. I'd store the start time/duration of the moved note, so I would skip the others at the same time period (leaving them for the next "round"). Making sure you always get the top note might be tricky, but I guess you could read a maximum of n number of notes and choose the highest one. Then rewind and repeat for the 2nd track, and so on. The logic described above may sound a bit weird... but CAL is no normal scripting language!

FWIW I still use sf2 as my preferred sampling format. My main reasons: 1. They're easy to manage as they're self contained (unlike sfz which has all the samples loose in a separate folder). I can also easily combine many of them into a single sound-font. 2. It's supported by several different players across many platforms. 3. Most players are far lighter on CPU than something like Kontakt. The only thing that I find missing from sf2 is it not supporting release samples, but I've never found this to be a huge issue. Setting the release time on the player usually suffices for me. Sure, if you want massive control over your samples and need scripting, then Kontakt is the way to go... but 99% of the time sf2 does the job. Oh, and I use SampleLord as my preferred player. It's 32 bit so I run it through JBridge in CbB. I also have it running on my SMPro V-Machine.

It's not in the EA release. It'll be in the main release.

As it stands it won't be bound to anything by default, but you'll be able to bind it yourself. I've bound mine to ALT + F2 so it doesn't interfere with using F2 for renaming tracks.

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

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!

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/

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.