Pod Farm prevents PT from recognising MBOX.

[Peter Manganay]

I loaded up Podfarm twice using the licence manager and online authorisation only to find that when I activate PT it defaults to the Pod XT as the ASIO device, which it then cannot open, and won't let me open a session to reset preferences. All PT, MBOX, and Line 6 drivers are up to date. I ended up uninstalling Pod Farm as a fix but note that Avid are now selling Line 6 plug ins. Has anyone experienced compatibility issues with PT10 and Pod Farm and is there a fix? I7, 2600K 3.4 g quad core, 1 TB HD, Windows 7 64 bit.
Thanks,
Peter

[nst7]

A couple of things to mention:

The line 6 plugins you see in the Avid store are actually Digidesign TDM plugins for HD TDM systems. Line 6 developed them and Digi (now Avid) bought the licenses about 15 years ago and Digi/Avid maintains support for them.

However, Pod Farm definitely is compatible with Protools, but there may be some confusion on which version you have. If you bought the version that's authorized by Ilok, then it should work with any interface, or no interface, as long as the Ilok is plugged in.

I think the problem is, you may have bought the other version of Pod Farm, that actually requires your POD XT to be plugged in. The POD XT acts as a license dongle.

I was a little unclear on whether you had the POD XT plugged in or not.

Assuming you have this version, the POD would need to be plugged in. However, I don't know if that means that it also has to be selected as the recording interface. You still may be able to switch to your Mbox when Protools is open. Or hold down the "N" key while launching protools.

[Peter Manganay]

Thanks , I have the Pod XT version and have tried to start up PT with the POD connected. This is where I get into trouble and get the "cannot connect to ASIO driver chose another" message. I then choose the Pod XT as it's the only option given and try to open the session. Sometimes PT allows this to happen, but mostly I get a message that the device could not be connected and a prompt to quit. Seems the way around this must lay in setting the ASIO driver for PT outside of the program, though I haven't been able to work out how to do this.
Thanks,
Peter

[Draulym]

FWIW if you have Podfarm 2 download the free upgrade to 2.51 (I just did the exercise last night!!) - mine worked fine with my 003 both as a plugin & as a standalone (I had to go into Podfarm & set the input device to the 003, but it gave me the option straight away - even defaulted to 003 Ch 1 DI in for input)...

You will need the ilok authorisation to do this though

[Peter Manganay]

Thanks, I'm using Pod Farm 1.12 and am unlikely to pay for an upgrade given the current issues we're experiencing.

[Draulym]

Originally Posted by Peter Manganay

Thanks, I'm using Pod Farm 1.12 and am unlikely to pay for an upgrade given the current issues we're experiencing.

Umm.... take it from me - the problem isn't Podfarm, it runs fine for me (Protools, Reaper, 003 & mbox mini)