Rayzoon Technologies LLC

[t9c]

I have been using JS 1.3 (can't recall the beta as I am at work right now) without any problems when using 44.1kHz, but I now have a project using 96kHz and JS is hammering the cpu when I press NTrack Play. All of the internal JS sounds load up then immediately it starts to croak, stammer & stutter, pegging the cpu usage meter (n-track feature) eventually requiring a stop command.
I have disabled all unnecessary programs running. No other effects or vst's running, and only 5-6 recorded tracks. Happens on all songs recorded @96kHz.
My interface is a MOTU 828MkII with their latest ASIO drivers and software. N-Track is v4.05. CPU is 2.4gHz, 1.5m memory, SATA 10k HD. Dual monitor setup using 16k rez. I am stumped. Any ideas where I can start to fix this?

Thanks,
Rick

[Ralph [RZ]]

Hi Rick,
96kHz is very CPU-intensive on all fronts. Compared to 44.1kHz, all your VST instruments and effects must process and calculate more than twice as much data in the same amount of time.

On our XP 3000+ tester, Jamstix requires about 1.2 to 1.5 more CPU power at 96 kHz, which is expected since the processing rate is about 1.17 times higher and Jamstix also needs to use interpolating logic at any rate other than 44.1 kHz to eliminate resample antialiasing.

Please try building a normal-sized project at 96kHz with your standard VSTi and effects but not Jamstix and you should see likely very high CPU usage.
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com