[INFORMATIONS] Jack Reaper wineasio kontakt 5.5

Unofficial support for the KXStudio Linux distribution and applications.
More info at http://kxstudio.linuxaudio.org/

Moderators: khz, MattKingUSA

Established Member
Posts: 30
Joined: Mon May 06, 2013 6:08 am

[INFORMATIONS] Jack Reaper wineasio kontakt 5.5

Postby daeavelwyn » Sat Mar 26, 2016 12:03 am

Hi every one,

1.1-Just a post to give informations about jack, reaper and wine / wineasio in kxstudio. When installing reaper, avoid to check "ReaRoute ASIO Driver", this option cause issue with wineasio.

1.2 - If you try to work with firewire devices built on DICE architecture, be careful that you couldn't use FFADO driver directly if you got a kernel higher or equal than 4.2. Indeed, from 4.2, snd_dice module can make alsa using you firewire device. So, in Cadence (jack configuration window), be carefull to use ALSA driver instead of Firewire (even if your device is a firewire). If you still want to use FFADO, you have to add

Code: Select all

blacklist snd-dice

at the bottom of

Code: Select all


2- You have to use jack2 (and jack2-firewire in my case) otherwise, using kontakt libs that require kontakt higher than 5.3.1 result in crashing reaper/wine/wineasio links. You can observe this by opening catia, then start reaper, create a virtual instrument track with kontakt and load a vsti that requires kontakt higher than 5.3.1, repear disappears from catia (wineasio crash ??)
here is the output I got from jack log :

Code: Select all

ERROR: JackEngine::XRun: client = reaper was not finished, state = Running
ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error


Code: Select all

ERROR: JackEngine::XRun: client = reaper was not finished, state = Triggered
ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error

3- kontakt upper than 5.3.1 won't work with wine / wineasio / reaper without some tweaks. The issue comes from msvcp120.dll and is solved in wine 1.9.5, but kxstudio uses the 1.8 for now.
The issue is quite well documented and you can find informations here : https://appdb.winehq.org/objectManager. ... &iId=32836
Use this workaround instead of wine-staging, because wine staging is still unstable and buggy and doesn't want to easily work with wineasio. Cf: https://bugs.winehq.org/show_bug.cgi?id=40219

I retranscribe the workaround :
During installation Wine needs to be configured to Windows 7, but the application will not run unless Wine is running under Windows XP mode after installation.

Native versions of MSVCP120.DLL and MSVCR120.DLL need to be installed in the appropriate system directories as installation of the Visual C++ 2013 packages do not install the .dll's properly. Configure overrides for both of these .dll's to "native".

WARNING : on http://www.dll-files.com, they make a mistake packaging the DLL, the 64bits version is in fact the 32bits and the 32bits is the 64bits...read comments in the appdb.winehq.org post I mentioned upper in this post.

1. Use the Wine Configuration tool "winecfg" to set the Windows Edition to Windows 7
2. Install Kontakt and the Native Instrument service center (you can download on Native Instrument website)
3. Obtain the .dll's from an existing Windows installation, or from a dll site such as http://www.dll-files.com
4. Place the .dll's in the following directories:
a. 64 bit .dlls go into /home/username/.wine/drive_c/windows/system32
b. 32 bit .dlls go into /home/username/.wine/drive_c/windows/syswow64
5. Use the Wine Configuration tool "winecfg" to set the override for the .dll's to be set as "native" (https://i.imgsafe.org/812e22f.png)
6. Use the Wine Configuration tool "winecfg" to set the Windows Edition to Windows XP otherwise, detecting kontakt vst in reaper will result in crashing reaper_host32.exe (https://i.imgsafe.org/6720f65.png)
7. Run Kontakt

I also have to mention that using official kernel 4.4 lowlatency makes my saffire pro 40 (using ALSA as driver) crashes. So I have tried another kernels and got the best result with the liquorix kernel https://liquorix.net/#install No xruns, really reasonable latency (i'm at 5.8ms), and no driver/kernel module crash.

So, I hope it can help....
Last edited by daeavelwyn on Mon Apr 11, 2016 11:35 pm, edited 6 times in total.

Established Member
Posts: 159
Joined: Mon Jan 07, 2013 7:27 am

Re: [INFORMATIONS] Reaper wineasio kontakt

Postby Snap » Sun Mar 27, 2016 11:38 am

Thanks for the info. I haven't used Kontakt in ages, but that's great info to have in the stash just in case.

Reaper 5 is finally way more Linux friendly than the former 3 and 4 versions. It works noticeably smoother without crashes or hickups. The 64-bit version thanfully works on wine now. Some samplers finally work. VSTs work noticeable better, etc... Don't know (or hope) there will ever be a Linux version, but the current Reaper 5 is finally a reliable to go DAW on wine.

Gotta try you suggestions on some reluctant samplers like shortcircuit just in case (I used to love it and still have tons of drumkits for it), though I'm more than fine with sforzando or the native ReaSamplomatic for my drums and some occasional piano and organ. Only need/use samplers for that.
KXStudio: First Draft by wolftune viewtopic.php?f=47&t=10558

KXStudio Manual: http://wiki.linuxaudio.org/wiki/kxstudio_manual

glowrak guy
Established Member
Posts: 1380
Joined: Sat Jun 21, 2014 8:37 pm

Re: [INFORMATIONS] Reaper wineasio kontakt

Postby glowrak guy » Mon Mar 28, 2016 5:31 am

I've had similar happy experiences with Reaper 5.xx
Also, the linux version of Bliss sampler from discoDSP
is working well, sampling sounds from native linux vsts,
like zebra and zynaddsubfx. ACE and amsynth should also
work, covering the alphabet quite nicely.

Another thanks to daeavelwyn, for posting a useful wineasio/Kontakt tip!

Return to “KXStudio Discussion”

Who is online

Users browsing this forum: MSN [Bot] and 1 guest