Package Details: reaper-bin 6.58-1

Git Clone URL: (read-only, click to copy)
Package Base: reaper-bin
Description: A complete digital audio production application for computers, offering a full multitrack audio and MIDI recording, editing, processing, mixing and mastering toolset
Upstream URL:
Licenses: custom
Provides: lv2-host, reaper, vst-host, vst3-host
Submitter: david0
Maintainer: Nocifer
Last Packager: Nocifer
Votes: 100
Popularity: 2.35
First Submitted: 2018-08-10 15:40 (UTC)
Last Updated: 2022-05-19 12:19 (UTC)

Required by (20)

Sources (4)

Latest Comments

Nocifer commented on 2022-04-22 16:15 (UTC)

Heh, alright, it happens to the best of us :)

phunni commented on 2022-04-22 15:03 (UTC)

NVM - it was all down to a rogue .desktop file launching a rogue (and old) installation. If I run the actual latest install it includes lv2 support. Thanks for the help anyway and sorry to be a bother.

Nocifer commented on 2022-04-22 13:52 (UTC)

@olivierlm you're right, that's probably it. Installing an LV2 plugin system-wide via the package manager (as suggested by @phunni having stuff in /usr/lv2) should have pulled in the lv2 dependency transparently, but that still wouldn't solve the case where one only uses LV2 plugins installed manually in ~/.lv2, so we still need lv2 as a direct dependency of Reaper.

@phunni, please install lv2 and check to make sure that this is indeed the case, and if so I'll release a new update later in the day.

olivierlm commented on 2022-04-22 13:03 (UTC)

Do you have the lv2 package installed ? Looks like reaper is using some its files at runtime

phunni commented on 2022-04-22 12:51 (UTC)

It was built using this package on an x64 system.

I've checked and I have plugins in /usr/lib/lv2 and in ~/.lv2

Am baffled as to why there's no reference to lv2 in reaper.

Nocifer commented on 2022-04-22 08:22 (UTC)

This is how it looks on my system. If your Reaper lacks the LV2 section, the only reason I can think of is that you're using a build that doesn't support LV2 (e.g. x86 or arm, I think it's only supported in x64).

phunni commented on 2022-04-22 07:34 (UTC)

There is no reference to lv2 anywhere in the preferences - including where you specified.

Nocifer commented on 2022-04-22 07:06 (UTC)

What do you mean it doesn't have support? You mean the plug-ins won't load/work properly or that Reaper doesn't see them at all? If the latter, maybe your paths are not configured correctly in Preferences -> Plug-ins -> LV2.

phunni commented on 2022-04-21 21:11 (UTC)

For reasons that aren't clear my installed version (installed via this package) doesn't seem to have any support for lv2 plugins.

Did I miss a step? Or is there something else I need to do. All help appreciated.

Nocifer commented on 2022-03-12 15:54 (UTC)

@kumax I don't know either and it's been getting on my nerves since forever (I'm not even on Gnome). It's being created during runtime, not during the setup, so I'm guessing it's something that must be fixed by the Reaper devs.

kumax commented on 2022-03-12 13:37 (UTC)

Why is there $HOME/.gnome created every time I upgrade it? Will it be fixed?

xenobrain commented on 2021-09-23 23:31 (UTC) (edited on 2021-09-23 23:33 (UTC) by xenobrain)


provides=('lv2-host' 'vst-host')

would be helpful

Nocifer commented on 2021-07-25 19:01 (UTC)

@gameslayer You're absolutely right; I completely forgot the fact that the PKGBUILD's $arch variable is not a single value but rather an array, and I never encountered this very obvious issue myself because my system is x86_64 which just so happens to be the first value in that array. Gah. Should hopefully be fixed with this new release.

Also, sorry for the long time it took me to respond but I'm on vacation.

gameslayer commented on 2021-07-19 15:13 (UTC) (edited on 2021-07-19 15:32 (UTC) by gameslayer)

pkgbuild file needs to be fixed, seems to pick the wrong arch when looking for the install script.

Cloning reaper-bin build files...
Checking reaper-bin dependencies...
Resolving dependencies...
Checking inter-conflicts...
Download of aribb24 (1.0.3-3) started
Download of aribb24 (1.0.3-3) finished
Checking keyring...
Checking integrity...
Loading packages files...
Checking file conflicts...
Checking available disk space...
Installing aribb24 (1.0.3-3)...

Building reaper-bin...
==> Making package: reaper-bin 6.32-1 (Tue 20 Jul 2021 01:10:41)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading reaper632_linux_aarch64.tar.xz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
100   345  100   345    0     0    149      0  0:00:02  0:00:02 --:--:--   149

  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0
100   320  100   320    0     0     90      0  0:00:03  0:00:03 --:--:--   346

  0     0    0     0    0     0      0      0 --:--:--  0:00:03 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:04 --:--:--     0
  6 9791k    6  659k    0     0   117k      0  0:01:23  0:00:05  0:01:18  330k
 50 9791k   50 4927k    0     0   747k      0  0:00:13  0:00:06  0:00:07 1644k
 86 9791k   86 8512k    0     0  1121k      0  0:00:08  0:00:07  0:00:01 2130k
100 9791k  100 9791k    0     0  1247k      0  0:00:07  0:00:07 --:--:-- 2304k
==> Validating source_aarch64 files with sha256sums...
    reaper632_linux_aarch64.tar.xz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting reaper632_linux_aarch64.tar.xz with bsdtar
==> Entering fakeroot environment...
==> Starting package()...
sh: /var/tmp/pamac-build-corey/reaper-bin/src/reaper_linux_x86_64/ No such file or directory
==> ERROR: A failure occurred in package().

Nocifer commented on 2021-06-16 08:07 (UTC)

@obionar you're absolutely right, and I see now that there's also support for i686 and armv7l. I'll add all three in the 6.30 update.

obionar commented on 2021-06-16 05:20 (UTC)

Application have ARM support. Runnning on my Pinebook Pro ('aarch64')with some PKGBUILD changes:

arch=('aarch64' 'x86_64')

"linux_x86_64.tar.xz" replace with "_linux${arch}.tar.xz" "/reaper_linux_x86_64/" replace with "/reaper_linux_${arch}/"

olivierlm commented on 2021-03-23 09:26 (UTC) (edited on 2021-03-23 09:26 (UTC) by olivierlm)

It might need extra/aribb24 at some point (starts fine without anyway):

$ reaper
swell: dlopen() failed: cannot open shared object file: No such file or directory

Nocifer commented on 2020-12-08 09:39 (UTC)

@david0 Nicely done, thanks. This "" place is a pure goldmine for our purposes :)

david0 commented on 2020-12-07 12:53 (UTC)

Hi Nocifer, nice to see that you take over this package :-)

