# FMOD 2.02 integration with Reaper 7 fails (subprojects)

**URL:** <https://qa.fmod.com/t/fmod-2-02-integration-with-reaper-7-fails-subprojects/22084>\
**Category:** FMOD Studio\
**Created:** [September 12, 2024, 9:39am UTC](https://qa.fmod.com/t/fmod-2-02-integration-with-reaper-7-fails-subprojects/22084 "2024-09-12T09:39:28Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Leah\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/leah_fmod/32/3685_2.png) [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)\
**Post date:** [September 13, 2024, 1:42am UTC](https://qa.fmod.com/t/fmod-2-02-integration-with-reaper-7-fails-subprojects/22084/2 "2024-09-13T01:42:45Z")

</div>

Hi,

There’s currently a [known issue](https://qa.fmod.com/t/reaper-integration-render-issue/20336) specifically with Reaper’s command line interface (which FMOD Studio uses to integrate with Reaper projects) where the usage of some VSTs causes the render process to crash. While we have reported this crash on to Cockos [on their official forums](https://forum.cockos.com/showthread.php?p=2686814#post2686814), this is unfortunately not an issue we can address. There are a few workarounds listed in the known issue post, but you can also try using VST2 versions of any VST3 plugins, and disabling the offending plugins after bouncing audio in place.

To confirm that this is in fact the issue you’re running into, I’d recommend trying to use the Reaper CLI with the `-renderproject` argument to render your central Reaper project and see whether you get the same issue.

---

_[View the full topic](https://qa.fmod.com/t/fmod-2-02-integration-with-reaper-7-fails-subprojects/22084)._