Repair team

[AndrewBelt]

The Repair team is the first VCV Community team to launch. The goal is simple: For each open-source plugin in the Plugin Manager, help the developer by sending a pull request that makes it build against the latest master branch of Rack. If you are not quite familiar with GitHub and git, the procedure is the following.

• Make sure to git checkout master and git pull the latest Rack source code, and build it.
• Pick your favorite plugin and click Fork on its GitHub page.
• git clone the forked repo in your plugins/ folder.
• Inspect the code, and apply the changes mentioned in the Plugin API Updates Thread
• Update the form of the Makefile to follow the Template Makefile, including the RACK_DIR which will be useful later.
• Try building it with make -j$(nproc). If you changed everything correctly and it finally builds, make a commit with a message like "Updated to Rack 0.6 API", and git push.
• On your GitHub fork, click "Create Pull Request", and submit it back to the plugin developer.
• After the plugin developer accepts your pull request, you may delete your personal repository.

[cschol]

This post contains the list of all open source plugins in the community repository that need to be validated against the v0.6 API.

If you are interested in helping per @AndrewBelt's instructions above, please

1. Post below with module name that you are working on, so other developers know that it is being taken care of. I will take care of keeping the list up to date with checking off plugins from the list.

2. reference this issue (link to: https://github.com/VCVRack/community/issues/269) in your Pull Request to the plugin repository so we can track the Pull Requests and their completion.

If you are a PLUGIN DEVELOPER and you know you would like to handle the conversion to the v0.6 API yourself without the help of the Repair Team, please comment below.

A checkmark means the plugin is actively being worked by the Repair Team OR the developer has decided to do the update themselves.

Once the plugin is confirmed to be migrated to v0.6, i.e. source code is available in the developer's repository, the plugin name will be marked bold and a clone url will be added. Once the plugin is building on all supported platforms (Linux, Windows, Mac), the plugin will be crossed off the list.

PLEASE NOTE: Once a plugin has been MIGRATED TO THE NEW REPOSITORY structure, the plugin will be REMOVED from this list! It will be re-added if further issues are found that need attention.

Last update of plugins: 9/1/2018

Remaining plugins:

• [x] CastleRocktronics (3/25/18 PR pending)
• [ ] dekstop (3/21/18 Should follow the Fundamental example to include libsamplerate as a dependency for the plugin)
• [x] JE (3/25/18 PR pending)
• [x] PulsumQuadratum-rtlsdr
• [x] StellareModular-Link (3/18/18 Depends on 3rd part library, reported to developer)
• [ ] IO-Simple (7/30/2018 has graphics issues and requires slug update)

Additional plugins (not in community repository yet):

• [x] JLmod | clone url (3/25/18 Needs VERSION update, reported to developer)
• [x] Via For VCVRack | clone url (4/8/18 Pending intergration into community repository)
• [ ] TechTechTechnologies | clone url
• [ ] JEM-Modules | clone url

[dhemery]

I develop DHE-Modules, and have completed the conversion myself.

[cschol]

@phdsg Oops. That was an artifact of how I generated the list. Removed. Thanks.

[AndrewBelt]

Looks great, I'm working on mine. People can't check your own checkmarks, they'll just have to post here.

[cschol]

@AndrewBelt Crap, I was hoping they could. I'll keep the list up to date from people posting here below. Updated the instructions above to have people post the name of the module they are working on.

[wizardishungry]

PulsumQuadratum-rtlsdr: I'm doing it myself. (It also needs to have its dependencies built as git submodules before it will build without special instructions)

[Strum]

@cschol

I'll do mine myself, and can help with others if you need it.

[cschol]

@Strum Thank you. Which ones are your's again?

[AndrewBelt]

Added one additional instruction to make sure that your Makefiles are up-to-date and follow the Template Makefile or the Fundamental Makefile.

[Strum]

@phdsg thanks.

[luckyxxl]

@cschol fixed mine just now

[mdemanett]

Bogaudio is up to date. Cheers.

[djpeterso23662]

I will take care of MrLumps. Thanks!

[alikins]

I have converted my plugin ('Alikins') to the 0.6 API in it's master branch.

[alikins]

Pr for mtsch at https://github.com/mtsch/mtsch-vcvrack-plugins/pull/5

[dllmusic]

I will update moDllz... just waiting to see how the MIDI is implemented

[cfoulc]

cf - working on mine, may need some help at some point, will ask here and/or there EDIT : done, everything working fine and uploaded to my repo :)

[gbrandt1]

i'll work on mine (Southpole) - the update will depend somewhat on the various MI / Parasites repos i copied from

[jhoar]

I've done AmalgamatedHarmonics.

[cschol]

Thank you for the PR @alikins!

[AScustomWorks]

I'll work on mine

[antoniograzioli]

I am updating my plugins, started a couple of days ago, I will (hopefully) finish them tonight. Bear with me I am quite busy and there are quite a lot of changes to be done ;-) also, my https://github.com/antoniograzioli/Autodafe repository is a complete mess, and needs to be erased completely...

[Strum]

ok mental modules are done, the new code is on the 06dev branch.