I was scraping the reaper webpage using this script: from cron

madskjeldgaard commented on 2020-12-07 11:38 (UTC)

@Nocifer : Thanks for doing this :)

Nocifer commented on 2020-12-07 10:55 (UTC)

Seeing as no one has rushed to jump the queue and adopt this package, I guess I will do so for the time being. But until I find a way to get some kind of automatic notification whenever Reaper releases a new version (I don't use it nearly enough these days to reliably use its built-in update manager - but at least I do still use Arch :P), please be kind enough to notify me here for new versions if a day or three have passed and I still haven't released an update.

Also, if anyone feels they're up to the task of adopting this package and actually doing a good job with the updates, please tell me and I'll happily give you the door keys.

@david0 If and when you see this: do you perhaps know of any communication channel (e.g. a newsletter, a third party site with an RSS feed...) that announces new Reaper versions the moment they come out, without requiring you to check for them yourself?

david0 commented on 2020-12-05 18:57 (UTC)

Hi everyone, sorry for the waiting, please find the newest version now. Luckily I did not get the virus up to now. I hope everyone of you is doing fine.

I'm atm not using arch anymore, so I will disown the reaper package to not hold you back any longer.

Take care, David

madskjeldgaard commented on 2020-12-05 18:04 (UTC)

I agree with @funkmuscle that we should have patience in this time. It's impossible to know if people are okay right now.

I made this PKGBUILD for myself to be able to install 6.18 if anyone wants it

funkmuscle commented on 2020-12-05 17:32 (UTC)

@putte64 Let's hope he's ok as I've flagged this since 6.16 and had to edit the PKGBUILD to get as far as 6.17 but getting errors now for 6.18. David0 is not the only one not updating or responding so I'm hoping these guys are ok and not affected by the virus.

putte64 commented on 2020-12-03 09:04 (UTC)

Hi David0.

Please kindly spare a few minutes and update Reaper to 6.18.

Thank you for your time.

teetest commented on 2020-10-26 01:41 (UTC)

@torturelini It seems you got issues from JACK. Can you use ALSA instead JACK in REAPER? Or you post it to Cockos Linux forum. There will be more quickly response.

ici commented on 2020-10-21 14:20 (UTC)

Hi david0,

Can you update Reaper to 6.15 please? Thank you <3

torturelini commented on 2020-10-06 15:52 (UTC)

Hi madskjeldgaard,

thank you for the fast reply! I tried that, my terminal output is:

jack: created client jack: setting TIME_CRITICAL = 93 jack: activated client Killed

Thank you!!

madskjeldgaard commented on 2020-10-06 15:47 (UTC)

Hi torturelini. Try running reaper from a terminal (by executing reaper) and see if it outputs any errors. Often you can find bugs in your own setup like this, maybe there's something there to lead you closer to the problem.

torturelini commented on 2020-10-06 15:42 (UTC)

Hi, running Reaper 6.14 on Manjaro with GNOME.

A few moments after starting Reaper the GUI just freezes and gets unresponsive, sound works as well. In the earlier version, everything worked just fine.

Does anyone have a suggestion?


madskjeldgaard commented on 2020-08-15 19:16 (UTC)

Hi! Could you extend this package to work with arch arm as well? reaper has an arm version as well... Or should it be a seperate package? Thanks!

SpotlightKid commented on 2019-12-03 23:33 (UTC)

I think you meant to use version number 6.0 instead of 5.0, as you did :)

SpotlightKid commented on 2019-09-23 15:45 (UTC)

@david0: the package version is broken again.

JohnnyDeacon commented on 2019-08-25 23:53 (UTC)

Could somebody update the package, please?

SpotlightKid commented on 2019-07-30 14:24 (UTC)

Something seems to have gone wrong with the package version number, the minor version part is now missing.

Sangeppato commented on 2019-01-21 22:58 (UTC)

Currently on Gnome if you pin Reaper to the Dock and launch it, it will create a second icon for the running instance. Adding the line "StartupWMClass=REAPER" to the .desktop file solves the problem

yan12125 commented on 2018-09-11 06:25 (UTC)

Done package movement - I merge reaper into reaper-bin instead of deleting reaper to keep comments and votes.

teetest commented on 2018-08-16 12:30 (UTC)

I agree with @jhernberg.

