Starship Krupa

I just gave this a try in Studio One, and all you need to do is open Inspector and set the clip's timebase to "seconds" instead of "beats." Works a treat. In Mixcraft, it's switching the clip from "Use Project Tempo" to "Time Stretch." I'd love for it to be this simple in Sonar. SM/BAN required Googling and a trip to the Reference Guide, which seems kinda obscure.

I'm sure I did, it all happened so quickly. Likely dragged it to the wall after I SM/BAN'd it. That's a thought I had when @msmcleod posted the formula: Sonar has access to a LOT of computing power, and it's a simple enough formula, so why should I have to get out a pencil and paper and then adjust the clip myself?

Indeed. Final optimization of things, etc. We'll just have to wait and see, but as I said, if anything, over the years the overall direction has been that the engine works more smoothly, requiring fewer resources. I hope it continues in that way.

I did some more Googlin' and came across @David Baay's preferred method of using Set Measure/Beat at Now. That did it up just dandy, despite my not understanding how it worked at all. I just trimmed the leading edge of the clip so that it started with the notes, dragged it all the way to the left, split it 4 beats later, set the Now time to zero and hit Shift+M and it set the project time to what I had tapped and left the MIDI data alone. If I don't entirely understand the process, I suppose I don't really need to, unless at some point in the future I try it and it doesn't work. Still, it would be nice for MIDI clips to obey being set to absolute timebase.

I swear I once knew how to do this; it's something that comes up fairly often. Let's say I'm noodling around on my keyboard and come up with some nice chord changes and want to document them quickly. I record arm the MIDI track and throw Cakewalk into Record mode and play my chords for a few bars and stop. Before I started, I didn't bother to set a tempo, I just wanted to get the chords down while they were fresh. So it's at the default 120. Later, I want to develop this into a larger piece, and I want to set the project tempo closer to what I actually played, which is much slower, around 60 or 70BPM. I just want to adjust the project's tempo to my actual playing so that I can add other parts at the same tempo. If I just listen to my playing and use a tempo tapper to capture it, then set Sonar's project tempo, the tempo of the existing performance will change along with it and become very slow. How do I tell Sonar to leave my data alone when I change the tempo? (I tried changing the timebase of the clip from Musical to Absolute in Inspector and it did diddly schnit)

Hidden gold here.

As others have already pointed out, REAPER is only free during the trial period, after that, if you use it, you're in violation of the use agreement. So your plan was/is to dump CbB because it has a login request screen "every few days or so" in favor of using REAPER in post-trial pirate mode, where the nag screen comes up every single time, and takes upward of 30 seconds before you can banish it? If you want a free option, better to cozy up to Waveform Free. I always recommend being familiar, if not fluent, with multiple DAW's anyway.

Studio Cat is the overwhelming choice of people on this forum due to their excellence and the fact that the owner of the company frequents the forum. If you want something that works well for Cakewalk and any other DAW, @Jim Roseberry is your go-to.

I don't have the plug-in, but I assume that what it is is some sort of sequencer or MIDI generator or processor that loads as an instrument and sends MIDI to another instrument? I do have experience with multiple plug-ins of that type, Loop Engine and Chordjam among them. MIDI routing can be puzzling at first, but once you figure it out they work fine. When you say that you are not able to change any parameters, can you elaborate? What parameters? It sounds like you've gotten Rhythmizer to output MIDI and the synth to receive it. Do you mean that you're unable to interact with the Rhythmizer UI?

The .vstpreset files. I've been feature-requesting about this for years, including with Cakewalk Next. The VST3 spec outlines 3 different canonical locations for .vstpreset files. Sonar seems to understand where they are, because if a plug-in obeys the convention, loading a preset from the VST3 menu will go straight to the correct location. I first discovered this with Plugin Alliance/brainworx products, they are the biggest company whose products don't include their own preset managers. https://steinbergmedia.github.io/vst3_dev_portal/pages/Technical+Documentation/Locations+Format/Preset+Locations.html

