[HellMood]

Actually a) polymorphic asm instructions, like "add [bx+si],al" which is 0x0000 b) jumping into middle of instructions to save bytes and reuse opcodes

In hundreds of tiny experiments, this one stuck out, just by the sound of it. When i unfolded what's left and removed "the rest" i had a hard time to grasp what's really going on. i myself didnt expect that the explanation would go this deep for just these few bytes xD

[blackle]

There's lots of cool details like this which you share in this thread but aren't present in the writeup, which is a bit of a shame! I'd love to hear more about how you arrived at this sequence of bytes. Was it the same kind of process as Memories or did you have a different approach this time? How do you mean by "unfolded what's left?" Were you generating these experiments manually or automatically?

[HellMood]

Hey, Blackle! Yeah, i agree :/ In short, for now: Manually, dozens or hundreds of them. The process was just tinkering around with CAs and sound. "What's left" is how it still sounds remarkably different than it should on a clinically clean memory segment, but in a way that i like much much better xD So the unfolding would be, why does it sound like this, and how can i steer it, and then, how can i minify it. Maybe it can be folded into the original 16 bytes as well =)