I've been following the dialog on this since X3a. Essentially with the introduction of VST3 capability some mono / stereo switching has become more precise and Line 6's design for PodFarm doesn't quite fit how things work in Sonar X3 (is how I interpret the issue).

I use PodFarm a lot, and have seen the comments from Noel that the issue was fixed in X3c, but that fix introduced alternate issues for other things, so it was removed from X3d.

I also read SCook's comment to dust off the PodFarm workaround, and Craig's comment that at least there is a workaround.

I forgot what the workaround is.

Can someone reply and note what the workaround is again without referring to a thread that has pages of unrelated musings?

Thanks!

 
Go into Utilities > Cakewalk Plug-in Manager > VST Audio Effects > Pod Farm 2 > Plug-in Properties > disable "Enable mono processing".
 
Don't tick "Force Stereo operation" as that limits the output to stereo and there is no need (there have been some suggestions stating to do that but you really don't have to... or even want to).
 
Grum.

Thanks - that clear, concise answer is what I was looking for!

grumbleweed4162
 
Go into Utilities > Cakewalk Plug-in Manager > VST Audio Effects > Pod Farm 2 > Plug-in Properties > disable "Enable mono processing".
 
Don't tick "Force Stereo operation" as that limits the output to stereo and there is no need (there have been some suggestions stating to do that but you really don't have to... or even want to).
 
Grum.

Do I do that ONLY for POD Farm 2 or all the other POD Farm entries?

Bapu - great question. Now that you mention it, I'm going to hedge on doing it on all of them until advised otherwise.

It's all of them.

Grum.

http://www.cakewalk.com/Support/kb/reader.aspx/2007013356
 
someone should update the knowledge base as potential sonar users looking at the above may not want to invest in sonar if pod farm is their main vst for guitar tones.

myconsumerclub
http://www.cakewalk.com/Support/kb/reader.aspx/2007013356
 
someone should update the knowledge base as potential sonar users looking at the above may not want to invest in sonar if pod farm is their main vst for guitar tones.

Five things come to mind when I see that.

1. You're probably right the KB article should be updated.
2. The workaround works, easy to do
3. Shouldn't be an issue/concern for anyone using PodFarm
4. This issue does highlight how helpful the forum is for all of us to find advice
5. Noel has pointed out the root cause is with Line 6 in this case