Package Details: wineasio 1.0.0-1

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 wine
Licenses: LGPL
Submitter: shinlun
Maintainer: None
Last Packager: chuckdaniels
Votes: 50
Popularity: 0.004346
First Submitted: 2007-05-27 07:28
Last Updated: 2020-07-18 17:06

Pinned Comments

chuckdaniels commented on 2020-07-18 17:05

You need to add your user to realtime group to use wineasio.

You also need to register wineasio in you Wine prefix:

  • For 32bit, run: regsvr32 wineasio.dll

  • For 64bit, run: wine64 regsvr32 wineasio.dll

Latest Comments

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

marceliq commented on 2015-04-01 09:58

Ok, I'll stick with jack-dbus workaround, it looks it works.

jhernberg commented on 2015-03-18 21:23

@marceliq: Sorry I can confirm the bug with jack2 and 32bit wineasio. It happens with JACK2 (with or without dbus). I also get this error msg from JACK2:

ERROR: JackPosixSemaphore::TimedWait err = Connection timed out

But it works with jack1 and 32bit wineasio. 64bit wineasio works with both jack versions.

IMO, it's either badly packaged or 32bit support in JACK2 is broken.

Workarounds: use jack1(-dbus) or use 64b wineasio.

jhernberg commented on 2015-03-18 19:55

@marceliq: Sorry, it's called jack-dbus: https://aur.archlinux.org/packages/jack-dbus/

jhernberg commented on 2015-03-18 19:51

