Starship Krupa

These are all fine ideas, but they require employees or consultants to do them. As far as I know, the only staff on Cakewalk are the developers and support. From my observations, BandLab's promotional budget for Cakewalk is next to nil. The only money I've seen them spend was sending some staff to Anaheim for the NAMM Show a couple of years back when we used to have NAMM Shows. I've suggested that there be Cakewalk laptop stickers and t-shirts made available for purchase. I've done some cleanup work on a few of the legacy Wikipedia pages, and made sure that Cakewalk by Bandlab is on all of the lists of DAW's and audio software, but there's still no page for Cakewalk by Bandlab itself.

I'm in favor of exposing as many commands as possible to keystroke bindings.

I haven't read the VST licensing agreement, but it would not have been good business sense to sign anything that would permit Steinberg to force you to stop selling existing plug-ins and hosts you made under the agreement. Adoption of the VST spec would have been hindered; who would give control over such a thing to a competitor? It just occurred to me that there is another negative scenario: although I'm pretty sure that anyone who got a VST2 license prior to 2018 has it in perpetuity (meaning they can carry on supporting VST2 with plug-ins and hosts), this may prevent host support for VST2 by new companies. So if you want a DAW from a brand new maker of them, it might not be able to load your VST2's without something like Unify. Again, no biggie for me, I am not in the market for a new DAW or NLE, and if I just had to have one from a new company, there is always Unify, and I imagine other shells/wrappers. And there may be a loophole where an old license could be utilised. Silver lining: whenever Steinberg flexes like this, it provides encouragement for advancement of other formats. So far none have really taken off, but there is the example of MIDI 40 years ago. Sometimes companies can work together for the good of all. The trouble is, though, MIDI hasn't advanced very much in those decades.

Really, the question of text etiquette is more important than the matter of Steinberg pulling VST2 support from their DAW's, unless they're Cubase users. It will affect nobody else. Other DAW manufacturers have no reason whatsoever to discontinue support for the VST2 format. Actually, the announcement gives them a competitive advantage over Cubase and Nuendo, and they don't even have to write any new code. It takes a long, long time for plug-in formats to fade away, unless a company forces the issue on their users. There are DAW's and NLE's out there other than Cakewalk that still support DX. All of Vegas Pro's audio FX are still in that format. Some audio hosts have yet to support VST3. If I were a Cubase user, I would be royally urinated; my iLok is full of plug-ins that only come in VST2 format, such as Exponential Phoenix, R2, R4 and Nimbus, and all of my AIR synths. These are my most-used go-to FX and instruments, used on every single project, and in both cases, I'm pretty sure there are never going to be VST3 versions of them, because the developers have long since frozen their code. About half of Glitchmachines' product line is VST2-only. Even if I were at all interested in Cubase, this announcement puts it entirely off the table for me. Who wants to do projects in a DAW where the next major update will make all of their existing projects obsolete? It's a minus for Steinberg and their user base. For everyone else, it's a snooze.

