Starship Krupa

Who are "they?" If you are having problems combining VST2 and VST3 plug-ins in Cakewalk that is a bug, either in the plug-ins or in Cakewalk. If you're getting it in some other DAW, well, yet another reason to use Cakewalk. My experience is that I can mix VST2 and 3 with no issues, in both Cakewalk and Mixcraft. It doesn't even get a second thought. When installing plug-ins, I now go with VST3 when it's available, but see no real advantage to this practice. One thing I will say, there is more than one plug-in I have where the VST3 version doesn't work but the VST2 version does. Your reason 2 and....other reason 2 are both things that Craig's article listed as "myths." Cakewalk still supports DXi and is highly unlikely to drop support for VST2, especially considering how all of their bundled plug-ins are in VST2 (or DXi format). Ableton didn't even support it until 10.1. Dropping support for VST2 plug-ins any time in the foreseeable future would be a suicide move for any DAW. Most of them at this point even support 32-bit plug-ins, which I find slightly odd, but why force people to ditch software that they probably paid a lot of money for? Yes, the VST3 spec expands on the available features. Most of those features had already been included by plug-in manufacturers' implementation of VST2. (sidechaining, resizable UI's: little-known fact, the VST2.4 spec includes resizable UI's)The one biggie, the ability to go dormant when they're not processing audio, is a feature that I have seen exactly one developer implement, Meldaproduction. And he only implemented it last year. This is after 12 years of the VST3 spec being the standard. One single developer (other than, perhaps Steinberg) has implemented the feature that, to me, is the only really useful one. Craig's article is excellent and thorough and I agree with every point he makes. I also have to wonder whether some of the "myth" trash talk he mentions came from my forum posts, as I have had a loud mouth about knocking VST3. Since the Meldaproduction implementation (I own 57 of their plug-ins, so this is pretty huge) I have backed off a bit, but I still think that VST3 is the "New Coke" of plug-in standards. It could have been a lot better, could have implemented lots of things like multiple instances of a plug-in sharing the same kernel, the ability for the plug-in and the host to share patch info, integration with control surfaces, improved error handling, inter-plug-in communication, etc. What if there were easier ways for plug-ins from different manufacturers to communicate with each other, like being able to sync LFO rates and delay times without locking them to the project tempo? I would LOVE such a feature. All of that could have been put in the spec. I tend to rant about this subject because it bothers me. I've had a lot of experience with crashy VST3's, my former main DAW, Mixcraft, only got their support working in the most recent release. Before that, I avoided VST3's like the plague. Yes, the issue was with their implementation, but what was it that forced them to have to do that? The plug-ins I would love to see get aesthetic makeovers are the Sonitus fx. An update to VST, scalable more "2020's" interfaces. I think they sound great, I just don't use them because the UI's are too tiny for my eyes. The Cakewalk Creative set, not so much, too much good freeware will do what they do.

A classic clipper.

I'd really like to be able to try out Big Beautiful Channel in Cakewalk, especially since I also picked up the free add-on pack with another 4 processors. A weird thing is that it shows up on neither of my systems, yet on both it loads just fine in Mixcraft. I've forced rescanning of all my plug-ins in Plug-In Manager (including failed), looked for excluded ones, nothing to be found. There's nothing in there that's not covered by MTurboEQ and MTurboComple (and of course ProChannel), both of which I have, but I always learn something when test-driving FX.

You should be setting the output of the MIDI track to the plug-in. This will appear as an available output once you do my Step 3, as shown in Steve's graphic. From your screenshot, it seems you may have some confusion as to how to set the output of a MIDI track. Down at the bottom of the MIDI strip (Console or Inspector): Or from the Track View Track Header:

I'm going to take this as a "no." I guess I'll contact PreSonus support about it.

Thanks for reminding me. I need to visit these images in EVA 01. I missed it due to being a mostly split instrument guy.

Interesting. What interface do you have that has an ASIO driver with a shared mode? The ones I've seen only allow one app at a time to use the ASIO driver, although I find I can still run other apps in WASAPI with varying results.

Is there anyone this hasn't bitten? One of the best features in the BandLab era is that Ripple Edit indicator, and even with that, I've futzed it up a time or two.

Scenario: I've just played piano for 5 minutes on my MIDI controller into Cakewalk. I play back what I just did and there's a nasty clinker where my thumb hit the wrong key at one of the chord changes. I hit M to drop a marker at that location for later cleaning, then stop the transport. I open the Piano Roll and it's centered on notes 4 minutes earlier in the timeline. I of course want to get to the one where I placed the marker, as fast as possible. What do I do? I can (dis)engage Scroll Lock, which will make Cakewalk to center on the playback cursor and then send the cursor to the marker using the Markers module in Control Bar. Is marker navigation something that I need to go back to the Track View to work with (unless I'm going prev/next with a keystroke)? No way directly from PRV? Better way to do this? I spend more time than I'd like scrolling up and down and back and forth in PRV trying to find the note(s) I want to edit.

What would be the benefit(s) of having those plug-ins in VST3 format rather than VST2? What changes do you think would get them "up to today's standards?" I personally think that they work pretty well as they are, including the UI's. BTW, the Feedback section is a better place for suggestions.

