mirror of
https://github.com/robbert-vdh/yabridge.git
synced 2026-05-07 03:50:11 +02:00
Reword changelog
This commit is contained in:
+21
-18
@@ -14,32 +14,35 @@ Versioning](https://semver.org/spec/v2.0.0.html).
|
|||||||
|
|
||||||
### Fixed
|
### Fixed
|
||||||
|
|
||||||
- Fixed recent _Arturia_ VST3 plugins running into memory errors during plugin
|
- Fixed recent _Arturia_ VST3 plugins running into memory errors at the end of a
|
||||||
scans in **REAPER** and **Ardour**. These plugins would try to read data in
|
plugin scan in **REAPER** and **Ardour**. These plugins would try to read data
|
||||||
the Windows event loop without checking whether that data was initialized,
|
in the Windows message loop without checking whether that data was
|
||||||
after the data had just been deinitialized.
|
initialized, after the data had just been deinitialized.
|
||||||
|
|
||||||
### yabridgectl
|
### yabridgectl
|
||||||
|
|
||||||
- Fixed a regression from yabridge 4.0.0 where VST3 plugins in the 'new' bundle
|
- Fixed a regression from yabridge 4.0.0 where VST3 plugins in the 'new' Windows
|
||||||
format, like _Sforzando_, were not set up correctly due to the subdirectory
|
VST3 bundle format, like _Sforzando_, were not set up correctly.
|
||||||
detection logic change from the previous release.
|
|
||||||
|
|
||||||
### Packaging notes
|
### Packaging notes
|
||||||
|
|
||||||
- The new `system-asio` build option forces asio to be used from the standard
|
- The new `system-asio` build option forces Asio to be used from the standard
|
||||||
include directories instead of being defined as a regular Meson dependency.
|
include directories. Otherwise the dependency is defined as a regular Meson
|
||||||
Asio does not have any pkgconfig or CMake [build
|
dependency. Asio does not have any pkgconfig or CMake [build
|
||||||
definitions](https://github.com/chriskohlhoff/asio/issues/1071), so it's
|
definitions](https://github.com/chriskohlhoff/asio/issues/1071), so it's
|
||||||
impossible to detect its presence and version in a normal way, and as such
|
impossible to detect its presence and version in a standard way. Because of
|
||||||
Meson will fall back to using the included wrap dependency. Configuring the
|
that the Meson build will always fall back to using the included wrap
|
||||||
project with `meson setup build -Dsystem-asio=true ...` will cause
|
dependency. Configuring the project with
|
||||||
`<asio.hpp>` to be used instead.
|
`meson setup build -Dsystem-asio=true ...` forces `<asio.hpp>` to be used
|
||||||
|
instead.
|
||||||
- The `ghc_filesystem` dependency now explicitly mentions the
|
- The `ghc_filesystem` dependency now explicitly mentions the
|
||||||
`ghcFilesystem::ghc_filesystem` CMake module because their inconsistent naming
|
`ghcFilesystem::ghc_filesystem` CMake module. `ghc::filesystem`'s naming is
|
||||||
prevents Meson from picking this up by default. The dependency will however
|
[inconsistent](https://github.com/gulrak/filesystem/pull/129) so Meson can't
|
||||||
not work with `ghc::filesystem` 1.5.0's default CMake definition as they
|
detect the correct module automatically. It also doesn't expose a
|
||||||
forgot to include a version number.
|
[version](https://github.com/gulrak/filesystem/issues/148), so even with this
|
||||||
|
change version 1.5.12 of the upstream dependency still won't be detected
|
||||||
|
correctly. There is a [PR](https://github.com/gulrak/filesystem/pull/149) that
|
||||||
|
fixes this.
|
||||||
|
|
||||||
## [4.0.0] - 2022-06-09
|
## [4.0.0] - 2022-06-09
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user