Clarify the issue in REAPER

It's caused by mutual recursion which at the moment does not work with
yabridge's communication model.
This commit is contained in:
Robbert van der Helm
2020-08-21 16:43:49 +02:00
parent 1db10aa694
commit 6073d812a5
2 changed files with 6 additions and 5 deletions
+4 -3
View File
@@ -402,9 +402,10 @@ some additional dependencies for their GUIs to work correctly. Notable examples
include:
- **REAPER** and **Renoise** can both freeze when using plugins that call the
`audioMasterUpdateDisplay()` function. Until REAPER and Renoise fix this issue
you can set an [option](#miscellaneous-fixes-and-workarounds) through
`yabridge.toml` to work around this.
`audioMasterUpdateDisplay()` function because of mutual recursion limitations.
Until this is fixed you can set an
[option](#miscellaneous-fixes-and-workarounds) through `yabridge.toml` to work
around this.
- **Native Instruments** plugins work, but Native Access is unable to finish
installing the plugins. To work around this you can open the .iso file
downloaded to your downloads directory and run the installer directly. When
+2 -2
View File
@@ -523,8 +523,8 @@ intptr_t Vst2Bridge::host_callback(AEffect* effect,
intptr_t value,
void* data,
float option) {
// HACK: Sadly this is needed to work around a timing issue with REAPER and
// Renoise. See #29 and #32.
// HACK: Sadly this is needed to work around a mutual recursion issue with
// REAPER and Renoise. See #29 and #32.
// TODO: We don't have access to the verbosity level here, but it would be
// nice to log that this is being skipped when `YABRIDGE_DEBUG_LEVEL
// >= 2`.