The vision for Memory Codex at the moment involves the theme of a multi-track compositor. I want the ability to composite a 15 minute short film, for example, gradually over several months and across many sessions, by carefully layering masked patterns onto frames; I want to be able to do this like a stop motion designer would, frame by frame, and also in algorithmic ways with voltage control in real time. I want an internal compositor used to mix down to a master file like you would with a 4-track. So that’s my direction of interest. Ed and Jonah have their own ideas on what they’d like to see out of it as well, and have some very interesting ideas from the clip sequencing and programming angles. So we’ll all collaborate and we’ll be in the position to really get some early feedback from you when we preview some of the features.
As far as latency goes – and immediate (like being able to load a bank of clips and switch/play across them with zero latency up, is important, even if that caps your sampling time in a way that continuous streaming modes don’t.)
Since the design has committed to being able to upgrade from the TBC2 hardware, we will work with that as our base for Codex. Meaning our limitations on sampling times and decoding speed are going to get worked at and optimized for the platform, and we won’t know what they exactly are until we hit them. It’s possible we’ll change have to change course or the identity of the module as we go. We also don’t know how much the expander panel is going to cost or how much external hardware is going to be involved. But we DO have a pretty badass structure on which to do all of this, with the software architecture for TBC2/Mempal starting to mature.