RAYZOON

Hi,
I use Reaper as a host and have noticed a performance issue with JS2.
Using windows task manager it look like there is some sort of regular spiking happening running JS2 as a VST.
On my Core2 Duo2 desktop it shows on both cpu's...a regular series of peak/valley patterns on the cpu usage history graph.
This did not appear on previous versions I'm fairly certain.

I just upgraded to the 2.5.1b2 and noticed similar spikes, but not as regular as 2.5


Cheers,
pc

Does this happen during play or while editing?

All modes. Even when Reaper stopped and working on another track.
The latest beta seems a little better thought. Let me run some more tests and see if I can nail it down and confirm more what the issue is/might be.

We need to separate spikes during play/record from those during editing. The latter can be caused by REAPER requesting the Jamstix data quite frequently.

If either of the systems has any,"Wi-Fi" enabled try disabling it.It's known to cause problems with recording software.

HTH

no wifi.

I still get the same with Reaper 3 Alpha 2.
Turn of the FX that has JS2 in, leaving all other tracks with FX ON, and the spiking on task monitor disappears, so it looks to me like there is some cyclic spiking happening between Reaper and/or JS2 as a vsti.

This *may* be a Reaper related issue. I reverted back to Reaper V2.51 and there is less cyclic spiking on the task monitor with JS2 enabled.