Meet Rabbit, the REAPER Accessibility Bootstrap & Bundle Installation Tool, your one and only tool to keep REAPER and all its extensions up to date
-
Meet Rabbit, the REAPER Accessibility Bootstrap & Bundle Installation Tool, your one and only tool to keep REAPER and all its extensions up to date.
Rabbit does make sure to update REAPER, OSARA, SWS, ReaPack, ReaKontrol, JAWS Scripts and FFMpeg on Windows and Mac, no matter if ARM or x64. It comes as a single executable that you can run and forget whenever you want. For nerds it also contains a CLI application that can be used to automate mass installations etc.
https://github.com/Timtam/rabbit/releases/tag/v0.1.0@ToniBarth @fubsepude Wow that's really cool, I like that!
The number of times I'm just too unmotivated to manually download reaper, manually download osara... Ugh.
Thanks a ton! -
@ToniBarth @fubsepude Wow that's really cool, I like that!
The number of times I'm just too unmotivated to manually download reaper, manually download osara... Ugh.
Thanks a ton!@ToniBarth @fubsepude FWIW I ended up having to actually unblock the open me first that is meant to remove the attributes from the app bundle... So I suppose in the end it would have been the same if I had ran the .app itself.
I don't reckon that was expected though? -
@FreakyFwoof @ToniBarth I realized that to bypass the gatekeeper the app had to remind in the same folder where the "open me first” was located. The minute I moved it into the “Applications" folder, the protection got enabled again.
Like Andre said though, i also was not able to install / update all the components. -
@FreakyFwoof @ToniBarth I realized that to bypass the gatekeeper the app had to remind in the same folder where the "open me first” was located. The minute I moved it into the “Applications" folder, the protection got enabled again.
Like Andre said though, i also was not able to install / update all the components.@vick21 @FreakyFwoof Try the newest 0.1.1 version, that should have fixed the unable to update problem.
-
@ToniBarth @fubsepude FWIW I ended up having to actually unblock the open me first that is meant to remove the attributes from the app bundle... So I suppose in the end it would have been the same if I had ran the .app itself.
I don't reckon that was expected though?@xogium @fubsepude From what Andre says, it seems like Mac has become really paranoid about such things. Looks like, unless I will pay hundred bucks every year to properly sign my app, that is what you'll have to do once when you download the app. Updates will later remember the unlocked gatekeeper though.
-
@xogium @fubsepude From what Andre says, it seems like Mac has become really paranoid about such things. Looks like, unless I will pay hundred bucks every year to properly sign my app, that is what you'll have to do once when you download the app. Updates will later remember the unlocked gatekeeper though.
@ToniBarth @fubsepude Right, that is no problem with me. Just thought I'd point this out. Maybe the best path forwards then is to mention this in the readme, given the open me first script doesn't quite seem to work as painlessly as you hoped it would? Just a thought.
Seems there would be no point keeping this in the repo if you have to pick between unblocking this or the app bundle itself.Mac might be a bit on the annoying side with this, but at least it's not like that horrible crap of windows defender always removing things from your machine without your say so. I’ll take mac gatekeeper over this every single day.
-
Meet Rabbit, the REAPER Accessibility Bootstrap & Bundle Installation Tool, your one and only tool to keep REAPER and all its extensions up to date.
Rabbit does make sure to update REAPER, OSARA, SWS, ReaPack, ReaKontrol, JAWS Scripts and FFMpeg on Windows and Mac, no matter if ARM or x64. It comes as a single executable that you can run and forget whenever you want. For nerds it also contains a CLI application that can be used to automate mass installations etc.
https://github.com/Timtam/rabbit/releases/tag/v0.1.0@ToniBarth I'm having a bit of an issue with Rabbit on my mac.
SWS, reapack, and reacontrol don't show up in my reaper extensions menu, due to the fact that rabbit installs the x64 versions on my computer, but my computers are both apple cilikon.
Is there any way to fix this in a later version?
You could add the ability in rabbit for the user to choose which versions of these components they want/need. -
@ToniBarth I'm having a bit of an issue with Rabbit on my mac.
SWS, reapack, and reacontrol don't show up in my reaper extensions menu, due to the fact that rabbit installs the x64 versions on my computer, but my computers are both apple cilikon.
Is there any way to fix this in a later version?
You could add the ability in rabbit for the user to choose which versions of these components they want/need.@fubsepude Which version of Rabbit are you running?
-
@fubsepude Which version of Rabbit are you running?
@ToniBarth 0.1.1
-
@fubsepude Thanks. you are running the universal rabbit build right? And what version of REAPER, the universal build?
-
@fubsepude Are you perhaps running it in Rosetta mode, or something like that?
-
@fubsepude Are you perhaps running it in Rosetta mode, or something like that?
@ToniBarth Nope.
The run in rosetta mode checkbox is unchecked on my machine, so it should be in normal mode. -
@ToniBarth Nope.
The run in rosetta mode checkbox is unchecked on my machine, so it should be in normal mode.@fubsepude Thanks, that is good to know.
-
@fubsepude Thanks, that is good to know.
@fubsepude Do you have a GitHub account and can download artifacts for testing? I might have a fix ready, but am trying to find a way to get it to you as comfortable as possible.
-
@fubsepude Do you have a GitHub account and can download artifacts for testing? I might have a fix ready, but am trying to find a way to get it to you as comfortable as possible.
-
@fubsepude Try this build if you like, you can just check the checkboxes to override the currently installed with the hopefully correct one this time. https://github.com/Timtam/rabbit/actions/runs/25639211302/artifacts/6906804048
-
@fubsepude Try this build if you like, you can just check the checkboxes to override the currently installed with the hopefully correct one this time. https://github.com/Timtam/rabbit/actions/runs/25639211302/artifacts/6906804048
@ToniBarth Hmmm... I just tried this build, but it still does the same thing re: installing the wrong versions of the components/plugins.
-
Meet Rabbit, the REAPER Accessibility Bootstrap & Bundle Installation Tool, your one and only tool to keep REAPER and all its extensions up to date.
Rabbit does make sure to update REAPER, OSARA, SWS, ReaPack, ReaKontrol, JAWS Scripts and FFMpeg on Windows and Mac, no matter if ARM or x64. It comes as a single executable that you can run and forget whenever you want. For nerds it also contains a CLI application that can be used to automate mass installations etc.
https://github.com/Timtam/rabbit/releases/tag/v0.1.0@ToniBarth This is very cool!
-
@vick21 @FreakyFwoof Try the newest 0.1.1 version, that should have fixed the unable to update problem.
@ToniBarth @FreakyFwoof I am still not able to update. Also, a few things: I am using dev snapshots (unknown release date) for both OSARA and ReaKontrol. Rabbit said “won't update” in the case of ReaKontrol but “Will update" in the case of OSARA.
Even after unchecking both, the app was not able to complete the install. BTW, what's your Reapack repo so that I can add it manually? Thx! -
@ToniBarth @FreakyFwoof I am still not able to update. Also, a few things: I am using dev snapshots (unknown release date) for both OSARA and ReaKontrol. Rabbit said “won't update” in the case of ReaKontrol but “Will update" in the case of OSARA.
Even after unchecking both, the app was not able to complete the install. BTW, what's your Reapack repo so that I can add it manually? Thx!@vick21 @FreakyFwoof ReaKontrol has no version information in the library files themselves, which is why it doesn't recommend you to update. OSARA however has, which might be why it recommends you to update. If possible, try to send me the setup-unix-<timestamp>.txt file of the latest, erroring run from your REAPER resource path/RABBIT/logs for diagnosis. Thank you.