jhernberg commented on 2018-08-16 10:39 (UTC)

I suppose that technically it isn't really needed to rename the package, still in the past it's been mentioned by Justin that he doesn't have anything against open source. So I'd say that there is a small possibility to see it open sourced some day in the future.

Reading this: seems to suggest that reaper-bin would be the right choice.

IMO adding the -bin suffix also indicates to the user that this isn't a package built from source, but rather packages something available in binary form.

/opt is the choice of upstream so I think in order to facilitate support it's reasonable to use it.

SWS should really be installed into ~/.config/REAPER/UserPlugins/ even if it might work installed elsewhere. Also note that SWS isn't really maintained by anyone anymore, so there won't be regular or many updates at all to it.

It is available from landoleet as an already compiled tarball for those that can't build it themselves. I suppose ideally it should be available for download from we'll see if that can be fixed someday, but without anyone really in charge of sws at the moment..:S

Is there some specific problem with having the package renamed to reaper-bin? IMO better to do so now, than maybe having to face problems in the future.

donvla commented on 2018-08-15 10:15 (UTC) (edited on 2018-08-15 10:24 (UTC) by donvla)

First why is it necessary to rename the package. As I understood the discussion, there should be no other option to install reaper than through the binary package. So reaper-bin is reaper. There is no other source package or similar.

Second, I'd recommend installing reaper into /usr/lib. I see no need in using /opt. It also breaks compatibility with plugins like sws.

I see this package as a drop-in replacement for the old reaper package which did not comply with the landoleet guidelines.

jhernberg commented on 2018-08-10 16:36 (UTC)



david0 commented on 2018-08-10 15:42 (UTC)


It will be deleted soon.

jhernberg commented on 2018-08-08 12:53 (UTC)

@david0: Hi, I'm writing this as someone complained on the reaper forum about this package. Tried to email you, but haven't seen any response..

FWIW, I just discussed this with the boss (Justin), he had this to say: "should definitely download the main releases! the landoleet builds are not supposed to be linked to from anywhere (it says that on landoleet!)" and "also yeah it should use the official swell binaries".

My personal thoughts:

  1. Create a new package called reaper-bin following the AUR guidelines to indicate that it's a package that installs something binary instead of building a package from source.

  2. Do not build SWELL, AFAIK the one shipped in the tarball is working perfectly fine on Archlinux.

  3. Do use the desktop support in the tarball as that is more recent and has better functionality than the one I wrote ages ago which you are still using.

  4. Please use the script included in the tarball to install reaper, it was made for that. I'd recommend to run "sh --install "/opt" --quiet --integrate-desktop", which will install reaper into /opt/REAPER and add the needed desktop support.

  5. Then you only have to create the symlink /usr/bin/reaper -> /opt/REAPER/reaper and create one for the license.

Any user wanting to use the LoL version can download it manually as Windows & OS/X users do.

Also if you don't change this package there is a high possibility that Cockos will block downloads from LoL for scripts like this, that would IMO be a very sad occurrence..

Thanks in advance for your understanding :)

aggraef commented on 2018-08-04 11:41 (UTC)

@cogwerkz, you're right. Well, at least it's on the official download page now. :)

@david0, the sha256 changed once again, it's 1f7daf933f5d246239f803a113cf0407357df7597b00cc135d8e05c845c0e599 now, so I guess that a new version is out already. Looks like the versions on Landoleet and in the official Reaper downloads are the same right now.

I guess I'm inclined to agree with pha-qu that the official Reaper downloads are the way to go. However, it's debatable whether putting a link in a shell script for convenience would count as a "link". After all, the PKGBUILD doesn't do anything that a user couldn't do manually. And the PKGBUILD certainly doesn't redistribute the tarballs, so we should be good there IMHO.

The fact that the tarballs keep changing all the time is really unfortunate. Well, I guess the only way to deal with this (apart from setting up a script which does automatic monitoring and updating the PKGBUILD every time the sha changes, which will not really be that secure either) is to flag the package as out of date as soon as anyone encounters this. Or maybe just accept the fact that the tarball keep changing all the time and use SKIP on it, like with a git repo.

pha-qu commented on 2018-08-03 20:53 (UTC)

I have a question, the PKGBUILD file still points to landoleet which carries the bellow message: 1. DO NOT REDISTRIBUTE ANYTHING FROM THIS WEBSITE 2. USE VERSIONS FROM HERE WITH CAUTION AND AT YOUR OWN RISK 3. DO NOT LINK TO THIS WEB SITE OR ANYTHING ON IT FROM ANYWHERE 4. PLEASE DISCUSS ONLY IN THE PRE-RELEASE FORUM The reaper website bundles the latest files for x86_64 distribution at this url: Shouldn't the PKGBUILD respect the above request from landoleet, I notice the tar from is near identical to the one from landoleet beside some of the problems with the frequency of the files being changed rendering sha-pgp checks invalid if you don'y update as soon as possible? Comments welcome

cogwerkz commented on 2018-08-01 15:09 (UTC)

@aggraef The version itself is a release candidate, but the whole linux port is considered experimental, so it's probably fitting to still have that warning there. It's even noted by cockos on the reaper download page:

"Note: Linux builds are experimental and unsupported. Please read the included readme.txt for more information."

aggraef commented on 2018-08-01 13:31 (UTC)

Also, I think that the warning about this being an unsupported experimental version can (and should be) removed now; AFAICT this is an official release candidate.

aggraef commented on 2018-08-01 13:28 (UTC)

