Leaderboard

Get it in your account - Expires on 17 Mar 2022 https://customer.focusritegroup.com/en/software/sound-collective-baby-audio

The actual discontinuation of support for VST2 plugins only applies to Steinberg products (i.e. Cubase). I would think that virtually all other DAW manufacturers will continue to recognize VST2 plugins until there just aren't that many left in circulation. <rant on> It bothers me a lot that a private company controls a standard as ubiquitous as the (VST) audio plugin interface. Why isn't this an open standard supported by an independent group? I don't think that I'm the only one annoyed by some of the decisions made by Steinberg in the past, like initially crippling Midi support in the VST3 interface (they eventually backed off on that). VST is just an interface! There is no required code behind it. Steinberg should relinquish control of it, or a new 'open' standard should be developed... Fat chance that will catch on, though 😒 Ok, all done. <rant off>

But if this was Apple saying no more support the minions were be okay take my $$$ Apple.

This group (Babylonwaves) has been working on mappings of articulations for years. For one purchase of about $97 - Version 8 just released - you get Sound Variations in Studio One 5+ mapped for more than 600 libraries or instruments. A whole package of 600+ library articulations specifically mapped to Studio One 5+ Sound Variations. So instead of manually typing in these mappings you can get all of these in one quick install. It’s pretty cool! Time is money - so it’s a fantastic deal even if not on discount. Example software and instruments are too many to list. Okay, here’s one. The Orange tree libraries - all of those guitars and their many articulations. All wired up and ready to go in Studio One. The list goes on and on - Heavyocity, Spitfire, Native Instruments… https://www.babylonwaves.com/studio-one/ If you click on the 9,000 Templates link on that page you get the full list of the many products it has included. Admittedly it leans very much into orchestral libraries but it also covers a good number of non-orchestral products - like guitar libraries and some key libraries. Forgot to mention they strive hard to make this as easy to use as possible. One thing to point out is that visiting the Babylonwaves site on first visit asks you to accept cookies just to see their website. It’s well worth the visit.

Recommending that to a newbie is like giving a bottle of vodka and the keys to the Ferrari to your teenage son... 😬

Unify is a great idea! It can host a variety of plugin formats, including VST2, and can then present itself to a host as VST3. But just pointing out that this latest announcement only affects Steinberg hosts and VST2. So for anyone else, including me, that is NOT using a Steinberg host, then you can relax for now... at least until your host of choice decides to bail out...

https://helpcenter.steinberg.de/hc/en-us/articles/4409561018258?fbclid=IwAR0C626P2_1HBG3kgwCLBUiGJsSqR9etv_26wK-jiSZL7qSGq8JdU6H9pKs Another reason to buy Unify. I apologize if somebody already posted this...

Website is now live... https://www.roland.com/global/roland-50th-anniversary/

VST is very much not open source. It requires a license to support/use in a DAW or a plugin. You have to send Steinberg paperwork (digital but still with a signature) and you get back a license. And if you didn't do this for VST2 before they closed the window, you cannot ship any VST2 plugins at all. (yes I registered my company with a VST2 license before the window closed). VST2 and VST3 are separate license also. It's a mess. This is just the next phase of killing VST2. Though I don't think they have sued or shut down anyone who didn't get a VST2 license, they always could. It's one of the reasons some new companies aren't including VST2 versions of plugins, they may not be able to legally get a license to do it. I don't think they can stop anyone that did get the license before they shut that down from supporting VST2 though. But they can stop supporting it in their products. The world would be much better off if VST was an open standard. But Steinberg won't give it up and no efforts to make a new standard have ever made much headway.

the official advice from Steinberg is to leave that off anyway as it's broken - like other parts of their VST3 implementation. https://forums.steinberg.net/t/c11-speed-improvements/159708/15 there's a thread over at KVR that gives more background - but basically SB are desperate to see the back of VST2. They have been actively trying to force developers to switch.... But lots of developers prefer VST2 and there are certainly plugins that work better in VST2 than 3. Progress is fine but this isn't progress - it's just removing functionality. What's next ? Midi 1.0 ? (so very 1980) - score editing ?(so very 1880). Steinberg can do whatever they want but IMO it's a dumb move, but we've come to expect that from Steinberg over the years. I'm sure whatever development time is saved will get squandered on a plugin that nobody wants or asked for...or 3rd rate sample library....or more likely improving their new licensing model. Apple can get away with a depreciating whatever they like because they are worth 3 trillion dollars...SB not so much. /rantoff

