Pod Farm 2 - modules crossed out

[The Paul meister]

Hi all,

I've uninstalled and reinstalled Pod Farm 2.59 on my Windows PC running Cubase Elements 13. However, when I select a preset, most of them are coming up with a few of the modules marked with a mini no entry sign - presumably meaning that module is not loaded properly.

Does anyone know how to fix this?

Cheers, Paul

[The Paul meister]

The built in Cubase Elements guitar AmpSimulator and Guitar Rig 6 player are both working fine.

[Wonks]

I’m surprised it works at all as it’s 32-bit and the latest Cubase versions don’t run 32-bit VSTs.

[sonics]

A couple of things come to mind.

Unless you purchased a license, I think POD Farm is tied to hardware. If so, is the hardware connected?

I think the install dumps both 32- and 64-bit VSTs in the same folder. Do a fresh install and check. I'd suggest removing the 32-bit files if you do not need them.

(NB: I've not used POD Farm or Cubase for some years...I moved on to amps and DAW pastures new!)

[The Paul meister]

Thanks for your replies,

I'm using a USB A iLok dongle. I have the 64 bit plug ins installed - the main one is called POD Farm 2 (x64).dll

The only folder where they are recognised is in the VST2 folder in C/Program Files/Common Files. In the Cubase VST Plug-in manager, they are listed as VST 2.4 files with x64 Architecture. The 32 bit ones are blocklisted.

I'm still getting the modules with the 'no entry' sign. When you double click on the module it says "This model is not authorized for use with the connected device. Use the model menu above to select a replacement model"

Does the above info help at all with fixing this?

Thanks, Paul

[Wonks]

Then it’s down to authorisation issues.

Have you previously used any of them with a Pod of some sort plugged into a USB port?

[The Paul meister]

I just googled Pod Farm VST 3 and I found this forum post:

https://line6.com/support/topic/63158-a ... atibility/

with the link: VST 2 Discontinued – Steinberg Support. This link shows this:

https://helpcenter.steinberg.de/hc/en-u ... scontinued

This would explain why it's not working properly. Seems ironic that Steinberg should discontinue VST 2 support while other DAWs do support it, when they invented VST in the first place.

However, some presets still load ok so it's not the end of the world, and I have it working properly in Cakewalk on my PC and Logic on the Mac.

Cheers, Paul

[sonics]

Ah, yes. Steinberg invented VST, which is why they have moved to VST3 and dropped VST2 support, of course.

If the plugin is essential, you could probably find a wrapper to run it, like Blue Cat's PatchWork.

Let us know if you do get it working, and how. I have a POD Farm license on my iLok so you never know...

[djangodeadman]

VST 2.4 plug-ins are currently still supported in Cubase on PCs, although Steinberg has announced their intention to end support in the future.

[sonics]

Actually, support is already over! The announcement from January 2022 stated a 24-month phasing out period. That should mean that releases from 2024 will not support VST2. I don't have any of their current products so cannot confirm the exact situation.

If you plan to upgrade your version of Cubase, then you should be rid of your VST2 plugins by now, or use another solution, as I mentioned in my previous post.

Developers have had fifteen years to move, but I note that a few of the bigger companies I use have released VST3 versions only recently.

[The Paul meister]

Hi Sonics,

Thanks for the heads up about the Blue Cat's Patchwork. It looks cool, but at $99 or 99 euros, I don't think I'll be buying it. Are there any free ones you could recommend?

Also, what are your 'new pastures' in terms of DAW and amps?

Cheers, Paul

[sonics]

Thanks for the heads up about the Blue Cat's Patchwork. It looks cool, but at $99 or 99 euros, I don't think I'll be buying it. Are there any free ones you could recommend?

You're welcome.
I do understand that $99 may seem expensive just to get a single plugin working. I don't know of any free VST3/2 wrappers except one for Reason I've heard talk about. It's not a function I need since my DAW supports VST2.

Also, what are your 'new pastures' in terms of DAW and amps?

I decided to move from Cubase to Studio One a decade ago. I can't believe how good it has become. It's amazingly flexible, full-featured and reliable, and suits me perfectly.

As for amp sims, I use Brainworx modelling and the latest version of Amplitube mostly. The mic and cabinet modelling is very important, too. I still have a couple of hardware PODs, too!

[PippaPumpkin]

Hello,

have you tried to use the Pod Farm 2 VST in another DAW like reaper for example?

[The Paul meister]

Yes, I have it working in Cakewalk on my PC and Logic on the Mac.

[The Paul meister]

Hi PippaPumpkin,

Thanks for your private message about the Cubase and Line 6 forums - for help with Pod Farm 2 VST.

I couldn't reply privately to your message as it says 'Some users couldn’t be added as they have disabled private message receipt'

Cheers, Paul

[djangodeadman]

Actually, support is already over! The announcement from January 2022 stated a 24-month phasing out period. That should mean that releases from 2024 will not support VST2. I don't have any of their current products so cannot confirm the exact situation.

If you plan to upgrade your version of Cubase, then you should be rid of your VST2 plugins by now, or use another solution, as I mentioned in my previous post.

Developers have had fifteen years to move, but I note that a few of the bigger companies I use have released VST3 versions only recently.

And yet, despite that statement, support is not over. Unlike you, I do have current Steinberg products and can confirm that support for VST 2.4 is still present in Cubase 13 on PC. On M1/2/3 Macs, Rosetta is required, I believe.

It remains clear, however, that it is Steinberg’s intention to end this support at some point.

[Wonks]

But if they stick to their announcement, I expect Cubase 14 is very likely to be dropping it (but you probably should be OK with 13.5 if there is one).

And then they’ll bring out a VST4 format, just to annoy everyone even more.

[djangodeadman]

But if they stick to their announcement, I expect Cubase 14 is very likely to be dropping it (but you probably should be OK with 13.5 if there is one).

And then they’ll bring out a VST4 format, just to annoy everyone even more.

Your first point is likely to prove correct, I would imagine, although I also assumed that about Cubase 13, which still has the support. Steinberg has indicated that there will no longer be any .5 versions, by the way, but they could always change their mind on that, I suppose.

Your second point is pure speculation (or perhaps good-natured mischief making!) on your part, but if Steinberg were again to allow 15 years between the announcement of a new version of VST and the dropping of support for the previous version, there should be no need to panic anytime soon.

[sonics]

I do wonder just how helpful you'd find Steinberg support if you brought a third-party VST2 plug-in problem to them right now?

BTW, is there VST2 support in the whole Cubase 13 line-up? I will upgrade my version of elements if so.

[Wonks]

I really wouldn’t rely on Cubase support. Took them about 35 days to answer my recent support ticket. Studio One was next day.

[djangodeadman]

I do wonder just how helpful you'd find Steinberg support if you brought a third-party VST2 plug-in problem to them right now?

BTW, is there VST2 support in the whole Cubase 13 line-up? I will upgrade my version of elements if so.

I don’t use Elements.

This link does not give a definitive answer to your question, since it doesn’t mention anything about different versions of Cubase, although it does imply that the answer is yes.

https://www.steinberg.net/cubase/faq/#: ... tel%20Macs.

There is a trial version of Cubase 13 Elements available. Downloading that should definitely answer your question.

[djangodeadman]

I really wouldn’t rely on Cubase support. Took them about 35 days to answer my recent support ticket. Studio One was next day.

It is certainly the case that Steinberg support is slow to respond. I must say, though, that on the one occasion I have had to use their support, they were very helpful once they did respond.

[sonics]

... they were very helpful once they did respond.

Which is usually too late if you're working professionally IME.

I'm not going to bother with the trial. Steinberg have just announced a sale today, so I'll upgrade. I'm sure it'll support VST2. I only use it for compatibility with a couple of clients, and it can't be described as expensive.

[djangodeadman]

... they were very helpful once they did respond.

Which is usually too late if you're working professionally IME.

I'm not going to bother with the trial. Steinberg have just announced a sale today, so I'll upgrade. I'm sure it'll support VST2. I only use it for compatibility with a couple of clients, and it can't be described as expensive.

You’re quite right regarding the slow response times of Steinberg support, of course.
I’m also sure you’ll be fine with the latest version of Elements.

[The Paul meister]

I've figured out what's going on with the crossed out modules - they're for Platinum only.

I posted this on the Mac forum which explains:

https://www.soundonsound.com/forum/view ... hp?t=91109

Also, no need for Blue Cat's PatchWork. At least not for this anyway.

The crossed out modules are the same in Cubase, Cakewalk and Logic - contrary to what I said earlier.

Cheers, Paul