@david0, I think that your intent here was to create both reaper and reaper5 links pointing to the reaper binary in /usr/lib/REAPER? But the second ln command is wrong. It should read:

ln -s /usr/lib/REAPER/reaper "${pkgdir}/usr/bin/reaper5"

Also, to make the existing desktop files work you need, in addition:

ln -s /usr/lib/REAPER/reaper "${pkgdir}/usr/lib/REAPER/reaper5"

Obviously, this all gets a bit messy, but it works (see

Anyway, I'd suggest to follow @jhernberg's advice and see whether the --integrate-desktop option does the job, as far as the desktop files are concerned. Whether the application ends up under /usr/lib or /opt is a matter of taste; /opt sounds reasonable to me. Concerning the proper location for the symbolic link to the binary, however, I'd advise against a symbolic link under /usr/local/bin, it should go into /usr/bin -- /usr/local should be reserved for stuff the user installs locally and not be touched by packages IMHO.

jhernberg commented on 2018-08-01 11:10 (UTC)

Note that since a while reaper has it's own installation script taking care of most things. Something like "sh --install "/opt" --quiet --integrate-desktop --usr-local-bin-symlink" ought to take care of most everything.

We decided that installing reaper into /opt/REAPER and creating a symlink in /usr/local/bin was the best way to go. The installation script also takes care of the desktop/mime support and actually does it better than then old files I wrote which are used by this script.

Also note that the executable has recently been renamed from reaper5 to reaper.

I also question the need to separately build AFAIK the one included in the reaper tarball works perfectly fine on Archlinux.

Finally shouldn't this script really be caller reaper-bin?

capoeira commented on 2018-08-01 10:26 (UTC)

wait. isn't the problem of the PKGBUILD that it tries to create /usr/bin/reaper twice? have you tried removing only the second ln line @pha-qu?

what is the sense of the second ln line anyways? /usr/lib/REAPER/reaper5 doesn't exist

capoeira commented on 2018-08-01 10:23 (UTC)

@cogwerkz that's not the case here. I installed excluding those two ln lines

cogwerkz commented on 2018-08-01 10:18 (UTC)

@capoeira it works fine from the terminal. You just have to type reaper5, not reaper. :)

capoeira commented on 2018-08-01 10:11 (UTC)

actualy the binary should go to /usr/bin/, no? that's why you can't even run it with a simple "reaper" from terminal

pha-qu commented on 2018-08-01 00:33 (UTC) (edited on 2018-08-01 00:36 (UTC) by pha-qu)

Anyone scratching there heads, after you get 'ln: failed to create symbolic link' error pull up a terminal, and: cd /tmp/pamac-build-yourusername (or where ever pamac does the magic) sudo nano PKGBUILD CTRK-w (then type 'ln' and hit enter) add '#' symbol to the start of the two lines that start ln CTRL-o CTRL-x makepkg -c sudo pacman -U reaper-5.94rc1-1-x86_64.pkg.tar.xz Y<agree> sudo nano /usr/share/applications/cockos-reaper.desktop (or wherever your desktop config is stored) remove the 5 from this line: Exec=/usr/lib/REAPER/reaper5 %F to: Exec=/usr/lib/REAPER/reaper %F CTRL-o CTRL-x</agree>

Now test your menu entry item, and reaper should be good to go ;)

pha-qu commented on 2018-08-01 00:19 (UTC)

@david0 can you please desist from pushing broken updates that don't have a hope in Hades of updating. The PKGBUILD is still not working: ln: failed to create symbolic link '/tmp/pamac-build-pha-qu/reaper/pkg/reaper/usr/bin/reaper': File exists ==> ERROR: A failure occurred in package(). Experimental or not, the install script

echo "PLEASE NOTE -- REAPER for Linux is an unsupported experimental version." is not an excuse for not testing an update before pushing it out.

The script, I repeat, appears or is creating the required symlinks automagically. Removing lines ln ... from PKGBUILD results in a successful update

... end of transmission

capoeira commented on 2018-07-31 16:53 (UTC)

I see. I misunderstood his message. thought he was the owner. NOW: the version just changed to RC. I will mark the package

funkmuscle commented on 2018-07-31 15:52 (UTC)

hey @cap, pha-qu method worked

capoeira commented on 2018-07-31 13:33 (UTC)

I get the same error as Funk

pha-qu commented on 2018-07-30 20:02 (UTC) (edited on 2018-07-30 20:19 (UTC) by pha-qu)

Current pkgbuild fails. ln: failed to create symbolic link '/tmp/pamac-build-spongebob/reaper/pkg/reaper/usr/bin/reaper': File exists

I think those two ln's in the PKGBUILD are causing this, I think the reaper install script is already creating those symlinks quietly.

I've removed those lines from the PKGBUILD, done an offline build, and am back in business

PS .desktop entry for me still (WTF) points to 'reaper5' executable in lib folder, so you may need to change that to 'reaper', an upstream issue.

funkmuscle commented on 2018-07-30 17:51 (UTC)

build fails:

PLEASE NOTE -- REAPER for Linux is an unsupported experimental version.

REAPER installer -- install to /tmp/trizen-harv/reaper/pkg/reaper/usr/lib

Copying files... done Writing uninstall script to /tmp/trizen-harv/reaper/pkg/reaper/usr/lib/REAPER/

*** Installation complete ln: failed to create symbolic link '/tmp/trizen-harv/reaper/pkg/reaper/usr/bin/reaper': File exists ==> ERROR: A failure occurred in package(). Aborting... :: Unable to build reaper - makepkg exited with code: 4

UlrichH commented on 2018-07-30 17:25 (UTC)

