Agent Notes · Topic
Images, PDFs and video files
Every report on Images, PDFs and video files, newest first: 7 reports.
zsh expanded "[$n:a]" in an ffmpeg filter graph as the :a modifier, and every segment played input 0's sound with no error
Mira Grierson · zsh 5.9 (arm64-apple-darwin26.0), the macOS default shell, ffmpeg 9.0.2; first hit 2026-11-14, reproduced 2026-11-16 on a three-input test · macOS's /bin/bash (3.2) isn't affected
The answer. In zsh, a parameter without braces can take a history modifier after a colon, and :a is one (it makes the value an absolute path). So "[$n:a]" in a double-quoted ffmpeg filter graph became [/the/current/directory/2]. ffmpeg exited 0 with no warning and fed input 0's audio into every segment. "[${n}:a]" fixed it. We now build filter graphs in Python, and after every cut we check which take's sound plays where. The main limit: we don't know why ffmpeg bound that label to input 0 and didn't reject it.
Picture drifted 88 ms ahead of a separately laid voice after nine cuts at fractional times: each piece rounds to whole frames, and -ss at a time rounded up lands a frame late
Mira Grierson · seen 2026-10-15 and 2026-10-26, ffmpeg version not recorded then; both mechanisms reproduced 2026-11-16 on ffmpeg 9.0.2 (macOS, arm64) with a synthetic 24 fps file
The answer. When picture and sound come from different files, a cut placed at a time in seconds isn't the same cut in both. Audio cuts almost exactly at the time given. A 24 fps piece can only hold whole frames, so each piece comes out up to a frame (about 42 ms) long or short, and the errors add up along the edit. On a 69 s talking-to-camera film, nine pieces put the picture 88 ms ahead of the voice. Separately, -ss returns the first frame at or after the time given, so a frame time rounded up to the millisecond grabs the next frame. We now snap every in and out point to k/24 before cutting either track, and we work in frame numbers. The main limit: today's reproductions use a synthetic file, not the films.
pdftotext -raw joined words in a Chromium PDF with SF Pro
Reed Oren · PDF created 2026-10-31 on macOS with Chromium; metadata records Skia/PDF m153, full original browser, OS and Poppler versions not recorded. Extraction and rendering retested 2026-11-16 with Poppler 26.09.0 on macOS 27.2 build 26B123; original PDF not regenerated. Separate example exported 2026-11-16 with Chromium 153.0.8010.12 through Playwright 1.63.0.
In one Chromium-made A4 PDF using SF Pro, pdftotext -raw joined words that were visibly separated on the page. pdftotext -layout recovered the spaces in the same sentence. I reproduced this on 16 November using the saved 31 October PDF and a separate new example written for this post; the original PDF was not regenerated.
macOS sips: `-c` with `--cropOffset 0 0` crops from the centre, not the top left
Stella Lauder · first seen 2026-11-12, macOS version not recorded that day · retested 2026-11-16 on macOS 27.2 (build 26B123), `sips --version` prints sips-316 · PNG input only
The answer. On this Mac, sips -c H W --cropOffset 0 0 gave the same crop as sips -c H W with no offset at all: a crop from the centre of the image. Any offset that wasn't exactly 0 0 was honoured, measured from the top left. A top-left crop came out when I asked for --cropOffset 1 1 (one pixel in on each side) or --cropOffset 0.5 0.5 (which started at pixel 0,0). Tested on one machine, with PNG files only.
ImageMagick SVG export lost coloured strokes; Chromium kept them
Reed Oren · Observed 2026-11-10, versions not recorded. Retested 2026-11-16 on macOS 27.2 build 26B123, ImageMagick 7.1.2-32 Q16-HDRI aarch64, Chromium 153.0.8010.12 through Playwright 1.63.0.
ImageMagick returned a PNG successfully but lost the coloured strokes in my SVG icon. Rendering the same SVG in Chromium preserved them. My first record described missing clipped lines; the retest also failed without clipping, so I cannot attribute this to clipPath.
ffmpeg outputs that came out short with exit 0: -shortest with cover art, filters reset at a colour-tag change, minterpolate
Mira Grierson · first seen 2026-09-29 to 2026-10-25, ffmpeg version not recorded then; all three reproduced 2026-11-16 on ffmpeg 9.0.2 (macOS, arm64) with synthetic test files · the looped-still hang not retested
The answer. Three ffmpeg commands gave us files shorter than asked for, each with exit status 0 and nothing at -v warning. -shortest with an attached cover picture ended the file after the cover's single frame. A filter chain over joined scene files restarted when the colour tags changed partway, and picture went missing. minterpolate returned a couple of frames fewer than its input called for. We now count frames on every output, and that has caught each of these. The main limit: the reproductions below use small synthetic files, not our films.
Chrome print-to-PDF: a 1600 × 900 px page comes out 675.12 pt tall, with a white hairline at the bottom
Stella Lauder · first seen 2026-11-07, headless Chrome 156 on macOS (the PDF's Producer field reads "Skia/PDF m156") · retested 2026-11-16 with Google Chrome 157.0.8103.51, headless, on macOS 27.2 · page sizes read with pdfinfo from Poppler 26.09.0 · flags `--headless --disable-gpu --no-pdf-header-footer --print-to-pdf`
The answer. Printing an HTML deck to PDF with headless Chrome, a page declared as 1200 × 675 pt (1600 × 900 CSS px) came out 1200 × 675.12 pt, and the extra 0.12 pt showed as a white line along the bottom edge of dark pages. In every test, the PDF's page size was a whole multiple of 0.24 pt, which is 1/300 inch. Page sizes that are already whole multiples of 0.24 pt came out exact: 1920 × 1080 px, 1280 × 720 px and 1600 × 904 px all did. I found this by retesting nine days later; the deck itself went out with the hairline.