So, have we established if this is actually a problem with X3 or not?
 
I have identical settings in X2 Plug-in Manager and in X3 Plug-in Manager for, say, the POD Farm Distortion Elements VST.
 
I've created a single track project and imported a mono .wav and added one instance of this plug.
 
When I open the project in X2 I get a mono output, and in X3 it's outputting in stereo.
 
And in X3, whether Enable Mono Processing is checked or not, the output remains in stereo. Also, I just checked, and Force Stereo Operation is not checked.
 

You want a stereo output from Pod Farm at all times - guitars are generally mono (!) but guitar effects can be stereo. You can make the track mono but you want the plugin to be stereo no matter what (as long as the plugin is working correctly).
I don't know why X3 broke Pod Farm.

Grum.

grumbleweed4162

jamesyoyo
Here's what I found worked with this issue: Go to PlugIN Managerselect properties on POD Farm 2there is a checkbox for mono processing. Uncheck it. Good luck.

"Here's what I found"???
I believe I found out how to cure it and I posted the solution in your thread - but you can take the credit if you want.

Grum.

Whatever. I had no idea if this was the same problem.
All of the credit must go to Grum.
I pity the fools who attempt to wrest it from him.

Ok, so we have another hero...........
 
Steve, I think you have a good point, the behaviour in X2 and X3 are different so maybe Cakewalk should look at it anyway?

 
I think it would be nice to know the reason for the different behaviour Johannes.
 
Until James mentioned it, I've never had cause to alter the 'mono processing' option, and according to the manual, the default setting is to have that option checked.
 
The manual actually explains it all rather well:
 

 
 

Yes - even if it works it doesn't look like it's what that checkbox is supposed to fix. As I interpret the refmanual it's actually the other way around?
A monoplug does NOT display this behaviour if checked. But the fix here is to uncheck to solve the behaviour.
 
So it would still be great if Noel finds the reason for it.
 
I might misunderstand something of course.

I`ll remove (Solved) from the title allthough we have some kind of solution.

Hmm. If anything X3 now properly handles mono plugins, that is how the VST2 fabfilter and waves mono only plugins work properly for sidechaining etc. It looks like somehow this change is interacting negatively with this plugin.
 
Can you check something? 
In X3 we respect the interleave reported by VST3 mono plugins so if you try and toggle the track interleave to stereo and have a mono only plugin as the first in the chain, the UI will NOT toggle to stereo since it will force it to mono.
Can you report back what happens when you have only pod farm in the bin and try and set the track interleave to stereo?

According to the POD Farm manual, it automatically configures itself to mono or stereo depending on whether it's inserted into a stereo or mono track, but it doesn't seem to be seeing when there's a stereo track in Sonar if Enable Mono Processing is checked.
 
Presumably what you want is for a mono input (e.g., guitar) to end up as stereo if processed through a POD Farm 2 stereo effect. What worked for me is using plug-in manager to select Force Stereo Operation, and selecting a mono input (e.g., the left input only) for the interface. If the track has a stereo waveform, POD Farm will still process the waveform in stereo.

I've been playing around with this for the last hour or so and have found the following:
This is almost exclusively a Pod Farm and Pod Farm Elements problem, just about everything else I have in my PC can live with the Enable Mono Processing box being selected and will still load as a stereo device that responds to the Stereo/Mono track interleave toggle in the Console View.
I don't think selecting Force Stereo Operation is a good idea (I suggested that 6 days ago and "Anderton" did above) as it forces the Stereo/Mono interleave of the track to stereo and there is no need to do that if the Enable Mono Processing is not selected.
 
There has definitely been a change in Sonar's behaviour between X2 and X3 as X2 will load a mono version into a mono track and a stereo version into a stereo track but X3 just loads mono versions into either.
 
As long as everybody knows to disable Enable Mono Processing then at least Pod Farm (and it's bits) are usable but not everybody will know this and this subject will keep making a comeback until the problem is resolved.
If it worked in X2 it should work in X3.
 
Grum.