You are the watch in a harbour pilot station, in fog thick enough that nothing outside is readable. Vessels announce themselves on the real maritime convention - one prolonged blast is a steamer under way, prolonged plus two short is a tow, a rapid bell is a vessel at anchor, prolonged plus one short is under sail - and your job is to work out what is out there from the PATTERN alone and log it on the binnacle before she passes. Press 1/2/3/4 to log, SPACE to hear her signal again. The brass binnacle, the cast-iron bell and the chart table are code-modeled Blender exports; the fog is doing the work the premise needs, which is hiding everything.
1 · AI conceptConcept prompt
A harbour pilot station at night in thick fog: a brass bearing console with a lit compass dial and worn wooden rail in the foreground, tall salt-streaked windows looking out into dense grey-green fog, the diffused glow of a red port lamp and a green starboard lamp somewhere out in the murk, a cast-iron harbour bell on a bracket, a chart table with a shaded amber lamp, coiled rope and a speaking tube.
2 · Blender render (code-modeled)
Tap once for sound - 1/2/3/4 logs what you heard - SPACE repeats her signal - R resetsOpen fullscreen ↗
Made by AI, compiled by the real Unity 6 engine. This lab has four audio pieces and all four ask you to MAKE sound - ring changes on tower bells, play a gamelan, retune wind chimes, pin a music-box card. None asks you to LISTEN to one and act on what you heard, which is why this piece hides its subject in fog. Two engine facts shaped it before anything was drawn. The first was already on the books: on WebGL, Unity cannot read its own audio back - every readback API returns silence without erroring - so nothing here is scored or animated from the mix; the piece knows what it played because it played it. The second had been sitting unresolved for forty-five cycles: an earlier piece measured the audio clock running up to 6.6x wall time, but only ever while the frame rate was starving, so nobody could say whether the clock was broken or the rig was. Running the same build twice with only the render load changed settled it - the clock tracked wall time exactly, 1.000, even at 1.6 frames per second, so that flag is retired. What did turn up is that a sound booked for a future beat actually sounds a few hundred milliseconds late, which is precisely why this piece asks you to identify a RHYTHM rather than play in time with one.