FWIW I keep all my machines up to date with all updates as soon as they come out and I rarely have issues. I may wait a month before doing an upgrade, but I usually upgrade on at least one machine right away to check it's ok, the go ahead with the rest. I've had far more issues in the past trying to update an old machine which is way behind on upgrades.

"Steinbug". Hehehe... 😂

They should discontinue AAX also hehe. Recently while searching for extra space on my ssd I discovered about 40GB of plug-in data that had been automatically installed in an AAX folder. I always uncheck AAX when installing so these were a total surprise to find. If I move to VST3 exclusively then maybe I can get 80GB back? That would be amazing. Score.

it's fairly annoying for all those older plugins that are not and may never be updated to VST3...and it's currently quite a long list (superior drummer 3 ? soundtoys ? UVI ? XLN AD/AK, lots of NI plugs etc etc). Some will be updated for sure but probably as a paid version upgrade. $$$ There is no real technical reason to do it but they've been wanting to dump VST2 for years and they have got a bit frustrated waiting for the plugin developers to move to VST3...so they are forcing the issue by setting an arbitrary date. I hope they provide a wrapper but somebody at Steinberg has been making some strange decisions recently. At least the stupid licensing model was changed after all the protests - maybe they'll reconsider this to.....fingers crossed. as usual, restricting choice is always bad news for the consumer

We are happy to announce a brand new plug-in, Blue Cat's Connector, a virtual cable for your virtual studio! Connector is a universal connection plug-in that can stream audio and MIDI in real time, between any locations that can load plug-ins, even on different machines connected to a network. It lets you create your own routings "in the box", without any extra cable, and with minimal latency! As an existing Blue Cat Audio customer, you are eligible for a special introduction offer at €/$29, instead of 49 (40% off)! This customer offer ends on February 20th, 2022. https://www.bluecataudio.com/Products/Product_Connector/

Join Paul Thomson for the live launch and a chance to win the library! https://www.youtube.com/channel/UCJ7QbJQgJSSdd_v-VxdO6Gg

IK Hammond B-3X, FTW.

Nothing new under the sun but I bet it will be the largest sampled. You would think with their engine they would come up with better ideas.

https://u-he.com/support/faq.html#troubleshooting:vst3-issues

Get an additional 10% off using this code: DIGIFQ20 And find other deals here: http://www.digifreq.com/digifreq/deals.asp

I'm still amazed how terrible the installation process is for audio software. Obviously some developers are better than others. I've been running the app 'Everything' for file search on Windows, and I can sometimes find a plugin / instrument's files scattered across 20 different folders - plugin formats all over the place, documentation over here, presets over there, samples over there, images over here, files in Local app data, files in Roaming app data, files in generic users, files in admin user, files in 64 bit program files, files in x86 program files. Native Instruments seems to be the worst...and has been the worst since like 20 years ago. And if you...god forbid, delete the 32 plugins, which you sometimes have no choice to install, some manufacturers will consider that a "broken installation" in the installation manager. I think iZotope behaves likes this. "How dare you delete our precious 32-bit files! And did you delete the Russian language documentation! Plugin no longer work. Please reinstall it all again as punishment." It's what I love about the Plugin Alliance installer. Simple UI, can select exactly the format I want, filter by what I own, select plugin, installs in like 3 seconds. Almost no bloat at all. Somehow installing a PA synth takes 3 seconds, uses maybe 3 folders, but a Native Instruments synth takes up 20 folders on my drive and needs to install every single plugin format on the market. Worst offenders: Native Instruments, Waves and iZotope. Anyway. Another rant.

I've always had a hard time believing a company can own an interface. If there were actual code libraries involved that were created by a company, that represents a real product, but VST is just an interface, a collection of function definitions that need to be included in/supported by a DAW and a plugin. It's essentially a standard, not a 'product'. It's a standard that's supported (by real code) in a majority of DAWs, plugins, and other audio software. Unfortunately, it's that ubiquity that makes it almost impossible for a new standard to catch on. If that standard was close enough to allow an easy transition for existing software, Steinberg would almost certainly sue. I don't expect anything to change in the near future, I just wish... 🙂

