ReaPack: Package manager for REAPER

[me2beats]

Hi!
We can add scripts to Main and Midi sections, what about Midi Inline Editor section?

[hopi]

Originally Posted by me2beats

Hi!
We can add scripts to Main and Midi sections, what about Midi Inline Editor section?

The Inline editor sure could use some!

[bolgwrad]

Originally Posted by cfillion

ReaPack requires Windows Vista or newer, macOS 10.7+, Wine 1.8+ and (in beta) Linux. See here and here for more details about the lack of support for 16-years-old XP.

Many thanks for the reply, which also explains why millennial geeks recoil at XP like they do. Guess I'll just have to do some work, and not keep tweaking plugins. Guess what, my car's over 16 years old too

[RobU]

I have (finally), and for the most part, gotten my head around ReaPack

For my other scripts, which include several non-indexed files it works as intended, only the main script is indexed and shown in the action list.

However, I also want to provide the GUI library file separately under 'Templates' and include an example file. I would like the example script to appear under the Actions list, but not the gui library.

The headers look something like this:

GUI template (GUI.lua)

@description - A Lua GUI for Reaper
@about
  ### Features
  - Stuff
@version 1.0
@provides GUI Example.lua
nomain:

Example script (GUI Example.lua)

@description - Lua GUI Example
@about
  Demo and boilerplate code for Lua GUI for Reaper
@version 1.0
@noindex true
main=main

In ReaPack, the GUI template is listed and the example script is not, so far so good,

The example script shows up in the action list as intended, but the gui library shows up there too, even though I have included the 'nomain:' option.

Can anyone explain how to do this, or if it's even possible?

Cheers
Rob

[cfillion]

The options of the @provides tag such as (no)main goes between brackets at the left of the filename they are applied to:

@provides
  [nomain] .
  [main  ] GUI Example.lua

[RobU]

Originally Posted by cfillion

The options of the @provides tag such as (no)main goes between brackets at the left of the filename they are applied to:

@provides
  [nomain] .
  [main  ] GUI Example.lua

Thank you !

[Ivannn Bennnettt]

Hey! What about a reapack video blog?
I suppose it's time.

[me2beats]

[Robert Randolph]

So what's the correct way to get more repositories added to the website?

[mschnell]

With ReaPack we now have a "Standardizing Tool" for JSFX, e.g. introducing the "about by markdown" documentation standard to allow for the ReaPack JSFXes to be findable and usable.

IMHO it would be a good idea to define a standard for allowing JSFXes to interact and not to harm each others by using gmem.

I might suggest a preliminary definition:
- for any JSFX a "magic number" is generated from its "description". e.g. using the lows 7 bits of each letter (one by one), add to a variable, clear the bits <= 40, and rotate the lower 40 bits of the variable by 7 bits to the left.

- at the start of gmem, a table of - say - 128 entries is defined. each entry containing three variables:
- - magic number (or zero if empty)
- - start of the gmem area assigned to that JSFX (-set)
- - size of the gmem area assigned to that JSFX.

Now each JSFX can "malloc" an area of gmem variables by maintaining the table.

- If a "set" of JSFXes wants to share an area they can use the same magic number and easily find each other.

- if multiple instances of the same JSFX want to use different areas they can use a new magic number by incrementing the original value.

