I would like to take the opportunity to post a "thank you giancarlo for your support, help and guidance on the matter." I am doing intensive testing on Samplitude Pro X 32 and 64 bit to identify all issues. GUI issue seems to be solved on Pro X 32. I`ll report later today if the "no sound" issue on Pro X 64 is solved.
Hello Magic. Here in studio we have a magic/x sequencer too. We crossgrade to Samplitude X suites and Nebula3 Server 1.3.502 x64/x86 but we still working in 11 pro, we will switch to X after first update be available in the meantime we are testing and reporting issues.
Enrique Silveti. Acustica Audio customer and technical support.
I have tested running Nebula Pro v 1.3.502 with Samplitude Pro X 64 bit and are faced with the same issues as mentioned above, the CPU load increases dramatically when adding more 8 instances. At 8 instances the project idles around 20-22 % CPU load but goes beyond 100% when adding another instance. On Samplitude Pro X 32 bit all problems I had was solved with the upgrade to 1.3.502. Also, if or when I hit the "memory allocation" problem, I have learned that I benefit by running the 64bit server version locally.
I do not plan to upgrade to Samplitude Pro X 64bit before its stable. There are simply way to many bugs with the new bridge for 32 bit plugins.