# Attaching to the Reaper API VST2 vs VST3

**URL:** <https://forum.juce.com/t/attaching-to-the-reaper-api-vst2-vs-vst3/45459>\
**Category:** Audio Plugins\
**Created:** [April 11, 2021, 7:58am UTC](https://forum.juce.com/t/attaching-to-the-reaper-api-vst2-vs-vst3/45459 "2021-04-11T07:58:39Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![rMidi](https://avatars.discourse-cdn.com/v4/letter/r/ee59a6/32.png) [@rMidi](https://forum.juce.com/u/rMidi)\
**Post date:** [April 11, 2021, 5:02pm UTC](https://forum.juce.com/t/attaching-to-the-reaper-api-vst2-vs-vst3/45459/4 "2021-04-11T17:02:46Z")

</div>

What exactly do you need to communicate to/from Reaper about?  
Do you need to communicate from your Processor?  
Do you need to communicate from your Editor? (Very possible via OSC).

[See my babble about OSC] [Triggering abelton live clips from juce plugin? - Audio Plugins - JUCE](https://forum.juce.com/t/triggering-abelton-live-clips-from-juce-plugin/45359)

Look at the Default.ReaperOSC located at C:\Users\yourusername\AppData\Roaming\REAPER\OSC.  
It is (sort of) self documenting.  
At a minimum you should be able to discern what is available via Reaper / OSC.

---

_[View the full topic](https://forum.juce.com/t/attaching-to-the-reaper-api-vst2-vs-vst3/45459)._