[wizardishungry]

Is AudibleInstruments building for people? I.e. should it be unchecked?

[cschol]

@WIZARDISHUNGRY "Checked" means "somebody is working on it" (in this case @AndrewBelt). Once plugins are confirmed to be building against v0.6, I'll cross them off the list.

[DomiKamu]

Ohmer Module can compile against 0.6.0dev without error/warning, but Git fork and Co. hum... is like Chinese language for me!

I don't want to touch current release (0.5.3) on my repo, I've created a Pre-release 060devhere and posted related source code, but as usual here I'm lost in the Matrix! ;)

[AndrewBelt]

@cschol Could you add the checked/strikeout note in your main post?

[antoniograzioli]

Done upgrading my plugins at least on MAC (phewwwww) Tomorrow morning I will (hopefully) compile everything for Windows and Linux. getting ready for 0.6 :-)

[Strum]

@antoniograzioli

well done.

[alikins]

If someone wants to take a crack at 'dekstop' plugin, https://github.com/dekstop/vcvrackplugins_dekstop/pull/17 has a incomplete pass at it. Not sure how to handle the templates in dekstop/src/Recorder.cpp correctly...

[cschol]

@alikins Thanks for the PR! Sent you a supplemental PR to that port_to_v0.6 branch to finalize the dekstop plugin conversion.

[DomiKamu]

Hi, as I've indicated yesterday, unfortunately the "fork" story isn't clear in my mind. However, source code against v0.6.0 is placed in new branch (060dev): https://github.com/DomiKamu/Ohmer-Modules/tree/060dev

If somebody can explain clearly what I must doing, be sure it will be appreciated, thanks in advance.

[DomiKamu]

@phdsg I've deleted the posted reply, so please apologize me, you've understood I'm totally lost in this "can of worms" (I see GitHub like this, really isn't user-friendly in particular for unexperimented users). Also the initial message was not for me, I've understood but late, BTW sorry again x 1000! ;) :-)

EDIT: on second thought, I've replied (quickly) because your message above was a reply... on mine, as you've said :-) :-) sure it's not your fault.

[dizzisound]

PR sent for RODENTMODULES #https://github.com/RODENTCAT/RODENTMODULES/pull/3

[cschol]

@DomiKamu If you have updated your plugins yourself you don't need to worry about the "fork" part. Once Rack v0.6 is released, you can merge your 060dev branch into master and release the new version. "Forks" are only required if someone else was going to update your plugin and wants to send you a Pull Request with the changes.

[cschol]

I have decided to change the plugin list format a little bit, see the updated notes in the post above.

The plugin API conversion is progressing nicely with developers making changes as well as PRs being created. As PRs are merged and developers are done making their own changes, the next step is to start building the available source code on all supported platforms to flush out any potential cross-platform issues.

I will mark plugins ready for testing (with clone url) and the platform where the build/test has been successfully completed.

Any help in building available plugins against v0.6 once the plugin source code is available is much appreciated. Check the list, pick a platform that has not been tested yet, build the plugin source code from the developer's repository, and report any issues to the PLUGIN DEVELOPER. Success can be reported in this thread.

[AScustomWorks]

I finished the update to AS modules(tested on Mac), but branches and tags are still too confusing for me. If someone wants to guide me thru it I'll do it, otherwise I'll wait, thanks.

[cschol]

@AScustomWorks Are your changes committed?

[alikins]

I've built my plugin ('Alikins') for v0.6 on lin/mac/win and tested on linux and mac.

[AScustomWorks]

@cschol not yet

[phdsg]

@cschol update: 2018-02-27 some false positives slipped in yesterday, because i still had headers in rack's /ext dir that were moved to /dep in one of the last commits. so bidoo's ouaive(fixed 2018-02-28) and cf's PLAYER(fixed 2018-03-01) should've failed with a wrong include path, but didn't.

---

working, unlisted

• Bacon Music - all platforms: good
• JLmod - all platforms: good

[cschol]

@phdsg Thank you for testing and the PR.

[cschol]

@phdsg You can edit the post if you are planning on keeping on testing on Linux. I'll check your post.

[cschol]

Checked just means somebody did work or signed up for doing work. If the module is bold and the clone URL is available, the source code is publicly available and the module is ready to be tested on all platforms. I'll clarify in the post above later today.

[sebastien-bouffier]

Hello, I am developing bidoo plugins and I started the upgrade to 0.6. I target to push my code to github this week-end. I think it should be ok on Win and Lin but I expect some issues on OS X since my last release doesn't work on all OS X versions. Best.

[The-XOR]

0.6 is already available in the osc branch; will merge in the master branch soon

[AndrewBelt]

Fundamental, Befaco, ESeries, and AudibleInstruments are updated to the Rack 0.6 API

[AndrewBelt]

This issue is for community/management discussions only. Off-topic comments will be removed without notice. Open an issue in the respective repo for issues about that repo.

[AndrewBelt]

Not that it matters now, but I've ported Grayscale, PulseMatrix, and Console, and builds will be available upon the 0.6 release.

[The-XOR]

v 0.6.0 now on master branch