I've gone through phases in my development as a mix engineer, and as the audio software industry has changed over the past decade. Initially I budgeted nothing for plug-ins, just went with whatever was bundled with Mixcraft (which, admittedly, is known for bundling some nice plug-ins, such as the way underrated ToneBoosters stuff). At the time, the industry was moving to 64-bit, and the one-person freebie developers were stuck with SynthEdit, which took a LONG time to get a 64-bit replacement. Now we have JUCE and others. Then MeldaProduction kicked off this era of loss leaders by topflight developers. That was a watershed moment. MeldaProduction has since made a fortune from people who tried their free bundle and were hooked (like me). The sound and features were so far ahead of anything else available for free. Got deals on the iZotope Elements suites of the time. At that point, my mixes and masters got the the point where I was no longer frustrated with the results I was getting, it was then all about shaving off that final 10% of skills and tools. Being a fixed income frugal dude, when I switched to CbB as my primary DAW and discovered this forum, it was off to the races. Plugin Alliance virtually giving away licenses, IK Multimedia TRacks freebies (I now have every TRacks processor I ever wanted, not paid a dime for any of them), Plugin Boutique freebies (which have included some top-tier things like sonible and Kilohearts specialty EQ's), Native Instruments freebies, iZotope Exponential $10 reverbs, Waves freebies, I now have a FEROCIOUS collection of top-tier processors and synths for which I've paid very little in the scope of the hobby (and thanks to my main DAW being freeware). I think the only thing anyone would find "lacking" in my quiver of tools would be if they were really fond of Waves, FabFilter or UAD. The only plug-in categories that now interest me for acquisition are sound-design-y things like Unfiltered Audio, Glitchmachines, Freakshow Industries and the like. Also synths, but only freebies. There's no way I don't have all the bread-and-butter mixing and mastering categories covered multiple times over. I have so much stuff that I've barely touched the iZotope bundle since I got it. No buyer's remorse, it's industry-standard stuff and I'm glad it's there. Indeed. And heaven knows plenty of "This One Secret!" videos that were "all you need is your DAW's stock plug-ins." ? They get clicks, though, even from us jaded skeptics who click on them just to roll our eyes.

Oh gawd yes! "Hi everybody, this is Johnny Fuzznutz. He's completely new to our industry and has been brought in to develop this complex interoperability specification." Let's tie our shoelaces together before the big race, eh? As everyone else stands by, watching helplessly....

Did you ever read my old humorous "description" of how Steinberg came up with the VST "standard?"

Ah, so they use the API that allows a host to query a plug-in dll for its presets. Having only ever installed the VST3's, I didn't know that brainworx did that. That mechanism actually does exist for VST3's, but for some reason brainworx mostly don't use it. I know of 2 Plugin Alliance plug-ins that do use it, Millenia NSEQ-2 and Lindell TE-100. They're VST3's and their factory presets show up right there in the Sonar preset menu. Go figure. I've been lobbying the Cakewalk developers for years to have Cakewalk/Sonar read the .vstpreset files from the canonical folder locations and populate the Sonar preset menu, but my pleas don't seem to have gotten any traction. That's why we put together that project to make .SPP files for as many of them as possible. At some point beating your head against the wall becomes tiring, and the end result was the same, I get to have my presets in the Cakewalk Sonar menu. Both Studio One and REAPER read the .vstpreset files from their canonical locations and populate their native preset menus with them automatically. I sure wish Sonar did. If anything, the VST3 spec made it easier by specifying folders rather than having to embed the presets in the DLL's. All the plug-in installer has to do is drop the .vstpreset files in the right spot, all the host has to do is read the files. Simpler. The problem is that so few plug-in manufacturers actually follow that part of the spec. I would so much prefer to have plug-in presets show up in the hosts' own menus rather than having to hunt around the plug-in UI for the location of the preset manager. In this case, at least, I can't blame the VST3 spec itself, rather the companies that failed to implement this part of it. Which is Cakewalk, some other DAW's, and the majority of plug-in makers. And as I said, the mechanism that VST2 plug-ins used to use still works for VST3 plug-ins. Very few use it though.....

