GPU Audio - Early Access

Get it while you can. Next level tech. Must have a GTX1xxx video card

2 Likes

That looks very promising!

1 Like

I tried it on my laptop (i7 11800H, RTX 3060 6GB GDDR6).
All my reverbs use only 1% to 3% of the cpu. This Fir Convolver uses over 25% !!

Very disappointing, no explanation or details on a possible setting that would allow to exploit the gpu and not the cpu.

Furthermore, the choice of reverb parameters is limited to 2 buttons: one selector for 10 IR types and one Mix button, it’s mind-boggling.

Finally, on the site, all the comments are very complimentary but all in the conditional tense… as if nobody had used this plugin.

I uninstalled this totally useless and greedy plugin while waiting for feedback because the process seems interesting to use in a machine with a powerful graphics card but which does not present any particular advantage in GP.

4 Likes

I signed up too but at the time no plugins were available. I see that a beta of the FIR Convolver is available but the first beta version says that it’s “initial AMD support”. I would guess that would mean it doesn’t support NVidia, so it may be unsurprising it bombs out with your RTX 3060.

To be frank, GPU Audio hasn’t seemed to share a lot of details on the technical aspects and details of their products and their FB page has a lot of glitz and promos and livestreams and announcements and razmataz but I really haven’t seen anything I’d call the real thing and user feedback yet. LoL - comparing the GP community type stuff to theirs and you would think they are trying to sell snake oil. I’d advise continuing to monitor but the real deal, even in beta form, hasn’t materialized yet.

1 Like

I was careful to get the right version: gpu_audio_nvidia.dll.

1 Like

I downloaded the product and sofar have had any notice about a version for NVidia. I’m posting the information from the installer file so everyone can read it themselves as there are some critical notes, to be expected as a beta early access program. It does say that it expects to find two GPU cards, as is found in certain gaming rigs and leaves one for the display and the other for audio GPU processing. The notes on how to measure what is doing what are interesting as that remains to be resolved for mainstream use - eventually.

It may have a lot of promise, but my opinion is it’s far from prime time. I have a GFORCE RTX 3070 Extreme in my system, but only one of them, and from previous gaming issues switching between the onboard Iris Display chip and drivers Im not going to mess around with this plugin unless I have a lot of time and inclination in case things go sideways. Others may be more enthusiastic :slight_smile:

GPU Audio - FIR Convolver
(Early Access Demo Version 0.18.1)

Hey there! Thanks for downloading the latest Early Access Demo Version of GPU Audio’s new FIR Convolver. Believe it or not, this is the fastest FIR convolution reverb VST3 designed to be powered by GPUs. The FIRC is a simple, single wet/dry knob convolution reverb plugin, with a rotary switch for selecting between 10 custom Impulse Responses. You can also replace these with your own impulse responses, for often surprising results! Read on for the latest updates, install instructions, etc.

early access is meant for testing and community feedback. this is not a final product and should not be viewed as one, & used with caution when on risky or important projects :slight_smile: always back up your DAW sessions

I.
System Requirements:

Operating Systems/Hardware
⦁ Windows PC’s, Windows 10/11 OS
⦁ Discrete NVIDIA GPU that is CUDA capable (recommend series 10xx and up) or certain AMD GPUS
⦁ Currently Officially Supported DAWs:
⦁ Bitwig Studio
⦁ Ableton Studio 10/11
⦁ Cakewalk
⦁ MOTU Digital Performer
⦁ PreSonus Studio One (known issues)
⦁ Reaper (recommended for EA)
⦁ Magix Samplitude Pro X
⦁ Magix Sequoia
⦁ Cubase
⦁ Studio One (some issues reported)
⦁ Not Officially Supported Yet: FL Studio (if you test, see Discord), ProTools (try a wrapper)

