A repository of Max/MSP/Jitter
objects for the emulation and virtual manipulation of old school video game
systems and their respective sound chips. Max/MSP/Jitter
users can use these objects to reproduce the
sounds (and visuals) of these
systems and modify them as they see fit.
Mostly finished jit.gb. I'll release the final version soon, but if you'd like to give it a try before then, just send
me an email.
I recently uploaded some old videos to Vimeo showing an old patch: jit.atari2600.automator. I've also made some
substantial progress on GameBoy and Vectrex externals. Coming soon.
I'm back in school, and have been spending some time building a new graphics environment called oGFx. I recently
took a few days to integrate an Atari 2600 emulator into it. Check out my blog for screenshots.
jit.nes is coming along nicely. Eye candy for the curious:   . jit.gameboy is proving to be a bit more difficult.
Finally finished the Universal Binary for
Starting to make
external sources available.
I've finally updated the
intellivoice~ externals and .help files for both Windows XP and OS X. These versions
feature the virtual circuit bending techniques I demonstrated at Bent 2006. See the
projects page to download.
I've put together two new
externals: a Nintendo Sound Format (NSF) and a Game Boy Sound Format (GBS)
player for MSP. These
externals feature the ability to selectively enable and disable specific sound channels,
and modify the emulated sample rate. They can be
downloaded on the projects page.
This year's circuit
bending festival, Bent 2006 is now over. This
year, I led a workshop on how to construct
Max/MSP/Jitter externals that lend themselves to manipulation,
henceforth known as "Virtual Circuit Bending".
Here is the slide set.
has taken a major evolutionary step from a modifiable emulation environment to an Atari 2600
micro-hacking studio. Version 0.8 includes many new
and exciting ways to corrupt your virtual Atari2600
console, including a jsui-based runtime ROM visualizer
and sprite manipulator, which allows the user to hack
ROMs during game emulation. These modified ROMs can then be saved for future reference.
Played a show. Here's
The term "virtual circuit bending" appears to lack a consistent
definition. In the context of the pages that
follow, I am using the term to describe
a specific process with respect to software emulation. Any application
that emulates the
execution of a piece of hardware has an inherent set of properties that allows it to
the task. For example, an Atari 2600 emulator contains a very specific set
of instructions to move the game
sprites around the screen in a manner consistent with
the operation of the original Atari 2600 hardware. What
happens if we change those
properties? Suppose the emulator adds together two bytes from the cartridge ROM
the color of the player sprite. What
if I am able to modify those values from outside of the
This idea applies to operations throughout the emulator, ranging from the content
of the bytes read from memory
to the way these bytes are interpreted by the virtualized
hardware. Would the original console behave the same
way if it were possible (which
it is not) to make these modifications to the CPU or ICs? Probably not, because
it is an emulator.
Sometimes it's interesting to ask what if.
Max/MSP Chiptune Externals
The jit.atari2600 Max/MSP External
The jit.intellivision Max/MSP External
for interactive modification of video game emulation.
Kyle Buza 09/09/06;