It won't generate a package, the new ln commands seem wrong

spider-mario commented on 2018-07-28 20:44 (UTC)

The executable is now called reaper instead of reaper5. Would it be possible to fix the /usr/bin/ symlink?

dtris commented on 2018-07-22 17:00 (UTC)

I tried running u-he's native Linux build of Zebra2 inside REAPER and it fails to load.

According to this thread, the solution to this is to make libSwell with PRELOAD_GDK defined (e.g. by running make PRELOAD_GDK=1. I tested that out and it seems to work and, AFAICT, it doesn't affect anything else.

Would you consider adding that to the PKGBUILD?

liberodark commented on 2018-07-19 17:11 (UTC)

REAPER 5.93 officialy on linux :D

Solace_Greyowl commented on 2018-06-21 04:00 (UTC)

pkgver doesnt equal 5.92rc2 on the landoleet website, thus making the newest release unable to install because it cant download . I don't know if I have the ability to make changes to the pkgbuild but the correct version should be 592.

spider-mario commented on 2018-05-08 19:27 (UTC) (edited on 2018-05-08 19:28 (UTC) by spider-mario)

No, it’s only an error because of -Werror which turns warnings into errors, and ALLOW_WARNINGS suppresses that flag:

You can see it in the failing build log:

cc1plus: all warnings being treated as errors

donvla commented on 2018-05-07 19:24 (UTC)

But this option only suppresses the warning. The error - if it's one - still persists.

twisted-space commented on 2018-05-07 18:00 (UTC)

@ spider-mario, thanks that (make ALLOW_WARNINGS=yes) worked.

spider-mario commented on 2018-05-07 17:46 (UTC) (edited on 2018-05-07 17:47 (UTC) by spider-mario)

The problem is that the upstream Makefile sets -Wall -Werror unless ALLOW_WARNINGS is defined, and GCC 8, which just reached [core], introduces new warnings.

You can fix that by replacing make in the PKGBUILD with make ALLOW_WARNINGS=yes (or =whatever, all that matters is that it’s defined).

twisted-space commented on 2018-05-07 17:23 (UTC)

@funkmuscle yes, same error here.

funkmuscle commented on 2018-05-07 14:23 (UTC)

anyone having issues upgrading reaper 5.81pre8-1?

Go ahead? (Y/n): Building reaper ==> Making package: reaper 5.81pre8-1 (Mon May 7 10:20:22 EDT 2018) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found reaper581pre8_linux_x86_64.tar.xz -> Found ==> Validating source files with sha256sums... reaper581pre8_linux_x86_64.tar.xz ... Passed WDL ... Skipped ... Passed ==> Extracting sources... -> Extracting reaper581pre8_linux_x86_64.tar.xz with bsdtar -> Creating working copy of WDL git repo... Cloning into 'WDL'... done. -> Extracting with bsdtar ==> Starting build()... make: freetype-config: Command not found make: freetype-config: Command not found make: freetype-config: Command not found make: freetype-config: Command not found make: freetype-config: Command not found make: freetype-config: Command not found make: freetype-config: Command not found make: freetype-config: Command not found make: freetype-config: Command not found swell-miscdlg-generic.cpp: In function ‘LRESULT swellFileSelectProc(HWND, UINT, WPARAM, LPARAM)’: swell-miscdlg-generic.cpp:730:47: error: ‘%s’ directive output may be truncated writing up to 2047 bytes into a region of size 2032 [-Werror=format-truncation=] snprintf(msg,sizeof(msg),"File exists:\r\n\r\n%s\r\n\r\nOverwrite?",buf); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~ In file included from /usr/include/stdio.h:862, from swell-types.h:29, from swell.h:54, from swell-miscdlg-generic.cpp:30: /usr/include/bits/stdio2.h:64:35: note: ‘builtinsnprintfchk’ output between 31 and 2078 bytes into a destination of size 2048 return builtinsnprintfchk (s, n, USE_FORTIFY_LEVEL - 1, ~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ bos (s), fmt, va_arg_pack ()); ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ swell-miscdlg-generic.cpp:693:47: error: ‘%s’ directive output may be truncated writing up to 2047 bytes into a region of size 2020 [-Werror=format-truncation=] snprintf(msg,sizeof(msg),"Error opening directory:\r\n\r\n%s\r\n\r\nCreate?",buf); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~ In file included from /usr/include/stdio.h:862, from swell-types.h:29, from swell.h:54, from swell-miscdlg-generic.cpp:30: /usr/include/bits/stdio2.h:64:35: note: ‘builtinsnprintfchk’ output between 40 and 2087 bytes into a destination of size 2048 return builtinsnprintfchk (s, n, USE_FORTIFY_LEVEL - 1, ~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ bos (s), fmt, va_arg_pack ()); ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ cc1plus: all warnings being treated as errors make: *** [<builtin>: swell-miscdlg-generic.o] Error 1 ==> ERROR: A failure occurred in build(). Aborting... Error: makepkg failed</builtin>

pha-qu commented on 2018-04-22 13:37 (UTC)

@david0 appologies for not replying sooner, I probably need to set up notifications, or at least check them ;) I've managed to get the installation from AUR synchronized properly. The problem I was experiencing seems to be a result of the frequency of update/change at landoleet. The PKGBUILD file was stale when I found it (hence 404). It's not something I've experienced in Arch/AUR before as I'm not a developer or subscriber to nightly build packages in general, just a learning experiencing with PKGBUILD and makepkg :D

