-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repair team #269
Comments
This post contains the list of all open source plugins in the community repository that need to be validated against the If you are interested in helping per @AndrewBelt's instructions above, please
If you are a PLUGIN DEVELOPER and you know you would like to handle the conversion to the 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 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:
Additional plugins (not in community repository yet): |
I develop DHE-Modules, and have completed the conversion myself. |
@phdsg Oops. That was an artifact of how I generated the list. Removed. Thanks. |
Looks great, I'm working on mine. |
@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. |
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) |
I'll do mine myself, and can help with others if you need it. |
@Strum Thank you. Which ones are your's again? |
Added one additional instruction to make sure that your Makefiles are up-to-date and follow the Template Makefile or the Fundamental Makefile. |
@phdsg thanks. |
@cschol fixed mine just now |
Bogaudio is up to date. Cheers. |
I will take care of MrLumps. Thanks! |
I have converted my plugin ('Alikins') to the 0.6 API in it's master branch. |
Pr for mtsch at mtsch/mtsch-vcvrack-plugins#5 |
I will update moDllz... just waiting to see how the MIDI is implemented |
cf - working on mine, may need some help at some point, will ask here and/or there |
i'll work on mine (Southpole) - the update will depend somewhat on the various MI / Parasites repos i copied from |
I've done AmalgamatedHarmonics. |
Thank you for the PR @alikins! |
I'll work on mine |
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... |
ok mental modules are done, the new code is on the 06dev branch. |
Is AudibleInstruments building for people? I.e. should it be unchecked? |
@cschol Was the submodule for Valley updated? Apparently my commits on branch v0.6 are ahead of the submodule |
Starting now, all plugin developers need to follow the instructions at https://github.com/VCVRack/community#for-plugin-developers-addingupdating-your-plugin to update your plugins from the state in the Plugin Manager. PRs will no longer be accepted from anyone except team members, and this issue is now limited to only Repair Team members. |
Never mind. I understand now why this was done. I will create new PR(s). |
Sorry, I have been out of town for a few days. Plugin list has been updated. @phdsg qwelk and LFSR should be ready for integration into the community repository. |
@cschol Welcome back! |
makefile versioned 0.6.1 |
IO-simple has merged changes for 0.6 compatibility. |
@phdsg Yeah, sorry, work/life gets in the way right now. :) I updated the list and crossed off |
@phdsg Is Nohmad just waiting for a build or is there anything else wrong with the plugin? |
it's not added as a submodule because it wasn't ready during the transition and the dev hasn't opened an issue here yet. there are a few more of those cases. i'll spend a few moments in the next days to invite them to open their channel here if they want to be added to the plugin manager. |
Ah, I see. Sorry, been trying to catch up here. Thanks. |
Hello! Andrew... you suggested I post to this thread (to offer assistance on lowering the 20+ manhours.... ?) 👍 . Looks like this thread is a little errrr. musty with age? Last posting was for yikes! May of last year? I'm not sure what exactly a "bounty" consists of..... but How might I be of assistance? |
@JeffGreenlee42 Well, there hasn't been much to repair so therefore there is no activity here. I am still a little confused as to what you are exactly looking for. Can you elaborate? Thanks. @AndrewBelt I read the thread on Facebook, but I am confused what the time would be used for. Update manifests to the new |
@JeffGreenlee42 Oh yes, I forgot to respond to this. Didn't you mention on Facebook that you wanted to offer a financial bounty (or perhaps encourage other people to do so) for the Repair Team's time here? |
Oh... My apologies,. I was not offering financial support.... ( I am dry as
a turnip) but I read in the thread that you might need "manhour"
support..... Just folks who might be able to do tasks to lower the burden.
I am a software tester..and errrr.. well it takes a village.. . So maybe
some of us could help?
Jeff
…On Fri, Jan 11, 2019 at 6:24 PM Andrew Belt ***@***.***> wrote:
@JeffGreenlee42 <https://github.com/JeffGreenlee42> Oh yes, I forgot to
respond to this. Didn't you mention on Facebook that you wanted to offer a
financial bounty (or perhaps encourage other people to do so) for the
Repair Team's time here?
But yes, it's dead here because all interesting plugins we know of have
been ported to 0.6, so we're just waiting on the Rack v1 API to become
stable to begin helping AWOL developers to upgrade their code.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#269 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AVifXaHeDKDXazzeKVpUAXAojfM6pBXkks5vCUdYgaJpZM4SFm1L>
.
|
Oh yes, you can certainly join. Just subscribe to this thread and wait for new information when the Rack v1 API is stable. |
I seem to be the first to revive this thread :) |
@catronomix That had happened to me before for unknown reasons. The solution was to simply proceed with phase 2, and it will magically fix itself. |
@AndrewBelt in this case, it's a little different:
but specifics being a custom component. |
but yes, I ran into the deprecated wrappers issue, and pressing on fixed those issues. |
@JerrySievert I moved the initialization of recball_x and recball_y to the constructor of recball like this:
and in the plugin hpp:
Which didn't fix the crash. Then I followed @AndrewBelt 's advice and proceeded with the conversion as per the manual. It all builds fine but the crash still happens. I'm on Windows 10, using VSCode and then mingw/gcc to compile with make dist and then I copy the plugin to the rack plugin directory to test if it works. But Rack always crashes without showing any error. log.txt also never showed me any errors ever :/ I would like to debug my plugins to see where things go wrong, but I dont find a tutorial on how to debug.Only bits of info in issues like these https://github.com/VCVRack/Rack/issues/172 but I can't make heads or tails of it. |
@catronomix I'll open a PR on your module in your repo, and continue the conversation there. |
If you look on the developer FB group, I posted asking about debuggers. There was quite a bit of response that should help you (I’m using VSCode too) |
yep lots of info. the super basic is:
look at the screen and figure out what happened. Or google "gdb cheat sheet" |
but how does it know where to find rack? because thats installed in windows, but the plugin gets compiled in my dev folder where the rack sdk is located. I guess I have to compile some debug version of rack inside the dev folder as well? |
Closing since the VCV Community forum is a better place for discussing adopting plugin maintenance. |
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.git checkout master
andgit pull
the latest Rack source code, and build it.git clone
the forked repo in yourplugins/
folder.RACK_DIR
which will be useful later.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", andgit push
.The text was updated successfully, but these errors were encountered: