It’s been along time since I’ve looked at the ii bits in the code.
IIRC there was a voltage difference 5v for the aleph and 3.3v for the modules but I could well be imaging this.
One concern I had was how to properly protect the ii bus from accidental connection to cv or audio if the module used 3.5mm jacks. I had spent some time looking for a different style of connector that was durable and compact…
Do you see the aleph as a master (like the tt) or slave (like the trilogy)? EDIT - I see you are thinking of aleph as a slave. In a way I now see that as more interesting than as a master.
Probably not as hard as you think. Someone would need to step up to do the leg work though.
You’d probably want to hard fork the teletype codebase, then you can customise the ops in a manor sympathetic to the Aleph.
How would you interact with the DSP/BFIN bits? I guess in a similar way to sending II commands to modules.
Sorry. (Seriously though, if you do find a coder with the time, desire and expertise to want to port Teletype over to the Aleph, I’d be more than happy to help with info and support. At this point I know the Teletype codebase inside and out.)
I’m right there with you… Just juggling the many things competing for time. Literally within the last 24 hr I’ve started to think about the relationship between aleph, crow, and the modular world again.
Maybe we should talk about specifics as to what might be a good first step…
yeah only the basic functionality has been tested. it should not be hard to add knowledge of the II ecosystem (pulled from libavr32). guess i’d keep the raw event type in the “OS” layer (IIRC that also works fine right now - the source you linked is an even earlier standalone hardware test) and leave device-specific stuff to the “app” layer.
i wish i could say i’m going to work on this. but realistically there is just no way. (i don’t even really have a eurorack setup anyways.) i do have some particular desires for a new aleph standalone firmware (no bees, no sdcard.)