Recordings start with a long silent head and clip the speaker at the tail (both OP25 and Trunk Recorder) #48
Open
opened 2026-11-08 00:48:36 -05:00 by logan
·
1 comment
No Branch/Tag Specified
main
feat/45-trunk-recorder
fix/44-upload-spool
feat/41-disk-reporting
fix/41-updater-prune
fix/discord-voice-join
fix/updater-safe-directory
fix/28-amd64-images
fix/18-install-token-argv
fix/19-image-tag-skew
feat/discord-system
feat/24-p25-conventional
feat/local-ui-usable
fix/14-15-provision-ota
feat/sdr-pins
feat/secondary-sdr-priority
feat/second-sdr-adsb-ais
feat/publish-public-images
fix/install-rerun-pickup
pulse-recorder
v1.1.0
v1
Labels
Clear labels
area/ai-pipeline
area/auth
area/billing
area/correlation
area/discord
area/frontend
area/governance
area/growth
area/infra-deploy
area/legal
area/map
area/mqtt
area/node-ota
area/osint
area/recording-audio
area/sdr-radio
area/transcription
board
board:agenda
Scene/entity extraction, summarizer, AI providers, embeddings
AuthN/Z, roles, tenancy/org scoping, API keys, credentials
Plans, entitlements, AI spend accounting and caps
Incident correlation, linking, lifecycle, severity, corr_debug
Discord bot, radio bots, voice streams, bot tokens, webhooks
Web UI: Next.js app and the edge-node local dashboard
Board process, minutes, unattended runner, agent tooling
Go-to-market, outreach, cold email, discovery conversations
CI/CD, VM, registry, Firestore rules/indexes deploy, Terraform/Caddy
ToS, retention, licences/DAAs, CAN-SPAM, E&O, name suppression
Live map: pins, paths, tiles, legend, geocoding
Node-C2 MQTT, checkins, commands, node sweeper, dynsec
Node install, enrollment, OTA updater, image skew
External feeds: cameras, 511, ADS-B, AIS, outages, and their licences
Call capture, boundaries, PulseAudio, ring buffer, trimming, attribution
OP25 decode, SDR hardware/tuning, conventional, second SDR, mesh radio
STT, transcript correction, place verification, name accuracy
Board process: minutes and board-filed items
Needs board scoping at the next sitting; CEO removes the label once scoped
kind
behavior-bug
Wrong product behavior; the instrument reads it correctly
kind
measurement-bug
Corrupts the recording/instrument (debug data, evals, health checks), not behavior
priority
p0
Drop everything: prod broken, live exposure, or owner-ruled P0
priority
p1
Next up: blocks a gate, a customer, or core incident quality
priority
p2
Normal: real defect or planned work, schedule in turn
priority
p3
Low: minor, cosmetic, or someday
status
blocked
Waiting on an external party, spend, or another issue
status
in-progress
Branch or PR open against it
status
needs-decision
Waiting on an owner or board ruling before work
status
needs-info
Root cause or repro unknown; needs a reading first
type
bug
Something built is wrong: code, data, or a measurement
type
chore
Maintenance, refactor, tests, pinning, cleanup: no user-visible change
type
decision
A ruling to make or record: board minutes, owner calls, legal reviews
type
docs
Docs, runbooks, CLAUDE.md, skills, SOPs
type
feature
New capability or an extension of an existing one
type
security
Security, privacy, credential or tenant-isolation exposure
type
tracking
Tracker, checklist, initiative or punch-list spanning several changes
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: logan/node-26#48
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Owner listening test, 2026-11-07, node-002 (MTA Zone 2): recordings often start with a long stretch of silence and then cut the last speaker off at the end. It happens on both the OP25+PulseAudio recorder and the Trunk Recorder backend (node-26#45 trial).
Since both backends show it, suspect a stage they share before blaming either recorder: the edge trim/upload path, C2 storage or transcoding, or the frontend/Discord player. Not yet localised. First step: pull a handful of raw uploaded files from GCS, compare head/tail against the node-side timestamps (audio_start_epoch/audio_end_epoch, which C2 ignores per DEFERRED.md), and check what audio_trim did to them.
This is the recording-quality foundation: a clipped tail loses the address or disposition, and that poisons transcription and correlation. Run drb-audio-review on any fix.
Owner listening test, 2026-11-09, node-002. Comparing the OP25 image pinned to gr310 5b58335 (main, src-a8111740) against the previous image.
So the tail-clip half of this issue is still open on the current decoder.