markg wrote:I am using OSX - the instructions for making duplicates are for PC. I tried by doing the obvious (to a layman) conversions. ie PC dll = OSX componant but it did not work, which is why I asked here to start with.
1. In the newly created Nebula3 Cuda.xlm change "<MAGIC> o010 </MAGIC>" to something like o012
2. Nebula3 Cuda.component "show package contents" -> Resources folder -> Nebula3 Reverb.rsrc. You'll find the same number in there twice. Change it to the same as above and you'll have a new plugin. It will still be called Reverb but you'll be able to run it as cuda (just gotta remember which is which)
Edit: By the way Mark. Why are you trying to combat the latency ? Logic fully compensates for it.
This works in generating a new plugin in OSX, albeit with the same name.
Does anyone know how to properly edit the Nebula3 Reverb.rsrc file such as to change the display name in the host AU menu to something else?
I tried changing every occurrence of "Nebula3 Reverb" in the .rsrc file to "Nebula3 Reverb CUDA", to match my component name change, but that somehow broke things so that the new plug is no longer visible to the host. Maybe I should only change some of the occurrences?
Reason: I'm trying to break up my large library among multiple plug instances along these lines:
ok, maybe we'll create an application like we did on pc side, in order to check your system. It's possible your cuda driver is not corretly installed, or supported. It's possible cudabridge is not working for some reason. Or simply there is an hidden bug.
Thanks Giancarlo. It's definitely a "black box." I have no idea what might be wrong. I suspect it might be related to a conflict between CUDA 3.0 and OSX 10.6.6 (and the correlated Nvidia drivers), but there's no way for me to know for sure, I guess. Maybe I could try to contact Nvidia?