Amplitube5 in Latest Reaper

[DK072257]

Hello,

I installed the update to Reaper v6.37 yesterday.

Today I tried to load the vst3 and it shuts down Reaper.

Prior to installing the reaper update, I had no problem with Amplitube 5 working fine. I know all my hardware is good so what changed in the update to kill Amplitube? And how do I go back to the previous version of Reaper?

Also, I was able to run Amplitube 4 without any problems, but I want Amplitube to work

Thanks

[garfy]

Hello DK072257

Sorry to hear you're having these issues.

Prior to installing the reaper update, I had no problem with Amplitube 5 working fine

Have you asked the same question on a Reaper forum, seeing it was that update that borked AT5?

Alternatively, I would suggest opening a ticket with Official IK Support. They endeavour to reply within 2 working days, but obviously considering the current situation things may take longer than usual.

And, to help others who run into a similar problem, please let us know what you did to resolve the issues, but without directly quoting any correspondence from official support.

[DK072257]

Thanks for the info.

Yes I have posted in the Reaper Forum however have not received any reply.

[captship]

FWIW - On my WIN10 machine I am not experiencing any issues with Reaper 6.37 and AT5.

Assuming Reaper works fine on project that does not have AT5 plugin loaded. You may need to rescan plugins. I did have a problem after I upgraded AT5 to 5.2, the VST3 would not load when the Reaper automatic startup rescan of plugin's choked on the AT5 VST3. I was on version 6.36 then and ultimately after a few hours of fiddling around found an unnamed VST3 which surprisingly when I clicked on it was AT5, I renamed it to AT5 and all has been well since.

Suspect someone on the Reaper site will have more knowledge than I

To roll back to 6.36 check your download folder to see if version 6.36 installation file is there, if so, uninstall 6.37 and reinstall 6.36 should do the trick. You may/will need your license code though . . . .