latency with Strum GS-2

I just downloaded a trial version of a guitar app called Strum GS-2. It downloaded and installed fine. The glaring problem I consistently hear is the high degree of latency I hear. I could try going to my audio controls on Sonar, but the latency for all my hardware instruments seems fine. Any ideas? Are there separate controls for latency when using VST instruments? I don't use any of them consistently.
Thanks.
LNovik

I'm also wondering if the latency the you're reporting might be due to Strum GS-2's FX. If you click on the Effects tab in the GS-2 interface, you'll see its EQ, compressor, delay/distortion, vintage chorus/tremolo and reverb FX controls. As you change presets, the number and type of effects changes.
 
Does the amount of latency you notice change when you change presets? That would indicate to me that GS-2 itself might be part of the issue.

I have a  Focusrite sound card, which has worked with my system in the past. As far as what Scook says: "Disable all plug-ins for a general solution or individually to see which ones are causing the delay. The usual suspects included with SONAR are TS-64, LP-64 EQ, LP-64 MultiBand"--I do have a question or two. First, certainly, these plugs in, such as TS-64, LP-64 EQ, etc,  have not been activated by me in my current project. Need I still disable them. I realize that just because I haven't inserted them into my project, perhaps they are still "active." ANd 2)Can someone tell me in a sentence or two how to disable my plug ins--other than the Strum GS-2 that I am trying out. If the latency disappears, I can then slowly add any others that I need to.
 
Lastly, I will look at the Strum's FX's as well. Perhaps they are overloading my computer.
Thanks.
LarryN

What is Focusrite mix control set as?
If it's a saffire update to 3.6. Uninstall previous version, reboot and do a full reset of the saffire after installation. Doing a manual loopback test and adjustment in Sonar accordiingly is recommended as well afterwards but probably won't solve this particular issue.

It is my understanding that you would set your buffer size as low as possible (64/128/256) FOR RECORDING (dedicating CPU to recording) and as high as possible (1024/2048) FOR RENDERING (freeing up CPU for rendering).

Anytime you're bouncing to audio tracks or files. You're not worried about latency at that point. The primary (only?) reason to have small buffer sizes is to minimize latency. But, the larger the buffer size, the lower the load on the CPU, so there's the trade-off.
 
I'm sure others with more knowledge of the internal workings of SONAR's audio engine can be more correct, and more useful.