Starship Krupa

TrueVerb is a great, natural-sounding reverb. It has a very thorough and comprehensive manual and if you dig into the Waves website's free downloads page, there's a file with celebrity presets including some good ones for TrueVerb.

Thank you, more precisely what Cakewalk by BandLab's licensing is is a free subscription, like Tape Op. We all know about Tape Op, right? Don't cost nothin', but once a year they contact you and at that time you need to confirm that you still want it and that your mailing address is still the same. Then they keep sending you your monthly issue. Similar deal with CbB, only the terms and mechanism are slightly different. There's a little program that contacts their servers and blesses your installation of CbB and it just needs to do that at least once every 6 months or CbB will slip back into demo mode. Anyone who wants to try to "bash" me for stating that obvious truth, step right up.

BandLab doesn't have a version of Sonar. Sonar was a program that used to licensed for a fee by a company called Cakewalk. Now a company called BandLab licenses a program called Cakewalk for free. Confusing, I know. All you need to know is that that Cakewalk is a thing. Sonar is defunct. It is no more. I have run Sampletank 3 under Cakewalk by BandLab and it has crashed the host program in both its VST2 and VST3 versions. I would not recommend attempting to run the combination in a live performance situation.

The L-Phase series would be such a joy to have available.

I love the way Mixcraft implemented it. Every folder is a submix, with full FX rack, automation, everything, and you can nest them infinitely and take stems from any of them you wish. Drag and drop a submix into another submix and it's nested. You can expand and collapse them to save screen real estate as you wish. The program also has buses that function just as buses do in Cakewalk. Mixcraft was obviously strongly influenced by Sonar, and it would be nice to see the influence come back around to Cakewalk.

Funny you should mention it, Grem, he already owns a Tascam Digital Portastudio, which he hasn't gotten around to using due to technophobia. I'm suggesting a workflow of tracking to the Tascam, then transferring to the notebook, where he can either work on it himself or pass it along to me. A friend bequeathed to me his Zoom Q8 camcorder with the X-Y mic pair and I did a band video shoot for some friends' 4-piece rock band using just the built-in X-Y pair and a single dynamic for the lead singer, and we were all very happy with the result. Now you know what my living room looks like. And my 1970 Slingerland New Rock kit (that's not me playing it).

Good to hear the news about Ryzen optimization. Also good to get the word on clock speed being the better thing to seek than number of cores. I'm trying to help a buddy spend some money on a Windows notebook, and he wants to run Cakewalk on it, he identifies as a comp-u-phobe and I figure that if he ever works his way up to 4 simultaneous tracks of audio that'll be pretty neat. He's been sending me iPhone Voice Memos of band practice jams that I've had fun seeing how good I can make sound using the tools I have available to me. I've been trying to ignite his interest from there by telling him that all he needs is a not-even-that-powerful notebook computer (I usually work my "magic" on my #2 system, an aging Core 2 Quad that just loves CbB), and he can get miles better audio quality even if he only just sets up a couple of dynamic mics into a mixer so he can give me a stereo recording to work with using the onboard sound chip. I know that anything that can boot Windows 10 would work for him, but I'd like to minimize his investment and maximize his gain. Keep it under a grand I guess. My hunch was AMD processor, go for clock speed, last year's technology? Optical drive might be nice to have for burning band CD's.

First, thank you for alerting me to the existence of this feature, second, I'm surprised it doesn't work that way in the first place. Or I would be if it weren't that Cakewalk seems rather non-real timey-wimey in odd places like when moving markers. Moving markers along the ruler always reminds me of playing fetch with a dog. I indicate where I want the marker to be and then it goes obediently charging off to take its place on the ruler. Same with moving clips and slip editing. I move a pale fragile ghost of the thing, then the actual thing comes along later.

Indeed, I agree that nested folders and submixes would make your task much simpler. There must be some way to adapt what I was suggesting, though, until such time as Cakewalk gets that feature. Perhaps by using Aux tracks? I would have to think about it more. How do you deal with this situation now when you are faced with it? Do you fork the project and set up all the routing manually as requested by the client? Do you do it in another DAW?

