HOWTO: REAPER on Ubuntu Linux with wineasio (updated)
I’ve updated this HOWTO to work with Ubuntu Hardy and the latest (as of this writing) wineasio and fixed the link to Steinberg’s site. If you notice any errors, please let me know so I can fix them. I also need to say thanks to Peter Jones for his work on wineasio and the information he contributed to this howto.
You may have already heard about REAPER. If not, REAPER is an extremely powerful digital audio workstation brought to you by the creator of Winamp. It’s also very reasonably priced. Unfortunately, it’s also Windows based, which presents a problem for people like me who avoid Microsoft products like the plague. REAPER can run under Linux with Wine, but up until recently that solution has left a lot to be desired (even compared to current Linux-based audio production solutions). The reason for this is because REAPER had to use the standard wavemapper interface to get audio to play. To put it mildly, that sucks. Even then it was very unreliable.
The other day, my friend Aaron (pipelineaudio) turned me on to a project called wineasio (or wine asio). What this does is allow REAPER to use the ASIO interface, which works much better. wineasio takes the connections from the ASIO interface and exposes them to JACK, which gives you a whole world of routing and configuration possibilities as well as a reasonably low latency interface to your soundcard. So, let’s get started.
First things first, you need to be running Ubuntu and it needs to be the x86 desktop version of 7.04 (Feisty Fawn) 8.04 (Hardy Heron). You need to make sure you’re up to date and that your sound already works. If you need help with any of those things, please look for it in the Ubuntu Forums. Once you’re sure you have all of those things, we need to install a few pieces of software. Here are the packages we’ll be installing:
- wine
- wine-dev
- libjack0.100.0-dev
- qjackctl
- build-essential
linux-rt(I removed this because running the RT kernel is beyond the scope of this howto)
If one were so inclined, he could search for the above packages in Synaptic and install them there, but we’ll be using apt-get to do this, so click on Applications » Accessories » Terminal. Type or copy and paste the following command to install everything:
sudo apt-get -y install wine wine-dev libjack0.100.0-dev \
qjackctl build-essential
After you put in your password, this is going to download and install about 64mb worth of stuff, so if you’re on a slow connection it might take a while. This is a good chance to get a cup of coffee, a sandwich or spend some time in the thinking room. When it finishes, go ahead and reboot your computer and be sure to boot up with our shiny new low-latency kernel.
Once you’re back to your desktop, we need to jump on the web and download some more stuff. The first thing we need to get is wineasio. As of this writing, the file we need is wineasio-0.7.4.tar.bz2. Just download that right to your desktop. If there’s a newer version, you can use that instead but remember to change the commands below to account for the different file name. The next thing we need is the Steinberg ASIO 2.2 SDK. Unfortunately, I can’t provide a direct link to the archive, so you’ll need to sign up for an account to get to the download. The file you’re after is asiosdk2.2.zip, and make sure you put it on your desktop with wineasio-0.7.4.tar.bz2. While you’re at it, go ahead and download the newest version of REAPER to your desktop as well.
After you get those 2 files downloaded, let’s get back to our terminal. We need to change directories to the desktop with this command:
cd ~/Desktop
Next we need to extract the two archives we just downloaded with these commands:
tar xvjf wineasio-0.7.4.tar.bz2
unzip asiosdk2.2.zip
Now, we need to change to the wineasio directory and copy in the asio.h file from the ASIO SDK. We can do that with these commands:
cd wineasio
cp ../ASIOSDK2/common/asio.h .
Now we need to compile wineasio with one very simple command:
make
As long as you don’t see any errors (warnings are OK), then it compiled fine and we can install it with this command:
sudo make install
You may need to put in your password again before it will go. Now we need to register the wineasio.dll with Wine using this command:
regsvr32 wineasio.dll
Now it’s time to set up Wine to work with REAPER. Type this command at your terminal to bring up the Wine configuration:
winecfg
This will hopefully pop up the Wine configuration window which should look something like this…
You need to change the “Windows Version” at the bottom to Windows XP. Then click on the Audio tab at the top. There will probably be some delay and a popup telling you there is no default audio driver or something. Go ahead and just close the popup and you should have the audio configuration window which looks something like this…
Here you want to make sure that JACK is the only driver selected. I’m told that this isn’t strictly needed for REAPER/wineasio, but will allow other software running with Wine to be able to make noises while JACK is doing its thing. Once you’ve done that, go ahead and click Apply and then click OK.
Now click on Applications » Sound & Video » JACK Control. This little utility is very important. This is what you’re going to use to adjust your buffer settings and latency and whatnot. It should look like this:
Go ahead and click on the Setup… button on the right, which will give you a screen similar to this one:
The settings in the screenshot are the ones that ended up working for me. You can use them as a starting point, but eventually you’ll want to experiment and find something that works best with your hardware. The Frames/Period and Periods/Buffer are what determine your latency. You can see in the lower right hand corner what your latency will be, so try to pick some settings that seem sane for your hardware. Once you’re satisfied with what you’ve done, click OK to close the setup window.
Hopefully, the display will light up like the above screenshot. If it does, you’re in business. Now it’s time to install REAPER. Right click on the icon for the REAPER install and choose “Open with other application…” from the menu. Click on “use a custom command” at the bottom of the window and type in wine like I did above. Then just click the open button. This will run the REAPER installer. You should be able to just double-click on the installer, but it will probably take a few seconds to pop up. Just click through it like you normally would if you were running Windows. When it asks if you want to run REAPER, click Yes. Close the project settings window, close the error about not being able to initialize audio (if there is one) and close the registration window. In the very upper right hand corner, click where it says [audio device closed]. This will bring up the REAPER preferences, which should look something like this:
In the audio system drop down box, choose ASIO. This should make your configuration look pretty similar to mine as shown above. We need to make sure we’re using the wineasio driver and that there are some inputs/outputs showing up. If there are, then click OK and try playing the sample project. With any luck, you’ll be treated to the glorious sounds of Brad Sucks. But, there’s probably a good chance it’s going to click and pop and stutter or do something else nasty. If it does, close REAPER and stop the JACK control. Adjust the JACK settings for latency we looked at earlier, start the JACK server and double click the REAPER icon on your desktop and try again. It’s a trial and error thing but you should eventually be able to get it to play smoothly.
Anyway, that’s it. If you want to chat or discuss any of this, you can find me in #reaper on irc.cockos.com as daveisadork. Good luck!
April 29th, 2007 at 9:47 am
neat post…
I don’t feel like looking it up, but there is another multitrack/mastering program that works for linux which I’ve heard of a few studios actually using…
some day I’d like to have a linux workstation running in my studio…but as of now, it’s not quite practical…
April 29th, 2007 at 2:59 pm
thanks! that helped very much.
Btw, you cannot use midi inputs in this config I think, one needs to choose ALSA and deselect Jack and OSS. Midi works through alsa.
May 11th, 2007 at 5:35 pm
@kelsey
That multitrack app you’re thinking of is called Ardour (www.ardour.org), version 2.0 came out recently and it’s great. Give it a try!
As for mastering, most people use JAMin.
Thanks for this excellent howto, by the way
July 7th, 2007 at 6:48 am
You saved my day, man! I love the Reaper, and it works great under Ubuntu as you described. Latency is very low, and I get to use my VST effects.
Yeah!
Peter
July 17th, 2007 at 6:01 am
A few more notes as of 7/17/07 :
Yes, you should select the ALSA driver *only*, there is no need to select the Jack driver in winecfg. Wineasio won’t work without it.
As a matter of fact, Reaper will run nicely under Wine without wineasio, but only with a powerful enough machine. I run it with wineasio on my 32-bit box (JAD) and without it on my 64-bit iron (64Studio). Both machines are AMD64-based, one is a 3800+ and one is a 3200+ CPU.
Amazingly, 32-bit VSTs will load and run with Reaper on my 64-bit box. Well, some do and some don’t.
Recent versions of Wine have a deep bug that has destabilized VST support. If you experience X-based errors try switching to an earlier verion of Wine. I’m using 0.9.9, it works beautifully with Reaper, FST, and ArdourVST (my build).
I now recommend Reaper and Audacity to my Windows-bound students, it’s a terrific combination for them to learn the basics of recording and processing digital audio/MIDI.
And yes, thank you for this tutorial.
Best regards,
dp
July 17th, 2007 at 6:04 am
Oh yeh, make sure that your sample rate for wineasio is the same as what you’ve selected for Jack.
August 3rd, 2007 at 7:38 am
Hi, I followed your tutorial and got reaper working. But, the chat window in ninjam doesn’t work. I press enter after typing something
and nothing happens.
September 8th, 2007 at 4:42 am
I’ve a patch that lets you store wineasio’s ASIO to JACK routing:
http://bugs.winehq.org/show_bug.cgi?id=2161
(it’s against wineasio-0.3)
September 15th, 2007 at 4:11 pm
awesome instructions. I got Reaper to work in Ubuntu without much trouble at all. Thanks for the tips.
one thing has happened since I installed everything I seem to have lost audio with my flash plugin. eg. on webpages with youtube or flash animations there is no sound now… and they worked fine earlier today.
any idea on what it might be or how to fix it? i’m a noob with Ubuntu and Linux, so step by step instructions may be needed.
thanks for any help.
- jeff
September 21st, 2007 at 9:52 am
In the winecfg setup I don’t seem to have Jack as an option but yet it is installed and after I did the Jack Control setting Jack will start.
Any Idea why Jack is not listed in winecfg.
Thanks
September 25th, 2007 at 2:58 pm
Timothy:
(1) wineasio won’t show up as a device in winecfg (just as an ASIO driver doesn’t show up as a device in device manager in Windows).
(2) if you’ve got JACK as an option in winecfg, don’t use is (as that’s not wineasio). Select ALSA only. (AIUI, an older patch to Wine had this option.)
Anyway, this is just an excuse to say wineasio-0.5 has been released with my patch
.
October 4th, 2007 at 12:45 pm
Thanks Peter
October 4th, 2007 at 12:47 pm
Buy the way will this setup work on a 64bit Linux system?
Seem to have some trouble on my Ubuntu Fiesty 64bit setup
October 5th, 2007 at 7:29 am
Timothy:
Yes, you can run Reaper in a 64-bit environment, but you won’t be able to use the wineasio driver. At this time there’s no way for a 32-bit app to communicate with 64-bit JACK.
You’ll need to build or find a Wine package for regular 32-bit operation *built for a 64-bit platform*. Use the OSS or ALSA driver. Latency is horrible, but if you don’t need much realtime support the program is usable. And yes, some VST plugins will work there too (which amazes me).
Btw, I run Reaper on 32-bit JAD and 64-bit 64Studio.
November 4th, 2007 at 2:26 am
Thanks for the guide, I used these instructions on Gutsy with no problems.
Two things to note, the linux-lowlatency kernel has been replaced by linux-rt in Gutsy and the newest version of WineASIO is 0.5 (wineasio-0.1.tar.gz).
November 16th, 2007 at 12:22 pm
greetings! Total Linux nooob here.
I tried to past the first command into the terminal… Paste didn’t work
I typed it in, double checked it for accuracy… voila… life!
then, alas! I am presented with this:
ubuntu@ubuntu:~$ sudo apt-get -y install wine wine-dev libjack0.100.0-dev \ qjack build-essential linux-lowlatency
Reading package lists… Done
Building dependency tree
Reading state information… Done
E: Couldn’t find package wine
ubuntu@ubuntu:~$
and now, I am at a total loss…
is this due to my distro being KUBUNTU?
any assistance would be much appreciated!
cheers,
.t
November 16th, 2007 at 1:01 pm
Tallisman: If you’re running the latest Ubuntu (or Kubuntu, 7.10) then there are a few things that won’t work. I’m planning on updating it this weekend some time so check back soon. If you’re running Kubuntu 7.04, then you need to make sure all of the extra repositories are enabled. I’m not familiar with the KDE package management software, so I can’t give you specific instructions about how to do that.
November 16th, 2007 at 2:24 pm
thanks very much for the reply!
I have this page bookmarked in about 5 places
I feel like I may be in for a long ride!
.t
November 26th, 2007 at 12:09 pm
Great HOWTO, thanks so much.
I have this working with Ubuntu 7.10 (Gutsy).
I saved a bit of time by going here and installing the wineasio .deb file.
November 28th, 2007 at 11:19 pm
I did just like this tutorial says (almost, actually I had to choose ONLY alsa in the wine audio conficuration).
It’s working fine!
Thanks so much, you have no idea of how that makes me happy
December 1st, 2007 at 3:54 pm
Hi all,
I’ve updated my patches to wineasio and the version number has grown to 0.7.0 (to allow more breathing space for bug fixing). I’ve posted the updates to JackLab and 64Studio teams, so expect to see stuff happen in the next few days.
More details on the new version here:
http://forum.jacklab.net/viewtopic.php?t=563
December 1st, 2007 at 10:31 pm
Wow! Amazing! You really know how to get things working. When people try this hard to get Reaper and NINJAM working it deserves all the love in the world. Hope to meet you on ninjam sometimes. We all owe you!
love,
rolf (dk)
December 19th, 2007 at 8:35 am
I didn’t use this howto to install reaper, I used it to install traktor dj studio 3, because without wineasio there is no sound output, you may not be able to help me, because this howto is for some completely different software, but when i try to run traktor, nothing opens, i give the command “wine ” and i’m just taken back to bash again with no output from wine
December 19th, 2007 at 8:41 am
You need to supply wine with the path to your exe file, so you would do something like this:
wine ~/.wine/drive_c/Program\ Files/REAPER/reaper.exeTo run Reaper. Obviously you’d need to replace it with the path to Traktor, but it will be similar. Don’t forget that the path is case sensitive and you have to escape your spaces with a forward slash.
December 19th, 2007 at 8:53 am
sorry your comment script blocked some of my reply because it thought it was an html tag, i didn’t just give the command wine, i gave “wine pathtoapplication”
December 19th, 2007 at 8:57 am
hmm, its not looking bright then, i can’t get my head round this, because normally when wine can’t run an exe, it’ll tell you why! whats more annoying is that i’d given up on traktor months ago, i had everything working but sound output (pretty important lol) and i just stumbled over your blog now and thought my prayers had been answered!
December 19th, 2007 at 8:59 am
That is strange, but I’m afraid I can’t help as I don’t have a copy of Traktor.
December 20th, 2007 at 7:59 am
re: Traktor under Wine: It may not work. Helpful as is Dave’s tutorial, it’s not 100% effective with other applications. From what I can tell, the more kosher the original Windows programming, the easier it will be to run the app under Wine. Unfortunately, music and sound applications in Windows often perform many proprietary tricks to work with the system, and as I say, the more clever the original programming, the less of a chance it has to work under Wine. The Wine devels are focused on resolving problems with Wine, not with Windows applications, and they are not working to solve program-specific problems. The Reaper devels actually monitor their app’s performance under Wine, i.e. they are aware that some users prefer to run Reaper under Linux and they don’t just turn their backs on those users. An impressive attitude, one that is sure to garner loyalty among the program’s users.
I’m a little surprised that Traktor fails with Wine. It’s built on JUCE, a very powerful multi-platform development framework. Some Linux apps already use JUCE (GRACE, Jost, Mammut) and they run beautifully (of course, they’re native Linux apps). I’d like to see JUCE used more widely for Linux sound & music software, but so far its acceptance has been slow. Btw, there’s a persistent rumor that eventually we’ll see a Linux Traktor, but it seems to me that they’re waiting too long. Ardour 2.0 is all I need for pro-audio recording, and Reaper functions very well as a VST host under Wine. Traktor may well show up late for the party only to find that everyone’s already happy with what they have..
December 20th, 2007 at 3:33 pm
i actually got it working, i just reinstalled wine lol
the audio is a bit jumpy, but i think thats down to me not having a very good soundcard, with a bit of effort though i think i can get it working properly, because traktor runs with no problem in my windows install
i heard talk of a linux traktor over on the native instruments forums, but i really doubt NI would persue it, though it would really be great!
ooh and thanks for the tutorial
January 16th, 2008 at 5:37 pm
@richard: can u explain step-by-step how u produced sound in traktor 3?
i followed this howTo, i am running ubuntu gutsy, used the .deb packager of wineasio, did the configuration, start with wine asio driver, and the song starts, traktor is registering sound output, but i hear nothing
any hELP?
rgz
ivo
January 24th, 2008 at 3:31 pm
just fiddle about with the settings in the jack audio connection kit, it takes a bit of trial and error, the low latency kernel (or linux-rt as it’s now called) is essential, i did get it working fully in the end, i’ve just come back now because i’ve had to reinstall my system because hardy broke EVERYTHING! don’t install it!
January 31st, 2008 at 6:22 am
Will these instructions now work under Ubuntu Studio 7.10? Thanks for the article!
January 31st, 2008 at 8:36 am
Oh and do I need to install build-essential under Ubuntu Studio 7.10? As it looks like the only other things that need installing are wine, wine-dev and wineasio for me to get this working with Reaktor *fingers crossed*.
January 31st, 2008 at 9:39 am
Alex: I’m not sure about Ubuntu Studio, I haven’t ever used it. I imagine it’s extremely similar to the standard Ubuntu so it shouldn’t take much modification. If you have any notes from your installation, please post them here for everyone else.
February 4th, 2008 at 1:55 pm
I managed to get this working perfectly with Ubuntu Studio. I wondered if you can help me with another small problem though.
I have installed Kontakt and through Reaper it plays back perfectly but if I run it in external mode and use the connect option in jack to route its outputs to my sound card I don’t hear any sound, despite it appearing to work correctly.
I tried routing it back into Ardour to record the output but no go either. Other than that it appears to work.
February 4th, 2008 at 2:05 pm
Sorry, one more thing to add, Reaper actually disappears from the Audio Connections list in Jack if you don’t have the window active. If you click another window and it goes inactive the ASIO_REAPER in Output ports disappears. When you make the window active again, the routing goes back to default and anything you set up is lost.
February 4th, 2008 at 2:09 pm
Hehe, sorry again. I fixed that last issue by unchecking “close audio device when stopped” in Reaper. Please clean up my spam if you wish.
Would love to get Konkakt running in it’s own external mode though if you can help with that:)
February 4th, 2008 at 2:12 pm
Unfortunately I don’t have a copy of Kontakt, so I can’t provide much assistance. Maybe someone else could help you out. If you do manage to get it going, do remember to stop back by and let us know what you did.
February 4th, 2008 at 3:07 pm
OK, thanks anyway, Dave.
It seems to run with a VST host ok(ish) – some crackles and pops but I would much prefer to run standalone.
If I solve it I will report back here.
February 8th, 2008 at 7:32 am
hey everyone… i’m trying to get this whole linux-reaper thing to work because i love reaper, but dont really care for windows.
i’m having a problem with the jack configuration it’s throwing an error that to me is very esoteric.
here’s my dilemma posted on the reaper forums:
http://www.cockos.com/forum/showpost.php?p=154215&postcount=23
any help here or there would be greatly appreciated.
February 28th, 2008 at 4:15 am
Re: Traktor being built on JUCE – I think you are confusing Traktor (a DJ application from Native Instruments) with Tracktion (a sequencer now from Mackie, originally written by the author of JUCE).
March 2nd, 2008 at 11:13 am
Adam, applications “disappearing” from qjackctl is generally a sign they’ve been booted from the server. This happens if jackd decides they’re a menace. It happens all the time to me if I’m running a stock kernel and occasionally if I’m running “too many apps” on an -rt kernel. WINE can start counting as “too many apps” quite quickly compared with native programs.
March 3rd, 2008 at 5:09 pm
Hi guys,
I’ve been trying to figure install WineAsio but whenever I try to compile it (after the Make command), I get an error. I should not that I have used the newest version (0.7.3) of WineAsio available found in the parent folder of the link given
http://people.jacklab.net/edogawa/files/wineasio/
Heres the error (I included the dir command to show you I copied all that was needed)
chris@LinuxLaptop:~/Desktop/wineasio-0.7.3$ dir
asio.c config.h Makefile README.TXT settings.h
asio.h main.c port.h regsvr.c wineasio.dll.spec
chris@LinuxLaptop:~/Desktop/wineasio-0.7.3$ make
gcc -c -I. -I/usr/include -I/usr/include -I/usr/include/wine -I/usr/include/wine/windows -m32 -g -O2 -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -o asio.o asio.c
gcc -c -I. -I/usr/include -I/usr/include -I/usr/include/wine -I/usr/include/wine/windows -m32 -g -O2 -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -o main.o main.c
gcc -c -I. -I/usr/include -I/usr/include -I/usr/include/wine -I/usr/include/wine/windows -m32 -g -O2 -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -o regsvr.o regsvr.c
winegcc -shared wineasio.dll.spec -mnocygwin -o wineasio.dll.so asio.o main.o regsvr.o -ljack -lodbc32 -lole32 -loleaut32 -lwinspool -lwinmm -lpthread -luuid
winegcc: gcc-3.4 failed
make: *** [wineasio.dll.so] Error 2
chris@LinuxLaptop:~/Desktop/wineasio-0.7.3$
I’m running Ubuntu with a RT kernel on an 32 bit system with wine 0.9.55 downloaded from the WineHQ repositories.
Thanks
March 3rd, 2008 at 5:13 pm
I’ve actually tried with wineasio ver 0.1 and I get the same error
March 4th, 2008 at 6:12 pm
Chris:
You need to install gcc-3.4. Wine uses a wrapper for gcc (winegcc) that expects to see gcc-3.4. If you only have gcc-4.x, then it’ll fail.
March 6th, 2008 at 8:15 am
Setting INPUTS and OUTPUTS
WOW! I finally succeeded to get reaper running on Ubuntu Studio! Graphically, it is quite okay, not too sluggish.My latency is 1-3 ms!!!
I have been trying it out for more than a week, but could not figure out how to set it up to have it show all my inputs in Reaper. Now here’s the hack (remember I am Linux newbie).
When you download and unpack wineasio, make sure to put the above mentioned asio.h (from the steinberg ASIO SDK) into the the unpacked wineasio-0.7.3 directory. Go to this directory, either with the commandline or the filebrowser, and use gedit or right-click on the file “settings.h” go to the lines:
static const int DEFAULT_NUMINPUTS = 2;
static const int DEFAULT_NUMOUTPUTS = 2;
and change the values to the amount of hardware inputs and outputs that you know you have. I even wonder if you can make more in and outputs than hardware, and use them for internal routing to and from soundmodules and synths? I have 18 hardware ins and outs, but 8 in and out will do for now:
static const int DEFAULT_NUMINPUTS = 8;
static const int DEFAULT_NUMOUTPUTS = 8;
After this, follow the instructions on compiling and installing like said in the manual above.
Another tip: the latest version of Jack can be found on http://jackaudio.org/
make sure you get that one.
last tip: I discovered “Patchage” a very nice tool to patch your ins and outs. Every App you launch shows up there and can be patched in any way you desire. If itś not on your system (itś a standard Ubuntu Studio thing), look for it in your Ubuntu repositories or installer or synaptic.
Now a final question: I have now installed a new version of JACK. But the old one keeps popping up. How can I deinstall the old one? Two instances of the same program is a little bit confusing.
Thanks!!!
March 16th, 2008 at 11:13 am
To uninstall the old jack I would have thought you could just use your package manager, assuming you installed it that way and not compiled from source.
March 27th, 2008 at 2:54 pm
This is not actually related to reaper, but if all you are doing is hosting vst plugins, you might want to try Kristal. It’s a free Windows based DAW, not nearly as capable as Reaper I am sure, but it uses asio, is a capable VST host, and is free for non-commercial use. I have it working beautifully on my JAD 1.0 machine. See my post here http://forum.jacklab.net/viewtopic.php?f=5&t=730 for knfo and a screenshot. It runs with very few xruns with 16 tracks of audio and a slew of VST effects active (with qjackctl settings at 1.5ms!). I am happy, at least!
April 8th, 2008 at 7:10 am
Uh, “…either “globally” (”ASIO”) or…”, I mean.
April 8th, 2008 at 7:12 am
From the README.TXT for WINEASIO, for those who haven’t read it. (Editing the source is not required…)
2. USER INSTRUCTIONS
The driver can be configured in two ways: either using environment variables
or using a configuration file.
The configuration file can be set per user in “.wineasiocfg”.
As a fallback, a site file can be provided in “/etc/default/wineasiocfg”
if desired.
The format for the configuration file is simply “var=val”.
If using the shell, either include the assignment on the command line:
ASIO_INPUTS=0 ~/bin/reaper.exe
or ensure the variable has been exported:
EXPORT ASIO_INPUTS=0
~/bin/reaper.exe
The available variables are as follows:
ASIO_INPUTS
ASIO_OUTPUTS
ASIO_INPORTNAME
ASIO_OUTPORTNAME
ASIO_INPORT
ASIO_OUTPORT
The last entry allows you to change the client name from the default, which
is constructed from the program name prefixed by “ASIO”. For example,
ASIO_reaper.exe=REAPER
All of the entries beginning ASIO_ can also have entries specific to a client,
using the assigned client name. For example,
REAPER_INPUTS=0
INPUTS and OUTPUTS
These let you limit the number of JACK ports allocated to this client.
INPORTNAME and OUTPORTNAME
These allow you to rename the input and output ports for the client.
The default names are “input_” and “output_”. For example,
REAPER_OUTPORTNAME0=left
REAPER_OUTPORTNAME1=right
INPORT and OUTPORT
These allow you to connect the client to JACK ports of your choice.
The default is to connect JACK’s “hardware” inputs to your client’s inputs
and your client’s outputs to JACK’s “hardware” outputs. You might be
running some other application, e.g. an icecast server, and want to
send output to that. For example,
ASIO_OUTPORT0=idjc-mx:aux_lt
ASIO_OUTPORT1=idjc-mx:aux_rt
April 8th, 2008 at 7:14 am
Oh well, that didn’t format so well and reading it, it looks like I need to update some of it before 0.7.4 goes out!
April 9th, 2008 at 4:15 pm
And, indeed, 0.7.4 is out.
wineasio has a “real home” now, on SourceForge:
http://sourceforge.net/projects/wineasio
August 11th, 2008 at 10:22 am
This happened to me. nothing but errors. followed all your instructions. am i doing something wrong?
wineasio$ make
gcc -c -I. -I/usr/include -I/usr/include -I/usr/include/wine -I/usr/include/wine/windows -m32 -g -O2 -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -o asio.o asio.c
asio.c:44:23: error: jack/jack.h: No such file or directory
asio.c:52: error: expected ‘)’ before ‘nframes’
asio.c:139: error: expected specifier-qualifier-list before ‘jack_port_t’
asio.c:181: error: expected specifier-qualifier-list before ‘jack_client_t’
asio.c: In function ‘IWineASIOImpl_Release’:
asio.c:218: warning: implicit declaration of function ‘jack_client_close’
asio.c:218: error: ‘IWineASIOImpl’ has no member named ‘client’
asio.c:221: error: ‘IWineASIOImpl’ has no member named ‘terminate’
asio.c:222: error: ‘IWineASIOImpl’ has no member named ‘semaphore1’
asio.c:224: error: ‘IWineASIOImpl’ has no member named ‘stop_event’
asio.c:226: error: ‘IWineASIOImpl’ has no member named ‘semaphore1’
asio.c:227: error: ‘IWineASIOImpl’ has no member named ‘semaphore2’
asio.c: In function ‘__wrapped_IWineASIOImpl_init’:
asio.c:375: error: ‘jack_status_t’ undeclared (first use in this function)
asio.c:375: error: (Each undeclared identifier is reported only once
asio.c:375: error: for each function it appears in.)
asio.c:375: error: expected ‘;’ before ‘status’
asio.c:376: warning: ISO C90 forbids mixed declarations and code
asio.c:393: error: ‘IWineASIOImpl’ has no member named ‘toggle’
asio.c:394: error: ‘IWineASIOImpl’ has no member named ‘client_state’
asio.c:397: error: ‘IWineASIOImpl’ has no member named ‘terminate’
asio.c:400: error: ‘IWineASIOImpl’ has no member named ‘semaphore1’
asio.c:401: error: ‘IWineASIOImpl’ has no member named ‘semaphore2’
asio.c:403: error: ‘IWineASIOImpl’ has no member named ‘start_event’
asio.c:404: error: ‘IWineASIOImpl’ has no member named ‘stop_event’
asio.c:405: error: ‘IWineASIOImpl’ has no member named ‘thread’
asio.c:405: error: ‘IWineASIOImpl’ has no member named ‘thread_id’
asio.c:406: error: ‘IWineASIOImpl’ has no member named ‘thread’
asio.c:408: error: ‘IWineASIOImpl’ has no member named ‘start_event’
asio.c:409: error: ‘IWineASIOImpl’ has no member named ‘start_event’
asio.c:410: error: ‘IWineASIOImpl’ has no member named ‘start_event’
asio.c:429: error: ‘IWineASIOImpl’ has no member named ‘client’
asio.c:429: warning: implicit declaration of function ‘jack_client_open’
asio.c:429: error: ‘JackNullOption’ undeclared (first use in this function)
asio.c:429: error: ‘status’ undeclared (first use in this function)
asio.c:430: error: ‘IWineASIOImpl’ has no member named ‘client’
asio.c:436: warning: implicit declaration of function ‘jack_get_client_name’
asio.c:436: error: ‘IWineASIOImpl’ has no member named ‘client’
asio.c:436: warning: format ‘%s’ expects type ‘char *’, but argument 5 has type ‘int’
asio.c:438: error: ‘JackServerStarted’ undeclared (first use in this function)
asio.c:447: warning: implicit declaration of function ‘jack_set_process_callback’
asio.c:447: error: ‘IWineASIOImpl’ has no member named ‘client’
asio.c:447: error: ‘jack_process’ undeclared (first use in this function)
asio.c:449: warning: implicit declaration of function ‘jack_get_sample_rate’
asio.c:449: error: ‘IWineASIOImpl’ has no member named ‘client’
asio.c:450: warning: implicit declaration of function ‘jack_get_buffer_size’
asio.c:450: error: ‘IWineASIOImpl’ has no member named ‘client’
asio.c:461: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:462: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:470: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:471: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:472: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:473: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:474: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:479: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:480: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:488: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:489: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:490: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:491: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:492: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c: In function ‘__wrapped_IWineASIOImpl_start’:
asio.c:548: warning: implicit declaration of function ‘jack_activate’
asio.c:548: error: ‘IWineASIOImpl’ has no member named ‘client’
asio.c:555: warning: implicit declaration of function ‘jack_get_ports’
asio.c:555: error: ‘IWineASIOImpl’ has no member named ‘client’
asio.c:555: error: ‘JackPortIsPhysical’ undeclared (first use in this function)
asio.c:555: error: ‘JackPortIsOutput’ undeclared (first use in this function)
asio.c:555: warning: assignment makes pointer from integer without a cast
asio.c:561: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:564: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:564: warning: implicit declaration of function ‘jack_port_register’
asio.c:564: error: ‘IWineASIOImpl’ has no member named ‘client’
asio.c:565: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:565: error: ‘JACK_DEFAULT_AUDIO_TYPE’ undeclared (first use in this function)
asio.c:565: error: ‘JackPortIsInput’ undeclared (first use in this function)
asio.c:566: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:567: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:567: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:569: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:578: warning: implicit declaration of function ‘jack_port_name’
asio.c:578: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:578: warning: format ‘%s’ expects type ‘char *’, but argument 8 has type ‘int’
asio.c:582: warning: implicit declaration of function ‘jack_connect’
asio.c:582: error: ‘IWineASIOImpl’ has no member named ‘client’
asio.c:584: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:595: error: ‘IWineASIOImpl’ has no member named ‘client’
asio.c:595: warning: assignment makes pointer from integer without a cast
asio.c:601: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:604: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:604: error: ‘IWineASIOImpl’ has no member named ‘client’
asio.c:605: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:606: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:607: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:607: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:609: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:618: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:618: warning: format ‘%s’ expects type ‘char *’, but argument 7 has type ‘int’
asio.c:622: error: ‘IWineASIOImpl’ has no member named ‘client’
asio.c:623: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c: In function ‘__wrapped_IWineASIOImpl_stop’:
asio.c:652: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:657: warning: implicit declaration of function ‘jack_port_unregister’
asio.c:657: error: ‘IWineASIOImpl’ has no member named ‘client’
asio.c:657: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:658: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:658: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:663: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:668: error: ‘IWineASIOImpl’ has no member named ‘client’
asio.c:668: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:669: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:669: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:673: warning: implicit declaration of function ‘jack_deactivate’
asio.c:673: error: ‘IWineASIOImpl’ has no member named ‘client’
asio.c: In function ‘__wrapped_IWineASIOImpl_getChannelInfo’:
asio.c:843: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:844: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:848: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:849: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c: In function ‘__wrapped_IWineASIOImpl_disposeBuffers’:
asio.c:871: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:873: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:874: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:875: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:882: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:884: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:885: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:886: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c: In function ‘__wrapped_IWineASIOImpl_createBuffers’:
asio.c:903: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:905: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:927: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:928: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:930: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:931: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:932: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:934: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:938: error: ‘IWineASIOImpl’ has no member named ‘input’
asio.c:961: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:962: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:964: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:965: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:966: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:968: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c:972: error: ‘IWineASIOImpl’ has no member named ‘output’
asio.c: At top level:
asio.c:1119: error: expected ‘)’ before ‘nframes’
asio.c: In function ‘win32_callback’:
asio.c:1199: error: ‘IWineASIOImpl’ has no member named ‘start_event’
asio.c:1204: error: ‘IWineASIOImpl’ has no member named ‘semaphore1’
asio.c:1207: error: ‘IWineASIOImpl’ has no member named ‘terminate’
asio.c:1209: error: ‘IWineASIOImpl’ has no member named ‘stop_event’
asio.c:1227: error: ‘IWineASIOImpl’ has no member named ‘toggle’
asio.c:1231: error: ‘IWineASIOImpl’ has no member named ‘toggle’
asio.c:1235: error: ‘IWineASIOImpl’ has no member named ‘semaphore2’
make: *** [asio.o] Error 1
August 11th, 2008 at 10:27 am
i thought the jack dev library was there, but it was not.
got lots of errors as you can see. hope this helps somebody else.
complete linux noob. wouldnt know what an app would look like even if i could find it in this new kind of… ‘mess’ if you’ll pardon the expression.
okay, sorry for the spam. thanks for the page.
August 19th, 2008 at 9:17 pm
I can’t seem to get reaper to see the aiso driver. I have uninstalled wine and reaper and went through it again and got the same problem. The wineasio.dll.so is in my /urr/lib/wine folder. I can get audio playback with directsound and waveout but no asio. Any ideas ? I havent had any problems with audio so far..
August 20th, 2008 at 6:43 am
brainskins: Did you remember to register the driver by doing “regsvr32 wineasio.dll”
November 23rd, 2008 at 3:54 pm
When I start wine I get:
~$ winecfg
fixme:mixer:ALSA_MixerInit No master control found on M Audio Audiophile 24/96, disabling mixer
When I hit the sound tab, my system (ubuntu hardy) freezes and I’ve to reboot
December 25th, 2008 at 2:54 am
Does anyone know where can I download a precompiled wineasio.dll 0.7.4?
(The 0.7.3 .dll available here: http://www.sandgreen.dk/index.php?side=linux_wineasio/ is more than a year old)
December 31st, 2008 at 2:00 am
Dave,
Awesome work mate! Up and running with Brad first time through. Also you have allayed any Linux fear I had, it is not so scary!!!
A huge thanks, I am half way closer to my goal now!!!!!!
Peace,
Andy..
January 10th, 2009 at 5:20 pm
[...] Alcune altre Guide: http://www.davehayes.org/2007/04/27/howto-reaper-on-ubuntu-linux-with-wineasio [...]
January 11th, 2009 at 6:34 am
[...] Alcune altre Guide: Ed ecco come usare il potente DAW Reaper su Linux http://www.davehayes.org/2007/04/27/howto-reaper-on-ubuntu-linux-with-wineasio [...]
January 19th, 2009 at 12:20 pm
Hi,
Is this possible if I have Ubuntu 8.10 64Bit and 4GB RAM. All the procedure will work, yes?
MM
January 19th, 2009 at 2:20 pm
I haven’t tried doing this with a 64 bit machine yet, so I can’t say for sure. Other users have reported being able to make it work.
March 1st, 2009 at 2:26 am
I couldn’t read all of the posts above…
Damn there is a lot of interest
It’s a personal dream of mine…going back 8 years or so to Mandrake 7
I’m glad to report that aside from a few rare exceptions, everything runs in Reaper.
I’m going to list everything I’ve got installed and running:
But before I do that….gonna see if this thing really posts
March 1st, 2009 at 3:00 am
OK…that’s crazy
Too much works!!Everything works except (so far)
Waves plugins (that’s too bad)
I managed to get directX9 installed
And Reaper is reading most DX plugins
But not Waves (probably something to do
with the waveshell format…tried waveshell-vst but no dice in wine
Oh anything DFD (direct from disc) seems to be out
So Kontakt3 etc..cant load my 1GB harp samples
Arturia synths run….but the interface is wonkey.
Anyone have news on that?
Kjaerhus plugs wouldn’t run at all…interface probs too I suspect.
IKMultimedia, Nexus, Spectrasonics…all perfect.
Haven’t tried Reason yet, but rewire is doubtful.
Fruity is working fine
And EnergyXT2 (and 1)
Well…that’s about it so far
Linux DAW has arrived!!!
March 1st, 2009 at 3:05 am
OH I meant to say:
UbuntuStudio is the way to go
The Hardy version has a low-latency kernel right out of the box
Dozens of Linuuxaudio apps
Just add wineasio and dssi vsthost (I ‘alien-ed’ rpm’s for both)
and there you have it….perfection.
BTW….grab some of the dozens of skins for Reaper
>Some are VERY cool
March 8th, 2009 at 9:43 am
I am a new user of Ubuntu 8.04 HH and must install an older version of Reaper otherwise I will have to quit.Your command to obtain the required software does not work with me in the terminal. I installed everything with Synaptic. Steinberg are a bunch of crooks.
I made a 3rd party account , they sent me an e-mail and when I tried to log in they say it is wrong!!!
It is really a pity that ssuch a lot of ba
March 8th, 2009 at 9:48 am
I would like to use Ubuntu instead of Windows and am trying for nearly three weeks to have it performed rightly but it doesn’t. This is also due to a lot of bad information given on the forums. Your command to obtain several software does not work with me in the terminal!! With Steinberg I made a 3rd party account and received their e-mail for login. On login they state my e-mail address or password are wrong!!!You can understand that I am very , very disappointed.
March 8th, 2009 at 10:21 pm
Hi,
1. to Pinguin39, make sure you copy/paste the entire url from the Steinberg activation email. My email client didn’t include the last half in the hyperlink. It was very frustrating until I realized that.
2. So it seems to get this working well you need:
a. Ubuntu-Studio 8.04.1 32 bit (low latency kernel, unlike 8.10)
b. wine version 1.1.8 for Ubuntu 8.04.1 32 bit.
c. wineasio
d. Steinberg ASIO SDK for the asio.h file.
-Is there anything I missed?
Happy hacking!
March 11th, 2009 at 1:24 am
is wine 1.1.8 an older version than the current? do i need backports enabled in my software sources?
unfortunately, i installed the 64 bit version of 8.04 studio. so is the only way for me to run reaper in wine installing 32-bit wine? is that how the 64 bit users got it to work?
-thanks
March 11th, 2009 at 1:28 am
mike: I don’t have any experience running Reaper via wine on a 64 bit machine. From what I understand, you do have to install the 32 bit version of wine, but it does work that way.
March 11th, 2009 at 2:10 am
For anyone wondering about this too, I’ve actually discovered an install script for Wine ASIO, hopefully for 64 too, I didn’t bother to check. Unfortunately, even with a readymade installer, I can’t get it to work, the noob that I am. It’s here:
http://stashbox.org/v/350755/LinReaper0.82.run
Here’s the page of the Cockos Forum I got it from:
http://forum.cockos.com/showthread.php?t=26690&page=5
March 11th, 2009 at 3:02 am
I think I just figured it out. Took me long enough.
wget http://www.sandgreen.dk/xt2/files/wineasio_0.7.3/wineasio.dll.so
mv /usr/lib32/wine
regsvr32 wineasio
NOTE: it’s “lib32″ not “lib,” I’m assuming since I’m using x64 ubuntu studio
I was confused by the fact that it kept telling me that it couldn’t find the folder and mistakenly thought I had to put it in /usr/share/wine.
I wonder if I’d have figured it out if I’d waited until later this morning to figure it out..lol. i think i underestimate the effects of sleep deprivation.
May 23rd, 2009 at 4:25 am
Thank you for your brilliant guide, I’ve got it running on the Dell Mini 9 using Ubuntu 9.04 Netbook Remix with the Ubuntu Studio additions – The latency (or lack of it) is excellent and I’m happily running Audiomulch with the ASIO drivers now. Sweet.
May 29th, 2009 at 9:08 pm
Hey everyone,
I’m a linux newbie and have been trying to figure this out for days. Every time I run the [make] command i get an error, summing it up to be “make: *** [asio.o] Error 1″
) but I REALLY need this to work. I am running 8.04 on a 64bit AMD
I am still trying to figure out why it isn’t working, and my dad wanted to me figure it out on my own (honestly i don’t know if he can do it either
just in case, i’ll post the rest of the error:
gcc -c -I. -I/usr/include -I/usr/include -I/usr/include/wine -I/usr/include/wine/windows -m32 -g -O2 -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -o asio.o asio.c
In file included from /usr/include/features.h:354,
from /usr/include/fcntl.h:27,
from port.h:30,
from asio.c:22:
/usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory
asio.c:32:33: error: wine/windows/windef.h: No such file or directory
asio.c:33:34: error: wine/windows/winbase.h: No such file or directory
asio.c:34:34: error: wine/windows/objbase.h: No such file or directory
asio.c:35:35: error: wine/windows/mmsystem.h: No such file or directory
asio.c:41:26: error: wine/library.h: No such file or directory
asio.c:42:24: error: wine/debug.h: No such file or directory
asio.c:44:23: error: jack/jack.h: No such file or directory
asio.c:49: warning: data definition has no type or storage class
asio.c:49: warning: type defaults to ‘int’ in declaration of ‘WINE_DEFAULT_DEBUG_CHANNEL’
asio.c:49: warning: parameter names (without types) in function declaration
asio.c:52: error: expected ‘)’ before ‘nframes’
asio.c:55: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘CALLBACK’
asio.c:58: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘const’
asio.c:98: warning: return type defaults to ‘int’
asio.c: In function ‘DECLARE_INTERFACE_’:
asio.c:99: warning: implicit declaration of function ‘STDMETHOD_’
asio.c:99: error: ‘HRESULT’ undeclared (first use in this function)
asio.c:99: error: (Each undeclared identifier is reported only once
asio.c:99: error: for each function it appears in.)
asio.c:99: error: ‘QueryInterface’ undeclared (first use in this function)
asio.c:99: error: ‘THIS_’ undeclared (first use in this function)
asio.c:99: error: expected ‘)’ before ‘REFIID’
asio.c:99: error: called object ‘STDMETHOD_(, )’ is not a function
asio.c:99: error: expected ‘;’ before ‘PURE’
asio.c:100: error: ‘ULONG’ undeclared (first use in this function)
asio.c:100: error: ‘AddRef’ undeclared (first use in this function)
asio.c:100: error: ‘THIS’ undeclared (first use in this function)
asio.c:100: error: called object ‘STDMETHOD_(, )’ is not a function
asio.c:100: error: expected ‘;’ before ‘PURE’
asio.c:101: error: ‘Release’ undeclared (first use in this function)
asio.c:101: error: called object ‘STDMETHOD_(, )’ is not a function
asio.c:101: error: expected ‘;’ before ‘PURE’
asio.c:102: error: expected expression before ‘ASIOBool’
asio.c:102: error: expected ‘)’ before ‘void’
asio.c:102: error: called object ‘STDMETHOD_()’ is not a function
asio.c:102: error: expected ‘;’ before ‘PURE’
asio.c:103: error: expected expression before ‘void’
asio.c:103: error: expected ‘)’ before ‘char’
asio.c:103: error: called object ‘STDMETHOD_()’ is not a function
asio.c:103: error: expected ‘;’ before ‘PURE’
asio.c:104: error: expected expression before ‘long’
asio.c:104: error: called object ‘STDMETHOD_()’ is not a function
asio.c:104: error: expected ‘;’ before ‘PURE’
asio.c:105: error: expected expression before ‘void’
asio.c:105: error: expected ‘)’ before ‘char’
asio.c:105: error: called object ‘STDMETHOD_()’ is not a function
asio.c:105: error: expected ‘;’ before ‘PURE’
asio.c:106: error: expected expression before ‘ASIOError’
asio.c:106: error: called object ‘STDMETHOD_()’ is not a function
asio.c:106: error: expected ‘;’ before ‘PURE’
asio.c:107: error: expected expression before ‘ASIOError’
asio.c:107: error: called object ‘STDMETHOD_()’ is not a function
asio.c:107: error: expected ‘;’ before ‘PURE’
asio.c:108: error: expected expression before ‘ASIOError’
asio.c:108: error: expected ‘)’ before ‘long’
asio.c:108: error: called object ‘STDMETHOD_()’ is not a function
asio.c:108: error: expected ‘;’ before ‘PURE’
asio.c:109: error: expected expression before ‘ASIOError’
asio.c:109: error: expected ‘)’ before ‘long’
asio.c:109: error: called object ‘STDMETHOD_()’ is not a function
asio.c:109: error: expected ‘;’ before ‘PURE’
asio.c:110: error: expected expression before ‘ASIOError’
asio.c:110: error: expected ‘)’ before ‘long’
asio.c:110: error: called object ‘STDMETHOD_()’ is not a function
asio.c:110: error: expected ‘;’ before ‘PURE’
asio.c:111: error: expected expression before ‘ASIOError’
asio.c:111: error: expected ‘)’ before ‘ASIOSampleRate’
asio.c:111: error: called object ‘STDMETHOD_()’ is not a function
asio.c:111: error: expected ‘;’ before ‘PURE’
asio.c:112: error: expected expression before ‘ASIOError’
asio.c:112: error: expected ‘)’ before ‘ASIOSampleRate’
asio.c:112: error: called object ‘STDMETHOD_()’ is not a function
asio.c:112: error: expected ‘;’ before ‘PURE’
asio.c:113: error: expected expression before ‘ASIOError’
asio.c:113: error: expected ‘)’ before ‘ASIOSampleRate’
asio.c:113: error: called object ‘STDMETHOD_()’ is not a function
asio.c:113: error: expected ‘;’ before ‘PURE’
asio.c:114: error: expected expression before ‘ASIOError’
asio.c:114: error: expected ‘)’ before ‘ASIOClockSource’
asio.c:114: error: called object ‘STDMETHOD_()’ is not a function
asio.c:114: error: expected ‘;’ before ‘PURE’
asio.c:115: error: expected expression before ‘ASIOError’
asio.c:115: error: expected ‘)’ before ‘long’
asio.c:115: error: called object ‘STDMETHOD_()’ is not a function
asio.c:115: error: expected ‘;’ before ‘PURE’
asio.c:116: error: expected expression before ‘ASIOError’
asio.c:116: error: expected ‘)’ before ‘ASIOSamples’
asio.c:116: error: called object ‘STDMETHOD_()’ is not a function
asio.c:116: error: expected ‘;’ before ‘PURE’
asio.c:117: error: expected expression before ‘ASIOError’
asio.c:117: error: expected ‘)’ before ‘ASIOChannelInfo’
asio.c:117: error: called object ‘STDMETHOD_()’ is not a function
asio.c:117: error: expected ‘;’ before ‘PURE’
asio.c:118: error: expected expression before ‘ASIOError’
asio.c:118: error: expected ‘)’ before ‘ASIOBufferInfo’
asio.c:118: error: called object ‘STDMETHOD_()’ is not a function
asio.c:118: error: expected ‘;’ before ‘PURE’
asio.c:119: error: expected expression before ‘ASIOError’
asio.c:119: error: called object ‘STDMETHOD_()’ is not a function
asio.c:119: error: expected ‘;’ before ‘PURE’
asio.c:120: error: expected expression before ‘ASIOError’
asio.c:120: error: called object ‘STDMETHOD_()’ is not a function
asio.c:120: error: expected ‘;’ before ‘PURE’
asio.c:121: error: expected expression before ‘ASIOError’
asio.c:121: error: expected ‘)’ before ‘long’
asio.c:121: error: called object ‘STDMETHOD_()’ is not a function
asio.c:121: error: expected ‘;’ before ‘PURE’
asio.c:122: error: expected expression before ‘ASIOError’
asio.c:122: error: called object ‘STDMETHOD_()’ is not a function
asio.c:122: error: expected ‘;’ before ‘PURE’
asio.c: At top level:
asio.c:139: error: expected specifier-qualifier-list before ‘jack_port_t’
asio.c:145: error: expected ‘:’, ‘,’, ‘;’, ‘}’ or ‘__attribute__’ before ‘*’ token
asio.c:200: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘WINAPI’
asio.c:210: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘WINAPI’
asio.c:235: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘WINAPI’
asio.c: In function ‘set_clientname’:
asio.c:278: error: ‘IWineASIOImpl’ has no member named ‘client_name’
asio.c: In function ‘read_config’:
asio.c:289: warning: implicit declaration of function ‘TRACE’
asio.c:308: warning: implicit declaration of function ‘isspace’
asio.c:315: error: ‘IWineASIOImpl’ has no member named ‘client_name’
asio.c: In function ‘get_numChannels’:
asio.c:338: error: ‘IWineASIOImpl’ has no member named ‘client_name’
asio.c: In function ‘set_portname’:
asio.c:355: error: ‘IWineASIOImpl’ has no member named ‘client_name’
asio.c: At top level:
asio.c:371: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_init’
asio.c:371: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_init’
asio.c:498: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_getDriverName’
asio.c:498: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_getDriverName’
asio.c:504: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_getDriverVersion’
asio.c:504: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_getDriverVersion’
asio.c:510: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_getErrorMessage’
asio.c:510: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_getErrorMessage’
asio.c: In function ‘get_targetname’:
asio.c:521: error: ‘IWineASIOImpl’ has no member named ‘client_name’
asio.c: At top level:
asio.c:533: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_start’
asio.c:533: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_start’
asio.c:643: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_stop’
asio.c:643: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_stop’
asio.c:682: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_getChannels’
asio.c:682: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_getChannels’
asio.c:698: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_getLatencies’
asio.c:698: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_getLatencies’
asio.c:712: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_getBufferSize’
asio.c:712: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_getBufferSize’
asio.c:734: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_canSampleRate’
asio.c:734: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_canSampleRate’
asio.c:745: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_getSampleRate’
asio.c:745: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_getSampleRate’
asio.c:758: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_setSampleRate’
asio.c:758: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_setSampleRate’
asio.c:769: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_getClockSources’
asio.c:769: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_getClockSources’
asio.c:788: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_setClockSource’
asio.c:788: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_setClockSource’
asio.c:803: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_getSamplePosition’
asio.c:803: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_getSamplePosition’
asio.c:825: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_getChannelInfo’
asio.c:825: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_getChannelInfo’
asio.c:860: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_disposeBuffers’
asio.c:860: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_disposeBuffers’
asio.c:894: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_createBuffers’
asio.c:894: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_createBuffers’
asio.c:1025: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_controlPanel’
asio.c:1025: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_controlPanel’
asio.c:1032: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_future’
asio.c:1032: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_future’
asio.c:1058: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘IWineASIOImpl_outputReady’
asio.c:1058: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wrapped_IWineASIOImpl_outputReady’
asio.c:1065: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘WineASIO_Vtbl’
asio.c:1093: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘asioCreateInstance’
asio.c: In function ‘getNanoSeconds’:
asio.c:1114: warning: implicit declaration of function ‘timeGetTime’
asio.c: At top level:
asio.c:1119: error: expected ‘)’ before ‘nframes’
asio.c:1189: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘CALLBACK’
make: *** [asio.o] Error 1
September 30th, 2009 at 1:06 pm
Thank you so much, Dave. I’m currently listening to a 35-track project on Jaunty + Reaper 3.11 + M-audio Delta 66 soundcard. Can’t say how cool is it.
BTW I found a quicker way to install WineASIO:
http://www.sandgreen.dk/xt2/files/wineasioinstaller-0.7.4-2.tar.gz
Rock on
Daniel
October 6th, 2009 at 5:07 pm
Thank you SO MUCH for writing this. Ive been bashing my head against a wall trying to get something on my computer with low enough latency to play guitar through, and this tutorial helped me achieve just that. rock on my friend
October 26th, 2009 at 4:23 am
Dear mr Hayes,
your how to was very clear, I used Linreaper for a while, but that stopped working correctly. Your how to made it possible to do it manually, step by step. Thanks!
I have one question though. It seems impossible to run VST instruments, as I keep trying to point Reaper to their spot, only one or two shop up. How can I install VST instruments so they are seen by Reaper? All instruments I installed, have been working perfectly for me on previous installs of Hardy..
Thanks for your time,
Alfons
October 26th, 2009 at 8:03 am
Alfons, the easiest thing would be to just drop the .dll files into REAPER’s plugins folder (it’s ~/.wine/drive_c/Program Files/REAPER/Plugins/FX on my system). If it’s a plugin that requires activation or a serial number or something like that, you might have to actually run the installer in wine under Ubuntu.
November 5th, 2009 at 3:31 am
folks there’s some misconception here, no need to put jack on in winecfg, you can use alsa (For midi) and use wineasio driver inside the host, wineasio will use jack still, but wine will tell the application that there’s also midi inputs and outputs.