JSFX now ReaPack Friendly & ReaTeam JSFX Repository

Hi everyone ! If you are a JSFX creator, you will be happy to hear that ReaPack, the incomming REAPER extension by cfillion that is meant to download/synchronize ReaScripts from Git Repos, can now works with JSFX ! This means that JSFX coded and upoaded on a Git System like GitHub can be downloaded right from REAPER by anyone using the ReaPack ! More if you update your FX, people will be able to be notified, and to download your new version with one click only ! To benefit from that, all you have to do is to have a (or alternative like GitLab) account and upload your script there. But you can also simply upload your JSFX on the brand new JSFX RaaTeam (ReaTeam is a collective of REAPER independent coders) public repo ! Just like , it can be a good place for collaboration and for centralizing JSFX, but if you prefer to be the only one to control your repo, then feel free to create one ! To make a JSFX ReaPack friendly, you only have to say .jsfx as extension, and to have an ReaPack friendly header, like this one : JSFX coders, are you ready for the ReaPack adventure ? :D Let us know if you have any concerns or questions ! See you on GitHub !

This is very cool and I hope it takes off but I'm super-busy and fairly lazy, so to entice people like me into supporting the worthy initiative, an explicit step by step "how-to" would probably be a good idea. If I had some simple instructions to follow, I might feel more inclined to invest some time in making my stuff compatible and uploading to a repository. Make it super-easy and people will probably start to use it, which would be a good thing. My eyes start to glaze over at the very sight of the word "git" and I doubt that I'm alone in that.

Here's one way of submitting contributions: Fork ("make a working copy of" in english) a ReaTeam repository ( or ) in your GitHub account Clone it ("download it on your computer") in the GitHub Desktop app Create a subdirectory to organize the packages by category for easy searching (eg. Envelopes, MIDI, Dynamics etc) Add some metadata at the top of the new files to at least tell ReaPack what version they are at (see X-Raym's posts above for more info on that) Once you're done making changes, create a branch and add at least one commit inside Send your commits to the original repository with a pull request After that, a member of will review the request, and if all is good, will merge it and update the package index. At this point the new package or update is available for download to ReaPack users! GitHub's help pages provide a good introduction to git and GitHub Desktop: . EDIT: I've only put version metadata in the video (that's the absolute minimum), but for prettier packages it's best to also put author information and a changelog. Check out the examples at .

Great !! Any planned way to manage documentation / user info file in such system and provide a searchable index for same ? -Michaek

Sounds very exciting, thanks team! I'll look into this soon. :) PS I wasn't a Git fan until I discovered GitKraken and now I (mostly) love it. :D

I have a few questions: 1 Does the Free Plan work OK? 2 Where is ReaPack? 3 Where is ReaPack Indexer? 4 Does everything go in the ReaTeam repository? 5 cfillion's scheme seems to suggest running your own repository; is that needed? Doesn't that cost $? 6 Once a script is uploaded to the ReaTeam repository, can any reaTeam member update the script? Anyone-else? How will a user search for the script that meets his / her requirements? Can user guides / screenshots etc be uploaded here too? (oops, that's what mschnell asked) ------------------------ Chambers Dictionary: git noun, derog slang a stupid or contemptible person.

Great job guys! So grateful to have this being worked on :)

Cool stuff! If I may suggest one thing: when you get this up and running, it might be worth to simplify the install/initialization process for ReaPack/Indexer or whatever. Just make it stupidly simple, like installing the SWS extensions. Many of the potential users probably don't have any experience in using these services like Git. For example, I just navigated to the ReaPack download page, but I have no idea what to do with those .dll and .dylib files (do i need one or both? where do i put them? etc...) Yep, some of us are a bunch of idiots :D please provide accessibility for the handicapped.

@Sju Actually is already pretty simple. You just have to put the right file in the right folder and hope it is running :D For the end users, no need to run Git ot whatsoever. GitHub and ReaPack indexer is for the coders only. It is more documentation than ReaPack itself that need to be simplified :p But we cannot write full docs until we didn't get to a v1.0 with "definitive" behaviors :) WHen v1.0 will came out, I'll create a detailed article on my website, and maybe some users (reaperblog ? :)) could make a video of it :)

Great work!