Another just outstanding theme, Matthew. I wish there were some kind of award I could nominate you for. And this theme should be called M-White?. I'm not a great fan of lighter themes myself, but this one I actually dig. Go figure. Are your latest "M" themes using what I think of as your "Netflix" wallpaper? I don't know because I have switched to my own custom one on my main DAW, but that was one sharp wallpaper, and served to remind me that I could set my own. I just wanted to sing your praises. I don't know why you do what you do, but if it's for "the nod," consider this a big one. Your work helps Cakewalk be more attractive and enjoyable for me to use, helps me to be enthusiastic about recording in general, and that's sharing the love.

Not once but twice for heaven's sake. And I wasn't being pedantic or nitpicking, it's common courtesy, and a gesture of parley when discussions like this one get heated, to show that one is not merely trolling. But I guess there wasn't much interest in that. I think it might be time to hit ye olde philtre of kille.

That's one of the goals of freezing an instrument/synth track, innit? Not only do you get the benefit of the FX' resources being freed up, you get the synth itself out of the picture as well. Not just the CPU, but I just checked what you said and CbB seems to be pretty good at unloading the synth from memory. I see that even the blessed Ref. Guide (BRG) doesn't do the best job of explaining this. It just says "to reduce the amount of CPU power needed," but thank heaven it extends to RAM as well. That's a dearer commodity around the Krupa household at the moment than CPU cycles. My CPU cores seem to mostly just sit around waiting for me to load an iZotope plug-in. For the benefit of others, from my experience with other DAW's, what's supposed to happen with frozen tracks is you get a fully-rendered audio version of a track so that you can use it for mixing, overdubbing, whatever and not incur the overhead of whatever plug-ins you loaded on the track. The host should "park" any track FX or synths until you unfreeze it, resulting in more CPU and memory for the other tracks to play with. This parking happens in a variety of ways to varying degrees of effectiveness depending on the host. Some hosts even let you decide what quality you want to use for frozen tracks, like you can use .OGG for frozen tracks in Mixcraft I think. It's good for when you want to track a lead vocal at low latency with this huge virtual sampled orchestral backing. Bang, freeze everything to OGG Vorbis and Mixcraft has the resource footprint of an MP3 player while your singer is singing to the LA Philharmonic and a rock band with a zillion effects. My hunch is that freezing an instrument track with FX is probably simple as things go, the DAW just needs to render a single track as it normally would and then unload the plug-ins. But un-freezing an instrument track seems like a task that would be fraught with a bit more danger. Depending on how the host turns the synth off, turning it back on might get weird. I've looked around and the only button for turning a synth plug-in on or off that I could find was in the Synth Rack, not in the Track Header or Console or plug-in UI. And what does this button do, exactly? Does it just grey out the UI or route audio around it or partially unload it from memory or what? It seems to reduce the memory usage a little more than freezing. Do does the host turn on the synth first and then the FX, or the FX first, or what? Lots of decisions. I tried to get some answers to these questions from other companies and crickets chirped. You know, stuff like "when I bypass a VST, does the audio route around it? Should I completely delete a VST from my plug-in rack to get it out of the audio path?"

