 |
VOOZH | about |
| Git Clone URL: | https://aur.archlinux.org/yabridge-git.git (read-only, click to copy) |
|---|---|
| Package Base: | yabridge-git |
| Description: | A modern and transparent way to use Windows VST2 and VST3 plugins on Linux |
| Upstream URL: | https://github.com/robbert-vdh/yabridge |
| Licenses: | GPL3 |
| Conflicts: | yabridge |
| Provides: | yabridge |
| Submitter: | robbert-vdh |
| Maintainer: | robbert-vdh |
| Last Packager: | robbert-vdh |
| Votes: | 8 |
| Popularity: | 0.000000 |
| First Submitted: | 2020-05-05 13:30 (UTC) |
| Last Updated: | 2022-12-23 19:11 (UTC) |
@robbert-vdh It would be useful to add
options=(!lto)
to the PKGBUILD so that this compiles on systems who default to using LTO
I think also it may be useful to deprecate -Dbitbridge=true and default to it being false in order to make the build compatible with Arch by default.
Over time, I think there will be less and less need for 32-bit support and if people want that then it should require going 'off-piste' rather than trying to support something that is probably not used by most people.
See https://github.com/robbert-vdh/yabridge/issues/437.
Yabridge's bitbridge is not and likely will never be supported when using a Wine build that uses the new WoW64 mode. Your options are indeed to either remove the -Dbitbridge=true, or to use a Wine build that uses the traditional WoW64 mode.
As some may already know, the latest yabridge release has issues with wine > 9.22.
For now, I am having success with the new-wine10-embedding branch, where a fix is being worked on. To make that work with this PKGBUILD:
and:
with these changes, at least the GUI issues are resolved for me. Thanks for yabridge, @robbert-vdh!
Build error https://pastebin.com/t7mCZv1Z
@robbert-vdh thanks, it worked
You've added /usr/lib/vst to yabridgectl. Don't do that. Run yabridgectl rm /usr/lib/vst and just hit enter at the prompt.
Hey everyone, anyone getting this kinda error?
Error: Could not remove '/usr/lib/vst/TPA-1.so'
Caused by: Permission denied (os error 13)
Before I would downgrade wine-staging but that failed to fix it..
@jpcima Unity builds sadly require a ton of memory. I now set the number of jobs to one job per every four gigabytes of memory available instead of only limiting the number of jobs when you have less than 8 gigabytes of memory (ninja defaults to $(nproc)). Let me know if that works better for you.
My machine has total_memory=14, and yet this build manages to oom kill my running processes. (note: it's 4-core/8-thread AMD)
@robbert-vdh: I disagree with your reasoning. Users installing VCS packages should know how to update them. They are not for general usage by by users who don't know what they are for.