Jamstix making Sonar quite sluggish

[sharke_]

I'm fully up to date with version of both Jamstix and Sonar. I've noticed quite a large performance hit with projects containing Jamstix - it's most noticeable with loading times, saving times and project closing times.

When I hit save during Playback in Sonar, the save happens without any glitch in the audio, even in huge synth heavy projects. With just one instance of Jamstix however, the audio cuts out for a second or two when saving.

When loading or shutting down a project containing Jamstix, there are big delays and it also locks up my computer for a good few seconds. So if I'm browsing on Chrome while a Jamstix project is loading or closing, my browser will seize up until it's done. When Jamstix is not present, no such freezing happens.

Do you know if this is a problem peculiar to Jamstix, or are other DAW's affected?

[Kevin_W]

I have a similar problem in Reaper. I haven't noticed any lockup of my whole system, but definitely project load and save times are far longer than with any other vsti.
The biggest headache is that I have Reaper set to autosave every 7 minutes, so sometimes there's a hiccup in the middle of practicing.

[sharke_]

Yeah there is no way I could enable autosave in a project with Jamstix instances. That would kill me, lol.

[Ralph @ Rayzoon]

Please try the 3.6.5 Beta, which modifies thread management and may help significantly with these issues.

Saving during playback always leads to some audio artifacts because Jamstix, unlike most plugins, must save the entire song arrangement and disable audio processing so that composition actions do not interfere with the saving.

[Andre Giroux]

Autosave (safety backup) is created every 15 minutes in MultitrackStudio when the transport is stopped. And it won't let you save while transport is going for the reason that it could cause hiccups!!!