Skip to content

ExecutiveAssistantAgent 1.0.2

Choose a tag to compare

@xhqing xhqing released this 08 Oct 11:38
· 68 commits to main since this release
bf6a04b

Record why MP4 playback in VS Code stays silent and add codec test samples

Added (tmp/codec-test/: samples and root-cause notes for VS Code's silent built-in player)

  • Why: a user asked why MP4 files open without sound in VS Code and why the speaker button does nothing. The root cause is that VS Code's bundled media library (libffmpeg.dylib) ships without an AAC decoder - AAC is a licensed codec, and VS Code only bundles a subset of what FFmpeg supports (see microsoft/vscode issues #167685 and #329811; a long-standing, by-design limitation). H.264 video decodes fine, the AAC audio track cannot, so playback renders video with no sound. The file itself is fine (it plays correctly in QuickTime; measured audio level -24.7 dB). The speaker button is just a standard player control with no decoded audio behind it.
  • What changed: added tmp/codec-test/ (gitignored, verification only) with three samples that keep the original H.264 video and only swap the audio codec: mp3-audio.mp4 (H.264 + MP3), flac-audio.mp4 (H.264 + FLAC), vorbis-audio.webm (VP8 + Vorbis), to check which audio codecs actually play in the editor.
  • Evidence for later reuse: VS Code's libffmpeg exports only the flac / h264 / mp3 / pcm / vorbis / vp8 decoders (no aac / opus / vp9 / av1 / hevc) and only the flac / mov (MP4) / mp3 / ogg / wav / raw containers (no matroska, so .webm files are likely unplayable at all); other Electron apps on the same machine ship both the AAC decoder and matroska support. For previewing videos with AAC audio, use a system player (QuickTime / IINA); to hear sound inside the editor, convert the audio to MP3 or FLAC inside an MP4 (video kept intact via -c:v copy) - the WebM route is not viable (no demuxer). The three samples are the final word on what actually plays.

Changed (CHANGELOG structure fix: restore the [1.0.1] heading)

  • Why: the previous edit accidentally deleted the "## [1.0.1] - 2026-10-07" heading, which moved the 1.0.1 entries into the unreleased section and left the latest real version heading at [1.0.0].
  • What changed: restored the "## [1.0.1] - 2026-10-07" heading so the termux-ssh entry sits under 1.0.1 again.