Modules with updates

[dromer]

Description

The following modules have updates that we can integrate.

Bugfixes:

• AudibleInstruments (CardinalModules)
• Bogaudio
• Bidoo (CardinalModules)
• Biset (CardinalModules)
• ChowDSP (CardinalModules)
• MockbaModular (tiny fix)
• HamptonHarmonics
• ML_modules
• Orbits
• AaronStatic (tiny fix)
• forsitan-modulare
• h4h4-modules
• HetrickCV (2.4.1 - double precision)
• MindMeldModular (2.5.0 - CardinalModules)
• Surge Rack (2.2.1 -> 2.2.5 - CardinalModules)

Features:

• JW-Modules (dark panels)
• ImpromptuModular (features + fixes - removed SMS16 so needs additional work)
• BaconPlugs (features + fixes)
• sonusmodular (features + fixes)
• LilacLoop (expander + model rename - CardinalModules)
• Fundamental (bunch of new modules and other features. requires custom panels)
• Meander (mostly fixes and two new modules)
• alefsbits (couple fixes and many new modules)
• EnigmaCurry (new module)
• Befaco (couple fixes and new modules)
• ComputerScare (2.1.11 - Toly Pools v2 - v1 is hidden)
• kocmoc (2.0.6 - new module and bugfixes)

Minor:

• LyraeModules (internal renaming)
• Little-Utils (some changes to port behavior)
• nonlinearcircuits (small refactor and svg renames/changes)
• ZZC (tiny fix)
• PathSet (rename of variable)
• AmalgamatedHarmonics (small UI updates)
• MockbaModular (2.0.1 - tiny fix)

[falkTX]

voxglitch is finally updated, I looked at Fundamental but dont quite think the new modules are worth it

[dromer]

I think we should try to have all fundamental eventually because users really expect those to be there from the start, but maybe not for this 24.09 release as it requires panels etc.

[rl2939]

You might want to add Befaco to the list, because v2.8.0 adds two new modules (Bypass and Bandit).

It might also be worth converting this list of bullet points into a task list so that the issue tracker itself can display how many tasks are left in the issue.

To create a task list, preface list items with a hyphen and space followed by [ ]. To mark a task as complete, use [x].

- [x] #739
- [ ] https://github.com/octo-org/octo-repo/issues/740
- [ ] Add delight to the experience when all tasks are complete :tada:

https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists

[rl2939]

Some extra notes (on modules that I am not able to update, maybe this will help you in updating these modules):

• The current versions of MindMeldModular (https://github.com/MarcBoule/MindMeldModular/tree/8136f0c941b41c57af70a5ebb5839f0086518b2b) and Lilac Loop (https://github.com/grough/lilac-loop-vcv/tree/cf9bb5cfa5fd41ecfc9976bb106c2f4a7667c9d7) both point to commits that are not part of a branch. This is significant because it makes it hard to update while keeping the Cardinal specific changes on the modules. Should we move Cardinal-specific changes to CardinalModules and git add the submodules there?
• alefbits complains about a missing include mutex statement on compile time
• Befaco has a similar complaint about not being compiled with c++ 17, along other errors.
• One of BaconPlugs new modules returns an error because it can't find a file (HilbertTransform.h) that does not exist:

Compiling BaconPlugs/src/BaconTestModule.cpp
BaconPlugs/src/BaconTestModule.cpp:5:10: fatal error: sst/basic-blocks/dsp/HilbertTransform.h: No such file or directory
    5 | #include "sst/basic-blocks/dsp/HilbertTransform.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [Makefile:2229: ../build/plugins/BaconPlugs/src/BaconTestModule.cpp.o] Error 1

[dromer]

You might want to add Befaco to the list, because v2.8.0 adds two new modules (Bypass and Bandit).

This list was created some time ago, so it is of course never fully up to date. By the time we are done with it some of the modules have likely updated again.

It might also be worth converting this list of bullet points into a task list so that the issue tracker itself can display how many tasks are left in the issue.

Good idea, have done that just now. Then when modules need updating again we can "un-check" them so they become active tasks again ;)

[dromer]

This is significant

Not really. We keep these forks around in https://github.com/CardinalModules organization.

We do try to push Cardinal specific changes upstream, but as long as these devs don't merge our changes we will have to keep our own forks around.