Ins and Outs

yeah, I think it depends on how you use the SSP.
e.g. Ive been doing quite a bit of mixing recently, so that ‘eats’ up IO quite quickly, its also relatively light on CPU… ( so you run out of IO before cpu :slight_smile: )

I’d say generally, the SSP is well balanced for IO, considering UI and cpu/ram…
but I’d think an expander would sell well with SSP owners.
(but of course, thats that market in itself is smaller compared to the whole eurorack market)

OT, but its I2C is quite interesting more generally, as a few modules are now support it to ‘link modules’… and being ‘just’ a data bus, it has lot of possibilities for use.

I’d agree, Although like you say with the addition of the PMIX on its own you could easily fill those inputs especially with multiple PMIX’s. I guess it’s just how things can evolve. I’d also agree I’d imagine there’s a market amongst the SSP users for an expander in the future, obviously entirely up to @bert, I’m sure he’s already thought about it.

I have a few (3 I think) modules that have I2C ports on them (Assim8, NerdSeq and the SSP) although as far as I know none are implemented (yet) to work together. I2C looks like something that would interest me although it might well make the expanders for the Nerdseq I have a bit redundant

1 Like

yeah, I2C is low level, so you need to build in support for particular modules - you cannot just support i2c as a thing (like midi) e.g theres some support between ‘monome’ modules, and some i2c support I believe in the er301.
on the flip size, its a pretty straightforward protocol, so its quite easy to support for devices.

i don’t have a huge interest in i2c as inter-module connectivity, as I don’t have many modules supporting it - but might be interesting for others.

1 Like

Thanks for the info!

I, for one, would definitely jump at an expander module if that ever came to fruition, as I’m also chewing IO up quite quickly leveraging the SSP’s mixing and external audio and CV routing capabilities. In particularly (bit of a digress here) because I’ve been unable to harness the full potential of SSP’s audio-over-usb into Bitwig, which my feeble brain believes will ultimately and eventually provide enormous relief with regard to output usage for audio routing once I figure that bit out :slight_smile:

I own an ES-8 and I would absolutely use it this way if it were possible.

1 Like

Well yes me too for a output expander addon!

Did anything ever come of this? I have an ES-9 and have a SSP on the way and would love to be able to use them together if needed :slight_smile:

well in a few days you’ll be able to test yourself
we await your report eagerly

My bet is, on Mac you can actually do it.

On Mac, you can sum multiple audio devices into one aggregate device.
I use a RME interface and the SSP together.

When I open my DAW and choose the aggregate device, it tells me I have 42 inputs. 24 Ins from the SSP, and 18 Ins from the RME. So I dont see why the ES-9 and the SSP shouldnt work together in the form of an aggregate device.

On windows, I tried many, many times to achieve this, but the only driver I know of thats capable of doing aggregate devices is Asio4All, and it is an absolute pain in the a**

That is a very good idea to make an aggregate device (having that ability is one of the reasons I got a Mac, because Windows sucks for that) :slight_smile:

I was wondering if anyone had hooked an ES9 (or ES8) into the SSP and had access to more I/O, not that I think I will need it, more of an experiment really :slight_smile:

So I did a thing, and sold my ES9 before my SSP has even arrived. I assumed it wouldn’t work with the SSP natively, and I needed the funds for another purchase. I also discovered that the SSP could fill the role of the ES9 when needed (communication with VCV) which is rare, so gave it a new home.

helas, now we’ll never know (!)

usb audio interfaces do work with the SSP, I tested this with my Zoom H5 (I sold my ES8)

the ‘issue’ (as ive mentioned before) is synthor is only interested in the the two audio devices we usually have the ‘built in’ and the usb device( not host!) ( aka ak4458ak5558aud, usb_gadget).

I believe I could create a VST, e.g. a USBIN and USBOUT , that would connect to a usb (hosted) audio interface, and would then expose this as normal vst io… if the usb audio interface supported dc coupled output (like the ES8/9) then we’d have audio and cv - this would be pretty effective.

is this the best option? well its an option that could work without any hardware changes.
but es8/9 are reasonably expensive, whereas if we could get an I2C expander working, this would likely be a bit cheaper… and probably more efficient (less latency).

of course the nice thing about using an es8/9, is you can of course choose to use it independent of the SSP… so it has some extra versatility.

1 Like

i was always under the impression (by tech/sales talk) that it would work out of the box with any plug&play (DC coupled) USB interface - without an extra (VST) layer

really? perhap a misunderstanding…

as I said, yes, my H5 is correctly identified and available as an alsa soundcard ‘out of the box’.

but in my test, synthor did not associate its IO to the INP /OUT channels.
even , restarting synthor did not change this.
(this was what I expected , and mentioned in this post even before trying.)

I should say, actually I would not want this automatic mapping anyway.
the issue is, if you map this audio interface to the same INP channels as the built-in adc, you have not expanded the number of channels, you have just overlaid them.

actually, I wish the the existing USB mode, did NOT do this, instead Id prefer we had a separate IN/OUT module where we could assign the these USB channels.
yes, I see its kind of convienient in some situations to have this ‘automatic’ mapping, but often id prefer to have the physical and usb i/o completely separated. (honestly, this merging could be easily handled in a patch)

anyway, its an interesting area to investigate…
I should say, whilst theoretically this feels simple to do, there may well be some nasty complications in practice e.g. the 128 audio buffer may not be sufficient for many usb audio interfaces, also theres fun and games around sync’ing clocks… that would need to be investigated.

i don’t mind a duplicate of the first 16 INS and 8 OUTS (although it would be nice if you could assign/config them from the SSP)
if we can assign/config the rest of the channels on the USB interface itself (like, OUT 1 on the USB interface corresponds to IN 9 from USB)
i thought this was exactly possible on the ES-9 software (to be flashed for standalone operation)
how many USB audio interfaces you know of have +8 INS and +16 OUTS (dc coupled?) anyhow ?

My bad wavejockey, I needed the funds to replace the money I used to buy the SSP, I was trying to wait out the delivery but a sale went through and I needed to ship it out. Having I2C expander(s) would be really awesome, and would put the SSP on track to severely outpace ES8/ES9 in terms of USB I/O, especially if multiple expanders could be linked together (not that I need that much I/O but it would be nice to have the option) :slight_smile:

One thing I am curious of (don’t want to start a whole other thread, since this is I/O related), is if the left USB port will ever be open to MIDI input, as I’d like to use USB from my sequencer and a MIDI Fighter to control parameters :slight_smile:

2 Likes

i’m relaying my MIDI sequencer information to a novation SL and then to the SSP

Ah this is a great idea! You have just sparked some ideas in my head… and made me thankful I have a few pieces of equipment in the process :slight_smile: I’m thinking MIDI Fighter and Vector Sequencer hooked up via USB to my MioXL then out of MioXL to SSP. I wonder if I can use a double ended USB-A cable to hook them together, as I’d like to go into SSP’s middle USB port, and keep the right most port open for use as a cv/audio interface with my computer. I believe this should allow me to use any MIDI device on my MIDI network with the SSP. Going to have to give it a try when I get a moment, Thank You!! :slight_smile:

1 Like