I used to be one myself. Then I was promoted to whipping boy and department sin eater.

We had a bit of fun recently doing a cover of a bit of an overlooked gem in the Priest catalogue, Blood Red Skies from the Ram it Down album: It's pretty faithful to the original, but with a lot of the orchestration that I always felt was missing - this is definitely a cinematic sci-fi kind of song, so it was just begging for some movie score treatment in it (but without overdoing it so it's no longer a metal song). Nice big fat 80s synths, BBC Symphony Orchestra as the main orchestration, and tight pants all-round! HAHA! Hope you guys dig it.

Yamaha has just announced the release of RUio16-D – a revolutionary audio interface which allows users to add VST3 plug-ins to any Dante-based audio system. https://europe.yamaha.com/en/products/proaudio/interfaces/r_series_usb/index.html

50% Off Hyperspace is discounted until the 30th of January. A 15-days fully working trial version is available. Buy now: €129/€64 https://unitedplugins.com/Hyperspace/

Thanks for mentioning the title, Lars, really appreciate that.

This is another great FREE resource: www.helixhelp.com

Download here http://reaper.fm/download.php REAPER 6.46: The Gang Makes a DAW Changelog items below may include • links to more information. Batch converter fix normalization (6.44 regression) • resolve item-related wildcards properly when converting a media item that originated in a different project • macOS fix arrow key keyboard navigation issues for various windows (6.43 regression) fix keyboard focus after closing transport selection/bpm edit boxes improve appearance of routing matrix in dark mode and default theme Media items fix adjusting media to tempo suggested by filename or metadata when inserting via action add actions to normalize items to common gain, or separately, using most recent settings show warning or error (depending on context) when some items could not be normalized Metadata add ASWG dialogue projection level field add OGG, Opus to displayed list of render formats that support Vorbis metadata MIDI editor improve scroll behavior when adjusting zoom • improve zoom to content action behavior • ReaScript Lua built-in print() function output is visible using DebugView on Windows • fix incorrect fuzzy matching in TrackFX_AddByName() etc • improve gfx_blit() documentation • Windows fix DirectX plug-in preset menu fix new VST path addition on 64-bit Automation fix potential incorrect automation when envelopes disabled outside of automation items • Control surfaces fix OSC control of FX wet/dry knob • FX add actions to clear delta solo for all FX on selected tracks or all FX in the project Import add cancel button to multiple media item import dialog JSFX fix set_pin_mapping() high-bit issue Metronome fix count-in issue at 180bpm 3/4 • MIDI add actions to reload track support data (bank/program files, notation, etc) for individual MIDI items or all items in the project • MIDI inline editor improve default note view sizing mp3 close .reapindex files when media is set offline • RS5k fix incorrect resampling at end of sample (most obvious with r8brain free) Theme fix layout actions for single-character layout names • Tracks if tracks are removed while renaming a track in TCP/MCP, close edit field VST do not allow scanning root directories on macOS/linux (revert 6.44 change) • WavPack fix incorrect truncation in 16-bit mode •

If you control when it updates, you can make a backup before you install (which considering there are usually some every month, it serves as your backup schedule). It also gives you time to check the forum, because a bad update will spur a flurry of posts here. I have not had any issues with only the necessary updates and not the "feature" updates.

I think it would likely upset a lot of folks if any other DAW hosts discontinued VST2 support. There is a large body of plugins that are and forever will be VST2 only, as they are no longer being actively developed. But they are still good plugins. Only true open source plugins could be picked up and migrated to VST3. For the rest of the VST2 plugins at "end of life" that have proprietary licenses, not so much, especially if the original developer is no longer in business. But in any eventuality, the workaround would be to use a host within a host, such as PluginGuru's Unify. It's available as a VST3 plugin, and can host VST2 plugin layers internally. They have a small dev team of 1, and I am sure he is not controlled by Steinberg!!!