It doesn't necessarily follow that there was something in the VST3 spec that allowed Melodyne to incorporate ARA, it just means that Celemony went along with the VST3=more advanced technology narrative. It's also a convenient way to filter out older hosts, because no host that only supports VST2 is going to support ARA. They might also have done it to get chummy or remain chummy with friends at Steinberg. I do you a favor now, you do us a favor down the road. As far as Vocal Rider, I just took a peek at it, and as I suspected, it does its thing via sidechaining. VST3 allowed Waves to have a button called "Sidechain" in the VST3 versions of its plug-ins. If you look at the instructions for the AAX and AU versions of Vocal Rider, they give the non-PlaySkool version that most other plug-in companies still use, where the host automatically sees that the plug-in has external inputs and creates routing for them. Nice position Steinberg was in: if the programmers of your host can't or don't want to figure out how to do that, like with Cubase and Nuendo, you can take the easy route (ha ha) and just come out with a new plug-in spec that forces the plug-in manufacturers to build sidechain routing into the plug-ins themselves. Make them do it for you! When I went to Steinberg's page on the (B)ST3 "revolution" and read the part about how plug-ins were now going to support this new thing "sidechaining," I had to stop for a moment and blink because I was wondering if they were talking about the same thing I had been doing for years. Nope, same thing, routing audio from a track to a plug-in on another track. Wow. Look around on the DAW forums, and the only people who think that the advent of the VST3 spec rocked their world are Cubase and Nuendo users who say that sidechain routing used to be a big pain in the....sidechain. Everyone else says they work exactly the same except maybe they crash more, and some people are worried that eventually hosts will stop supporting VST2's and then their favorite plug-ins will be useless. I like the VST3 spec for exactly one reason, and that is because in practice at least, it seems to set a standard location for plug-ins. I don't know how well that works out for people with humongous VSTi sample libraries, but I don't like chasing .DLL's all over the place trying to find ones that wound up in C:\Program Files\Steinberg\Vstplugins or whatever. Waves' installers are great, funny even, for putting their plug-ins in every place a host is likely to look for them.

That is pretty cool, and what I consider "above and beyond the call." Of course every company has to decide how they are going to handle this. Is the issue with the host's code or the plug-in's code? Is the plug-in dev interested in coming up with a patch? How much will it cost to come up with a patch? Do enough users use the plug-in that it's worth bothering with? It's funny what politics can come into play. (cough-cough) years ago I was on the QA team for a high-end photo editing program that was positioning itself as a challenger to Photoshop. Yeah, right? Well, if nobody had challenged Pro Tools, we wouldn't be here today. Our program could host the same plug-ins that Photoshop could, and photo plug-ins are subject to the same kind of weirdness that audio ones are. They could refuse to load, crash, crash us, crash the whole system, etc. Some of these plug-in companies I've noticed, are still around today, doing some amazing work. The thing was, our programmers HATED anything to do with these plug-ins with the fire of a thousand suns. This was for a number of reasons. First, Adobe had "created" the spec to work best with Photoshop just like VST was "created" to work best with Cubase. When did Ableton start supporting VST? Only in their last revision or something? In Pro Tools you still need a 3rd-party wrapper? The truth with these specs is that especially at first they're usually pretty sloppily drafted, and they're drafted after the programmers at the company are already coding plug-ins. These are programmers who have access to every line of code in the host program, so they can do it without the spec anyway. On the host side, what incentive do they have to make things easy for their competition? Just being nice? Is Steinberg going to smooth the waters for Digidesign and Cakewalk and PreSonus and Ableton and ImageLine and Magix? Is it any wonder that so many rejected VST for so long? Cakewalk bet on DX, Digi went their own way, the others have their own proprietary systems and VST support is or was a premium option. So outside Adobe, all we and the 3rd party plug-in devs had to go on was this roughly-drafted spec that may not have been drafted to encourage Adobe's competitors to succeed in the first place, knowhatimean? Second, the people who had made these plug-ins only had Photoshop to work with and test with, and they were not that enthusiastic about possibly having a second program on the scene to make sure their products were compatible with. It was hard enough to work with Adobe. They had little interest in seeing us succeed. Third, third-party add-ons in general are just a pain in the tuchus to deal with. Introducing elements over which you have no control into your system is inviting trouble. What this all boiled down to was they would give us these great state-of-the-art plug-in packs to play with, and when they would crash the snot out of our program, our poor devs had no leverage whatsoever with the plug-in houses and their devs because their code had been burnished to a fine gloss to work smoothly with Photoshop. So any query about bad behavior was answered with "works fine with Photoshop." Whether it obeyed the published spec or not, all that mattered was "works fine with Photoshop." So hard to pinpoint the blame when a VSTi plug-in was coded using the Steinberg SDK and tested in-house and in beta in Cubase and Reaper and StudioOne and then the developer gets a report that CbB chokes after their synth comes out of a freeze. CbB works fine with hundreds of other VSTi's doing the same operation. Sektor works fine with a dozen other hosts (if you flip the VST2/3 coin a couple of times). CbB probably didn't exist in its current form when the synth was developed. Whaddaya bet that the next rev of Sektor fixes this issue?

