hello patinete, I have the samplitude11 and protoolsLE8.04, I went through a similar problem and found along with the family nebula, interesting things about my hardware, and on my software... What happens in windowsxp32bits , is the limitation the memory usage of the plugin. I use winxp32bits, and with plugins simple, this is not a limitation, nebula has an engine You need memory. I use nebula at the protools, and samplitude11... I posted some songs done in both software, protools and samplitude, here in the forum. And really windowsxp32bits limited yes ...In this windows7 no problem ... The server version giancarlo commented,solves the problem in winxp32bits. the fault of the winxp32bits, I use, winxp32bits, because of compatibility. But samplitude, runs fine with me... and look at the mess around the Digidesign ASIO driver support, very bad. stay calm, giancarlo will help you ... Rely on family nebula. A big hug my friend, and hope that solves your problem as quickly as possible. Thanks. MIMI(miriam marcelo) The women's team record of production in Brazil
I’m running Samplitude Pro 11.2 and the latest Nebula Pro 3 in Windows 7 64 bit (Asus quad CPU) RME AIO and Lynx TWO C used as AES/EBU inputs from my HEDD AD/DA units.
Here is some strange things I run into: 1. Some libraries won’t show up 2. In some libraries that are sampled at 44.1kHz Nebula does not up sample them when I’m working in 96kHz sessions and some are fine so it is a bit of a mystery here. For example the entire Producer 1 library from CDSoundmaster show 44.1kHz-44.1kHz in 96kHz session and it doesn’t sound good at all. In fact, it sounds like a damaged MP3 file.
Michael, was very kind and attentive to this issue and guided me through some possible solutions (checking the RATE CNV parameter, trashing preferences etc) but to no avail.
3. Latency seem to be reported incorrectly and again this is somewhat inconsistent because the playback might start fine and then slowly phase when Nebula is used on AUX channels.
Unfortunately, this weekend I’m putting together a brand new computer and won’t authorize Nebula till Monday so I can’t verify or test anything until then.
BTW. I also want to mention that I have absolutely zero negativity and I’m super happy to be a member of this community. Thank you!
After install CPCL version 4 (copy N2V and N2P files to their respective folders) do this: 1. Delete all .XML files from Nebula Temp folder (\Nebula3TempRepository\Temp) 2. Delete ~scanboot.xml from Nebula Setups folder (\Nebula3TempRepository\Setups)
If this not fix it, enable log mode that should show us which emulation presets have errors. Example: