Bruno de Souza Lino

The best part of Kilohearts Essentials is not some of the modules it has, but Snap Heap. Not only you can do really interesting things by combining the essentials modules inside it, you can also use Snap Heap itself as a module.

If you have the professional version of Studio One, they have tools specific for making impulse responses since version 2.

The only downside of taking TTS-1 away is that you then have nothing capable of dealing with General MIDI files or even provide sounds outside of what Studio Instruments can give you. I think Only Studio One maps MIDI tracks to its equivalent Presence sounds.

If you have any modern graphics card, it does have their own screen recording thing which does very well for simple recording stuff. nVidia has Shadowplay, AMD has ReLive. They both use the card's dedicated encoder/decoder and have almost negligible performace hit on your machine.

MODO Bass uses synthesis to create all those bass sounds. It's not a sampled library, which explains why its size is so small in comparison to other similar products out there, which are several GB in size depending on how much different instruments and variants you have. MODO Drum only has the drum parts synthesized. All the cymbals are samples, and this is most of the 7GB of size it has.

That's either only one of the plugins or a combination of them. You'd have to go by elimination. My wild guess would be Waves Submarine causing it.

Bandlab already does that. It's called SongStarter. https://www.bandlab.com/songstarter

Sonic Anomally's TriLeveler 2 is also a pretty decent alternative to Vocal Rider and, much like the Waves version, it's made to be used on vocals.

But we already had a free Kontakt alternative for years. It's called Maize Sampler.

While that looks like a moment to celebrate, that reinstatement is just a stop gap solution to a problem Waves will reintroduce later. Don't be surprised if they plan some killer plugin and lock it behind their subscription plans. Or they slowly start fading away from their WUP model until you the only thing you have available is subscription plans. They would force you into subscription only if they had the same relevance and weight as Adobe or Avid have. These two could force their userbase into that model (although a good portion of ProTools users are also Avid shareholders, so it's no surprise there was little drama over their subscription model by comparison).

Mixbus is Ardour with some proprietary plugins thrown in. It's even developed by the same people.

And a years old bug lives in that program window: The scroll bar doesn't show up unless you resize that window. Depending on how much screen space you have, that window can cut at a point where you'll think you only have that amount of programs to work with. All Studio Instruments plugins have that issue, since they have the same interface.

While this isn't a very practical solution, you could emulate the behavior of a Chord Track using a MIDI Track and making use of the Chord Articulations that come with CbB. Then you'd just map that track as input to all the instruments you want affected. EDIT - Upon checking the feature (sending MIDI from one track to several). It's not possible to do that natively within CbB. You'd have to install a virtual MIDI driver like loopMIDI

You can do that using arrangements.

You can also create multiple arranger tracks, which makes them more versatile than markers, as you can stack them for different things and both are visible. While you can create multiple markers in the same place, only the most recent sits at the top.

"Using artificial intelligence A.I. to identify key elements of a spirited outtake from the 'Get Back' sessions, we've attempted to create a new arrangement of this forgotten Beatles moment that we hope fans will enjoy." So, this video is 1% AI, 112% human work. If anything, all the stuff done in the video could be accomplished without AI and the result would be more or less the same. Also, the lovely videos about AI always focus on that 0.1% where AI succeeds at a task instead of the other 99.9% where it was wrong.

The problem is that you'd have to bundle in already pre trained datasets which will still be several Gigabytes in size and you'll also push your system requirements to require a proprietary framework (CUDA) just to run the thing. And that assuming you even have enough computing power to run a local instance of any AI algo out there. The most optimized version of Stable Diffusion requires at least 16 GB of RAM and 10 GB of VRAM for example.

Considering all MPE controllers have pressure, having full MPE support would require supporting poly aftertouch. That means Cakewalk is not fully MPE compatible, as you cannot do anything with pressure messages sent by MPE controllers.

Some I can mention is this one https://hy-plugins.com/product/hy-seqcollectionwinmac/ Here's a free one https://stochas.org/ Both are MIDI plugins, but CbB sees it them an audio/instrument plugin, which means you can't add it to MIDI tracks nor use to process MIDI.

This is not possible in CbB as it doesn't have MPE support.

This is a feature that Studio One and had since the beginning. Essentially, it exposes your hardware inputs as channel strips you can access, except you can treat them as tracks and add effects to them. When you record from that track, the effect is printed to the recording as if you had your signal going through external gear before hitting the DAW. You can do this in CbB using either aux tracks or patch points (they're essentially the same thing under the hood), but it requires two tracks and they're only deleted after you detach the aux and patch point and reopen the project.

One thing to note is the number you see in the settings for your driver is not the value Pro Tools uses. ASIO4ALL shows that well. PT will sometimes change the buffer size without your consent because "it feels like it."

Another thing that makes CbB a cit cumbersome is you can't configure a plugin to be MIDI only. Those exist and you can't use them in CbB as they simply don't appear on MIDI tracks. Heck, even the built in plugins are no categorized as MIDI, which makes things weird when you want to use them in the PRV and they live in a strange "Uncategorized" field. Even adding plugins which are MIDI Only to the correct menu and saving the layout results in the plugin not showing on the list.

It's always a good practice to turn on your MIDI devices before starting Cakewalk. While some MIDI devices can be detected after the fact, that tends to only hold true for class compliant ones, which don't require a specific driver to work.

There are some things you can do in V-vocal which are impossible on Melodyne, because Melodyne is scope limited.