cogwerkz commented on 2018-04-20 10:15 (UTC) (edited on 2018-04-20 10:15 (UTC) by cogwerkz)

@Enverex that's probably because landoleet removes the old package before they upload the new one, so there's a gap in time between updates. Both appear to count as updates in his script, though.

As a general rule, just make a habit of checking this page for version number before you start the makepkg process. If the version number listed here is something like "5.-1" or anything with -1 or otherwise looks wonky, just wait a few mins/hours for the next proper update following cockos actually uploading the new reaper package to landoleet. :)

Enverex commented on 2018-04-20 10:07 (UTC)

"The PKGBUILD is automatically updated to follow whats on landoleet" - Are you sure? Build is failing form me with "Failure while downloading".

delaerep commented on 2018-04-18 15:24 (UTC)

The checksum is wrong : 8e82f3e8f2eab75ebb1e49b2d64365707ceb8bea8947a4d71e19de6baa0f291f works!

david0 commented on 2018-04-18 07:09 (UTC)

@pha-qu: I dont know what you mean with tout-suite. The PKGBUILD is automatically updated to follow whats on landoleet, but it polls landoleet so it might take some time (usually <1h if my PC is running). The versioning just follows landoleet, even if this means 579rc2 -> 579 shows up as a downgrade.

pha-qu commented on 2018-04-16 17:19 (UTC)

Hi I checked back, and although the url for the sources in pkgbuild is nearly correct. It isn't quite: curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Failure while downloading Aborting...

Today, note modified today (wtf!?), it is: Presumably when updates are pushed we need to apply tout-suite before the name changes and breaks the pkgbuild!?

pha-qu commented on 2018-04-15 14:47 (UTC)

Further the current package is at :

Just need to modify the pkgbuild

pha-qu commented on 2018-04-15 14:45 (UTC)

Tried to install today, the target for downloading the zipped package doesn't exist anymore. I just uninstalled the crap-hole that is Waveform thinking I'd flip and try Reaper ... seems not

igor45 commented on 2018-03-29 23:53 (UTC) (edited on 2018-03-29 23:58 (UTC) by igor45)

I fixed the mismatched package name by passing an argunent to yaourt like so: yaourt --m-arg "--skipinteg --skippgpcheck" -S reaper

diekrg commented on 2018-03-27 01:18 (UTC)

Hey, on the 25th of March 2018 the reaper version on changed to reaper579pre1, but I got the following error "One or more files did not pass the validity check!". The problem was with the validation of the sha256 with the tar file.

I changed the version in the PKGBUILD to reaper579pre1, generated the corresponding sha256 and put that value in the PKGBUILD and that fixed it for me.


spider-mario commented on 2018-03-16 22:12 (UTC) (edited on 2018-03-16 22:14 (UTC) by spider-mario)

I am not quite sure why there are those post_{install,upgrade,remove} functions at the bottom of the PKGBUILD. If they were required, they should go into a .install file, and they are not, since it’s all taken care of by various hooks in /usr/share/libalpm/hooks/ (for example, have a look at /usr/share/libalpm/hooks/update-desktop-database.hook).

david0 commented on 2018-02-21 21:12 (UTC)

@net147: while it would be possible, I think its not a good idea, since the linux release 5.76 is not a stable version at all. The linux version in general is not an official release.

net147 commented on 2018-02-21 08:57 (UTC)

@david0 Why don't you point to the 5.76 release in the "old" folder?

morrisar47 commented on 2018-02-12 16:22 (UTC)

Ufortunately, this did not build for me. ==> Starting build()... make: pkg-config: Command not found g++ -pipe -fvisibility=hidden -fno-math-errno -fPIC -DPIC -Wall -Wshadow -Wno-unused-function -Wno-multichar -Wno-unused-result -Werror -Wno-deprecated-declarations -O2 -DNDEBUG -s -DSWELL_TARGET_GDK=3 -DSWELL_LICE_GDI -DSWELL_FREETYPE -I/usr/include/freetype2 -D_FORTIFY_SOURCE=2 -c -o swell.o swell.cpp make: pkg-config: Command not found make: pkg-config: Command not found In file included from swell.cpp:37:0: swell-internal.h:582:10: fatal error: gdk/gdk.h: No such file or directory #include <gdk gdk.h=""> ^~~~~~~~~~~</gdk>

net147 commented on 2018-02-11 10:46 (UTC)

@david0 v5.71-rc1 is available

goldpaw commented on 2018-01-31 19:00 (UTC)


The reason the current version doesn't work, is the same reason the build number says -1 currently: There is no linux versions available on

All we can do right now is to wait until a build becomes available again. Because is the only place we can get it.

donvla commented on 2018-01-31 17:48 (UTC)

Sry my fault! Though provided version does not work.

helldrak commented on 2018-01-27 04:22 (UTC)

Hi david0,

Thanks a lot for your soon answer and for your commits – everything is working like a charm now (btw landoleet x86_64 linux has been released on 2018-01-25 20:01).

david0 commented on 2018-01-25 08:27 (UTC)

Since quite some people asked, I changed the WDL url from the offical repo to the github clone, but I must admit that I don't understand what the problem with the offical one is.

The reason why the PKGBUILD is broken is simply because there is no x84_x64 build on Landoleet. You can change the PKGBUILD to use the url until they have provided a new build.

helldrak commented on 2018-01-25 02:14 (UTC)


First of all thanks for your work – it’s been pretty useful for me !