Up at the top of the topic, there's a button for "follow." If you follow a topic, you'll get notifications whenever someone replies. This. iZotope's stuff is great, but it's like a self-driving car: you still need to know your destination. :-) Here's my brain dump on masking and highpassing. At this point in my mix engineering learning, I know how to prevent a lot of buildups and collisions before they occur, but what I do to check to see if something's being masked, or colliding or whatever, is close my eyes and listen closely. Most of the time, if an instrument is supposed to be a featured part of the mix, you should be able to hear it clearly, as an individual element. The exception is where you want something like a pad or texture to provide an atmosphere. Something that The Beatles did in their post-Rubber Soul studio career, and Brian Wilson, Phil Spector. The idea is that every instrument should have its own sonic space. There are multiple ways to accomplish that, the first thing to do is "carve," which means that you use EQ to notch or highpass out the overlapping frequencies from one instrument to reveal the other(s). This happens with instruments whose ranges overlap. Bass guitar and kick drum is where everyone starts. You have to choose which one is going to take the very bottom, and then highpass the other one. Sidechaining, where the signal from the kick ducks the bass, is popular, especially in EDM. Wavesfactory makes what is probably the best single plug-in for eliminating masking, Trackspacer. It works via sidechaining. Wait for it to go on sale for about $40 and pounce. I think iZotope Neutron has facilities for doing this, but I had Trackspacer before I got Neutron, so I haven't spent much time checking it out. The next tip is highpassing. Most full-range instruments like guitar, keyboards and voice have information in the low end that is unnecessary in a full mix. Listen to The Beatles' acoustic guitars, and Tom Petty and the Heartbreakers'. Martin and Emerick highpassed The Beatles guitars and vocals like crazy. All you get is the top end, which with strummed acoustic guitar is all you want to hear in a full mix. Same with organ and piano (solo or sparse mixes are another story). My go-to for highpassing is the ProChannel Quadcurve EQ, but most EQ's have high and low pass filters. I would choose one with a graphical display like the Quadcurve, or iZotope's most excellent EQ. I'll highpass a vocal up to 400 or 500Hz or higher. Same with rhythm guitar. Highpassing has a magic counterintuitive (at first) effect, which is that you'll start to hear more bass, due to letting one instrument have that sonic space. Another technique that's essential to know, and I'm sure the iZotope AI knows how to do it, is finding and cutting the "honk" or "bark" frequencies of sounds. These are nasal or tubby or shrill frequencies that can make a sound poke out in a mix rather than having its own space. Most of the time it's good to do this, but not all the time, sometimes, those frequencies help the sound stand out in a good way. It can also be counterintuitive: cutting the loudest frequency allows you to push the sound's level higher in the mix, so it ends up becoming more audible. This is the main bread-and-butter use of compression on individual sounds. They don't poke out, so you can crank them. Lastly, and this is next-level stuff, you can create sonic space with panning and use of mid/side techniques. If you have rhythm guitar and organ, pan them apart from each other. I'm really into mid-side EQ and compression. It sounds more complicated than it is, basically it just means the processing gets applied to either sounds common to both Left and Right, the mono component, or it gets applied to the sound that spread outside the center, the stereo component. So think of a big keyboard pad, a lush stereo sound. You can give it its own sonic space by compressing or attenuating the middle and letting the sides come through. That way, other instruments that are center panned have that physical space to themselves. A lot of the time, synth sounds stack up at the sides, because big, wide pads sound great by themselves. But unless the pad is a featured sound, it doesn't need to take up the entire panorama to do its job. Mid-side EQ works the same way, you can cut the highs in the center and let them come through on the side, or whatever. If you get into this, you should check your mix in mono before putting it out there. Boz' freeware Panipulator is my tool of choice for that. Close listening to well-mixed material will give you a better idea of these concepts. One of the best acts ever for having mixes that give each instrument its own space is Steely Dan. Throw Aja on your studio monitors or good cans, listen to "Peg" or the title track, and you'll hear every note from every instrument. Also an iconic singer who once hated his own voice to the point that on their first album, there are 3 different lead vocalists. They even let the drummer sing one, so we know how desperate they were. All this is more what you can do, rather than precisely how, but maybe it will help you make better use of the iZotope software. Even with great AI, it's important to understand what the goals of applying it are. And maybe someday you'll be able to outdo the iZotope AI. After all, it doesn't know exactly what you're going for. It was a triumphant moment for me when I could outdo the Mastering Assistant in Ozone Elements.

I think I have a teensy addition: on p. 31, Track view/Unfocused Track Background is used for folders as well as un-selected tracks.

Is it unreasonable to expect people to follow a social convention that's been around for over a quarter of a century? It's been that way for a long time. All caps=shouting. All lower case=teenage girl who writes poetry.

Just overheads. As is typical with Meldaproducts, I found the documentation to be unhelpful in respect to suggested use scenarios. I picked up what I could from the Meldaproduction forum and came to the conclusion that my drum kit would be happier if I just used MAutoalign on the overheads. You know how much respect I have for Vojtech and his products, but the lack of application notes in his documentation is so frustrating. The plug-ins are amazing, and have really deep feature sets, but about half the time I don't even know what the feature or even the entire plug-in is supposed to do. MDrumleveler is an example. I can't figure out if I'm supposed to use it on individual drum mics, the overheads, the whole drum bus, or what. So a potentially useful plug-in just sits. Same with some of the others I got in the Essentials bundle. And with a lot of the ones I do use, I feel like I'm living in a house with rooms I've never gone into. 😄 The ones I do use are worth every penny I've spent and a lot more, but there's a lot of signal processing going to waste. Matter of fact, I took a look at what Nugen has to offer and concluded that there's nothing I want that isn't already covered by Meldathings like MSpectralPan. But again, it was reading the ad copy for the competitor's product that got me to understand the possible applications for MSpectralPan. That seems wrong, somehow.😏 P.S. I know that Chandler has done YouTube videos for a lot of Meldaproduction products, but I don't retain as well from videos as I do written material.

