# VST3 not found when using duplicate.py

**URL:** <https://iplug2.discourse.group/t/vst3-not-found-when-using-duplicate-py/172>\
**Category:** macOS\
**Created:** [28 July 2020 16:47 UTC](https://iplug2.discourse.group/t/vst3-not-found-when-using-duplicate-py/172 "2020-07-28T16:47:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![david](https://avatars.discourse-cdn.com/v4/letter/d/aeb1de/32.png) [@david](https://iplug2.discourse.group/u/david)\
**Post date:** [28 July 2020 16:47 UTC](https://iplug2.discourse.group/t/vst3-not-found-when-using-duplicate-py/172/1 "2020-07-28T16:47:33Z")

</div>

I’m trying to get up and running on Mac OS and am running into an annoying issue that probably stems from my lack of Reaper knowledge.

I’m using the duplicate.py script to create my own projects. The build goes fine and a .vst3 is generated in ~/Library/Audio/Plug-Ins/VST3. When Reaper opens, however, the plug-in can’t be found. I can manually add the plug-in through Reaper without issue.

I am changing PLUG\_MFR\_ID (no spaces) and PLUG\_UNIQUE\_ID (is “randomly” making something up good enough for this value?), as instructed.

Any ideas? Thanks!

---

<div class="post-metadata">

**Author:** ![bindernews](https://avatars.discourse-cdn.com/v4/letter/b/c2a13f/32.png) [@bindernews](https://iplug2.discourse.group/u/bindernews)\
**Post date:** [30 July 2020 06:42 UTC](https://iplug2.discourse.group/t/vst3-not-found-when-using-duplicate-py/172/2 "2020-07-30T06:42:13Z")

</div>

For PLUG\_UNIIQUE\_ID I believe you can randomly make something up. As for the Reaper setting, just add the plugin manually the first time then save the project. Once you’ve saved the project with the real plugin added, it should load correctly in the future.

---

<div class="post-metadata">

**Author:** ![david](https://avatars.discourse-cdn.com/v4/letter/d/aeb1de/32.png) [@david](https://iplug2.discourse.group/u/david)\
**Post date:** [30 July 2020 14:51 UTC](https://iplug2.discourse.group/t/vst3-not-found-when-using-duplicate-py/172/3 "2020-07-30T14:51:38Z")

</div>

Thanks – that’s the work around I’ve been doing. I’m wondering if it’s a bug with the script or something on my end. Perhaps it will avoid someone else’s future confusion.