(Or is it better to implement a mechanism via "global ? )

- JSFXes should be required to use this procedure to be accepted for ReaPack.

I think this procedure is "save enough" for the purpose.



-Michael

[cfillion]

Sorry for the delays! I finally had the time to clear most of my ReaPack backlog.
https://forum.cockos.com/showthread.php?p=1852919

@kyotosound I couldn't reproduce nor figure out that crash unfortunately.
@Claudiohbsantos I've added some of these new types in the new build.
@me2beats MIDI Inline Editor: done in ReaPack, reapack-index will follow soon. "Upload date": for now you can see that info in the browser, with "me2beats" as filter.
@Robert Randolph I've just inserted the new repos listed on your thread (thanks), and I've also added a button "Edit this list" at the top.
@mschnell Not sure I can (or should) help with that.

[mschnell]

Cfillion,

Would it be possible to enhance ReaPack in a way that it also creates an entry in the Help menu and here presents a window to select one of the installed ReaPack aware products and clicking on one of them shows the appropriate "about" window ? Supposedly those product that don't provide any "about" / description information should be not be presented in the list. Hence the list might be rather short right now. (But at least my contributions would show up .)

On top of that it would be great if pressing "F1" with something appropriate selected in the Effect Chain window (or using some right click local menu) could offer the "about" window for a JSFX directly, but I am not sure if this is (easily) possible.

-Michael

[mschnell]

Originally Posted by cfillion

I've just inserted the new repos listed on your thread (thanks), and I've also added a button "Edit this list" at the top.

Where to see this ?
-Michael

[mschnell]

Originally Posted by mschnell

"About" information in the Help Menu

On top of that I would be happy to be part of a team of volunteers providing "about" text for the Reaper stock JSFXes,

For this, we would need a dedicated repository for the files, and a way to have ReaPack manage just the description text but not the source code of the JSFXes. (I seem to remember an option to manage affiliated files, which might be extended to handle the stock JSFXes.)

Moreover a dedicated forum or at least a sticky thread for the team members would be nice to have.

-Michael

[Erriez]

Today I discovered ReaPack which is very useful. I've a question about creating the index.xml file (on Windows).

My .jsfx script contains a slider to parse text configuration files:

// REAPER\Effects\my_effect_dir\myscript.jsfx:
slider1:/midi_config_dir:none:MIDI config file:

The text files are located in:

REAPER\Data\midi_config_dir\GM Basic.txt
REAPER\Data\midi_config_dir\GM Extended.txt
REAPER\Data\midi_config_dir\Another file.txt

I could not include it with the provides keyword. How can I configure the .jsfx script to include these .txt files to install it into REAPER\Data\midi_config_dir\?

[James HE]

Originally Posted by Erriez

How can I configure the .jsfx script to include these .txt files to install it into REAPER\Data\midi_config_dir\?

I don't think this is currently implemented. You might be the first to want to use the DATA path for a plugin. Hopefully cfillion can make it happen!

[nofish]

Originally Posted by Erriez

Today I discovered ReaPack which is very useful. I've a question about creating the index.xml file (on Windows).

My .jsfx script contains a slider to parse text configuration files:

// REAPER\Effects\my_effect_dir\myscript.jsfx:
slider1:/midi_config_dir:none:MIDI config file:

The text files are located in:

REAPER\Data\midi_config_dir\GM Basic.txt
REAPER\Data\midi_config_dir\GM Extended.txt
REAPER\Data\midi_config_dir\Another file.txt

I could not include it with the provides keyword. How can I configure the .jsfx script to include these .txt files to install it into REAPER\Data\midi_config_dir\?

http://forum.cockos.com/showthread.php?t=169127&page=15 (from post #575)

The way mentioned there (using rename operator ">") should work in your case also I'd think.

edit:
Not sure it also works with .txt files though.

[Erriez]

I don't think this is currently implemented. You might be the first to want to use the DATA path for a plugin. Hopefully cfillion can make it happen!

I think you're right: I've installed all 840 scripts and no new files are added to the REAPER\Data directory.

The way mentioned there (using rename operator ">") should work in your case also I'd think.

edit:
Not sure it also works with .txt files though.

The provides keyword seems to ignore my .txt files.

My repository:
https://github.com/Erriez/erriez-reaper-jsfx

The .txt files are located in a subdirectory:
https://github.com/Erriez/erriez-rea...y_viewer_drums

Script:
https://github.com/Erriez/erriez-rea...wer_drums.jsfx

provides: [data] midi_velocity_viewer_drums/GM Basic.txt > midi_velocity_viewer_drums/GM Basic.txt

Any idea?

[cfillion]

Originally Posted by mschnell

Would it be possible to enhance ReaPack in a way that it also creates an entry in the Help menu and here presents a window to select one of the installed ReaPack aware products and clicking on one of them shows the appropriate "about" window ? Supposedly those product that don't provide any "about" / description information should be not be presented in the list.

The end goal being to have a list containing only packages with a documentation? I think adding a new kind of filter (eg. has:about) in the Package Browser would be a simpler way to to this (and more powerful in the long run if adding others filters later).

Originally Posted by mschnell

On top of that it would be great if pressing "F1" with something appropriate selected in the Effect Chain window (or using some right click local menu) could offer the "about" window for a JSFX directly, but I am not sure if this is (easily) possible.

This could probably be done with a ReaScript actually, using the new API I've added to ReaPack in the latest beta.
As long as the filename of the focused effect can be obtained (I haven't looked into it).

Originally Posted by mschnell

Where to see this ?

https://reapack.com/repos

Originally Posted by mschnell

On top of that I would be happy to be part of a team of volunteers providing "about" text for the Reaper stock JSFXes

Theoretically you could build an index file describing the stock FX and having it set as Disabled in ReaPack so that it doesn't try to manage the files.

[cfillion]

@Erriez

ReaPack always supported data files (since v0.10-beta actually).

The rename operator (>) is not needed when keeping the filename as it is on the repository.

provides: [data] midi_velocity_viewer_drums/GM Basic.txt

or, to add every txt files from the subdirectory to the package:
provides: [data] midi_velocity_viewer_drums/*.txt

After commiting the change and running `reapack-index --amend` to update the version already released in the index:

[mschnell]

Originally Posted by cfillion

The end goal being to have a list containing only packages with a documentation?

This would be great but of course beyond the scope of the contributors of this thread

Originally Posted by cfillion

I think adding a new kind of filter (eg. has:about) in the Package Browser would be a simpler way to to this (and more powerful in the long run if adding others filters later).

In fact I have been argumenting on behalf of the "common" user to whom ReaPack is just a tool occasionally used to find and install something. (S)he will seek for help for anything already in place in the Help menu and not in the "Extensions" menu. (And there in fact is where it belongs, IMHO.)

Originally Posted by cfillion

This could probably be done with a ReaScript actually, using the new API I've added to ReaPack in the latest beta.
As long as the filename of the focused effect can be obtained (I haven't looked into it).

Great to know (both facts)! Consequently a more advanced ReaPack could provide it out of the box together with the additional "Help" menu entry .

Originally Posted by cfillion

https://reapack.com/repos

I meant the "Button".

Originally Posted by cfillion

Theoretically you could build an index file describing the stock FX and having it set as Disabled in ReaPack so that it doesn't try to manage the files.

Great to know that this already seems to be possible. I would like to try this, even if it does not make much sense as long as there is no Help Menu entry for the Reaper users to easily find it. So could you elaborate on "build an index file", so that I can try to provide an example ?


-Michael

[Philbo King]

In the install instructions you might want to consider clarifying which ReaPack should be downloaded. It says "select the one that matches the Reaper architecture" or something like that...

What I fould:
Running Reaper 32 bit - download ReaPack 32 bit
Running Reaper 64 bit - download ReaPack 64 bit

Seems obvious, right? But I run Reaper 32 bit on a 64 bit Win7 PC.
So, after loading the 64 bit Reapack, I was left scratching my head as to why it wouldn't work... I finally figured out that the ReaPack 32bit goes with Reaper 32bit.

It should give some indication that the OS wordsize is not important, what matters is the Reaper wordsize.
-----------------------

Also:
For those of you who use ReaMenu - The ReaPack Menu item shows up under Memory->Default menu: Main Extensions->ReaPack. I'll probably add a copy to the Memory menu so it will show up there too.
-----------------------

Thanks to the OP for his amazing work on this thing!!!

[Erriez]

@cfillion

ReaPack always supported data files (since v0.10-beta actually).

The rename operator (>) is not needed when keeping the filename as it is on the repository.

Code:

provides: [data] midi_velocity_viewer_drums/GM Basic.txt

or, to add every txt files from the subdirectory to the package:
provides: [data] midi_velocity_viewer_drums/*.txt

After commiting the change and running `reapack-index --amend` to update the version already released in the index:

Problem solved: Now it works perfect after following your clear description.

Thank you very much for your fast help! :-)

[cfillion]

@mschnell

I've added "Show ReaPack about dialog for the focused JSFX" to ReaTeam Scripts. It supports track FX as well as item FX.

Originally Posted by mschnell

I meant the "Button".

It's right there on that page (it's more a "Edit this list" link than a button you might say).

Originally Posted by mschnell

Great to know that this already seems to be possible. I would like to try this, even if it does not make much sense as long as there is no Help Menu entry for the Reaper users to easily find it. So could you elaborate on "build an index file", so that I can try to provide an example ?

The index format is documented here: https://github.com/cfillion/reapack/wiki/Index-Format.

Caveats to have in mind:
- Documentation cannot be displayed on the Linux port yet
- The index must list at least one file per package with a download URL (you can put one such as http://not/for/download for testing only to bypass this limitation)
- Using ReaPack not to actually install stuff is kind of a hack (because it's not made to do that – see above point)

I think this idea has potential – let's continue talking about this on the development thread to not clutter this one.

@Philbo King

Nice suggestion, I've added that on the wiki.

[mschnell]

Originally Posted by cfillion

@mschnell
I've added "Show ReaPack about dialog for the focused JSFX" to ReaTeam Scripts. It supports track FX as well as item FX.

I installed it via ReaScript, but I don't see anything via Right-Click, F1 or "Help" menu". Seemingly I am being too silly
,,,
OK I found that I need to define a shortcut for the action before using it.
So it does work nicely. GREAT !!!

But to have it in place as a decent help even for newbies, it should not need any preparation. But of course ReaPack should be installed right away with a new Reaper installation "out of the box", as well, so this is an affiliated issue...

-Michael

[mschnell]

Originally Posted by cfillion

I think this idea has potential – let's continue talking about this on the development thread to not clutter this one.

Great to have your attention !
Maybe we could create a dedicated thread "documenting stock JSFXes" in the Script forum for this, and request for marking it sticky ?

-Michael

[mschnell]

Originally Posted by cfillion

The index format is documented here: https://github.com/cfillion/reapack/wiki/Index-Format.

Sorry, but I have no Idea what I could do with this information.
-Michael

[Win Conway]

So what is the voodoo that is needed to get this working ?
I just keep getting connection refused.

[cfillion]

Are you behind some sort of firewall? ReaPack needs access to internet through the REAPER process.

*If your DAW computer is offline you can use another (online) machine to download the packages. The latest beta series has a new dedicated import/export function specifically for that purpose.

[Win Conway]

Sorry i have been ill, no firewall blocking reaper at all

[Sju]

Just got this error... mind your script names guys

[Xenakios]

Originally Posted by Sju

Just got this error... mind your script names guys

Or maybe ReaPack should be updated to correctly deal with Unicode characters.

[cfillion]

@gpunk_w Looking more closely at your gif, it can indeed connect to github.com, but not raw.githubusercontent.com. Apart from the common culprits (firewall/proxy/vpn & cie) I don't know what could cause that, sorry.

@Sju ReaPack does support Unicode (the bullet character is a feature of that script). What software is this in the screenshot and how to reproduce?

[Delucci]

Is there a way to sort the scripts by upload date? I like to check if there are new scripts available

[nofish]

Originally Posted by Delucci

Is there a way to sort the scripts by upload date? I like to check if there are new scripts available

Click on the "Last Update" column header to make this the sorting order.
(If ypu don't see the "Last Update" column by default, rightclick in the column header to make it visible).

[Delucci]

Wew, thanks!

[nofish]

You're welcome.

[Time Waster]

Is there a way to get metrics on ReaPack activity?

[cfillion]

Originally Posted by Time Waster

Is there a way to get metrics on ReaPack activity?

This can only be done server-side (independently from ReaPack). GitHub don't provide any download metrics for repositories hosted on its servers.

[nofish]

Is it my internet connection or does GitHub has some problems currently ?

When trying to synchronize I get this:



(This is after several synchronize tries, after the first one it showed this error for all currently enabled repos)