II.
Important Links:
EA Plugin Download:
https⦁ ://⦁ earlyaccess⦁ .⦁ gpu⦁ .⦁ audio
Discord (Resources and Community): sJ7zxgeb7T
⦁ YouTube: ⦁ https⦁ ://⦁ youtube⦁ .⦁ com⦁ /⦁ gpuaudio
Bug/Crash Reporting:
https⦁ ://⦁ docs⦁ .⦁ google⦁ .⦁ com⦁ /⦁ forms⦁ /⦁ d⦁ /⦁ e⦁ /1⦁ FAIpQLSdhmSudEdPJ⦁ 0⦁ nlfu⦁ 9⦁ cOoFSK⦁ 4⦁ l⦁ 0⦁ GwBcMYGda⦁ 40⦁ i⦁ 65⦁ CBaSHA⦁ -3⦁ A⦁ /⦁ viewform⦁ ?⦁ pli⦁ =1
SDK Signups:
https⦁ ://⦁ docs⦁ .⦁ google⦁ .⦁ com⦁ /⦁ forms⦁ /⦁ d⦁ /1⦁ MoZp⦁ -2⦁ rUMcehqLGYT⦁ 83⦁ XISic⦁ 6⦁ vBeAAPlV⦁ 1⦁ rgwrnh⦁ 0⦁ O⦁ 0/⦁ viewform⦁ ?⦁ edit⦁ _⦁ requested⦁ =⦁ true

III.
Updates for Version 0.18.1:
⦁ Extended the trial period
Updates for Version 0.15.1:
⦁ Fixed performance regression introduced in previous version
⦁ Better long buffers support
⦁ Correctly responds to incompatible setup configurations
⦁ Better support for various sample rates/buffer configuration (96khz/96 samples still recommended)
⦁ Numerous Performance and Bug Fixes
⦁ Audio hiccups on “looping” should be fixed. Please test.
⦁ AMD GPU early access support (see guide, below).
⦁ Better single-GPU support. Now you can try running some plugins at low latency together with OBS running!
⦁ Fast-Rendering Feature Support:
⦁ GPU AUDIO - based heavy projects (lots of tracks and long timeline) can be rendered / exported faster compared with CPU or DSP alternatives. We want users to try tens or hundreds of GPU FIR Convolvers running on timelines of at least 10 minutes, and render it. It should work faster compared with CPU-based cases. Currently, we expect 3-10X faster synthetic case.
⦁ After VST3 limitations will be resolved or gone (maybe with CLAP integration) we can assume the speed-up up to 20X-40X, depending on the case. While making the CPU mostly free during the rendering. We know. That’s huge :slight_smile: Let’s do it.
⦁ Known Workarounds:
⦁ Studio One and other DAW users may experience CPU spikes when returning data from the GPU. Fix: work within EAP buffer settings (96 samples, 256 block as a starting point)

IV.
AMD GPU List (7/5/22)
⦁ With AMD’s official support, we were able to bring AMD GPU support for CUDA processing much faster than anticipated. As a temporary limitation, AMD has asked us to start with “PRO” drivers which does limit the models currently in play. There is an important limitation:
⦁ In an AMD Laptop system, there are two GPUs, one in the APU and one discreet
⦁ When you install the PRO driver, the consumer grade driver on the APU will be removed by default
⦁ Laptop users may experience this. Read on for instructions

⦁ TESTED AMD Drivers:

  • 22.10.20-220524a-380149C-AMD-Software-PRO-Edition

⦁ AMD support is beginning in Early Access with PRO DRIVER support, which means you will need to MANUALLY install the correct driver. The following is a guide:

⦁ Currently, the following is recommended for a dual AMD setup:

  1. Download official driver supporting both APU & GPU 1. https1. ://1. www1. .1. amd1. .1. com1. /1. en1. /1. support

  2. Download Pro driver that is the nearest equivalent.

  3. Install the PRO driver.

  4. APU will be pretty much disabled, so your resolution and desktop effects settings will probably be disabled.

  5. Try out the plugin.

  6. Revert to originally downloaded installer that supports APU

  7. Once installed, the PRO driver will stop recognizing the APU and this is handled for APU only systems in the installer. For dual AMD GPU systems, the consumer drivers will pretty much make the system stop recognizing the APU. For this reason, please keep both the official driver AND your PRO driver easily accessible, to revert back after using the Early Access AMD plugin.

  8. Currently Supported AMD GPUs by Architecture:

  9. Vega* Navi 1X Navi 2X
    ⦁ navi21 (gfx1030)
    ⦁ navi22 (gfx1031)
    ⦁ navi23 (gfx1032)
    ⦁ navi10 (gfx1010)
    ⦁ navi14 (gfx1012)
    ⦁ vega20 (gfx906)
    ⦁ vega10 (gfx900)

