mirror of
https://github.com/robbert-vdh/yabridge.git
synced 2026-05-07 03:50:11 +02:00
Reword the socket rework changelog entry
This commit is contained in:
+10
-9
@@ -10,15 +10,16 @@ Versioning](https://semver.org/spec/v2.0.0.html).
|
||||
|
||||
### Added
|
||||
|
||||
- The way yabridge communicates between its plugin and the Wine host process has
|
||||
been completely revamped. This was necessary to allow yabridge to handle
|
||||
nested or mutually recursive function calls. What this boils down to is that
|
||||
yabridge became even faster, more responsive, and can now handle a few edge
|
||||
case scenarios that previously required workarounds. This means that yabridge
|
||||
will now work out of the box with _REAPER_ and _Renoise_ and the
|
||||
`hack_reaper_update_display` workaround for is no longer needed. I have been
|
||||
testing this extensively to make sure that the change does not introduce any
|
||||
regressions, but please let me know if this does break anything for you.
|
||||
- The way communication works in yabridge has been completely redesigned. This
|
||||
was necessary to allow yabridge to handle nested and mutually recursive
|
||||
function calls, as well as several other edge cases. What this boils down to
|
||||
is that yabridge became even faster, more responsive, and can now handle a few
|
||||
edge case scenarios that would previously require workarounds. This means that
|
||||
yabridge no longer requires the `hack_reaper_update_display` workaround for
|
||||
_REAPER_ and _Renoise_, and the loading issues in Bitwig Studio 3.3 beta 1
|
||||
have also been resolved. I have been testing this extensively to make sure
|
||||
that the change does not introduce any regressions, but please let me know if
|
||||
this does break anything for you.
|
||||
|
||||
TODO: Expand on this
|
||||
|
||||
|
||||
Reference in New Issue
Block a user