Package Details: reaper-bin 6.13-1

Git Clone URL: (read-only, click to copy)
Package Base: reaper-bin
Description: Digital Audio Workstation
Upstream URL:
Licenses: custom
Conflicts: reaper
Submitter: david0
Maintainer: david0
Last Packager: david0
Votes: 75
Popularity: 1.56
First Submitted: 2018-08-10 15:40
Last Updated: 2020-07-23 13:30

Latest Comments

1 2 3 4 5 6 ... Next › Last »

madskjeldgaard commented on 2020-08-15 19:16

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

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

@david0: the package version is broken again.

JohnnyDeacon commented on 2019-08-25 23:53

Could somebody update the package, please?

SpotlightKid commented on 2019-07-30 14:24

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

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

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

I agree with @jhernberg.

jhernberg commented on 2018-08-16 10:39

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

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.