⦁ Jun 2017 Jul 2019 Nov 2020
⦁ Radeon RX Vega/Radeon VII(7nm)
⦁ Radeon RX 5000
⦁ Radeon RX 6000
⦁ *Vega isn’t officially supported yet, but should still be tested.

V.
About GPU Load Metering:

The Windows Task Manager is useful for seeing how adding instances of a VST3G scales processing loads, however, it is not showing you the “actual” GPU load. Our device scheduler completely occupies the GPU for specific time-slices, if any tasks are running within that particular frame. So in theory, a single channel could show up as “100% GPU” even though we could run 100-200x - orders of magnitude - more channels.

VI.
Install and Setup Tips for Early Access FIRC:

⦁ Installing FIRC:
⦁ Close all DAW applications
⦁ Double click the latest GPUAUDIOEAP Installer and follow the instructions on the screen.
⦁ Files will be installed in C:\Program Files\Common Files\VST3\GpuAudio
⦁ Restart your computer. You will be prompted - if you don’t, things can break.
⦁ Boot up your DAW of choice

⦁ GPU Settings:
⦁ Set your PC monitor to use integrated graphics for the screen
⦁ Set your NVIDIA Settings to Performance Mode (Prefer Maximum Performance)

For best results, set the buffer in your DAW to 256 as a starting point
⦁ First, for accurate performance, it is recommended to have 2 GPUs in your system: some integrated (Intel or AMD) for display connection, and the discrete one - for the processing. This is commonly the case in “gaming” or “production” laptops like Razer, Asus, MSI, or most PCs.
⦁ If so - please set your default graphics adapter to “integrated” to get the most performance.
⦁ Load FIRC to your inserts as you would any vst3 plugin.
⦁ As it’s an EA version, please set the buffer higher to increase the number of instances you can create without dropouts (useful for stress testing)
⦁ If stress testing, turn down your volume on the track not in use, by -18db to avoid overloading
⦁ The recent update includes performance boosts for single-GPU systems :slight_smile:

VII.
Installing Custom IRs (Impulse Responses):
A custom impulse response is a .wav file that captures the characteristics of an acoustic environment through a transient attack, followed by a tonal sustain and decay. These sounds may be short or long in duration (for example, a hand clap or sweeping sine wave in a corridor or cave).

⦁ To install your own IRS, go to
C:\Program Files\Common Files\VST3\GpuAudio\EAP\Impulse Responses

⦁ Open the Impulse Response folder.
⦁ Inside you’ll see the current impulse responses.
⦁ To add your own, create 10 unique folders, 0-9, and add a single IR .wav to each folder.
⦁ They will correspond to the rotary knob +1 (ex: folder 0 will correspond to knob position “1”).
⦁ Drag and drop the stock IRs into a different folder on your desktop for now.
⦁ To hear the changes, you’ll need to reboot the DAW at this point in time.

About Early Access:
⦁ As an Early-Access product, we want to set up expectations, share known issues that we are working on, and details about compatibility as we update. It is meant to be a fun way for us to benchmark with the community of users, and is not a final product with final feature sets/max performance, etc. Please note that new features are often experimental, and that is why we are here - to get your reports!

⦁ The Early Access Program will continue even when the full open-beta Suite is released. We will use EAP to roll out new features such as Pre-M1 Mac OS support, M1 support, iGPU support, Audio Unit support, and various new features and quality-of-life improvements.

⦁ This EA version is running our GPU Plugins with the official SDK, but not with the official GUI design stack. This will be rolled out iteratively.

⦁ The final suite, coming in Beta, uses gorgeous embedded GUI graphics that even supports 3-D, openGL and more, and a container method for loading multiple plugin chains for production, without crazy visual design overhead for small plugin developers.

UPDATE!!! I installed the beta and it does give the user the option to install either the NVidia or AMD drivers within the installer routine.

When the installer finished it crashed my system - and it was a hard crash. After restarting my computer whatever was going on at the System/Kernel level was causing severe multi-core loading and high RAM usage - 92% of 64gb ultra fast ram. Fortunately the uninstaller did work after hanging for a few minutes (probably due to the huge system and ram loading) and everything is back to normal.

