Arch Linux User Repository

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: wineasio 1.2.0-10

Package Actions

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:	57
Popularity:	0.59
First Submitted:	2007-05-27 07:28 (UTC)
Last Updated:	2024-09-20 08:42 (UTC)

Pinned Comments

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.

xiota commented on 2024-09-02 18:02 (UTC) (edited on 2024-09-19 10:06 (UTC) by xiota)

Problem is some 9.x version of wine stopped building the 32-bit odbc library. wine-staging works because it hasn't been updated recently.

Edit: Removed suggested solutions.

falkTX commented on 2022-02-17 22:59 (UTC) (edited on 2022-02-17 22:59 (UTC) by falkTX)

Update for wineasio-1.1

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:

For 32bit, run: regsvr32 /usr/lib32/wine/i386-windows/wineasio.dll
For 64bit, run: wine64 regsvr32 /usr/lib/wine/x86_64-windows/wineasio.dll

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 15 Next › Last »

jhernberg commented on 2016-09-15 07:46 (UTC)

Well, I do use wine-staging and sometimes build wine-rt locally. The functionality as far as allowing windows high priority threads to run SCHED_FIFO is exactly the same in both versions, which is all the patch really does. The only difference in this respect is the renaming of the environment variables. Sometimes I build it just because I'm impatient to try the latest version, but other times I've found plugins not working in wine-staging that works in vanilla wine, or some other regression in wine-staging that breaks something for me. Seeing that reaper for instance works so well, there is little or nothing that the rest of the changes in wine-staging can really give me.

jrdnjhntn commented on 2016-09-11 23:27 (UTC) (edited on 2016-09-11 23:37 (UTC) by jrdnjhntn)

Ah, so you still are using wine-rt, just not packaging it for Arch? So thus far, you prefer wine-rt over how staging is doing it? I took at a look at the rt patch in wine-staging, quickly... I can still build wine-rt here, but I was curious about wine-staging.. Thanks for the tips! maybe, I'll give your script a try and see how it compares. side note: i'm not actually using linux-rt right this minute, just linux-bfq (but on a well-configured core i7 system, ssd, etc). I'm not really getting any xruns (well, wine-staging aside). I'm using with jack2, wineasio, etc running pulseaudio+memfd and zita-a2hbridge+snd-aloop, etc in the background too. i'll keep #reaper-linux in mind. thx a lot

jhernberg commented on 2016-09-11 23:10 (UTC)

Sometimes, if I get too impatient for a new build I build wine-rt ;) Try something like this: linux-rt installed Soundcard interrupt at priority 95 Jack at 80 #!/bin/sh export STAGING_RT_PRIORITY_BASE=60 export STAGING_RT_PRIORITY_SERVER=66 export WINEPREFIX=/home/jack/reaper schedtool chrt -f 61 wine ~/reaper/drive_c/Program\ Files/REAPER\ $x64$/reaper.exe And if you are on IRC, I just created #reaper-linux @ freenode. If you have any issues I'd be happy to help (if I'm around and have the time).

jrdnjhntn commented on 2016-09-11 15:44 (UTC)

@jhernberg - question; I would assume that you are using wine-staging these days, with your wineasio+reaper setup...? if so, how are you setting up the environment variables? ... I'm curious because testing wine-staging out with my reaper-wineasio combo -> I seem to be getting xruns and it's using higher cpu on average, under conditions where my older version of doesn't... thx

jhernberg commented on 2016-04-05 11:35 (UTC)

@benqu: I just tested the package, and it has no problem to download the source. Must have been some transient problem with sourceforge..

benqu commented on 2016-03-22 10:55 (UTC)

Download link has changed. Edit PKBUILD and replace line 21 with this: source=("http://downloads.sourceforge.net/project/wineasio/wineasio-0.9.2.tar.gz?r=&ts=1458643951&use_mirror=kent") Then it should work.

jhernberg commented on 2015-12-29 16:34 (UTC)

@fraunos: Sorry for the late reply... What app are you trying to use? Afaik, not all windows apps run well with wineasio and wine. Reaper is one that does for instance. Other problem at the moment is that you can't use 32b wineasio clients on a 64b jack2 system, on jack1 that works.

fraunos commented on 2015-12-19 23:58 (UTC)

I'm renewing the question - does anybody know how to get jack2 and wineasio working together? It returns constant flow of xruns. I'm getting quite bad results with jack1, high latencies and occasional xruns, still, would really appreciate any suggestions.

jhernberg commented on 2015-10-20 10:46 (UTC)

@eolien: You'd probably want to change the realtime scheduling priority of the interrupt servicing your soundcard too (or the usb hub it's connected to). Set it to 97 or something similarly high, this is to ensure that it get's scheduled with preference to most other threads on the system. Then run JACK in rt mode at priority 80.

jhernberg commented on 2015-10-20 10:36 (UTC)

@eolien: Think I recommended you (on irc) to install rt-tests and to run the cyclictest program to ascertain that your kernel is scheduling threads with the proper latency. I'd suspect that a system with vanilla kernel (no -rt kernel) and nvidia card, will have problems at low latency. I'd recommend to iron out this aspect with just JACK and a jack client first, before involving PA and wineasio. There are many places this can go wrong, so a structured approach to troubleshooting would probably be in your own best interest..