I am downloading them just nowNils Schneider wrote:Updating drivers should be the better choicecis-didge wrote:Maybe I should bake it.
Convolution Reverb for NVidia and ATI GPUs - saving CPU time
-
Nils Schneider Nils Schneider https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=45370
- KVRist
- Topic Starter
- 279 posts since 22 Oct, 2004 from Neuss, Germany
Sounds good You might try version 1.05 of my plugin then.
https://k1v.nilsschneider.de - Kawai K1 emulated as VSTi/AU
https://heatvst.com - Android Synthesizer with full VST integration
https://gpuimpulsereverb.de - Use your GPU as reverberation DSP
https://heatvst.com - Android Synthesizer with full VST integration
https://gpuimpulsereverb.de - Use your GPU as reverberation DSP
- KVRist
- 383 posts since 28 Jan, 2008
Maybe it sounds good, but it dont look good.Nils Schneider wrote:Sounds good You might try version 1.05 of my plugin then.
the newst demo 1.0.5 still crashes Live after updating to latest NVIDIA drivers.
I have activated the use of GPU, are there other adjustment i shall be aware of?
-
Nils Schneider Nils Schneider https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=45370
- KVRist
- Topic Starter
- 279 posts since 22 Oct, 2004 from Neuss, Germany
Sent you a PM!
https://k1v.nilsschneider.de - Kawai K1 emulated as VSTi/AU
https://heatvst.com - Android Synthesizer with full VST integration
https://gpuimpulsereverb.de - Use your GPU as reverberation DSP
https://heatvst.com - Android Synthesizer with full VST integration
https://gpuimpulsereverb.de - Use your GPU as reverberation DSP
-
- KVRist
- 34 posts since 19 Apr, 2011
Hey,
what kind of plugins could be done with gpu support?
I guess it's not possible to programm something like a "bridge", so you can run normal vsts on gpus, is it?
However, any further plans for upcoming plugs? I'd like to see a good EQ (with 96dB filtercuts ) or better: Dynamic EQ
However, I'll try the reverb out soon!
what kind of plugins could be done with gpu support?
I guess it's not possible to programm something like a "bridge", so you can run normal vsts on gpus, is it?
However, any further plans for upcoming plugs? I'd like to see a good EQ (with 96dB filtercuts ) or better: Dynamic EQ
However, I'll try the reverb out soon!
-
Nils Schneider Nils Schneider https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=45370
- KVRist
- Topic Starter
- 279 posts since 22 Oct, 2004 from Neuss, Germany
I have to say BIG THANKS to cis-didge, who helped me nearly every day finding out why the plugin was not running on his machine.
With his help, I could solve an issue that caused the plugin to crash at startup on many systems. The crashes should be gone forever.
Version 1.06 can now be downloaded from the plugins product page at http://gpuimpulsereverb.de
For a complete list of changes, please visit the Change Log page.
With his help, I could solve an issue that caused the plugin to crash at startup on many systems. The crashes should be gone forever.
Version 1.06 can now be downloaded from the plugins product page at http://gpuimpulsereverb.de
For a complete list of changes, please visit the Change Log page.
https://k1v.nilsschneider.de - Kawai K1 emulated as VSTi/AU
https://heatvst.com - Android Synthesizer with full VST integration
https://gpuimpulsereverb.de - Use your GPU as reverberation DSP
https://heatvst.com - Android Synthesizer with full VST integration
https://gpuimpulsereverb.de - Use your GPU as reverberation DSP
-
- KVRAF
- 14656 posts since 19 Oct, 2003 from Berlin, Germany
I take it that you still need to install the CUDA drivers/pack, no?
Or does it work right out of the box with just the normal GPU drivers?
Somebody has some benchmark data on NVidia 9500GT cards?
Mine is "underclocked" - would that create any problems?
Or does it work right out of the box with just the normal GPU drivers?
Somebody has some benchmark data on NVidia 9500GT cards?
Mine is "underclocked" - would that create any problems?
-
Nils Schneider Nils Schneider https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=45370
- KVRist
- Topic Starter
- 279 posts since 22 Oct, 2004 from Neuss, Germany
You do not need to install anything special anymore. If you are on NVIDIA, just download the latest drivers and you are fine.
If you are on ATI, select the "Catalyst with ATI Stream" driver package and you are fine, too
If you are on ATI, select the "Catalyst with ATI Stream" driver package and you are fine, too
https://k1v.nilsschneider.de - Kawai K1 emulated as VSTi/AU
https://heatvst.com - Android Synthesizer with full VST integration
https://gpuimpulsereverb.de - Use your GPU as reverberation DSP
https://heatvst.com - Android Synthesizer with full VST integration
https://gpuimpulsereverb.de - Use your GPU as reverberation DSP
-
- KVRAF
- 14656 posts since 19 Oct, 2003 from Berlin, Germany
So NVidia bundled the "basic CUDA" drivers with their packs... hm... need to roll back my image these days anyway. Might as well test the latest drivers.
Thanks.
Thanks.
-
- KVRAF
- 14656 posts since 19 Oct, 2003 from Berlin, Germany
Just tested this reverb, and I'm a bit... baffled so to speak.
First and foremost, after an upgrade of my drivers, this thing works like it should. But not as expected. I expected a GPU load of about 5% per instance. Yet I got 25% with short IRs from StudioCat in either 44kHz or 48kHz. I'm running on an i7 with Windows in 32bit, tested in Cubase 5 and Cubase 6 with a sampling rate of 48kHz and a bitrate of 24bits.
On top of that... I can only use one instance simultaneously? Loading a second instance of this reverb with it's independent IR resultet in a GPU load of 88% on instance one, and way over 95% on instance two. Resulting in a slowdown of my rig. Again, doesn't matter if it's a 44kHz IR or 48kHz IR.
It is an interesting concept now doubt, but at the moment, not usable for my needs. Maybe it's due to my GPU (which is a GeForce 9500GT with 32 cores and 1GB RAM), maybe it's the code. I can't tell what's going on.
I can however assume, that one plugin eats about 8 cores per instance. Unless somebody has a CUDA core monitor to see how many codes are actually used up.
Guess I'll wait for an update then.
First and foremost, after an upgrade of my drivers, this thing works like it should. But not as expected. I expected a GPU load of about 5% per instance. Yet I got 25% with short IRs from StudioCat in either 44kHz or 48kHz. I'm running on an i7 with Windows in 32bit, tested in Cubase 5 and Cubase 6 with a sampling rate of 48kHz and a bitrate of 24bits.
On top of that... I can only use one instance simultaneously? Loading a second instance of this reverb with it's independent IR resultet in a GPU load of 88% on instance one, and way over 95% on instance two. Resulting in a slowdown of my rig. Again, doesn't matter if it's a 44kHz IR or 48kHz IR.
It is an interesting concept now doubt, but at the moment, not usable for my needs. Maybe it's due to my GPU (which is a GeForce 9500GT with 32 cores and 1GB RAM), maybe it's the code. I can't tell what's going on.
I can however assume, that one plugin eats about 8 cores per instance. Unless somebody has a CUDA core monitor to see how many codes are actually used up.
Guess I'll wait for an update then.
-
Nils Schneider Nils Schneider https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=45370
- KVRist
- Topic Starter
- 279 posts since 22 Oct, 2004 from Neuss, Germany
The GPU usage includes the time to transfer data to/from the GPU. If you are running at a low latency, the usage will raise. You will notice that loading big IRs won't make a big difference in GPU usage because the computational cost is low in comparison to the data transfer if using small block sizes.
There is an automatable parameter called "High Late" which will switch to 2048 samples of latency which reduces the usage dramatically.
But instead of increasing latency, I can't do anything about it, the transfer overhead is huge, GPUs are not suitable to transfer small chunks of data, this is the current state of OpenCL and I cannot prevent it.
I profiled the CPU code and data transfer a lot and optimized several years since I started with the first CUDA version, but I can't overcome the limits of the current hardware.
There is an automatable parameter called "High Late" which will switch to 2048 samples of latency which reduces the usage dramatically.
But instead of increasing latency, I can't do anything about it, the transfer overhead is huge, GPUs are not suitable to transfer small chunks of data, this is the current state of OpenCL and I cannot prevent it.
I profiled the CPU code and data transfer a lot and optimized several years since I started with the first CUDA version, but I can't overcome the limits of the current hardware.
https://k1v.nilsschneider.de - Kawai K1 emulated as VSTi/AU
https://heatvst.com - Android Synthesizer with full VST integration
https://gpuimpulsereverb.de - Use your GPU as reverberation DSP
https://heatvst.com - Android Synthesizer with full VST integration
https://gpuimpulsereverb.de - Use your GPU as reverberation DSP
-
- KVRAF
- 14656 posts since 19 Oct, 2003 from Berlin, Germany
I retried it again, this time not in Cubase 6, but Wavelab 5.
Turns out that I can use "two" instances simultaneously now, at about 44% each (88% CPU load), stereo 48kHz IR's, about 57MB each (a 5%).
I tried it with my usual low latency setting: 256samples (3ms)
This results in the two times 44% overload
I also tried it with high latency settings: 2048samples (about 21ms)
This resultet in "somewhat" 13-15% per instance.
Still I'd love to see a tool like with ProTools HD, where it shows how many cores I have left.
I just think your GPU doesn't like Cubase 6, or Cubase 6 doesn't like your IR. I can however confirm that it works in Wavelab 5.
Oh, and I found a GUI bug in WL5:
Click on the EQ button, it illuminates. Then turn the EQ off, and it's still illuminated.
I'm keeping an eye on this one.
Turns out that I can use "two" instances simultaneously now, at about 44% each (88% CPU load), stereo 48kHz IR's, about 57MB each (a 5%).
I tried it with my usual low latency setting: 256samples (3ms)
This results in the two times 44% overload
I also tried it with high latency settings: 2048samples (about 21ms)
This resultet in "somewhat" 13-15% per instance.
Still I'd love to see a tool like with ProTools HD, where it shows how many cores I have left.
I just think your GPU doesn't like Cubase 6, or Cubase 6 doesn't like your IR. I can however confirm that it works in Wavelab 5.
Oh, and I found a GUI bug in WL5:
Click on the EQ button, it illuminates. Then turn the EQ off, and it's still illuminated.
I'm keeping an eye on this one.
-
- KVRer
- 2 posts since 13 Sep, 2011
When trying to insert the demo version as an effect into Sonar, I get an error message:
More details: Plugin is version 1.07, Sonar is version 8.53 PE x64, OS is Windows 7 Professional R1.
Curiously it worked once, sort of, prior to some re-configuring of my computer that I did to bring down the latency.Program execution failed with the following error:
Unknown plugin error, code 29
[plus some other text...]
More details: Plugin is version 1.07, Sonar is version 8.53 PE x64, OS is Windows 7 Professional R1.
-
Nils Schneider Nils Schneider https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=45370
- KVRist
- Topic Starter
- 279 posts since 22 Oct, 2004 from Neuss, Germany
It may be the case that the system ID has changed, this causes this error. You may want to re-download the demo and you will be happy again
https://k1v.nilsschneider.de - Kawai K1 emulated as VSTi/AU
https://heatvst.com - Android Synthesizer with full VST integration
https://gpuimpulsereverb.de - Use your GPU as reverberation DSP
https://heatvst.com - Android Synthesizer with full VST integration
https://gpuimpulsereverb.de - Use your GPU as reverberation DSP