cool,
if its already in rack SDK (i.e not a MM specific), I may already be Im already using this, so it’ll “just work”™
I’ll double check - thanks 
We’re getting close to releasing this. Recently added polyphony to most 4ms modules (all the ones it makes sense to), and fixed a number of issues. Poly cables are now shown as extra-thick on the patch view, so they’re easier to spot.
Here are the latest builds:
VCV plugin:
7 Likes
Great work here - looking forward to the final release!
fantastic news… looking forward to this.
btw, to help manage expectations a bit…
are you going to update modulefinder to indicate if simd support is included? or some metric of polyphony impact?
as you say in original post, those with simd could be efficient, but some modules might not be so kind to the cpu - and so users, could get variable results depending on the modules they use
I think one ‘minor’ issue here, is we cannot see per module load on the MM (unlike vcv), so the culprit may not always be obvious.
frankly, we already see some with unrealistic expectations (with patch complexity).
Id hate to see a great new feature, be used against the MM rep.
I guess “With great power comes great responsiibiltiies”
2 Likes
That’s a good idea to add CPU numbers for use with poly in the Module Finder.
And yeah, I’ve had a back-burner idea to show per-module cpu numbers in the patch info dialog.
3 Likes
I added cpu tests for poly jacks (I’ll update the website at the same time), and fixed a bunch of bugs.
Here’s the latest release candidate:
https://github.com/4ms/metamodule/releases/download/firmware-v2.2.0-rc3/metamodule-firmware-v2.2.0-rc3-firmware-assets.zip
Also updated the VCV plugin (includes all 4ms modules being polyphonic, and two features from @gabrielroth: letting you type in a min/max value, and persistent user settings)
4 Likes
Hi Dan, excited to try this. Am I correct in understanding that I can lift the 4 channel poly limit on a local build if I just bump up rack::engine::PORT_MAX_CHANNELS, or will that break things?
I haven’t tested that yet but in theory it should work. You will need to do that for the firmware and for the plugins and rebuild everything.
Oh you also have to change the MaxPoly number in CoreProcessor
Could this be an option eventually maybe?
Handy if you’re just using the MM as an oscillator and doing filtering, envelopes etc outside of the box.
For sure, the plan is to have full polyphony for v3.0 firmware. All plugins will need to be re-compiled (plugins for v2.x will not work)
1 Like
Great to hear it!