So I opened the project I was working on yesterday and found I had no fake acoustic guitars today.
I rolled back to "I", I opened the same project in X3, checked and rechecked the routings but no sound.
The solution was to change the chosen loop (within the plugin) to a different one and then change it back. That made it play until Sonar was closed and opened again - same problem.
The final solution was to create another midi track feeding into Strum Session and drag the loop from the plugin into the new track. Then set the playback to Guitar rather than loop.
 
I do like using Sonar but it's things like this that test my patience.
 
Grum.

Actually, I don't believe this is a Sonar issue.  Here's why.
 
I have Strum GS-2.  It has a "standalone" application that allows you to play it without a VST host.  Even using it in standalone mode, without Sonar, you have to use your workaround to get it to initially play when using Loop mode.
 
Paul

Hi!
 
Ditto here! Although I have not used my GS-2 that much yet, I have the EXACT same problem! (on Sonar Platinum JP)
 
Applied Acoustics have an "enthusiastic" marketing, but their support are almost nonexistent unfortunately!? No updates, no bug fixes, no communication with their customers in forums etc...
 
A pity, as they have an excellent product otherwise!?

Glad it's not just me!
The reason I mentioned Sonar was that it is a bundled instrument - if it doesn't work right then it reflects on the company that bundled it.
I wasted the afternoon I thought I would have spent moving forward on my song trying to make it work like it did when I saved it. That sucks.

Grum.

Yes, it sucks!
Since the days of Cubasis and Easy Guitar I was longing for an equivalent. Strum session was good (probably much better than EG...), but this bug made me upgrade to GS-2, hoping that the "full version" had this problem solved. But, NO! And, Jamaica Plain? No, bug still there!
 
So, be aware everyone that this anomaly exist in GS-2 too! It couldn't be much work for AAS to fix this, so hopefully they will eventually do this!? But, in the meantime it's not a fully functioning instrument!
 
Or, has anyone a solution to share with us?

Has anyone reported this to AAS ?
 
AAS responded quickly to me before, on a different issue.

I reported the problem to AAS and they are attempting to address the issue.
 
From the tests they asked me to perform, it looks like if you run Strum at 44.1kHz, the issue is not present.  So it seems like it's related to the sample rate.
 
Paul