patrickl/yabridge

Team Workflows Projects in Copr
1

Description

Yabridge for Fedora 33 for use with

https://copr.fedorainfracloud.org/coprs/patrickl/fedora-wine-tkg-esync-fsync/

and

https://copr.fedorainfracloud.org/coprs/patrickl/fedora-kernel-preempt-fsync/

Installation Instructions

Instructions not filled in by author. Author knows what to do. Everybody else should avoid this repo.

Active Releases

The following unofficial repositories are provided as-is by owner of this project. Contact the owner directly for bugs or issues (IE: not bugzilla).

Release Architectures Repo Download Fedora 33 i386 (0)*, x86_64 (0)* Fedora 33 multilib x86_64+i386 (0 downloads)

* Total number of packages downloaded in the last seven days.

External Repository List

The following repositories are accessible during builds

This is a companion discussion topic for the original entry at https://copr.fedorainfracloud.org/coprs/patrickl/yabridge/
2

Hi there,

Any chance of rebuilding for fedora 40? This comes with wine 9.10, but that’s to high for yabridge:

Error: 
 Problem: conflicting requests
  - nothing provides wine(x86-32) = 9.4 needed by yabridge-5.1.0-1.fc40.x86_64 from copr:copr.fedorainfracloud.org:patrickl:yabridge
  - nothing provides wine = 9.4 needed by yabridge-5.1.0-1.fc40.x86_64 from copr:copr.fedorainfracloud.org:patrickl:yabridge

Thank you for all your work!

3

This yabridge COPR depends on this version of wine-tkg by the same repo maintainer
make sure to follow all the instructions of this COPR as well:

https://copr.fedorainfracloud.org/coprs/patrickl/wine-tkg/

4

Hi there. I have followed all the instructions here and at the /wine-tkg/ linked above–including the Fedora 40 special steps–to install yabridge, and everything seems to be installed correctly. I did yabridgectl add ~/.vst and yabridgectl add ~/.vst3 to add TDR Nova and Kotelnikov (two test plugins so far), which I had previously extracted there. Following that, yabridgectl sync seemed to be successfull, with a wine config dialog briefly showing up, and yabridgectl status shows

TDR Kotelnikov.vst3 :: VST3, legacy, 64-bit, synced
TDR Nova.vst3 :: VST3, legacy, 64-bit, synced
yabridge/TDR Kotelnikov.vst3 :: VST3, bundle, 64-bit, synced
yabridge/TDR Nova.vst3 :: VST3, bundle, 64-bit, synced
yabridge/yabridge/TDR Kotelnikov.vst3 :: VST3, bundle, 64-bit, not yet synced
yabridge/yabridge/TDR Nova.vst3 :: VST3, bundle, 64-bit, not yet synced

I then launch REAPER and rescan the VST folders (same as listed above), but there are no new plugins available in the plugin list. Do I need to add a path to REAPER’s VST scan, or how can I access the plugins?

UPDATE: After writing all of the above and exploring yabridgectl and REAPER a bit more, I notice yabridgectl suggested doing a sync --prune. In REAPER, I then did “Clear Cache and Rescan” or whatever it’s called, and lo and behold it found the plugins! So far I have TDR Nova, TDR Kotelnikov, and OrilRiver working. Not sure if necessary, but each time I extract a plugin to the .vst3 folder I run yabridgectl sync --prune and then rescan in REAPER. Seems to be working great. Thanks!

5

Hi Patrick,

Thanks for putting this together. I had yabridge on hold until I read the notes about the other repos you’ve kindly put together. Is there any chance of doing a Fedora 41 repo?

Thank you.

1 Like
6

This does not work on Fedora 42. Could it be rebuilt for the current Fedora version?