@danboid: Sorry I somehow missed this one. AFAIK it's not needed to be a member of the audio user group to use wineasio.
Search Criteria
Package Details: wineasio 1.3.0-2
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: | 62 |
| Popularity: | 0.039938 |
| First Submitted: | 2007-05-27 07:28 (UTC) |
| Last Updated: | 2025-07-28 23:58 (UTC) |
Dependencies (5)
- jackAUR (jack2-gitAUR, pipewire-jack-gitAUR, pipewire-full-jack-gitAUR, pipewire-jack-ldacAUR, jack2, pipewire-jack)
- python-pyqt5 (python-pyqt5-sip4AUR, python-pyqt5-webkitAUR, python-pyqt5-pre-releaseAUR)
- realtime-privileges
- wine (wine-stable-nextAUR, wine-stableAUR, wine-valveAUR, wine-pure-gitAUR, wine-pure-gitAUR, wine-tkg-staging-ntsync-binAUR, wine-asahi-gitAUR, wine-gitAUR, wine-staging-gitAUR, wine-tkg-staging-binAUR, wine-tkg-staging-wow64-binAUR, wine-cachyosAUR, wine32AUR, wine-staging)
- gcc (gcc-gitAUR, gccrs-gitAUR, gcc-snapshotAUR) (make)
Required by (1)
Sources (1)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 15 Next › Last »
jhernberg commented on 2018-02-07 19:27 (UTC)
jhernberg commented on 2018-02-07 19:25 (UTC)
It shouldn't be... But I really ought to revisit this package...:)
I'll try to get some time in the upcoming days/week to have a look at it.
There used to be an issue with 32b wineasio not working on 64b jack2, but AFAIK this was fixed a long time ago.
Gimmeapill commented on 2018-02-06 20:12 (UTC)
It seems that Wineasio is still broken with jack2 on 64 bit systems, is that correct?
danboid commented on 2016-11-29 22:30 (UTC)
Currently, wineasio notifies the user of the need to run the regsvr32 command to register the dll after the package has been installed. I would like to see this message added to to also point out that non-root users need to be a member of the audio group to use wineasio. It should also notify them of the requirement to logout and back in again to enable the audio group permissions, if they weren't set already.
Thanks
jrdnjhntn commented on 2016-09-16 15:04 (UTC)
Cool. that makes total sense!
I'm building staging right now, with some other patches applied to it too. I don't expect to see any real advantage of staging either (with reaper anyway). thx
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
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.dllKazel 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.