ReaPack: Package manager for REAPER

[Anarchron]

Originally Posted by cfillion

Mmh... might be worth signaling that false-positive to Bitdefender if that keeps going. Looks like they have a form for their users at https://www.bitdefender.com/consumer.../answer/29358/.

Done.

[hexSPA]

Hi, I just installed reapack (I think) but 83 entries gave this error:

This script could not be registered in REAPER

It was in the error tab in the transaction window. Do I need to do anything?

[cfillion]

What are the entries you're trying to install? If they're .py scripts then Python needs to be installed in the system and configured in REAPER's preferences. (Otherwise this could mean you have reached REAPER's action count limit – unlikely.)

[hexSPA]

Originally Posted by cfillion

What are the entries you're trying to install? If they're .py scripts then Python needs to be installed in the system and configured in REAPER's preferences. (Otherwise this could mean you have reached REAPER's action count limit – unlikely.)

I just Options/Install when synchronizing, hit OK (I think) and about 4,000 things installed minus those 83 (I assume). This was my first time installing reapack. But, just now, when I synchronized, I got one new installation (reateam extensions/fx/realim: fixed latency...) and no Errors. I definitely do not have python installed on my system so if any .py files are included in the default reapack then that could explain it. I only have SWS as the other extension package so too many actions, like you say, is probably not the cause. Ordinarily, I take screenshots of these types of things but this time I didn't.

Anyway, thanks for creating this. I feel honored to get direct support like that. Really, all I wanted was the ZenoMod VU meter and the action to delete all time signature markers from the time selection. Thousands of new actions - it's kind of overwhelming (especially as a non-coder).

[mschnell]

Why did you install 4000 "things" you supposedly don't know what they might be useful for ?

-Michael

[Cool Rekz]

Hello,
I've just installed Reapack but everythime i try to "syncronize packages" i get an error stating "The revocation server is offline".

Can anyone hep me please?

Thanks"

[hexSPA]

Originally Posted by mschnell

Why did you install 4000 "things" you supposedly don't know what they might be useful for ?

-Michael

Because I'm an idiot, obviously

Actually it's because the guide that I followed seemed to recommend just installing everything since it doesn't slow reaper down. Plus, I was not really wanting to install reapack now because I generally research things pretty thoroughly before jumping in. However, I really wanted the zenomod VU meter so I just went for it. I guess this is what I get! It's easy to uninstall, right?

Here's the quote:
"I recommend you leave them checked and install all of these!"
from: https://www.reapertips.com/post/how-to-install-reapack

Maybe next time I'll stick with reaperblog or kenny.

[cfillion]

Originally Posted by Cool Rekz

everythime i try to "syncronize packages" i get an error stating "The revocation server is offline".

A variety of network-related issues could do that... (VPN/firewall/DNS/etc)

Can't help troubleshoot the root cause, however disabling "Verify the authenticity of SSL/TLS certificates" in ReaPack > Manage repositories > Options > Network settings should work around the problem.

[mschnell]

Originally Posted by hexSPA

installing everything since it doesn't slow reaper down.

It doesn't slow Reaper down and the amount of disk space used supposedly is not that huge. Only the count of plugins in the appropriate search procedure is vastly increased.

-Michael

[hexSPA]

Originally Posted by mschnell

It doesn't slow Reaper down and the amount of disk space used supposedly is not that huge. Only the count of plugins in the appropriate search procedure is vastly increased.

-Michael

Right. Plugins and actions. I know I called them "things" and I feel like you might have taken that personally. In my comment, I did mention they're "actions" and I assume most of it is scripts and I saw a few .png files too so, yeah, "things". Peace.

[nofish]

@hexSPA
Not sure if it's en- or disabled by default, but there's an option in ReaPack to not install everything automatically.
https://forum.cockos.com/showpost.ph...&postcount=747

[cfillion]

It's disabled by default. Default mode is to let users choose to install only what they want from the package browser.

[fawudd]

Originally Posted by mschnell

It doesn't slow Reaper down and the amount of disk space used supposedly is not that huge. Only the count of plugins in the appropriate search procedure is vastly increased.

-Michael

I accidentally installed all of the packages (somehow I checked all) 2 weeks ago. I chose not to undo this at the time. This may be totally unrelated, but for the first time in years of using Reaper, I got spinning beachballs and Reaper became unresponsive 2-4 times per week. Particularly around manipulating plugins. Last weekend, I uninstalled all except those I had originally. So far this week, no infinite beachballs. This is far from scientific, but it just reinforced the stance of only installing extensions that I need.

[hexSPA]

Originally Posted by fawudd

I accidentally installed all of the packages (somehow I checked all) 2 weeks ago. I chose not to undo this at the time. This may be totally unrelated, but for the first time in years of using Reaper, I got spinning beachballs and Reaper became unresponsive 2-4 times per week. Particularly around manipulating plugins. Last weekend, I uninstalled all except those I had originally. So far this week, no infinite beachballs. This is far from scientific, but it just reinforced the stance of only installing extensions that I need.