Not going to be trying that again until there are enough other users singing it’s praises before trying it again. I’m just not into this to be spending my time on the bleeding edge when what I have works more than satisfactorily for my personal set up.

1 Like

Just tried in Reaper: 1 track with this plugin: Reaper cpu display = 0.5 to 0.8%
It’s much better but still more greedy than for example ValhallaRoom: 0.1 to 0.4%.

What I don’t like about their presentation: “Download our free early-access plugin to try the fastest convolution reverb powered by GPU”.
Maybe they should specify that it doesn’t free up the cpu load though.

They tend to make it sound too good and forget that it’s a beta-beta-beta-version.
I was lucky not to have a crash, but other users report having serious crashes as well (French forums and KVR forum).
Anyway, it doesn’t work properly (for the moment only?) in GP, so I forget.

Wait and see…

1 Like

You should report that to them

1 Like

@dhj That’s what I wanted to do but I gave up because I don’t like not having the choice to refuse cookies, not finding a contact link to be able to send a comment and having to create an account with a password and signature to send a comment.

I had already given my email address to download the plugin, maybe I’ll get messages from something other than a no-reply address.

@CruiseCycle CUDA is not installed on my computer, malfunction in GP may be due to that. But I doubt it because it would also malfunction on Reaper, which is not the case.

1 Like

This technology is interesting to me just because it’s new and pushing into hardware where it was deemed to be inapplicable for this type of use. However, my rig has enough resources that this would not be useful to me personally, and if necessary, there are tried and true applications to hand off DSP processing to other resources. Short version - I’m not going to spend much time trying this out. I’m also guessing that the company making this is hoping the mainstream plugin producers will use this technology in their products rather than making plugins themselves, so I’m happy to wait and see :slight_smile: !!!

I use temp addresses, private browser window and/or container extension, and just delete cookies afterwards in this kind of situation.

FYI I just opened that site in a private browser window and right-clicked the Contact Me button, got the following direct email address (attached here as image)

screenshot_6253

2 Likes

So simple! I thought this was for professionals (editors, developers,…).
Before sending a message, I would like to clarify something so as not to talk nonsense:

  • in GP, the cpu indicator shows 30% for the gpuaudio plugin and 1% for a classic reverb (valhallaroom).

  • In the windows task manager the global cpu displays 3%, around 1% for GP with gpuaudio and 0.5% with valhallaroom.

How can I explain these very different indications in my message?

The indicator in GP measures only the time taken for the audio processing thread. If that value is high, then they are doing something inside that thread that is VERY slow….maybe related to communication/sharing audio buffers with the GPU not being handled well (speculation on my part)

2 Likes

For your information, I sent the following message:

Hello,

I tested Fir Convolver on my computer and I give you information particularly on its use in real time.

  • Fir Convolver works correctly on Reaper but the CPU load remains 2 times more important than with other reverbs: approximately 2% against 0.5% for valhallaroom for example.

  • On the other hand, I meet a big problem with my software for the live : Gig Performer - Deskew Technologies.
    The percentage of time used by the cpu (integrated cpu indicator) is 35% against 1% for valhallaroom and other reverbs (convolution or others).

  • There are also audio crackles in Gig Performer below 256 samples buffer while other plugins run without concern with a 96 samples buffer.

Of course Gig Performer has nothing to do with a daw as it is designed primarily for real time use.

Characteristics of my equipment (dedicated to audio only) :

  • Dell G15 Laptop / i7-11800H / 16GB DDR4 3200MHz / 2x SSD M2. 1TB / NVIDIA RTX 3060 6GB GDDR6
  • OS: Windows 11 21H2
  • System fully reformatted and optimized for audio applications / no other applications and services / disable: LAN, WLAN, firewall, antivirus, wifi, bluetooth.
  • Configured for real time use (concerts, performance).
  • RME Babyface pro FS audio interface.

I am providing this information at the suggestion of the Gig Performer developers who are very attentive to the improvement of their application and to the successful integration of third party applications.

I hope that this information will be useful to you.

Sincerely.

1 Like