VST3 Plugin Not Recognized as ARA in Reaper

Audio Plugins
1

Hi everyone,

I’m currently working on testing an ARA2 implementation for my project and encountering a DAW-specific issue.

Current behavior:

My plugin is compiled with ARA2 flags/support
In Cubase: Works correctly as an ARA2 plugin and creates 3 processor logs (inserted as a clip extension)
In Reaper: ARA Support is checked from the settings but plugin is only recognized as VST3 and initializes in non-ARA mode (inserted as a clip effect)

Technical details:

Using VST3 format
JUCE Version 7.0.8
ARA2 implementation verified working in Cubase (v14.0.5 ARM)
Reaper is up to date with latest version (v7.34 ARM)

Has anyone encountered similar issues with ARA2 plugin recognition being DAW-dependent? Any suggestions for making Reaper properly recognize the ARA2 capabilities would be greatly appreciated!

Thanks in advance,

B

2

Hi, wanted to follow up here :slight_smile:

3

I’ve had cases where Reaper “forgets” that my plug-in is ARA. I think it was resolved after setting Plugin ARA Document Archive ID in the JUCE project settings.