Skip to content

10 December 2025

M. T. Kimmins edited this page Dec 28, 2025 · 10 revisions

Took a look at some of the single-raw dumps like the Eric Carle books (seahorse, cricket) and their Segment 4-Region 13 areas.
Some conclusions that can be gleaned:

  • Region 13 is definitely conserved
  • All copies of the seahorse and cricket dumps agree (although not depicted) within this transitional 4-byte area. Here are the byte ranges: (first pipe divides segment 3 and 4 [as they currently stand], while second pipe shows start of Region 13).
  • Seahorse area = 82 | 0A 04 F1 00 | 42 01 00 00
  • Cricket area = 0A | 82 08 F1 00 | 42 01 00 00 I want to say that the "00" at the end of the 04 F1 00 that we see between the starts of Segment 4 and Region 13 is incidental, but it is curious that multiple books end in "04 F1 00" prior to Region 13... I have updated the definition of Segment 4 to be 8552 bytes long instead of 8556 as originally thought. This will align the starts of Segment 4 and Region 13 nicely.

Also added the byte length and conserved Region 13-24 data in the data template. That would be all the conserved data that can be gleaned as of yet. Next steps would be to pick at the regions themselves and try to see if sub-regions can be delineated. It seems that preliminary results suggest there are -- if indeed they are PCM audio, then there is a table of differentials at the end of each of those regions. More to come.

seahorse cricket

Region-specific observations

I wonder if the first 4 bytes of each region is the length of the region. In comparing first 4 bytes to length, here is the list for Big Shark Little Shark Baby Shark (BSLSBS). I will list what the bytes look like in the data, then translate them to a number of bytes to see if it matches my count of bytes in the region. Reminder: converting to decimal requires retrograde construction (ie: 42 88 00 00 = 0x8842 as the address).

Region # First 4 bytes (hex) First 4 bytes (decimal) length (bytes) Difference (length-decimal) Percent decimal (decimal/length)
SEGMENT 3
1 42 88 00 00 34882 35214 332 0.99057193161
2 02 1E 00 00 7682 7828 146 0.98134900357
3 F2 5A 00 00 23282 23592 310 0.98685995252
4 6A 5B 00 00 23402 23778 376 0.98418706367
5 FA 48 00 00 18682 18978 296 0.98440299293
6 EA 49 00 00 18922 19420 498 0.97435633367
7 72 35 00 00 13682 13988 306 0.97812410637
8 62 36 00 00 13922 14164 242 0.98291443095
9 EA 2B 00 00 11242 11470 228 0.98012205754
10 72 6C 00 00 27762 28886 1124 0.96108841653
11 CA 41 00 00 16842 17254 412 0.97612147907
12 9A 35 00 00 13722 13910 188 0.98648454349
SEGMENT 4
13 42 01 00 00 322 326 4 0.98773006135
14 9A 03 00 00 922 926 4 0.99568034557
15 EA 03 00 00 1002 1006 4 0.99602385685
16 EA 03 00 00 1002 1006 4 0.99602385685
17 22 03 00 00 802 806 4 0.99503722084
18 D2 02 00 00 722 726 4 0.99449035812
19 5A 02 00 00 602 606 4 0.99339933993
20 AA 02 00 00 682 686 4 0.99416909621
21 BA 01 00 00 442 446 4 0.99103139013
22 72 03 00 00 882 886 4 0.99548532731
23 92 01 00 00 402 406 4 0.99014778325
24 D2 02 00 00 722 726 4 0.99449035812

Some conclusions:

  • It seems that the first 4 bytes do reference some length of each region.
  • For Segment 4 regions it seems that those last 4 bytes are indeed important for some reason. All have 4 extra bytes. All end in "6" meaning all pointers land at a number ending in "2". Then again, perhaps the last 4 bytes actually do not count, but account for the first 4 bytes being a pointer and not being a part of the "data" chunk. This would also follow for segments 1-12.
  • Percentages look like they are random with no useful pattern.

Let us then classify these new sections:

  • First 4 bytes will be called the "PCM Address" (to differentiate it from the Segment 1 pointers). PCM would mean in this case Pulse-Code Modulation (PCM) is what I think these regions are (most likely just the first 12 regions).
  • The data following the address, ending at the PCM address (inclusive -- a guess at this point) will be the "PCM Body."
  • The rest of the data (if applicable -- only for segments 1-12) will be the "PCM Map."

G+ Eventor and audio

In order to explore G+ Eventor (G+E), I have made "silence.wav" (silence for 30s duration) and a "sine.wav" (sine tone of 400hz for 30s duration). My aim is to import these .wav files into G+E to see what the resulting file looks like as binary and perform a thorough exploration of the application in these devlogs. Those files are now uploaded on the github under a new section "/G+EventorPCMAreas".


⟵ Older Table of Contents Newer ⟶

Clone this wiki locally