@marceliq: I can't reproduce the bug. Just tried with jack2-dbus, lib32-jack2 wine-rt 1.7.38 and this time 32b reaper (was 64b last test) and it works fine. But I see from the trace that something goes wrong. It's supposed to setup 4 io channels (2 inputs and 2 outputs), but ends up initializing only 2...:( Can't see why though. Maybe the jack config?

Unless I can find an error in the code, there is also a jack1-dbus package that i've created. It should work just as well as jack2-dbus, the only thing is that there is no device reservation for getting pulseaudio to release the soundcard. but it will work with pa if nothing is playing when you start jackdbus. pa even played back through jack when i tested it.

jhernberg commented on 2015-03-18 19:50

@marceliq: I can't reproduce the bug. Just tried with jack2-dbus, lib32-jack2 wine-rt 1.7.38 and this time 32b reaper (was 32b last time) and it works fine. But I see from the trace that something goes wrong. It's supposed to setup 4 io channels (2 inputs and 2 outputs), but ends up initializing only 2...:( Can't see why though. Maybe the jack config?

Unless I can find an error in the code, there is also a jack1-dbus package that i've created. It should work just as well as jack2-dbus, the only thing is that there is no device reservation for getting pulseaudio to release the soundcard. but it will work with pa if nothing is playing when you start jackdbus. pa even played back through jack when i tested it.

marceliq commented on 2015-03-18 16:12

@jhernberg: I also have wine-rt 1.7.38 but compiled from AUR, I also tried other versions of Wine (stable, staging, ..) I'm on x86_64, I'm using 32bit wine prefix with proper wineasio architecture. Here are the traces:

Start of Reaper: WINEDEBUG=-all,+asio WINEPREFIX=/home/marcel/.wine wine ~/.wine/drive_c/Program\ Files/REAPER/reaper.exe
trace:asio:WineASIOCreateInstance pobj = 0x176b50
trace:asio:Init iface: 0x176b50, sysRef: 0x20068
trace:asio:Init JACK client opened as: 'reaper'
trace:asio:Init 4 IOChannel structures allocated
trace:asio:Init 4 IOChannel structures initialized
trace:asio:Init WineASIO 0.9.2 initialized
trace:asio:GetDriverName iface: 0x176b50, name: 0x938768
trace:asio:GetDriverVersion iface: 0x176b50
trace:asio:GetChannels iface: 0x176b50, inputs: 2, outputs: 2
trace:asio:GetBufferSize iface: 0x176b50, minSize: 0x938810, maxSize: 0x938814, preferredSize: 0x938818, granularity: 0x93881c
trace:asio:GetBufferSize Buffersize fixed at 1024
trace:asio:GetSampleRate iface: 0x176b50, Sample rate is 48000
trace:asio:CreateBuffers iface: 0x176b50, bufferInfo: 0x938840, numChannels: 2, bufferSize: 1024, asioCallbacks: 0x9418ac
trace:asio:CreateBuffers Buffersize fixed at 1024
trace:asio:CreateBuffers The ASIO host supports ASIO v2
trace:asio:CreateBuffers The ASIO host supports kAsioResetRequest
trace:asio:CreateBuffers The ASIO host supports kAsioResyncRequest
trace:asio:CreateBuffers 4 ASIO audio buffers allocated (32 kB)
trace:asio:CreateBuffers 2 audio channels initialized
trace:asio:GetLatencies iface: 0x176b50 Latency = 1024 frames
trace:asio:Start iface: 0x176b50
trace:asio:Start TimeInfo mode enabled
trace:asio:Start TimeCode supported
trace:asio:jack_thread_creator arg: 0x7d44ffc8, thread_id: 0x7d44ffdc, attr: 0x33d098, function: 0xf22a6fd0
trace:asio:jack_thread_creator_helper arg: 0x7d44ffc8
trace:asio:Start WineASIO successfully loaded

After I hit play there is nothing.. No audio, no log, time marker just stay on zero, but I get [Playing] status in Reaper.

After hitting stop button, again no log. I can see only [Stopped] status.

Same behavior is in different prefix with ASIOSigGen tool.

Linux native Bitwig Studio works without any problems with jack2-dbus.

And here is the wierdest part - everything miraculously works after installing jack(1) and lib32-jack(1) and get rid of lib32-jack2 jack2-dbus. (jack2 also doesnt work for me)

And I have no clue why is that.. :(

I also get rid of all alsa/pulseaudio configurations and than reinstalled alsa, but with the same result.

marceliq commented on 2015-03-18 16:09

@jhernberg: I also have wine-rt 1.7.38 but compiled from AUR, I also tried other versions of Wine (stable, staging, ..) I'm on x86_64, I'm using 32bit wine prefix with proper wineasio architecture. Here are the traces:

Start of Reaper: WINEDEBUG=-all,+asio WINEPREFIX=/home/marcel/.wine wine ~/.wine/drive_c/Program\ Files/REAPER/reaper.exe
trace:asio:WineASIOCreateInstance pobj = 0x176b50
trace:asio:Init iface: 0x176b50, sysRef: 0x20068
trace:asio:Init JACK client opened as: 'reaper'
trace:asio:Init 4 IOChannel structures allocated
trace:asio:Init 4 IOChannel structures initialized
trace:asio:Init WineASIO 0.9.2 initialized
trace:asio:GetDriverName iface: 0x176b50, name: 0x938768
trace:asio:GetDriverVersion iface: 0x176b50
trace:asio:GetChannels iface: 0x176b50, inputs: 2, outputs: 2
trace:asio:GetBufferSize iface: 0x176b50, minSize: 0x938810, maxSize: 0x938814, preferredSize: 0x938818, granularity: 0x93881c
trace:asio:GetBufferSize Buffersize fixed at 1024
trace:asio:GetSampleRate iface: 0x176b50, Sample rate is 48000
trace:asio:CreateBuffers iface: 0x176b50, bufferInfo: 0x938840, numChannels: 2, bufferSize: 1024, asioCallbacks: 0x9418ac
trace:asio:CreateBuffers Buffersize fixed at 1024
trace:asio:CreateBuffers The ASIO host supports ASIO v2
trace:asio:CreateBuffers The ASIO host supports kAsioResetRequest
trace:asio:CreateBuffers The ASIO host supports kAsioResyncRequest
trace:asio:CreateBuffers 4 ASIO audio buffers allocated (32 kB)
trace:asio:CreateBuffers 2 audio channels initialized
trace:asio:GetLatencies iface: 0x176b50 Latency = 1024 frames
trace:asio:Start iface: 0x176b50
trace:asio:Start TimeInfo mode enabled
trace:asio:Start TimeCode supported
trace:asio:jack_thread_creator arg: 0x7d44ffc8, thread_id: 0x7d44ffdc, attr: 0x33d098, function: 0xf22a6fd0
trace:asio:jack_thread_creator_helper arg: 0x7d44ffc8
trace:asio:Start WineASIO successfully loaded

After I hit play there is nothing.. No audio, no log, time marker just stay on zero, but I get [Playing] status in Reaper.

After hitting stop button, again no log. I can see only [Stopped] status.

Same behavior is in different prefix with ASIOSigGen tool.

Linux native Bitwig Studio works without any problems with jack2-dbus.

And here is the wierdest part - everything miraculously works after installing jack(1) and lib32-jack(1) and get rid of lib32-jack2 jack2-dbus. (jack2 also doesnt work for me)

And I have no clue why is that.. :(

jhernberg commented on 2015-03-18 10:40

@marceliq: I just installed (on x86_64) jack2-dbus, lib32-jack2. I had wine-rt 1.7.38 and wineasio installed from the archaudio-production repo, and it appears to work with no problems. What architecture?

Could you try to start reaper with WINEDEBUG=-all,+asio wine reaper.exe in a terminal? This will produce a trace of what wineasio is doing and might uncover something. Note that this script was broken a long time on AUR (since I took it over), but I think that was just for i686. But this has been fixed a few months ago.

marceliq commented on 2015-03-13 14:06

Is this currently working for you with latest version of wine? Did you ever try to use jack2-dbus? My build does not work with Reaper, it just freeze without any sound and I can see only xruns.

Thanks.

jhernberg commented on 2014-10-23 19:58

Why did it get flagged out of date?