It’s very impressive. I’m really looking forward to it.
1 Like
Oh wow. My guess is that you won’t run out of coffee any time soon 
1 Like
he he… 
so this ones quite fun… the idea is to be a mixer that you can use to control final mix, and sub mixes.
quite a lot of uses… e.g. Ive got it mixing physical audio inputs on SSP with granular generated on SSP.
then use the aux channels to decide what is going to a reverb or clouds, or to a physical output (e.g. my octatrack)
an ‘added bonus’ is you can set an input track to AC/DC, if its marked as AC (the default) then it has a DC blocker - this means if you chuck a RVB on an aux you don’t need a HPF anymore
(also generally the mixing of audio is considerable clearer without DC offsets)
Im considering a change to the output tracks…
currently its :
- 8 mono IN (w/ pan) -> Main (stereo) + Aux 1-3 (stereo)
though I thinking of changing it to
- 8 mono IN (w/ pan) -> Main (stereo) + Cue (stereo) + Aux 1-2 (stereo)
then there will be a CUE button for a track, which will mute the output on MAIN, and send to CUE output instead. (then un-cue will do the reverse)
this is useful for ‘previewing’ behaviour and its also useful when you have modules/external instruments that might be sending a ‘monitored’ output back.
btw: the 8 in/4 st out is very deliberate, as it means with the 3 track buttons, you can instantly change things like levels… as this is ‘performance’ oriented, i didn’t want you to have to start ‘paging’ thru channel pages.
I’ve still to do some more ‘behavioural testing’, where I play with it in my real patches, to see if if feels and behaves as I want it too…
theres a bit of a balance here, I want to keep it fairly light (cpu), and also not have a ton of options on it… but the more I play the more I see how many options a modern mixer has
also… the SSP (and eurorack) is modular, so whilst I want this to feel ‘complete’, its also possible I’ll want to supplement it with other modules… rather than put everything into one module.
anyway, its pretty close - and I do think/hope many will find it useful.
tip: I always put it on page 1/slot 1…
that way, whenever i load a patch, pressing P takes me straight to the mixer
6 Likes
I’m thinking of making a slight change to the buttons…
currently,
Im using red on black (invert on active)
what Im thinking of doing is changing it so that :
for black SSP buttons - white on black (invert for active)
for RED SSP buttons - red on black (invert for active)
possibly also shift buttons might be white on dark grey (vu meter background colour)
this is a bit of a departure from SSP modules,
but the idea is it’ll help the user ‘see’ the relationship between physical buttons and the virtual buttons.
I don’t know why, but sometimes I find myself look at the screen, and pressing button 4, rather than left shift.
and Im wondering if this might help.
thoughts?
I’ll probably just have to ‘give it a go’ and see if I like the look or not.
I think it might not look quite as tidy, but may help orientation a little - as a block of 2 x 7 similar buttons is a bit large perhaps.
(this change would then be reflected in my other VSTs on next update)
2 Likes
I vote yes, I do the same thing with pressing the wrong button. Something visual is not quite gelling and what you’re describing sounds like it would be clearer.
yeah, I think it looks better…
this is on my mac, but it’ll look much the same on the SSP… (only difference is it always looks a bit smaller :))
(-EN would not normally stay inverted, but its useful to see what the inverted red looks like)
what’s nice i think about this colour scheme is the block of 8 black buttons is nice and clear.
strictly the LS/RS should be black/white, and ‘menu’ buttons , should be white/black to reflect physical buttons.
but I think this is a bit clearer - it kind of highlights ‘system’ buttons vs, ‘user’ buttons.
at a future time, I might reduce the size of the buttons, and also the encoder text a little…
I wanted them to be same as SSP modules - but I think they could go down one size, and still be very readable.
it would also allow for a little more text in them, assuming i dont reduce the bounding boxes, which is tempting too 
3 Likes
Is it (MIDI) remotely controlable?
I”d expect a send level (aux) on the IN bus, but i don’t see it (?)
Per channel button(s) aka nr(s) for which OUT to send to would be pro/fab
So you could choose to send ch IN1 to 1/2 and 3/4, IN2 to 1/2 & 5/6, IN3 to 1/2, 3/4, 5/6, IN4 to 5/6 etc etc
Why (again) boxes for MUTE /SOLO (right below) if you have those ‘checkboxes’ on every channel already?
vst’s on the ssp cannot receive midi
(well i could probably make it so they could , but the idea is they use cv instead)
there is a send level on every in channel for each of the aux buses (1-3)
the reason for repeating the mute/solo is the main view shows all channels at all times,
the ‘buttons’ are for changing the state, and only show 4 channels at once (as there are only 4 buttons)
when its released, it’ll make more sense
1 Like
oooh that looks awesome!
Will the master sections have the option to link l/r balances or will they always be independent?
let me rephrase then : can levels/sends/pans be CV controlled?
to permanently show out levels (in numbers) can maybe be a good thing
are the LED/bars of the instantaneous or hold type ?
what levels are they representing/calibrated for? (peak/RMS /ROHM/…)
not currently, since sdk v1 only allows 8 in/out (as has been previously discussed)
in v2 this will hopefully change.
currently RMS, as they felt better than peak.
based on a short window
I had the rms number displayed (I think thats what you mean) but didn’t like it much, but may add it back…
I do want to keep the UI simple/uncluttered, so thats always a ‘trade-off’ once you started having 8 channels, its easy to get a bit too much going on. e.g. I don’t want to use tiny fonts, which would allow more data on it
generally, my ‘inspiration’ for this is more something like the WMD Performance Mixer - though features will vary according to whats possible etc - I am not trying to create a DAW like channel strip -I think given the physical aspects of the SSP , imo, that would be a mistake.
you mean on the input side? (outputs are always stereo)
I’m toying with this, the underlying code supports this ( as you can see on the output side)… its just a matter of adding a l/r offset when channels are linked - so, I might add, as its relatively simple.
however… its not optimal, since the encoders would end up duplicating functionality, rather than separate channels. e.g. enc 1 & enc 2 would both change stereo pair,
this is because otherwise the UI metaphor breaks…
e.g. imagine ch1/2 stereo rest mono
we’d get
enc 1 = ch1/2 stereo
enc 2 = ch3
enc 3 = ch4
enc 4 = ch5
we can see relationship between the encoders is completely broken.
so Im not doing that
so i might do the ‘linking’, as i agree its handy…
however, Im also thinking that once this has been released/stabilised, and also adapted for sdk2.
then I might create a stereo variation of this… where all input channels are stereo (with mono to stereo on input if required) or perhaps a variation like the WMD which has some stereo, and some mono inputs.
the advantage of using stereo channels is when we have more cv inputs available, you can control more with less. eg. vca on 8 mono tracks is 8 extra cv, but a vca for 4 stereo tracks only requires 4. (*)
(*) I believe we will always have a limited number of cv inputs, so this is always a compromise… unless, I start using a mod matrix, which I’m not planning on at this stage (partly as it breaks the modular metaphor a little)
2 Likes
Well not much input from me except a big thank you, this is absolutely fabulous, to be similar to the WMD and then stereo with sdk2, this is getting. To control with MIDI if this is implemented to VST would be he cherry on the cake. Great work
1 Like
not sure if @bert has any plans to send MIDI messages to vsts in the future.
I don’t think any SSP module (except MIDI obviously ;)) has access to midi, generally the parameters of a module are only controllable via the UI and via CV.
perhaps one day MIDI learn could be added to the base SSP architecture to allow for parameters to be controlled that way - but that may not be possible (it assumes a common notion of module parameter which may or may not exist)
as i said though, potentially I could connect directly to midi devices (in the same way I assume MIDI module does), but it would be unable to coordinate its activities with the MIDI ssp module… so is a bit limited in use - but might be ok for midi learn type functionality.
anyway its not on my immediate plans - which I think are better focused on cv inputs as thats a more ‘modular’ approach
2 Likes
If you want to control VST modules using MIDI, you first insert a MIDI module in the grid, then send the modulation signals from the MIDI module to the VST input channels. If you need more MIDI CCs, you just insert multiple MIDI modules. Possibly you might also want to use the BUS module depending on what you want to achieve. Sending MIDI directly to the VST plugins is something i’m not planning on doing, the idea is that you convert MIDI to virtual CV signals which you then process and route in the SSP’s grid. So in a sense the VST support is there to make it easy for people to make modules for the SSP, but the idea is not to turn the SSP into a full-blown desktop DAW, with all the traditional things that a DAW on a desktop would do. Since the SSP lives in the eurorack world, it behaves as such and needs to be compatible with the eurorack way of thinking.
1 Like
Sorry, mis-read the topic on MIDI, absolutely CV all the way as it is modular
things are still bubbling (or boiling!) along in the background - pmix will be here soon 
published a small (public) update on my ko-fi page
6 Likes
Yay, release day is upon us…
Clds and Rngs have been updated to use the new VST SDK that’s being released.
Also, I’m releasing PMIX, the performance mixer today.
This has really changed how Ive used my SSP, so Im really excited to share with you.
these are all built on the new firmware/sdk that is being released today,
this firmware is very exciting, as it really extends what vsts are capable of on the SSP.
so huge thanks to @bert for these fantastic updates.
note: because all 3 of these plugins make use of new features in this firmware, you will need to update your SSP firmware.
so please update your firmware here
also if you follow me on instagram or ko-fi, you’ll have seen a sneak peak of my next vst
I’m planning on putting up a better demo on my youtube channel very soon (today!?)
so subscribe to my youtube channel if you want to catch that.
again many thanks to those that support me on ko-fi.com , I really appreciate your support. follow me there for more frequent updates…
happy patching.
Mark
9 Likes
awesome work! really excited about these and congrats on the release of the 2 updates as well as the new module
4 Likes
Heroic, sir. Simply heroic.
4 Likes
Contratulations, Sir, this really rocks.
2 Likes