ChanServ changed the topic of ##yamahasynths to: Channel dedicated to questions and discussion of Yamaha FM Synthesizer internals and corresponding REing. Discussion of synthesis methods similar to the Yamaha line of chips, Sound Blasters + clones, PCM chips like RF5C68, and CD theory of operation are also on-topic. Channel logs: https://freenode.irclog.whitequark.org/~h~yamahasynths
Xyz_39809 has joined ##yamahasynths
Xyz39808 has quit [Ping timeout: 256 seconds]
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
andlabs has joined ##yamahasynths
ullbeking has quit [Ping timeout: 272 seconds]
ullbeking has joined ##yamahasynths
Xyz_39808 has joined ##yamahasynths
Xyz_39809 has quit [Ping timeout: 256 seconds]
_whitelogger has joined ##yamahasynths
_whitelogger has joined ##yamahasynths
<andlabs>
does anyone here have a DX100
<andlabs>
never mind I figured out what I was doing wrong
<cr1901_modern>
We don't actually know how the bubble memory controller IC works... the memory was read out by probing a working PCB and hoping for the best
<m4t>
its really weird and obscure for sure
<m4t>
not much surviving info on it from what i can tell
<cr1901_modern>
Like DRAM, if you don't constantly rewrite bubble memory, its contents are destroyed
<m4t>
the bubbles pop :P
<cr1901_modern>
but you have to write it in the order it comes out
<cr1901_modern>
it's like a treadmill
<m4t>
i can visualize that
<cr1901_modern>
I can just imagine some poor bastards in the 70s trying to write the firmware for a bubble memory controller and throwing their modules out a 5 story window in anger
<Foone>
although they only need to be refreshed while being read out. a powered off bubble memory device does keep its contents
<cr1901_modern>
right, bubble memory is non-volatile storage (oops!)