Package Details: wineasio 1.3.0-2

Git Clone URL: https://aur.archlinux.org/wineasio.git (read-only, click to copy)
Package Base: wineasio
Description: ASIO driver implementation for Wine
Upstream URL: https://github.com/wineasio/wineasio
Keywords: asio audio jack wine
Licenses: GPL-2.0-or-later, LGPL-2.1-or-later
Submitter: shinlun
Maintainer: Kazel
Last Packager: Kazel
Votes: 62
Popularity: 0.039938
First Submitted: 2007-05-27 07:28 (UTC)
Last Updated: 2025-07-28 23:58 (UTC)

Pinned Comments

Kazel commented on 2025-08-20 23:57 (UTC) (edited on 2025-08-21 00:00 (UTC) by Kazel)

Your user must belong to the realtime group in order to use wineasio.
This can be done with sudo usermod -aG realtime $(whoami)

For registering wineasio as an ASIO driver run: wine64 regsvr32 /usr/lib/wine/x86_64-windows/wineasio64.dll

Kazel commented on 2024-09-19 09:36 (UTC) (edited on 2024-09-20 08:46 (UTC) by Kazel)

I removed the 32 binary and put it in the aur as an extra package -> wineasio32

wineasio32 pulls in wine-staging as make dependency and doesn't install all the other files from the wineasio package (binary only), therefore it depends on wineasio.

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 Next › Last »

jhernberg commented on 2013-10-16 12:27 (UTC)

So far wineasio is only 32bit, that means it will work with 32bit windows programs in 32 or 64bit wine. I have it working with 64 bit windows programs too, but it requires a different asio.h than Steinberg has released, mainly due to long having a different meaning in 64bit windows and linux. The problem is that I don't really want publish this header due to the copyright issues surrounding ASIO, but I am going to try to get wineasio included in wine. Let's see how that goes. If not I might be able to come up with some script that patches Steinberg's asio.h

DanielD commented on 2013-10-16 09:47 (UTC)

Is it possible to make it available to x64 programs running in wine ? I tried "wine64 regsrv32 wineasio.dll", it's not working.

jhernberg commented on 2013-10-15 18:58 (UTC)

I just tagged and tarballed 0.9.1. It has the fix needed for wine > 1.7.2

schivmeister commented on 2013-10-14 16:19 (UTC)

Yes, thanks guys, that should be taken care of by the PKGBUILD. Joakim has said that he'll get around to making a release in a couple of days, so we'll just wait for that to update this. Anyway, thanks to Gimmeapill for the heads-up on the issue.

DanielD commented on 2013-10-14 16:01 (UTC)

Works like a charm now. Thank you all guys, and sorry for the noob question, I'm fairly new to this Arch way ;)

Gimmeapill commented on 2013-10-14 08:29 (UTC)

@DanielD: just delete the symlinks under /src before rebuilding (or the whole src folder). Altough it's true that this kind of cleanup could be handled by the pkgbuild.

DanielD commented on 2013-10-14 07:54 (UTC)

Ok, so it kinda worked with lib32-jack2 installed. But it can't create the link with asio.h, as it already exists (i installed steinberg-asio from AUR). If I comment the ln -s line I still get an error : what information do you need to analyze this if wanted ?

schivmeister commented on 2013-10-14 06:24 (UTC)

Yes, that is correct, but there is already a lib32-jack2 since August. Pacman pulls in the first dependency match regardless of whether there are other provisions. So, install lib32-jack2 first, then build this. I agree that there should be a better way to handle deps and provisions. Presently, the user is given a choice between provisions only when there are two or more packages with different names having the same provision. In this case, the name of the dep is lib32-jack, and there is a package with the same name. Pacman will just pull this, and not care that there is a provision for it in lib32-jack2.

Gimmeapill commented on 2013-10-13 16:54 (UTC)

@DanielD: I think I know why. On x86_64, wineasio depends on "lib32-jack", not on "jack" (wineasio doesn't seem to like native jack 64 bit), and as there isn't any package "lib32-jack2" that provides it, pacman asks you to install old jack instead. The fix would be then to craft a "lib32-jack2" pkgbuild on the model of "lib32-jack" so satisfy the dependency. @schivmeister: please correct me if I'm wrong ;-)