No, but I've had the Audacity to check out the LADSPA. 😄

So it's very similar to MAutoalign in that respect. 😄 I love MAutoalign, it's part of my drum recording templates for my overheads. Unfortunately, my overheads are spaced far apart in a Glyn Johns/Recorderman configuration, so it has a hard time. After all, according to my understanding, since the different elements of my kit are at different distances from these mics, MAutoalign can't completely figure out what "in phase" is. Is it for the snare, the kick, the ride cymbal? I need to experiment some with the pre-filtering so I can narrow it down to snare, which is where I center my mic distances. As it is, I just do multiple samplings and pick the one that sounds best, although I suspect that what I'm getting is a slight Haas effect😄. If it sounds good, it is good. It works as advertised on close mic'd acoustic guitar, though. The Nugen Aligner manual suggests doing the analysis from a single drum hit, which gives me the idea that at the beginning of a drum session, I should play some paradiddles on the snare for about 10 seconds to give MAutoalign or Aligner something easier to digest. And it occurs to me that it's sad that I should be picking up MAutoalign tips from another company's documentation.

Seven very detailed themes and counting over here! They each even have custom color presets! Link's in my sig! Enjoy! You'll love my custom buttons and iconography, really! 😄 (I work on themes while I'm waiting for musical inspiration to return, so that gives you some idea of how much time I spend waiting for musical inspiration to return) The thing about the Start Screen, for those of us who use it, is that it's the first thing we see when we start the program. So having it look nice and tidy and welcoming and inspiring is important. For much of the music world these days, and this includes me with the electronica I'm currently into, the DAW is the instrument. How much attention do guitarists put into the look of their instruments? And why? An instrument (or any other creative tool) should inspire you to pick it up and use it. If the first thing we see when we go to start a new project is a screen with our fine-tuned template projects, but with ugly generic icons that we've been unable to change, it's less inspiring. It's like having a cluttered workspace. Another reason is that it's basically just really fun to customize your stuff. Car, clothes, home, whatever, people love to put our personal stamp on the things we use. It makes them more "ours." Theme Editor is (obviously) one of my favorite features of Cakewalk for this reason. People aren't good at searching, I guess. I resigned myself to that a long time ago, but bonus: being a black belt in search engines makes me look way more knowledgeable than I really am. And BTW, although I consider myself a Google ninja, I have a lady dog of a time with the search function in this forum. Raising the dead thread means that at least new forumite Tree did do a search, but instead of finding the more extensive ongoing thread over in Tutorials, they found this one.

Ha, I found it on Zzounds. The ad has a bunch of good hi-res screenshots. It's interesting to see various features before they were rolled into Sonar. https://www.zzounds.com/item--CAKPROJECT5

WASAPI Shared allows other programs and the OS, for example system sounds (which you should have disabled on a DAW system anyway) to jump in and use the audio system, and to do this, it sits there waiting to get input from them. WASAPI Exclusive lets the program that has focus have exclusive uninterrupted use of the audio system, so it gives full attention to that. ASIO also gives exclusive attention to the program using it, and goes one better by bypassing the Windows audio subsystem for even greater efficiency and purity of audio playback.

Yes. That's a sure sign that you selected the FL Studio ASIO wrapper, which is basically ASIO4ALL. ASIO4ALL used to be pretty useful, but with the advent of WASAPI, it's needless, and Cakewalk doesn't like it, so the devs put in a checker. Plain ASIO4ALL will trigger it, the FL Studio ASIO will trigger it, and the Magix ASIO driver will trigger it. Probably others. They're all ASIO4ALL with just the logo changed. Your problems are surely down to using WASAPI Shared. The preferred driver is the Focusrite ASIO driver, and after that, WASAPI Exclusive.

Cakewalk should run just fine on that system, when properly configured. And it's not about what's "at fault" your computer or Cakewalk, it's a matter of getting them to play nice together. If the other DAW's work fine on your system, Cakewalk should also, and it suggests that we need to look at how Cakewalk is configured. Some things we need to know in order to help you: What model of Focusrite interace? In Cakewalk's Preferences/Audio/Playback and Recording, what driver mode are you using (WASAPI, ASIO)? By "what else is running on your system," I think b meant "open Task Manager and check to see if there are any weird processes."