11 May 2026

Region 2 Blank Data Body (FF)

I have filled Region 2's audio data with blanks (FFs). I ensured to cut the length the first 4 bytes's length away from the 7th byte (start of the audio data).

Results

• Attempt 1: It played a low "beep" and had a light seizure, then reset.
  I have miscalculated the number of bytes away from the 7th byte, leaving a bit of the terminal data of the audio unblanked. I have cut more off to equal the amount represented as an integer by the first 4 bytes. I double checked the data size I selected to blank matched the number of bytes represented by the first 4 bytes in ImHex.
• Attempt 2: It played a lower "beep" and had a worse light seizure. It failed to turn off the projector light triggering a delayed carousel turn. I could see the carousel turn while the projector light was still on. It then reset after a couple of back-to-back turns. Perhaps FF is not 'blank' when it comes to audio data? Let us try 00...

Region 2 Blank Data Body (00)

I filled Region 2's audio data with 00.

Results

Other Thoughts

Perhaps I have marked all the audio-light boundaries wrong when mapping the ImHex project file... I'll have to double check. This means that the systematic slices I took of the gold standards may also be wrong...
Perhaps I will sever what I think is the audio and decode it with the a1800-codec, then listen to what plays. If there is extra audio, I know I cut it too long (encroaching into the lights data). If there is an abrupt end to the audio, I know I cut it too short.

⟵ Older	Table of Contents	Newer ⟶