[Solved in X3c, workaround for X3/X3a/X3b/X3d] Pod Farm and X3 issue

X3B had very specific fixes.
This is from line6 right? Does the same plugin work in X2 with the same settings? 
 

.. edited out incorrect answer..

Well, what do you know. Same problem here. Tried it with AAS String Studio and exactly the same problem you describe with Pod farm. I tried some of the elements as well (Pod farm as separate fx's) and those behaved the same way. Clean signal right channel, fx on the left.
 
Also on Pod farm 2.55 and X3b Producer.

And this is a VST2 plugin and not VST3 is that correct?

Just to make sure I just tried it in X1d - it works there. Kind of knew because I used the elements a lot earlier this year on a project.

Thank you for your replies, hope they will fix it eventually.
 
In the mean time I have a work around using an empty Guitar Rig Player with left channel in after the Pod Farm, this works ok since I don`t use the stereo fx in Pod Farm.

You are most likely correct scook, but it seems that an empty Guitar Rig is rather light too.

Thank you Steve, but it seems that jamesyoyo have found the solution.
 
I`ll come back later.
 

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.

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.

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?

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.

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?

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.