I'm having a conniption fit over here. That's treating your product as a public beta. No wonder SONAR got a reputation for being a crash test dummy. BandLab seem to be running a tighter ship. You know, developers hate shipping software with bugs in it, it's like if we shipped a master with unwanted digital clipping in it or a dropout or an accidentally muted track or whatever. To me, this would be like if every record shipped with 5 different but similar mixes/masters, and not the "dance remix" or "2019 remaster" but the one the drummer did while the rest of the band was out buying brownies at the dispensary, and the one that the guitar player and his girlfriend liked, then the one that the producer and the record company liked, then one that had a killer feel but Don screwed up on that one part but they left it in, then one that everyone thought sounded good but the hi hat sounded ice-picky in the car, and the consumer is supposed to pick whichever one works the best on their system. If the "Don drops a clam" mix sounds jarring, try the one with the forward guitars. Don't sound good? Try the one that's all drums.

Yes, and I am amazed for the reason I said.

Oh good heavens, things were worse than I thought. Really? Wow. I wasn't kidding when I said that I'd never seen (nor heard of) any software company doing that, and given the egos I encountered when I was in the software biz, I find it astonishing. An OS update, yes, but they're usually touting the latest update as having fixed everything.

I've never seen any software company do that and it's hard to imagine one doing it. You get why: it's the equivalent of saying "we have so little faith in our QA process that we have this handy option for you to get rid of the latest and greatest improved version in case we've fscked it up." It will simply. Never. Happen.

Oh boy, can of worms there. Glad it's working. Cakewalk will substitute a VST3 for a VST2 if the plug-ins have a certain internal identifier set. Not every company uses this, so sometimes both plug-ins will show up in the pick lists in Cakewalk. Meldaproduction famously does not use the matching internal identifier, so I have to disable my 38 Meldaproduction VST2's using the Plug-In Manager. It's kind of funny that they thought that the "more advanced" VST3 would be the one that would have the problem! I'm not surprised, though, as my other DAW, Mixcraft, really doesn't like VST3's, to the point that as much as possible I avoid them when using Mixcraft. A sidenote, I'm just venting and it won't help paolo a bit, but this is the kind of thing that had me spitting nails when I dug more deeply into what was really behind Steinberg's much-touted VST3 spec and how little it actually covered and how little it was likely to improve things. Protecting the host and the plug-in from each other in case of errors, a standard protocol for trapping and handling errors, those are things that could have been part of a new VST spec that might have actually improved things, but instead what the industry got was mostly forced duplication of features that other companies had already implemented like sidechaining and GUI scaling. There was no big revolution where suddenly with VST3 my plug-ins started getting scalable GUI's and sidechaining, they all already had it if it were applicable. All I saw was plug-ins started to be distributed in both formats that worked exactly the same. Except the VST3 versions had more of a tendency to crash. I'm sure that for people who write these plug-ins, they write the code, then the development environment poops out various versions of the plug-in at compile time. We're at the mercy of the development environment and compiler when it comes to whether they're going to work well.

I like to have as much control of the end product as possible, so I prefer to supply all the formats myself as close to the source material as possible. If I let the client do this, they may take the FLAC I supply and make a low bitrate MP3 using a crappy converter, then when someone asks them for an AAC file, they may take their crappy MP3 file and use an even crappier converter to make a low bitrate M4A file and so on. And their converter program may apply its own limiting or compression or EQ or heaven knows what. Most people don't even know the difference between a 320K MP3 and a 120K one, and if a client wants "an MP3," I make sure to supply it as a 320K using the best CODEC I have available (Sound Forge, Cakewalk or MediaHuman). If they just say "send me the mix" I send it as a 320K M4A file, which everything will play these days. I also take the trouble to edit the internal file tags using MP3Tag so that when they play it back, the track name and their name (or my name) as artist scrolls across very nice in their player and my name as engineer, producer, etc. is embedded in the file if I want. This has resulted in clients and friends remarking that stuff I did for them sounded better and "how did you make my name show up on the car stereo?" ? And it just takes 5-10 minutes extra if that.