Are you trying to use BandLab, the browser-based DAW, or Cakewalk by BandLab, the one that runs natively in Windows? If you're talking about BandLab, this is not in the right place to try to get help on it. This forum is for Cakewalk.

And when vertical real estate is tight is when I notice how much useless space there is at the top of the hardware output strips. I use them sometimes, to equalize volume between my 4 monitor systems. One feature I find most amusing is the way you can widen/narrow the hardware strips down to the width of a normal bus or track strip. I sleep better at night knowing that that extra bit of width is there on my hardware outputs if I decide I need it, and conversely, if I want to run lean 'n' mean, I can shrink them. Still, the fact that they all change width at the same time means that it could be made even more versatile, more customizable.

So his lead tone. Yes, I'd say that an emulation of a transistor fuzz like a Fuzz Face and tune it as necessary with EQ. Go ahead and build one! It's fun.

Has anyone who doesn't also have Studio One gotten this to work in Cakewalk? I installed the Hub, jumped through all the hoops, Cakewalk says it's scanning the PreSonus VST3 shell, but it doesn't appear anywhere, not in the Browser or Plug-In Manager. I'd really like to have it around, because it works in Mixcraft so I saw what it can do. Packing a lot of stuff in this plug-in. Pultec-style, 4+2 parametric, and channel-style EQ's, 1176, LA-2A, and precision compressors, gate, limiter. It's a regular Swiss Army knife. Frigger won't show up in Cakewalk, though....

And I'd like to emphasize that Vegas Movie Studio is not Vegas Pro. I got both of them in a Humble Bundle a while back, and I did a few videos using Vegas Pro. I finally gave up on it after too many crashes and freezes, and gave Vegas Movie Studio a try. It's kind of an "Elements" version, but the extra features of Vegas Pro are things that I never and probably will never use. Movie Studio is much more stable, and shares the same workflow with Vegas Pro. You can get Movie Studio at a deep discount every so often through Humble Bundle.

It's a testament to a lot of things. BandLab's stewardship of the product, hiring the cream of the Cakewalk, Inc. developers. Allowing a developer-driven model rather than a marketing-driven model, where bug fixing is given a priority over feature additions (not to say that the new features we've seen aren't appreciated). The product that Cakewalk, Inc. was selling was licenses. The product that BandLab is selling is user satisfaction and enthusiasm. I've said it before, I've worked in commercial software development environments and software engineers hate bugs as much as if not more than the users do. Being forced by management to release a program with known bugs is like being forced to release a mix with glaring mistakes. Having freedom to fix all the bugs you want is heaven.

The good and the possible gotchas: this seems more like a 2.0 than a dot release. The UI is entirely redesigned and now resembles Convex (like Convex it's easier to understand the routing and what the modules and controls do), and has what looks like a new set of presets as well. Also it's now a VST3. What I'm going to do is just keep 1.2 installed side-by-side with 1.3 for compatibility with existing projects.

Need to know which of Justin's tones you're looking for. Post or mention a song and I'll try to help. Big Moody Blues fan here.

I like this idea.

Another way to get a tempo tap without affecting anything in your project is to use MMetronome from the Meldaproduction MFreeFX bundle. No switching to another program, just insert it as an effect.

When working on a laptop with precious screen real estate, I know that I'll be scrolling up and down to see all the controls on the strips in Console View. However, when I scroll, the hardware output strips scroll along with them even though there's no useful control or info above the Mute buttons. I suggest that the hardware output strips have their downward scrolling limited so that it stops when the divider above the Mute buttons gets to the top of the window.

Being pedantic here, but SONAR and the company who made it have been gone for over 3 years. Avoid confusion. If you could mention what make and model of mouse you have, whether it's wired or wireless, whether you've tried swapping in another mouse, that would help us help you sort out the issue. It's probably confined to your system, unless you're trying to do it in the Drum Grid, where mouse scrolling is crippled. I mousewheel all day long with no hitches.

I'd like to talk about an important thing called the Search feature. It's up at the top of the forum to the right. That way you can find out if the topic you're about to post is already being discussed and then join the discussion. Many, me included, agree that including a feature such as Ableton Live and Cubase have would be a great asset. We are already discussing it and welcome you to join in and describe exactly which features you would like.

Thanks for the reminder I need to get his book. You are the first person I've seen on the forum or YouTube who already knew about the feature. Cakewalk is so deep and has been around so long that sometimes it feels like walking around The Mines Of Moria. Minus the Orcs and Balrog.

Data point: that's exactly what my Dell Latitude E6410 has and it does fine with Cakewalk. It has a quad i7 in it, replacing the i5 that came with it. I think it's about 10 years old now. For electronic music production, there's nothing wrong with it at all. For many-tracked audio with lots of FX, I might have to do some freezing, but that's all in the game. Humongous movie score orchestral libraries would be beyond its RAM and drive capacity, but I don't do that sort of work. I'm guessing that this Apple silicon is some pretty fast stuff, so that Mini should work better than my aging Dell, although still limited in the same way as far as storage and the ability to hold big instruments in memory. I don't know what kind of resource hog Logic is, but it would also run Reaper and Waveform. Still, if I were buying a new computer in 2021, I wouldn't bother with less than 16G of RAM and 1TB of drive, because why fork out money if I'm still going to be constrained?