yeah the post (and the plugin dev manual) talks about using mm when designing panels, but i wasn’t sure if it applies to code as well. from what i can tell it does expect mm to be used, including nvg stuff, but then why does it convert to pixels (using mm2px) when creating inputs/outputs etc? i thought maybe it’s because these functions haven’t been converted to use mm but then even vcvrack’s own set of plugins has examples of both using same functions without pixel conversion and with conversion. it could be that not everything has been updated yet but that’s why i want to find some concrete info. i’ll ask on the vcvrack forum as well.
thank you. i thought it would be like this guess i have to make a whole seperate fork lmao. because of the main developers personal use case lmao.
edit: i am still new to open source software uhhh diplomacy? is it worth it to make a really good case for it and submit an issue again or a pull request to try to integrate whatever i come up with into the main branch. i personally think the favorites feature is invaluable, even if your favorites are changing all the time…
you can change the location in the code easily but if you want to take advantage of the helper script just use a different component type to get coordinates generated for you and then replace the components with screw components in the code.
and helper is a python script so adding support for new component types should be very easy. i modified it so that it generates code using my own custom components, this way i don’t have to update each time i update the panel.
sure. i would do some work to factor the core functionality into a separate repo (static lib target.) there are a number of improvements coming into the upstream (norns) version and i don’t want to have to manually sync them.
Has anyone run through the plugin dev tutorial lately? I just did on Mac w/ 1.1.6, using the Rack-SDK method instead of compiling Rack.
There’s a step about adding the module to plugin.cpp & plugin.hpp that’s in the output from the helper.py script, but otherwise the tutorial seems solid. That said, I’ve compiled and installed the tutorial module but it’s not showing up in the Rack module browser.
Is there an issue with the tutorial? Do I need to do something to Rack to trigger a re-scan of the available modules?
EDIT: Fixed. I had installed a bad build (before I found that extra bit in the helper.py output) and it was creating a namespace collision. NOTE: Logs are helpful. ~/Documents/Rack/log.txt if you’re looking.
EDIT2: I’ll submit a doc PR to add that helper.py bit.
Great, thanks! I think I want to tackle that then after I get farther along with the Nonlinear Circuits port.
This might be worth starting a separate thread, but I’m thinking that it might be fun to start a Lines Community VCV Plugin, with VCV module ports of a lot of the tools created here that would work well with “hardware” interfaces. Some ideas (and tagging for opinions):
I was recommended this thread for the first time today, and I wanted to add that WW, MP, and ES are in the pipelines, just not in the official library. There are interfaces for grids from what I can tell too.
Hello. Just dropping by to say thank you for this thread. I’ll be making regular use of these collected resources. I have idly entertained a module idea for a year or two and am now motivated enough to put to the test the claim on VCV’s website that ‘creating Rack plugins is a great way to learn programming and C++’. Cause at present I know nowt about it. I have nothing to lose, some knowledge and a module to gain.