Wellll, see my snarky parenthetical comment about a person's issue usually being something other than an update to Cakewalk itself. I just do not believe that there are enough instances where an update to the CbB software actually hoses someone's DAW system for it to matter. What usually seems to happen, in my observation, is that an upgrade ships, then someone's setup breaks a few days later and the upgrade is only one of the things that has changed by that time, including updates to Windows 10, plug-ins, drivers, etc. I've noticed that the cries for rollbacks seldom happen right after an upgrade ships, which is when you would expect to hear them if they contained code likely to have great negative effect. To be fair, when someone is in ripping your hair out troubleshooting mode, it could come in quite handy to be able to at least eliminate the Cakewalk update as the source of injury. I'm putting this up as an answer to an oft-asked question, and in case savvy users like you and Mark want to archive older builds. I really, really wish there were a Tips 'n' Tricks subforum on here. I know there is a Tutorials forum, but that is for posting links to offsite tutorials. Steve Cook has already posted it more than once, but not with the flashy title as its own topic. This one can be bump't if we get tired of people asking.? As Mark said, it's for peace of mind. Not what I would consider a necessity. I don't actually do it myself. Each build of CbB is thoroughly raked over by a horde of beta testers, and if there were any further nastiness it would be intercepted instantly by people who automatically let BA have its way and would post on the forum. The devs would code up a patch and push it out right away. So for people in the middle of mission-critical projects and whatnot, simply waiting a few days after each version drops is what I would consider sufficient insurance against bugs. Cakewalk: The Vanishing was about the worst bug I've seen make it into the wild in the BandLab era, and it was squashed pretty quickly.

That is weird with a beard. I tried Googling the error message and got zero results. BandLab support is your best bet. Offhand, I would guess that it will turn out to be a folder permissions issue, that Cakewalk is trying to write to a folder that you as a user don't have access to for some reason. I have no suggestions as to how to fix it from here. It's the weekend, maybe tomorrow you will hear from support.

This is an oft-broached topic, people bemoaning that something doesn't work right after an upgrade or how do I roll back to the previous version, yada yada (before figuring out that it was something else that changed on their system that broke it), so I'll share a tip. Typically when CbB is updated, the major changes only occur in C:\Program Files\Cakewalk\Cakewalk Core (assuming you have installed Cakewalk in the default location, if you have not, adjust accordingly) If you want to upgrade to the latest version of CbB yet also retain the ability to run the previous version, all you need to do is make a copy of Cakewalk Core before you let the upgrade do its thing. If you want to get fancy, you can rename the copied folder to reflect exactly which revision of the program it contains. In this way you could have 2 or 3 revisions of CbB sitting there if you wanted to. To set this up: Right click on C:\Program Files\Cakewalk\Cakewalk Core and select Copy. Right click in the C:\Program Files\Cakewalk folder and select Paste. This will result in there being a new folder with the name "Cakewalk Core - Copy" which you can rename "Cakewalk Core Previous" or whatever. Then let the upgrade run its course. If you want to run the previous version, all you need to do is run the Cakewalk.exe that is inside the "Cakewalk Core Previous" folder, which you can do directly or from a shortcut.

I agree with the others that it sounds as if the client has used a demo version of an audio conversion program to supply different formats for distribution. I gently suggest that this is an issue of client management. Ask them what formats they require for distribution so that you may deliver them in those final formats. Instruct them not to do any conversion themselves, that you will be happy to supply any further formats if required. This will prevent any future such problems. If this is not practical for whatever reasons, I recommend that you supply your files in FLAC format and that the client use MediaHuman Audio Converter to do their conversions. MediaHuman is 100% freeware and does not impose any watermarking. It is easy to use, available on Windows and Mac OSX and handles conversions to and from all popular formats. https://www.mediahuman.com/audio-converter/ I hope this helps!

Go to your Cortana area and type OSK to bring up the Onscreen Keyboard. In the lower right you will see a button for ScrLk. Click it. Thanks for asking this, because I noticed that my Dell Latitude also lacks a Scroll Lock key and it made me figure it out for myself!