However, I can’t build your AUR on my new laptop (and desperately need to do so for my students…) because PKGBUILD links to "${pkgname}${pkgver//.}_linux_x86_64.tar.xz" which resolves to – could you change this, in order to link to the correct current link (should be ?

Can you also answer net147 and abique request to change the current "git+" to "" ?

All the best,

abique commented on 2018-01-16 16:00 (UTC)

I share net147 request, can you switch the git repository to the one on github? makepkg does not work at all right now here.

net147 commented on 2017-12-16 06:53 (UTC)

git URL not working, please switch to mirror

david0 commented on 2017-12-15 08:31 (UTC)

@Aldar looks like they changed reaper570_linux_x86_64.tar.xz?! I updated the sums. @acerix: Thanks!

funkmuscle commented on 2017-12-14 15:43 (UTC)

I've tried pacaur and it will not update reaper or any other packages. tried trizen and it upgrades or look like it is but once program is launched, it's still the old version. something is wrong with upgrading packages from AUR

funkmuscle commented on 2017-12-13 15:49 (UTC)

@Aladar. I don't think it's just reaper as lmms-qt5-git and yoshimi are doing the same thing..

Aladar commented on 2017-12-13 15:21 (UTC)

Hey, thanks for the updates, but current version doesn't want to update. Any idea what's going on?

:: Checking reaper integrity... ==> Making package: reaper 5.70-1 (Wed Dec 13 16:20:36 CET 2017) ==> Retrieving sources... -> Found reaper570_linux_x86_64.tar.xz -> Updating WDL git repo... Fetching origin -> Found ==> Validating source files with md5sums... reaper570_linux_x86_64.tar.xz ... FAILED WDL ... Skipped ... Passed ==> ERROR: One or more files did not pass the validity check! :: failed to verify reaper integrity

I udnerstand that the sum is different, but no idea what to do with it.

acerix commented on 2017-12-13 03:04 (UTC) (edited on 2017-12-13 03:08 (UTC) by acerix)

Thank you for this great package and prompt updates! 5.7 isn't even mentioned on their homepage yet.

I am amazed at how well Reaper works in Linux, especially after the "UNSUPPORTED, do not discuss online" warning message that was showing up on start.


P.S.: Looks like the md5 has changed, I get '2e5f5cd5220984cd7ad4aa4bf6a4b61f'. Also, recommend updating to a secure hash like sha256.

abique commented on 2017-12-01 22:29 (UTC)

rc1 is over there right?

goldpaw commented on 2017-11-10 22:00 (UTC)

@kyotoshift That's actually the exact same thing the package maintainer does, so it's a perfect fix. :) Having that said, the main problem here is that cockos don't announce when new developer versions are ready on the landoleet site, nor do they always follow the same versioning scheme. And sometimes they update several times a day, so it's kind of hard for our package maintainer to stay on top of it given how unpredictable the changes over at landoleet are. So personally I've just made a habit of checking before upgrading this package to make sure I get the right filename/version number. That way it never fails. :)

kyotoshift commented on 2017-11-10 21:47 (UTC)

Until this gets updated, a quick fix: 1. Download "pre11_linux_x86_64.tar.xz" from 2. Use md5sum on the file and copy the result. 3. In the PKGBUILD, Replace the first hash with the one you copied. I'm not sure if this is a good way to do things, but it worked for me.

milkii commented on 2017-10-31 04:05 (UTC)

up to pre6 commented on 2017-10-29 07:01 (UTC) (edited on 2017-10-29 07:22 (UTC) by

@funkmuscle Here, I change it to "pkgver=5.65pre5" to get it work. But, it does not work well under ratpoison...

funkmuscle commented on 2017-09-27 17:08 (UTC)

pkgver=5.51rc2 needed to be pkgver=5.51rc2a in the PKGBUILD for it to start downlaoding for me. Dload Upload Total Spent Left Speed 100 348 100 348 0 0 348 0 0:00:01 --:--:-- 0:00:01 1035 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Failure while downloading Aborting... ==> ERROR: Makepkg was unable to build reaper. THEN AFTER FIX PKGBUILD: ==> Retrieving sources... -> Downloading reaper551rc2a_linux_x86_64.tar.xz... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 349 100 349 0 0 349 0 0:00:01 --:--:-- 0:00:01 940 100 8450k 100 8450k 0 0 1408k 0 0:00:06 0:00:06 --:--:-- 1528k -> Cloning WDL git repo... Cloning into bare repository '/tmp/yaourt-tmp-harv/aur-reaper/WDL'... -> Downloading % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 44398 0 44398 0 0 44398 0 --:--:-- --:--:-- --:--:-- 86209 ==> Validating source files with md5sums...

funkmuscle commented on 2017-09-02 17:08 (UTC)

thanx! :)

jhernberg commented on 2017-09-02 16:40 (UTC)

The lsb-release make dep can be removed, it's no longer needed.

jhernberg commented on 2017-09-02 16:35 (UTC)

That's because there was a detour in versioning where they took it out of rc status for a couple of releases. Now they are back on the normal rc. Nothing to worry about :)

funkmuscle commented on 2017-09-02 14:55 (UTC)

hey lately I haven't been getting updates when using pamac but I've noticed Reaper upgrades. The last one I received after running was version 5.50repre4. I just ran yaourt -S reaper and no issues building but before installing, I received this warning: loading packages... warning: downgrading package reaper (5.50repre4-1 => 5.50rc21-2) resolving dependencies... looking for conflicting packages... so am I really downgrading here? if so, why go from repre4 to rc21?

snieb commented on 2017-09-01 12:30 (UTC)