Just a wild guess but do you have a HDD (as opposed to SSD)? maybe macOS is indexing these thousands of files while you're using reaper. I turn that off on windows which slows down search but then I don't get that background activity (must save the 0.01% CPU for more instances of Massive )

[luiza177]

I recently moved to a new computer, I transferred my settings by exporting/importing them. I still have all the scripts I downloaded via Reascript in my old computer, but now Reascript doesn't seem to associate them with scripts downloaded with it. Is it possible to sort of 'reconnect' them?

[cfillion]

Exporting/importing REAPER settings does not copy over all files including ReaPack's database of installed packages. Best to copy the entire resource directory (Options > Show REAPER resource path in explorer/finder) or use ReaPack's import/export feature (Manage repositories > Import/export) in addition to REAPER's.

[jbradbury]

Is anyone able to help me make my project (https://github.com/ReaCoMa/ReaCoMa-2.0) compatible with ReaPack? I've been working with reapack-index and am generally command-line competent but I just really am hitting a wall getting the package to show up in a sensible fashion after I create the index.

I don't know if it is possible, but I have "user facing" scripts which use a library of other scripts I built under the hood to manage shared bits of code. I can't figure out how to make the bits of the package I want to show up as actions show up in there while also pulling in the underlying code that is require()d in Lua. Any pointers to an example project perhaps?

[cfillion]

The first step is to decide how to split (or not to split) the scripts into separate user-installable packages. (Is ReaCoMa best described as a set of tools/actions updated individually, or "one thing" consisting of multiple actions? Would it make sense to let users choose to install only a subset or have mismatched versions?)
(Generally, ReaPack repositories are meant to hold many packages, not just one big one. Have you considered releasing on ReaTeam?)

Then those user-installable packages need to be moved in a subfolder, which serves as the category name in ReaPack.

To include additional files beyond the package's file itself:

@provides
  [main]   user_action.lua
  [nomain] library_file.lua

If the library files are shared between multiple packages, each one using them must provide a different copy:

-- @description Script A
-- @version 1.0
-- @provides shared_library_file.lua > Script A/library_file.lua

dofile(self_path .. '/Script A/library_file.lua')

Installing 'Script A' will pull the correct version of 'shared_library_file.lua' from the time of its 1.0 release. Independently from the version of the shared library that a 'Script B' v1.4.8 might need.

In addition to the documentation, and even if building your own repository, I'd recommend referring to the GUI ReaTeam uploader (https://reapack.com/upload) as an interactive example of valid metadata.

(Also this is the user thread, the developer thread for questions like this is here: https://forum.cockos.com/showthread.php?t=169127)

[jbradbury]

Originally Posted by cfillion

(Also this is the user thread, the developer thread for questions like this is here: https://forum.cockos.com/showthread.php?t=169127)

I'll respond in the appropriate thread! Thank you for your help so far.

[luiza177]

Originally Posted by cfillion

Exporting/importing REAPER settings does not copy over all files including ReaPack's database of installed packages. Best to copy the entire resource directory (Options > Show REAPER resource path in explorer/finder) or use ReaPack's import/export feature (Manage repositories > Import/export) in addition to REAPER's.

Thank you so much!

[Infrabass]

Hey, hello everyone,

I wonder if there is an easy way to upload reascripts for beta testers only.
I guess having a secondary repository would do the trick.

[cfillion]

Add letters to the version number to make a pre-release version. Those are only installed if explicitly selected by the user or if pre-releases are enabled (either globally or per package).

In a scenario where a package has the following versions available (sorted from smallest to biggest number):

• 1.0
• 1.0.1
• 1.1beta1
• 1.1beta2

With pre-releases disabled (by default out of the box): the latest version shown is 1.0.1.

• Synchronizing will update to 1.0.1 if 1.0 is already installed
• Synchronizing will update to 1.1beta2 if 1.1beta1 is already installed (up to the next stable version)
• 1.1beta1 or beta2 needs to be selected explicitly in the 'Versions' menu to be installed

With pre-releases enabled (user changed the setting): there are no distinction between pre- and stable releases. 1.1beta2 is the version shown.

[Infrabass]

Awesome!

[mks]

I'm having a problem where the reapack package list is blank. Despite it showing that there are many available in the upper right filter area. That and all my installed items are functioning. I just can't browse or see things in this list. Any idea what's wrong or what I can do to fix this? I've already replaced the reapack.dll.

Thanks

[cfillion]

It sounds like the columns are hidden: right-clicking the list's header should show checkboxes to bring them back (or use "Reset columns"). If that's not it, can you post a screenshot of your package browser window?