kernels should be all the same size, at least 110 mseconds. Anyway I repeat, start testing it for reverbs. You have an huge advantage there. I would prefer to start testing from something which "should" work as expected before testing difficoult things
giancarlo wrote:kernels should be all the same size, at least 110 mseconds. Anyway I repeat, start testing it for reverbs. You have an huge advantage there. I would prefer to start testing from something which "should" work as expected before testing difficoult things
Thanks for the tip. But it's not like I would need more than 6 reverb send for a huge project. So the longer kernels are favored for Cuda.
Also want to know if it is possible to use Cuda for TIMED? All mode tested but I could not change any of them to TIMED.
Thanks for moving it here! Got a gtx760 and a gtx660 here to try it with. Both more modern and faster than the gt520 / 610 'it just shows a piture' cards , but not really the power hungry beasts you see in gaming rigs. I'm hopeful it can boost some reverb work.
So, to summarize: No TIMED mode (which is fine for me), only FREQD CUDA in the list 'OPT FREQD' you can choose from.
Works only good on long tails and tails of the same length, otherwise it becomes slower than native very quickly . So open a preset, go to the 'KERN' tab and take a look at the right side column. The numbers there should be 110ms or more, and the same between clean/even/odd. Do I say that right?
So AITB EAR-Rooms, the 'guitar room' for example, seems to have 1.5ms TIMED, and 3598.5ms FREQD and then '10.0ms FADE'. It will work? Just a single 3598.5ms in the FREQD column and that's more than 110 so Cuda can actually do some magic on it.
We still need the whole Cuda5 / Cuda6 SDK from nvidia to make this work?
Cuda dll x86 on Windows x86 -> system32 directory Cuda dll x64 on Windows x86 -> won't work Cuda dll x86 on Windows x64 -> syswow64 directory Cuda dll x64 on Windows x64 -> system32 directory right?