wineasio
Glitches at low samples rates, latency
Hi, I have been trying to use wineasio to have an acceptable latency using ableton live, which means to me at most than 256 samples per second. I have jack 1.9.22 installed and with my computer I easily run aeolus with no glitches at 64 samples per second, which I find. I installed the wineasio-amd64 5:0.10.0~git20200209 version from the kxstudio repository and then followed your instructions regsvr32 wineasio.dll wine64 regsvr32 wineasio.dll
I 've been running ableton live with the wineasio enabled in ableton live but I have glitches and xruns. Jacks messages the following : " Tue Mar 10 23:45:17 2020: New client 'Ableton Live 10 Trial' with PID 6132 23:45:18.238 Récupération désynchronisation (XRUN) (474). Tue Mar 10 23:45:18 2020: ERROR: JackEngine::XRun: client = Ableton Live 10 Trial was not finished, state = Running Tue Mar 10 23:45:18 2020: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error Tue Mar 10 23:45:18 2020: ERROR: JackEngine::XRun: client = Ableton Live 10 Trial was not finished, state = Running " Well, this many more times!! A bit of those :
" Tue Mar 10 23:45:19 2020: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error 23:45:20.100 Récupération de désynchronisation (XRUN) (7 sauté). 23:45:20.558 Récupération désynchronisation (XRUN) (482). Tue Mar 10 23:45:20 2020: ERROR: JackEngine::XRun: client = Ableton Live 10 Trial was not finished, state = Running " Also with triggered :
" Tue Mar 10 23:45:26 2020: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error Tue Mar 10 23:45:26 2020: ERROR: JackEngine::XRun: client = Ableton Live 10 Trial was not finished, state = Triggered "
Then I closed ableton live : " Tue Mar 10 23:45:58 2020: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error Tue Mar 10 23:45:58 2020: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error Tue Mar 10 23:45:58 2020: Client 'Ableton Live 10 Trial' with PID 6132 is out "
I can also say I have the same issue as this : https://github.com/jhernberg/wineasio/issues/6 : "Ableton 10 thinks there is a lot of load on my CPU but this isn't the case." When at 512 samples per seconds CPU is for me at 12% even if I don't play (then it grows at 17%) and it changes rapidly all the time. It often goes at more than 50% (only playing a sinewave on operator). With jack at 1024 samples per seconds there are much less xruns but still (and latency) and around 5% cpu load (still changing quickly), whereas when pulseaudio is the selected output in ableton, at 1024 samples per seconds there are no xruns at all and the cpu load is around 10% when not playing and 15% when playing, but stable at those values. The pulseaudio output is also going into jack. I use the lowlatency kernel.
Do you know what's going on? Is it a problem of mine, or a bug? Hope it can help both of us!
Cheers.
JACK is a lot more strict on buffer size and timing compared to pulseaudio, so understandable that they dont behave the same way.
Did you try to get good RT behaviour by declaring the variables for realtime usage? It requires wine-rt or wine-staging.
So try this:
export STAGING_SHARED_MEMORY=1
export STAGING_RT_PRIORITY_BASE=15
export STAGING_RT_PRIORITY_SERVER=10
export WINE_RT_POLICY=FF
export WINE_RT=15
export WINE_RT_PRIO=15
export WINE_SVR_RT=10
Then start your wine application from the same terminal where you exported those variables
Hi Filipe, Thanks for answering. Sorry for the delay but I had a really hard time installing wine-staging. Following your advice, I have installed : wine --version wine-5.4 (Staging)
and also wineasio version 5:0.10.0~git20200209
Then the terminal I did what you said : export STAGING_SHARED_MEMORY=1 export STAGING_RT_PRIORITY_BASE=15 export STAGING_RT_PRIORITY_SERVER=10 export WINE_RT_POLICY=FF export WINE_RT=15 export WINE_RT_PRIO=15 export WINE_SVR_RT=10
In the same terminal I ran the program, doing : wine "c:\programData\Ableton\Live 10 Trial\Program\Ableton Live 10 Trial.exe"
Then running Ableton Live I am able to use the wineasio driver.
But it didn't solve my problem : same crazy cpu usage and xruns.
Just for your info, in case it can be useful : I didn't use playOnLinux to install ableton live and wineasio : I installed wine and wineasio with synaptic and the terminal. But on playonlinux, the wine version proposed for 64 bits is the 3.10-staging, and when trying to install the wineasio driver with playonlinux, playonlinux says : 64-bit wineprefix is not supported. Please use a 32-bit prefix.
Also, when I use the winecfg gui, in the libraries panel I can't find the wineasio.
Do you have another tips? Do you recommand using playonlinux version?
Philippe
UPDATE : I tried Wine asio with the flStudio demo and it works with no latency. So I guess wineasio is not the problem, it is more a problem about my wine configuration I guess. So I stop bothering you. Keep up with the good work. Cheers!
UPDATE : I tried Wine asio with the flStudio demo and it works with no latency. So I guess wineasio is not the problem, it is more a problem about my wine configuration I guess. So I stop bothering you. Keep up with the good work. Cheers!
I am only seeing this now, so I guess it works for you after all. Cheers too.
No, it does not work for me for Ableton Live, only for FL Studio.
De : Filipe Coelho [email protected] Envoyé : mardi 14 juillet 2020 02:48 À : wineasio/wineasio [email protected] Cc : Philippe SICABAIG [email protected]; Author [email protected] Objet : Re: [wineasio/wineasio] Glitches at low samples rates, latency (#2)
UPDATE : I tried Wine asio with the flStudio demo and it works with no latency. So I guess wineasio is not the problem, it is more a problem about my wine configuration I guess. So I stop bothering you. Keep up with the good work. Cheers!
I am only seeing this now, so I guess it works for you after all. Cheers too.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/wineasio/wineasio/issues/2#issuecomment-657934356, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHMGLMSYQSWX7FTISEKCUHLR3PBO5ANCNFSM4LFJ2NTA.
Hey @philnsicab, did you solved the problem? I am on Guitar Pro and the latency is too much.
JACK is a lot more strict on buffer size and timing compared to pulseaudio, so understandable that they dont behave the same way.
Did you try to get good RT behaviour by declaring the variables for realtime usage? It requires wine-rt or wine-staging.
So try this:
export STAGING_SHARED_MEMORY=1 export STAGING_RT_PRIORITY_BASE=15 export STAGING_RT_PRIORITY_SERVER=10 export WINE_RT_POLICY=FF export WINE_RT=15 export WINE_RT_PRIO=15 export WINE_SVR_RT=10Then start your wine application from the same terminal where you exported those variables
Thx a lot @falkTX (for all the great dev and this suggestion) !
I've been experiencing the same problem of high DSP load and xruns with ableton live. The switch to wine-staging and those env parameters have done the trick perfectly !
Maybe the existence of the realtime feature in wine-staging and it's use to improve WineASIO response in certain situations could be documented in the README ? I don't measure how specific this issue is but RT feature and music seems to pair pretty generally to me.
Hey @philnsicab, did you solved the problem? I am on Guitar Pro and the latency is too much. Hi @mani-rai , no I didn't solve the problem. I reached to chose wineasio in the parameters of live but then live won't open anymore.
Did you try to get good RT behaviour by declaring the variables for realtime usage? It requires wine-rt or wine-staging. Hi @e-lie , no I didn't. I tried thought. On the first try I could select wineasio driver in live preferences but then I closed live and I couldn't open it again. I had opened it several times before thought with pulseaudio.
---- failed to open <asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\home\my_user_name\asioapp\dosdevices
z:\home\my_user_name\asioapp\dosdevices\z:\timeshift\snapshots\2022-01-18_14
-51-46\localhost\usr\share\ghostscript\9.50\Resource\CIDFSubst\DroidSansFallback
.ttf>
DroidSansFallback.ttf is a font.
@falkTX : I tried Wineasio with the flStudio demo and it works with no latency.
I retested and yes flStudio demo works flawlessly with wineasio, with no latency. Now I can select the wineasio driver in Ableton. When I do so, I have no latency but I still have the audio glitches.
I can select the flStudio asio driver in Ableton, and it gives me a little latency (it says 100 ms but I think it is like 30 to 40 ms), and no glitches !
I must also say that in winecfg, the selected audio driver is winepulse.drv. Is it normal ? If not, how do I change this ?
A weird thing happens when I launch Ableton live from the command line : Live opens but there is no instruments inside, no effects, etc...
I redirected the errors in a file and the
cat file | egrep *:err:*
and
cat file | grep fail
gives :
---- failed to open </usr/share/fonts/\type1\gsfonts\n019024l.pfb> as a font ---- failed to open </usr/share/fonts/\X11\Type1\c0419bt_.pfb> as a font
0114:fixme:font:freetype_set_outline_text_metrics failed to read full_nameW for font L"Ani"!
0114:err:winediag:ntlm_check_version ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. 0114:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problems
After installing the windbind package, those 2 previous errors disappeared, but didn't solve the behaviour.
0168:err:d3d:wined3d_context_gl_reacquire Acquired context 0000000000387D20 instead of 00000000002EADA0.
0168:err:d3d:wined3d_context_gl_reacquire Acquired context 00000000002B18F0 instead of 0000000000387D20.
There is also a load of : 0118:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (000000000011ED90 1 C) semi-stub and some : 0118:fixme:dxgi:d3d11_swapchain_Present1 Ignored present parameters 000000000011E5A0.
Any idea on how to solve this ?
Edit : I usually consider 256 samples / period beying okay for latency. But I tried with 512 and then there are no glitches in the audio in Ableton Live. Still erratic behaviour of the processor but with less charge.
Experiencing issues as well. I run jack2 and a motu interface. At 128 samples is kind of ok as long as I don't press any menus or file browser in live. It looks like the graphics are causing glitches. If anyone has a tip or experience on this please do tag me here and I'll provide more info. I tried rt kernel, wine from aur and run playonlinux