Then I would recommend staying as close to up to date as you can. Some folks have dedicated DAWs, and keep them isolated from the net and updates, but those are mostly pros that cannot afford any interruptions to their productivity. My preference is to only delay monthly updates by a few weeks, and the major feature upgrades by about 6 months. I delay the monthlies for a short period because most patch related issues are quickly identified and corrected by Microsoft in the days following release. I choose to let other users be the Day 1 "early adopter" testers. Then I tailgate when it's "all clear". FYI, if you let the feature version get too far behind, you will no longer receive support or updates, so avoid that. And as @msmcleod mentioned, you may run into extra issues trying to update a way out of date machine. Since you have Windows 10 Pro, just take advantage of the group policy editor to automate your decisions for you, such as how long you may wish to delay the monthly updates. You will then get the current monthly updates offered when that period (# days) expires. You really don't want to never receive updates. Then once a year, just set a new target version when you are ready to upgrade. If you leave the target set to your current version, you will never receive the next version. Windows is switching to an annual version upgrade (Feature Update) model from the previous semi-annual one.

I always create a "Notepad" document with the Serial # and save it on my Archive Drive in the folder with the Installer...

Cheers Lars, got to use this one on Edith!

An absolute must have. Great collection of classics! Very responsive. Greg Koch has a wonderful video on YouTube demoing these .

cool site.

That's exactly how I got sucked in, finally! 👍

Connector is here!

Room mics need to be turned off to save some CPU cycles.

The Undertones: Jimmy Jimmy

You can't get rid of AAX because of Pro Fools. If you want to play ball with Pro Fools, then you got to have AAX. And of course if you're a developer, then you want to play ball with Pro Fools because it's the "industry standard." But yeah, why do you ram it down my throat when I can't decide who I dislike more, Avid or Apple and refuse as much as possible to have anything to do with either one of them. You don't force me to install the AU versions. VST3 is supposed to solve the issue of companies hiding their VST plugins all over your system like they were Easter eggs or something.

Glad to help. Building new a DAW can be painful.

Yes, I am aware that there has been a previous thread (along with a moderator reprimand) on this topic. That said, now that the English version of Beat Magazine is available at Pugin Boutique, I could not help but (re)share this great deal with my fellow plugin addicts. I bought the February English version of Beat at PB. Everything worked beautifully and I was able to download my free AAS packs. It is a super value and not a bad issue of the magazine either. https://www.pluginboutique.com/product/3-Studio-Tools/94-eBook/8560-Beat-Magazine-193-February-2022?a_aid=4af297e055206

I completed my Andre Ettema collection with these 2 packs 30.876 Hz and Raw for UA VA-3. Good times!

I believe you can just delete the AAX stuff. I sure hope some of these developers with VST3s prone to crashing CbB get them figured out....

With Win 10 Pro you can set a few useful items in group policy editor (gpedit.msc) to prevent "early adoption" of newly released updates. In summary, you can set a target Feature Update (major annual version release, i.e. 21H2 is the current one) so you will not get an entirely new Win 10 version by surprise. Secondly you can set an automatic "deferral" period for monthly quality/security updates. I tend to defer them for about 3 weeks (21 days) so Microsoft can fix any current problematic monthly updates, but I do want to stay fairly current security wise, so I don't put them off forever. And definitely learn and make use of a regular disk image solution if you are not using one already. That way it's much easier and faster to roll back if things ever go sideways, than it is to rebuild Windows and all of your applications from scratch! Recommend Macrium Reflect Free that is perfect for home use and is very reliable! The Windows Update policies in group policy editor that I use are: Select when Quality updates are received: [Enabled, 21 days] Select the target Feature Update version: [Enabled, 21H2] I am currently updated to Win 10 Pro 21H2, and will not receive the next one until I update the policy to that effect. 21H2 is supported until June 2023. Windows 10 Home and Pro follows the Modern Lifecycle Policy. https://docs.microsoft.com/en-us/lifecycle/products/windows-10-home-and-pro

Does that mean that going forward, hosts will eventually stop scanning for/loading VST2 plugins? I tend to only install VST3 ones nowadays, but I'm wondering if it means I'll (eventually) no longer be able to use some of the older VST2 plugs I have.

Perhaps you should just purchase one copy of the magazine, enjoy your two free AAS packs, and then call it quits.

No...the $30 discount IS a coupon, so you can't add another one...