I am wondering if there are any plans to build/provide the other components of the wine-tkg-dev repo. I have tried wine-tkg using Wine v9.21 to no usable success.
When I ran the command “dnf copr enable patrickl/wine-tkg-dev” to to enable the repository and then ran the install command [copied from the instruction on the “patrickl/wine-tkg” page] :
The command returned errors about the non-availability of various packages. Unfortunately, I do not have the error log since I chalked this up to the unbuilt packages and decided to just wait. Hence my e-mail to you.
I know I have got to be doing something wrong. Can you please advise on further steps. Also I completely remove all wine and wine-tkg related items before trying wine-tkg-dev and after that failure removed anything having to do with wine or the copr. Just for the sake of a clean slate.
First time I looked at that tab Just ignore it. I have added brief installation instructions in the overview tab. When something does not install or it is complaining about missing something then wait an hour or so as that can happen when I’m updating packages.
So… acting on your instructions, I received this error from ‘dnf’ plus some prior lines:
Copr repo for wine-tkg-dev owned by patrickl 100% | 492.0 B/s | 1.5 KiB | 00m03s
Copr repo for fuseiso owned by pgdev 100% | 490.0 B/s | 1.5 KiB | 00m03s
Repositories loaded. Failed to resolve the transaction:
Problem: cannot install both wine-mono-11.0.0-0.1.fc43.noarch from copr:copr.fedorainfracloud.org:patrickl:wine-tkg-dev and wine-mono-10.4.1-1.fc43.noarch from updates
package wine-11.2-100.fc43.x86_64 from copr:copr.fedorainfracloud.org:patrickl:wine-tkg-dev requires wine-mono = 10.4.1, but none of the providers can be installed
cannot install the best candidate for the job
You can try to add to command line:
–no-best to not limit the transaction to the best candidates
–skip-broken to skip uninstallable packages
The installation with the COPR refresh was successful. A test of the utilities was also a success. I will soon be testing various plugin installations and operations and report back.
If a plugin only shows a black screen then that is another issue. The reason is that the plugin was built with JUCE 8 before the wine functionality in JUCE 8 was restored. You can ask the plugin vendor to apply the patch at Restore Wine functionality · juce-framework/JUCE@5179690 · GitHub
Testing a 64-bit Windows VST I tried installing the VST2/VST3 plugin ReMIDI 4.5 from Songwish. It failed with the Error: Invalid pointer operation. Runtime error 216 at 00406E2F.
One thing I notice is that ReMIDI installed succcessfully in wine-tkg using Wine v9.21-Staging, just was unusable due to the GUI issues. Here, failure from the start. I am not a programmer so this error log does not give me any clues. Maybe I am missing a Windows C/C++ Redistributable Library or something simple like that. Any advice would be greatly appreciated.
That is unfortunate. It is a problem in either ReMIDI, wine or yabridge so there is little I can about that as a packager. I recommend you ask in the yabridge #support discord channel at yabridge
FWIW I just installed the ReMIDI 4.5.0 trial with wine-11.4 and they do some weird things like installing ReMIDI (a VST3 plugin) in a non-standard VST2 location. In Bitwig clicking on ReMIDI’s trial screen does not work. So this may very well be one of those plugins that just does not work in wine.
Just ignore it. I have added brief installation instructions in the overview tab. When something does not install or it is complaining about missing something then wait an hour or so as that can happen when I’m updating packages.