In those cases, Plugin Alliance for instance, is it easier to use presets for the VST2 versions? I'm assuming you refer to the factory presets. If so, how is it easier? I know that brainworx-made (Lindell, elysia, Shadow Hills, etc.) plug-ins use the canonical VST3 locations for factory presets, so in order to load a factory preset for those, you have to load them from the VST3 menu in Cakewalk's plug-in header. For most of the Plugin Alliance brainworx-made ones, forum members, including me, have converted most of them to Cakewalk's native .spp format.

I initially read this as "orders of BS."

Seems that way to me, too. I've never saved anything as "Untitled Project[x]," although I have found "Autosaved Copy of (Untitled).cwp" files after crashes.

If that's so, then why did my "Untitled Project" number never rise beyond 2 in 6 years of using Cakewalk by BandLab? Also, on my laptop, it's only up to "UntitledProject2." And yes, I have created many new projects on both of my DAW systems. Really confused here....

I want this. Anybody able to help a bruv out with some inexpensive qualifying purchases? So far I got bupkis. I'll go for plug-ins, AIR synth presets. If there's nothing in those categories, then whatever's available for $5. When it comes to samples, I like chill, dark ambient.

The way that I'm used to it working is that unless I immediately saved a project with a name of my choosing, a new project (started from the Start Screen) would have the name "Untitled Project1" until I saved it, at which time CbB would prompt for a name of my choosing. If the program crashed or otherwise exited in a non-standard way, I'd end up with Untitled Project1 in my Cakewalk Projects folder, and if I didn't delete or rename it before starting another project, the next project would be called "Untitled Project2." Now for some reason, I'm up to Untitled Project23 and I'm trying to figure out why.

I only use at the most 3 per project, so yes. Probably the Quadcurve built into the Sonar Console view, MEqualizer, and a knob EQ of some sort, maybe TRackS EQ-81. Of course. Just as back in the day, when there was nothing but hardware, a mix engineer had their choice of only what was in the console strips and in the rack of whatever studio they happened to be working in. They couldn't go from studio to studio and get the same brand and model of board EQ or rack EQ's. You're saying that you're sure I'd notice the difference in sound between the same person mixing the same song using one company's emulation of a specific hardware EQ vs. another company's emulation and/or one company's 8 band parametric vs. another company's? So if someone gave the same mixing engineer access to, say, Fab Filter's parametrics for one song on a record and then Kilohearts' on the next song, I'd be able to tell that they were mixed using different products? I dunno, mate, I think you're giving me (the listener) too much credit there. And since the fact that there's a human being in the middle, using tools with 2 different-looking UI's, makes any kind of objective test invalid. A song mixed by the same person using exactly the same tools, then done again the next day will sound different each time. I'm a fan of The Beach Boys and if a certain number of songs on an album were mixed at one studio and a number at another, I am sure I wouldn't be able to tell you which songs were mixed at the same studio and which ones were mixed at different ones. Same for any other band. And I listen close, like "Music Bee sounds different from AIMP" close. Do you have examples of different songs by the same artist that were mixed with different EQ's by the same engineers that I should be able to tell apart sonically?

Gonna have to do that one.

Right, and that's true even between precision parametric types like MEqualizer and similar. Maybe you could get pretty close, but as you say, it takes a LONG time to copy an EQ curve from one EQ to another, even with the help of Plug-In Doctor. Also what you say about different emulations of the same hardware getting it way different: noticing that I had somehow wound up with 5 different Pulteclones, I decided to turn Plug-In Doctor loose on them. And no two of them were exactly similar. A couple of them were WAY different with the same settings. All of the differences were far off enough to be audible. Am I going to get different results depending on which one I use? Of course I will. I wouldn't pay much mind of the guy calling himself a "mastering engineer." He could change his sparkplugs and call himself a "mechanic," too. The only thing we can be sure of is that he's a "guy with a YouTube channel." It's just clickbait, of value only to the extent that it encourages us to think about these things.

If you set the VST2 versions to Exclude in Plug-In Manager, they'll still load in old projects, they're just hidden from display in the Browser and other places where you choose plug-ins.