Installing via Pamac 5.1.0-1 results in faulty *.desktop files that point to /tmp/pamac-build-{{user}}/reaper/pkg/reaper/usr/lib//REAPER/. makepkg does fine, so it's probably some problem with pamac and $pkgdir. Quick fix after install: sudo sed -i "s#/tmp/pamac-build-$USER/reaper/pkg/reaper/usr/lib/#/usr/lib#" -- /usr/share/applications/cockos-reaper*.desktop

david0 commented on 2017-08-24 12:26 (UTC)

@jhernberg: I will add it next week.

jhernberg commented on 2017-08-20 11:48 (UTC)

Would you please consider adding the desktop/mime support I wrote? See:

teetest commented on 2017-08-05 00:00 (UTC)

reaper daliy update...

svoufff commented on 2017-07-21 18:09 (UTC)

@45marcin : I had the same problem.Installing ttf-freefont solved the problem.See this post

45marcin commented on 2017-05-28 07:47 (UTC)

after fresh install on arch i get squares instead of letters

satriani commented on 2017-05-21 17:25 (UTC)

Please add following to the PKGBUILD to creating launcher cat > "/usr/share/applications/Reaper.desktop" << EOF [Desktop Entry] Name=Reaper Comment=Digital audio workstation Exec=reaper5 Icon=/usr/lib/REAPER/Resources/main.png Terminal=false Type=Application Categories=GTK;Audio;AudioVideoEditing;AudioVideo;Video; EOF install -Dm644 Reaper.desktop "${pkgdir}/usr/share/applications/Reaper.desktop" thanks :)

linos commented on 2017-05-09 20:35 (UTC)

You might try and change it to git://

mongrol commented on 2017-05-09 09:57 (UTC)

The WDL git repo appears to be unavailable.

david0 commented on 2017-05-02 08:19 (UTC)

Hi all, no need to comment every time a new release is out. Flagging out-of-date is enough. Thanks!

Abysmill commented on 2017-05-01 08:53 (UTC)

5.408 is out c25a9dca0ff63e12dc223c5723f15b5c

Abysmill commented on 2017-04-22 08:14 (UTC)

5.405 is out 8f6c3db8e06b13ef6f15b9e6f6016061

Abysmill commented on 2017-04-14 17:45 (UTC)

One more PKGBUILD change: pkgver=5.403 md5sums=('89f8036483340ce2ebb5e57492cfcc2c' 'SKIP')

kddavidson72 commented on 2017-04-11 14:43 (UTC)

PKGBUILD change pkgver=5.401 md5sums=('03236cf028b3e6e10ed98925e36c54e3' 'SKIP') and it will build.

murth commented on 2017-03-05 07:04 (UTC)

5.35 is out so current build fails as they removed the file. 5.35 md5 258cd292d6caf119ce3f08a2cf4ed5f9

jhernberg commented on 2017-03-01 21:33 (UTC)

Have a look at :)

sekret commented on 2017-02-23 17:28 (UTC)

You still need to add git to makedepends!

sekret commented on 2016-12-14 20:31 (UTC)

Please add git to makedepends, without it I get ==> ERROR: Cannot find the git package needed to handle git sources. ==> ERROR: An unknown error has occurred. Exiting... ==> ERROR: Build failed, check /home/sekret/.chroot/sekret/build when building in a clean chroot. Also please add lsb-release to makedepends, because without the build process starts with ==> Starting build()... /bin/sh: lsb_release: command not found /bin/sh: lsb_release: command not found

ObscureScience commented on 2016-11-27 19:56 (UTC) (edited on 2016-12-06 16:46 (UTC) by ObscureScience)

Where is it said that Reaper is distributed under a free software license (specifically GPL, as in the PKGBUILD)? (Update: I see that it's fixed. Just a leftover of a PKGBUILD template?)

david0 commented on 2016-11-27 19:31 (UTC)

Thanks for your hint, i fixed that. is included in the offical tar.xz, so no need to include the older one anymore.

aggraef commented on 2016-11-27 14:06 (UTC)

The name of the source package in the PKGBUILD is wrong, it should be version 529 (and the corresponding md5sum needs to be adjusted to cd0dad09aac722b0558632878c1a86bb). Also, it would be nice if the file from could be included in the package (it should go into $DESTDIR/REAPER).

MrHaroldA commented on 2016-09-23 08:17 (UTC)

Found on "And yet more REAPER for Linux news: on the dev section of the site, today a "" has appeared. Putting this into the /REAPER/plugins/ folder where you have extracted the linux dev REAPER allows the ReaTune plugin to use the Elastique engine now - so now it has the same pitch correction abilities as the Windows version :)"

david0 commented on 2016-02-05 13:37 (UTC)

Thank you, I fixed the PKGBUILD. This is not a stable release, hence your issues. From the readme: > This is a developer experimentation release. If you are not a programmer you should not bother reading this, nor running REAPER. The implementations for nice fonts is also a known issue: > The default libSwell targetting is to GDK, which uses GDK for top level > windows, and uses LICE for drawing/compositing child windows. An obvious > next step would be to make swell-gdi-lice.cpp render text using FreeType or > some other library, rather than the incredibly fantastic bitmapped font.

Greed commented on 2016-02-02 21:40 (UTC)

I had to edit the PKGBUILD in order to get this to build, both instances of: ${srcdir}/${pkgname}-${pkgver}/WDL-public/WDL/swell/ Had to be changed to: ${srcdir}/WDL/WDL/swell/ Above will build, but it appears to have font rendering issues (Possible that I do not have the right font installed) and does not correctly detect audio devices from initial testing.