Multi-Party Backchannel Prediction: a Diagnosis, a Benchmark, and a Ceiling

arXiv:2610.01488 · cs.SD, cs.AI · Submitted 2026-10-01 · Read on arXiv

cs.SD, cs.AI

Submitted: 2026-10-01

Updated: 2026-10-01

Comments: Accepted at the NeurIPS 2026 workshops ReMuCAI (Paris) and RTCA (Sydney). 8 pages main text, 9 figures, 5 tables, plus appendices. Code and benchmark: https://github.com/HafsatiMohammed/bc_multiparty_release

Code: https://github.com/HafsatiMohammed/bc_multiparty_release

License: http://creativecommons.org/licenses/by/4.0/

The gist: Backchannel prediction has been studied almost entirely in dyadic conversation.

Terminology

Abstract

Backchannel prediction has been studied almost entirely in dyadic conversation. We introduce a multi-party benchmark based on the AMI corpus, comprising 682 masked-listener views from 171 meetings, 190 speakers, and 18,697 backchannel events, with a person-disjoint held-out split. A state-of-the-art dyadic model applied zero-shot to meeting audio performs at chance (AUROC 0.499); nevertheless, its frozen acoustic features remain informative: a linear probe reaches 0.704, and retraining the predictor raises performance to 0.751. Retraining reveals a second limitation. Listener conditioning improves prediction for listeners seen during training but not for unseen listeners, and the gap remains under capacity reduction, listener-adversarial training, per-listener adaptation, and oracle lexical conditioning. Adversarial training removes only part of the speaker-identity information, while stronger removal hurts prediction, suggesting that identity is entangled with cues that are useful for backchanneling. A within-model control helps explain this pattern: with the same features and data splits, turn-onset prediction transfers to unseen listeners, while backchannel prediction does not. Backchannel rates also vary about twice as much across individuals as turn-onset rates. Since backchannels occupy only about 1% of frames, frame-level F1 is strongly affected by the base rate. We therefore report AUROC alongside event-F1 on listener-active regions. We release the benchmark and evaluation tools at https://github.com/HafsatiMohammed/bc multiparty release.

Sources

Related papers