You can load it (I’m on 1.1.1). Haven’t tried it yet- is it fully implemented?
I patched it up, and didn’t seem to do anything , and had 0% dsp load.
so, I took a look at GitHub… and there is no dsp code for it on main branch (used for release), its just a stub with the UI code present.
some dsp code is in async-sts branch , it’s a wip - I didnt look close enough to say how near it is to ready.
I suspect, it’s an oversight that this stub code got included in the released firmware ?! (its in 1.1.2 as well)
note: ofc, always a possibility, that dan has some code that’s not in GitHub that was used for the 1.1.2 release and I got my patching wrong.
Says experimental but no links so I interpret it as something to come but not available now. Also Sample Pack!
the confusion is, its available in the module browser on the MM with current firmware.
Yep. To comb through and be thorough 100% about everything at this time could be challenging due to bandwidth and prioritisation - havent we heard about these two delayers of stuff. 4MS interim file to get us by while VCV gets them into their latest update (as default) might have caused it.
4MS could issue a statement that certain modules are being planned for future. We could also help by clarifying that with those who asked. Hey, we are all invested in the MM right?
As far as I’m aware, the STS is what is coming. Dan said Catalyst and SWN won’t be coming, and he hopes to get Prism (the SMR port in VCV) onto Meta Module in the future.
1 Like
Sorry for the lack of communication here.
It was an oversight to leave the STS in the firmware list of modules, as it doesn’t do anything! I will remove it for the next version, I know it’s confusing to see a useless module in the list.
I do have a branch with the STS working, both on VCV and on hardware. But the UX is not so fun when going from VCV rack to the MM, and not all bugs are worked out.
The basic concept is that I want to be able to have a patch with multiple STS modules, and each one can have a different sample library.
I settled on letting you choose within each module one of multiple folders called “Samples-1”, “Samples-2”, etc… which must be present on an SD card or USB drive. Or you can choose “Root Dir” which uses the original STS SD Card format.
As I played with it, I realized it would be immensely more useful if it had a screen. The color = bank paradigm of the STS doesn’t translate so well to the MM screen. So I made a version with a screen, that’s playback only. I’m calling it the STSP (Stereo Triggered Sample Player). This is the current state of that:
Don’t take this too literally, the controls and layout is subject to change!
As you might have guessed I didn’t get it stable before release date, and I had to put it on hold to fix all the bugs and add quality-of-life features for v1.0 and v1.1. But the STSP not forgotten, and will be coming out soon™ 
9 Likes
I love the screen! Thank you!
Yay for incoming STSP 
amazing, cannot wait for STSP! one of the reasons i got the mm’s was to do heavy sampling. i’m curious will there be a “disc streaming” option to leverage larger longer files or is it a “whatever can fit into ram” kinda deal?
It does “Disk streaming” into a RAM buffer. Pure “RAM streaming” is a lot more simple, but that means you have to have smaller sample libraries and/or have a long delay if you switch banks.
1 Like
awesome ty! so then im curious, from the manual: “Maximum file size for playback: 4GB per file (6.7 hours per file at 44.1kHz/16b/stereo)” - will that also be the case with the stsp on mm? not that i could imagine ever having a need for playing something that crazy long 
Yes, because it’s streamed from disk
1 Like
ty for the dbl confirm on that… very exciting!!
Around how many of the STSPs do you believe the MM be able to load?
Would it be around 1, 5 or 10? Just trying to figure out if it could be used as a cool drums/percussion setup.
You can include a lot of sampler modules in a patch. Probably at least 8 (it’s not final yet). For percussive samples, which are usually short, disk access times won’t be a problem since short samples are loaded into RAM.
2 Likes
Nice, so plenty of room for a couple of samplers and a PEG or LFO to create movement in the sound.
Just bought an MM 
1 Like
oh wow, really looking forward to putting mm through some paces with STS x8!
wondering if we can build a Digitakt within the 4msMM…
Great to hear this will be available.
Curious also whether there may one day be a ‘multi-sampler’. I.e., a sampler that has many samples across the range, for example to create a somewhat realistic sounding piano sound. Or maybe there’s a solution with having say 8 STSP’s and some way of creating zones elsewhere that funnel MIDI to the correct sampler out of the 8 in there?