10 interesting stories served every morning and every evening.

Kimi K3 Tech Blog: Open Frontier Intelligence

www.kimi.com

Today, we are in­tro­duc­ing Kimi K3 — our most ca­pa­ble model. Kimi K3 is a 2.8T-parameter model built on our Kimi Delta Attention and Attention Residuals, with na­tive vi­sion ca­pa­bil­i­ties and a 1-million-token con­text win­dow. It is the world’s first open 3T-class model, de­signed for fron­tier in­tel­li­gence across long-hori­zon cod­ing, knowl­edge work, and rea­son­ing.

While its over­all per­for­mance still trails the most pow­er­ful pro­pri­etary mod­els, Claude Fable 5 and GPT 5.6 Sol, Kimi K3 demon­strated fron­tier-level per­for­mance across our eval­u­a­tion suite, con­sis­tently out­per­form­ing other tested mod­els.

Kimi K3 is avail­able to­day on Kimi.com, Kimi Work, Kimi Code, and the Kimi API. At launch, Kimi K3 will use max think­ing ef­fort by de­fault, with low- and high-ef­fort modes to be in­tro­duced in sub­se­quent up­dates. We are cur­rently work­ing closely with in­fer­ence part­ners and open-source main­tain­ers to align tech­ni­cal de­tails and en­sure a re­li­able roll­out across the ecosys­tem. The full model weights will be re­leased by July 27, 2026. Further de­tails on the ar­chi­tec­ture, train­ing, and eval­u­a­tions will be re­leased along­side the Kimi K3 tech­ni­cal re­port.

An Open 3T-Class Model

Kimi K3 is the first open model to reach 2.8 tril­lion pa­ra­me­ters. It marks the lat­est step in Kimi’s sus­tained push at the scal­ing fron­tier: for nine of the past twelve months, Kimi mod­els have set the up­per bound of open-model sizes.

Kimi K3 is built on Kimi Delta Attention (KDA) and Attention Residuals (AttnRes), two ar­chi­tec­tural up­dates de­signed to im­prove how in­for­ma­tion flows across se­quence length and model depth. We have also scaled up Mixture of Experts (MoE) spar­sity, ef­fec­tively ac­ti­vat­ing 16 out of 896 ex­perts when paired with a Stable LatentMoE frame­work. Together with re­fined train­ing and data recipes, these struc­tural changes yield an ap­prox­i­mate 2.5× im­prove­ment in over­all scal­ing ef­fi­ciency com­pared to Kimi K2, al­low­ing the model to con­vert com­pute into in­tel­li­gence more ef­fec­tively.

Coding

Kimi K3 has strong long-hori­zon cod­ing per­for­mance. Operating with min­i­mal hu­man over­sight, it can sus­tain long en­gi­neer­ing ses­sions, nav­i­gate mas­sive repos­i­to­ries, and or­ches­trate ter­mi­nal tools.

Kimi K3 also ex­cels in tasks blend­ing soft­ware en­gi­neer­ing with vi­sual rea­son­ing — it lever­ages screen­shots and vi­su­als to op­ti­mize game dev, fron­tend, and CAD.

The case stud­ies be­low show how Kimi K3′s cod­ing ca­pa­bil­ity trans­lates into open-ended soft­ware cre­ation and sci­en­tific re­search.

Kernel Optimization

We tested the mod­els’ ca­pa­bil­ity to op­ti­mize GPU ker­nels. Each model works in­de­pen­dently in an iden­ti­cal sand­box, with up to 24 hours to pro­file, rewrite, and bench­mark four tasks span­ning AttnRes, KDA, and a 512-head-dimension MLA ker­nel across NVIDIA H200 and GPGPU from an al­ter­na­tive ven­dor. Kimi K3 per­formed com­pet­i­tively with Fable 5 (with fall­back) and sub­stan­tially out­per­formed Opus 4.8, GPT 5.6 Sol, and GPT 5.5.

Claude Fable 5 was eval­u­ated by a third party, and its re­sults may in­clude fall­back be­hav­ior. Across most mod­els, some tra­jec­to­ries in­clude small, ac­cept­able pre­ci­sion short­cuts that re­main within our nu­mer­i­cal tol­er­ance. GPGPU de­notes gen­eral-pur­pose GPUs used for com­pu­ta­tion be­yond graph­ics ren­der­ing.

In the late stages of Kimi K3 de­vel­op­ment, an early ver­sion of Kimi K3 han­dled the ma­jor­ity of the team’s ker­nel op­ti­miza­tion works.

GPU Compiler Development

We fur­ther tested whether Kimi K3 could build a GPU pro­gram­ming sys­tem from scratch. Kimi K3 de­vel­oped MiniTriton, a com­pact Triton-like com­piler with its own tile-level IR layer over MLIR, op­ti­miza­tion passes, and a PTX code-gen­er­a­tion pipeline. Across sup­ported roofline bench­marks, MiniTriton de­liv­ers per­for­mance on par with or bet­ter than Triton and torch.com­pile — beat­ing Triton on cer­tain work­loads. Beyond mi­crobench­marks, MiniTriton sus­tains end-to-end nanoGPT train­ing with sta­ble con­ver­gence, the loss curve closely track­ing the ref­er­ence with only mi­nor di­ver­gence — val­i­dat­ing the full pipeline on a re­al­is­tic work­load. These re­sults demon­strate that Kimi K3 can build a co­her­ent end-to-end com­piler — from DSL fron­tend and IR passes to PTX code­gen and run­time — rather than iso­lated ker­nels; its from-scratch Tensor Core path al­ready ri­vals Triton’s ex­ten­sively op­ti­mized stack.

Game Dev and Digital Creation

Kimi K3 com­bines strong 3D rea­son­ing, cod­ing, and vi­sion ca­pa­bil­i­ties to turn con­cepts, im­ages, and videos into fully playable in­ter­ac­tive ex­pe­ri­ences. Kimi K3 achieves true vision in the loop” by seam­lessly it­er­at­ing be­tween code and live screen­shots—in­stantly see­ing and re­fin­ing out­puts.

Chip Design

As an early proof of con­cept, Kimi K3 de­signed a chip to serve a nano model built on its own ar­chi­tec­ture. In a sin­gle 48-hour au­tonomous run, K3 built, op­ti­mized, and ver­i­fied the chip us­ing open-source EDA tools on the Nangate 45nm li­brary. Within 4 mm², the chip closes tim­ing at 100 MHz and sus­tains over 8,700 to­kens/​s de­code through­put in sim­u­la­tion, pack­ing 1.46M stan­dard cells, 0.277 MB of SRAM, and an INT4 MAC ar­ray with fused de­quan­ti­za­tion. A chip built by a model, for a model, re­flects K3′s long-hori­zon agen­tic ca­pa­bil­i­ties.

Coding for Research

Kimi K3 bridges sci­en­tific lit­er­a­ture and ex­e­cutable code, au­tonomously im­ple­ment­ing, val­i­dat­ing, and an­a­lyz­ing com­plex com­pu­ta­tional re­search work­flows.

In one case, Kimi K3 com­pleted in about two hours what would typ­i­cally re­quire one to two weeks of work by an ex­pe­ri­enced re­searcher. To re­pro­duce the I–Love–Q uni­ver­sal re­la­tions in com­pu­ta­tional as­tro­physics, it re­viewed and cross-val­i­dated 20+ pa­pers, im­ple­mented the full nu­mer­i­cal pipeline, eval­u­ated 300+ equa­tions of state, iden­ti­fied in­con­sis­ten­cies in pub­lished for­mu­las, gen­er­ated 3,000+ lines of Python code, and pro­duced an in­ter­ac­tive HTML dash­board for ex­plor­ing the re­sults.

Knowledge Work

Kimi K3 ad­vances end-to-end knowl­edge work. Beyond pub­lic bench­marks, Kimi K3 (max) demon­strates con­sis­tent gains across our in­ter­nal eval­u­a­tions, which are de­rived from re­cur­ring pat­terns and chal­lenges ob­served in real-world user-agent work­flows. These con­sis­tent ad­van­tages across dis­tinct pro­duc­tion-ori­ented work­flows re­flect a broad im­prove­ment in Kimi K3′s agen­tic knowl­edge work ca­pa­bil­i­ties.

Research with Interactive Visualization

Below are a few ex­am­ples of what Kimi K3 in Kimi Work can pro­duce across fi­nan­cial con­sult­ing and sci­en­tific re­search:

Case 1: Interactive 42 years of AI ASIC in­dus­try re­search web­site

An in­ter­ac­tive re­search re­port you can drill into: 42 years of the ASIC in­dus­try, cre­ated through 120+ rounds of re­cur­sive self-im­prove­ment. Kimi K3 trans­forms ev­i­dence into be­spoke charts, an­i­mated di­a­grams, and in­ter­ac­tive vi­sual nar­ra­tives. It pulled data via 2.8k+ web searches/​fetches and 1.1k+ ter­mi­nal data pulls, across 11k+ pages span­ning 87 quar­terly re­ports and 99 orig­i­nal PDFs.

Case 2: Fusion Industry Research

A con­sult­ing-style in­dus­try re­port with in­ter­ac­tive vi­su­al­iza­tions—in­clud­ing time­lines, Funnel Chart, Range Bar Chart, Gantt Charts, and pub­li­ca­tion-qual­ity slides.

Case 3: GWTC-5 Gravitational-wave Analysis

An analy­sis of 391 grav­i­ta­tional-wave events us­ing 20+ con­cur­rent sub­agents, pro­duc­ing 7 sci­en­tific vi­su­al­iza­tions, 2 ta­bles, and a lit­er­a­ture syn­the­sis from 10+ pa­pers.

Kimi K3 is also par­tic­u­larly ef­fec­tive at pro­duc­ing in­fo­graphic-style pre­sen­ta­tions, such as the fully ed­itable heatmap and an­nual re­port shown be­low:

Widgets and Dashboard

In Kimi Work, we in­tro­duce two new fea­tures - Widgets and Dashboard - which make in­ter­ac­tions with Kimi K3 more vi­sual and per­sis­tent. Widgets let you gen­er­ate in­ter­ac­tive com­po­nents di­rectly within a chat, with con­nec­tions to lo­cal data or ex­ter­nal plu­g­ins for con­tin­u­ous up­dates. Dashboard brings the wid­gets you care about most into one per­sis­tent, per­son­al­ized view or­ga­nized around a topic, pro­ject, or goal.

Video Editing

Kimi K3 ex­cels at mo­tion de­sign, an­i­ma­tion, and video edit­ing be­cause its na­tive mul­ti­modal ar­chi­tec­ture un­der­stands text, im­ages, and video within the same model.

In one ex­am­ple, K3 cre­ated a 3Blue1Brown-style mo­tion-graph­ics ex­plainer of its own ar­chi­tec­ture, trans­lat­ing tech­ni­cal ideas into an­i­mated di­a­grams and tran­si­tions.

In an­other, Kimi K3 edited its own teaser video from 56 source clips, han­dling clip se­lec­tion, mo­tion-matched cuts, frame-ac­cu­rate beat syn­chro­niza­tion, au­dio pro­cess­ing, and mul­ti­ple rounds of re­vi­sion. A high-den­sity short video like this would typ­i­cally take an ex­pe­ri­enced ed­i­tor one to two work­ing days, or a be­gin­ner three to five.

Architecture and Infrastructure

Kimi K3 is built on Kimi Delta Attention (KDA) and Attention Residuals (AttnRes). KDA pro­vides an ef­fi­cient foun­da­tion for scal­ing at­ten­tion, while AttnRes se­lec­tively re­trieves rep­re­sen­ta­tions across depth rather than ac­cu­mu­lat­ing them uni­formly. Together, they form the ar­chi­tec­tural back­bone of a model de­signed to scale well be­yond the tril­lion-pa­ra­me­ter regime.

Kimi K3 uses Stable LatentMoE, ef­fec­tively ac­ti­vat­ing 16 of 896 ex­perts. At this level of spar­sity, rout­ing and op­ti­miza­tion be­come first-or­der chal­lenges. Quantile Balancing de­rives ex­pert al­lo­ca­tion di­rectly from router-score quan­tiles, elim­i­nat­ing heuris­tic up­dates and a sen­si­tive bal­anc­ing hy­per­pa­ra­me­ter, while Per-Head Muon ex­tends Muon by op­ti­miz­ing at­ten­tion heads in­de­pen­dently for more adap­tive learn­ing at scale. Sigmoid Tanh Unit (SiTU) and Gated MLA im­prove ac­ti­va­tion con­trol and at­ten­tion se­lec­tiv­ity re­spec­tively. Together, these ad­vances en­able sta­ble and ef­fi­cient train­ing at the 2.8-trillion-parameter scale.

Kimi K3 ap­plies quan­ti­za­tion-aware train­ing from the SFT stage on­ward, us­ing MXFP4 weights with MXFP8 ac­ti­va­tions for broad hard­ware com­pat­i­bil­ity. To pre­vent ex­pert im­bal­ance from de­grad­ing through­put at large ex­pert-par­al­lel scales, we in­tro­duce a fully bal­anced ex­pert-par­al­lel train­ing method with sta­tic shapes and no host syn­chro­niza­tion on the crit­i­cal path. Since in­fer­ence ef­fi­ciency like­wise ben­e­fits from larger high-band­width com­mu­ni­ca­tion do­mains, we rec­om­mend de­ploy­ing Kimi K3 on su­pern­ode con­fig­u­ra­tions with 64 or more ac­cel­er­a­tors. Finally, as KDA poses new chal­lenges for con­ven­tional pre­fix caching, we have con­tributed a cor­re­spond­ing im­ple­men­ta­tion to the vLLM com­mu­nity, to be re­leased along­side the model. KDA with pre­fill cache al­lows us to serve Kimi K3 at a highly com­pet­i­tive to­ken price de­spite its scale and long con­text.

More tech­ni­cal de­tails will be avail­able in our com­ing re­port.

Availability

Kimi K3 Agents: Download or up­date to the lat­est Kimi app from your mo­bile app store, avail­able on iOS, Android, and HarmonyOS, or visit kimi.com.

Work with Kimi K3: Download the lat­est Kimi Work desk­top app, ver­sion 3.1.0 or later, avail­able for Windows and Apple sil­i­con Macs.

Code with Kimi K3: Run Kimi Code in your ter­mi­nal and se­lect Kimi K3 us­ing the /model com­mand.

Build with the Kimi API: Visit the Kimi API Platform and se­lect kimi-k3. Pricing is $0.30/MTok for cache-hit in­put, $3.00/MTok for cache-miss in­put, and $15.00/MTok for out­put. Powered by Mooncake’s dis­ag­gre­gated in­fer­ence ar­chi­tec­ture, the of­fi­cial Kimi API achieves a cache hit rate above 90% in cod­ing work­loads.

Bring Kimi to your or­ga­ni­za­tion: Kimi Enterprise pro­vides en­ter­prise-grade data pri­vacy and mem­ber man­age­ment, with com­plete sep­a­ra­tion be­tween per­sonal and or­ga­ni­za­tion ac­counts. Visit the pric­ing page and se­lect Get Kimi Enterprise” to sub­scribe for your team.

Full Benchmark Table

Footnotes

All Kimi K3 re­sults re­ported be­low are ob­tained with the rea­son­ing ef­fort set to max’, set­ting tem­per­a­ture = 1.0 and top-p = 1.0. Depending on the bench­mark, each model is eval­u­ated un­der one of three agen­tic har­nesses — KimiCode, Claude Code, or Codex — as spec­i­fied in the notes be­low.

Coding bench­marks

DeepSWE. Kimi K3 is eval­u­ated with the KimiCode har­ness. The GLM-5.2 score is taken from the GLM-5.2 re­lease blog (https://​z.ai/​blog/​glm-5.2); all re­main­ing scores are from the of­fi­cial DeepSWE leader­board (https://​deep­swe.dat­acurve.ai/), un­der which Kimi K3 at­tains 67.3 with the mini-SWE-agent har­ness.

Terminal-Bench 2.1. Kimi K3 is eval­u­ated with the KimiCode har­ness. For all other mod­els, we re­port the best score across har­nesses: GLM-5.2 with Claude Code (https://​z.ai/​blog/​glm-5.2); Claude Opus 4.8 and Claude Fable 5 with Terminus 2 (https://​ar­ti­fi­cial­analy­sis.ai/​eval­u­a­tions/​ter­mi­nal­bench-v2 – 1); GPT 5.5 and GPT 5.6 Sol with Codex (https://​ope­nai.com/​in­dex/​pre­view­ing-gpt-5 – 6-sol/).

Program Bench. Kimi K3 is eval­u­ated with the KimiCode har­ness. The GLM-5.2 score is from https://​z.ai/​blog/​glm-5.2; all other scores are from https://​www.vals.ai/​bench­marks/​pro­gram­bench.

SWE Marathon. Kimi K3, Claude Opus 4.8, and Claude Fable 5 are eval­u­ated with the Claude Code har­ness; GPT 5.6 Sol is eval­u­ated with the Codex har­ness. The GLM-5.2 score is from https://​z.ai/​blog/​glm-5.2.

FrontierSWE. Kimi K3 is eval­u­ated with the KimiCode har­ness and GPT 5.6 Sol with the Codex har­ness; all other re­sults are from https://​www.fron­tier­swe.com/. Dominance scores are re­com­puted from the raw scores us­ing the of­fi­cial eval­u­a­tion script and are cur­rent as of July 16, 2026.

PostTrain Bench. Scores for GLM-5.2, GPT 5.5, and Claude Opus 4.8 are adopted from the of­fi­cial PostTrainBench re­sults. Kimi K3, Claude Fable 5, and GPT 5.6 Sol are eval­u­ated with the of­fi­cial Harbor im­ple­men­ta­tion at max­i­mum rea­son­ing ef­fort, av­er­aged over three runs — Kimi K3 and Claude Fable 5 with the Claude Code har­ness, and GPT 5.6 Sol with the Codex har­ness. Under the Claude Code har­ness, re­quests re­fused by Claude Fable 5 due to its us­age pol­icy au­to­mat­i­cally fall back to Claude Opus 4.8.

MLS Bench Lite. Kimi K3 is eval­u­ated with the KimiCode har­ness; GLM-5.2 and the Claude mod­els with the Claude Code har­ness; GPT 5.5 and GPT 5.6 Sol with the Codex har­ness.

KCB 2.0. Kimi K3 is eval­u­ated with both the KimiCode and Claude Code har­nesses; GLM-5.2, Claude Opus 4.8, and Claude Fable 5 with the Claude Code har­ness; GPT 5.5 and GPT 5.6 Sol with the Codex har­ness. All mod­els are eval­u­ated at max­i­mum rea­son­ing ef­fort, ex­cept GPT 5.5, which uses the xhigh” set­ting.

Productivity and agen­tic bench­marks

For OfficeQA Pro, each test case pro­vides the agent with the en­tire PDF cor­pus, with all PDFs ren­dered as im­ages and no ma­chine-read­able text avail­able.

OfficeQA Pro and SpreadsheetBench 2. Kimi K3, GLM-5.2, Claude Opus 4.8, and Claude Fable 5 are eval­u­ated with the Claude Code har­ness; GPT 5.5 and GPT 5.6 Sol are eval­u­ated with the Codex har­ness.

MCP Atlas. All mod­els are eval­u­ated on the 500-task pub­lic sub­set with a 100-turn limit, us­ing Gemini 3.1 Pro as the judge.

AutomationBench. All mod­els are eval­u­ated on the 600-task pub­lic sub­set, fol­low­ing the of­fi­cial GitHub setup in all other re­spects.

BrowseComp. We adopt the con­text-com­paction strat­egy used in the Claude model cards, trig­gered at 300K to­kens. When eval­u­ated with a 1M-token con­text win­dow and no con­text man­age­ment, Kimi K3 achieves a score of 90.4. The re­sults of Claude Fable 5, Claude Opus 4.8, GPT 5.6 Sol, and GPT 5.5 are cited from https://​www.an­thropic.com/​news/​claude-fa­ble-5-mythos-5 and https://​ope­nai.com/​in­dex/​gpt-5 – 6/.

GDPval-AA v2 and AA-Briefcase scores are cited from https://​ar­ti­fi­cial­analy­sis.ai/.

Multimodal bench­marks

Except for ZeroBench, which fol­lows the of­fi­cial set­ting and is run five times, all mul­ti­modal scores are av­er­aged over three runs. MMMU-Pro is eval­u­ated fol­low­ing the of­fi­cial pro­to­col, pre­serv­ing the orig­i­nal in­put or­der and prepend­ing im­ages to the text in­put.

PerceptionBench. PerceptionBench is an in-house bench­mark that fo­cuses on atomic vi­sual per­cep­tion ca­pa­bil­i­ties.

Limitations

Sensitivity to think­ing his­tory. K3 was trained in the pre­served think­ing his­tory mode. If the agent har­ness fails to pass back all the his­tor­i­cal think­ing con­tent as re­quired, or if an on­go­ing ses­sion with an­other model is switched over to K3, gen­er­a­tion qual­ity may be­come highly un­sta­ble. We rec­om­mend us­ing a har­ness with ver­i­fied com­pat­i­bil­ity, such as Kimi Code, and avoid­ing switch­ing to K3 in the mid­dle of a ses­sion.

Excessive proac­tive­ness. K3′s train­ing places par­tic­u­lar em­pha­sis on long-hori­zon, chal­leng­ing tasks. As a re­sult, when it en­coun­ters mi­nor is­sues or am­bigu­ous user in­tent dur­ing task ex­e­cu­tion, it may make un­ex­pected de­ci­sions on the user’s be­half. If your ap­pli­ca­tion re­quires the agent to op­er­ate within well-de­fined bound­aries and re­frain from ex­ces­sive im­pro­vi­sa­tion, please im­pose more ex­plicit be­hav­ioral con­straints on K3 in the sys­tem prompt or in AGENTS.md.

Despite be­ing a highly com­pet­i­tive model over­all, K3 nonethe­less ex­hibits a no­tice­able gap in user ex­pe­ri­ence com­pared with Claude Fable 5 and GPT 5.6 Sol.

Measuring Progress Toward AGI

www.kaggle.com

$100 AI Music Video: Claude Fable 5 vs. GPT-5.6 Sol

www.tryai.dev

We built a small agen­tic har­ness with one job: hand a model a song, a hard dol­lar bud­get, and a set of tools, then get out of the way and let it pro­duce a full mu­sic video on its own. The model re­searches which video mod­els ex­ist, gen­er­ates clips, watches its own footage, ed­its with ffm­peg, and as­sem­bles a fi­nal cut.

A few read­ers of our last build-off said they wanted to see how tool use ac­tu­ally varies be­tween mod­els, so we gave fron­tier-level mod­els an open-ended, long-hori­zon task where each model de­cides on its own what to re­search, what to gen­er­ate, and how to edit. We log every tool call, so you can see ex­actly how each one worked (full tran­scripts be­low).

We ran two mod­els, Claude Fable 5 and GPT-5.6 Sol, each at two bud­gets ($25 and $100), for four runs to­tal. Every run got the same song (Bruno Mars and Mark Ronson’s Uptown Funk”), a short text de­scrip­tion, and a time-stamped lyric tran­script.

The setup

Each model ran an au­tonomous tool-call­ing loop with six tools:

plan: a tool for think­ing (no cost, no ac­tion).

we­b_search: to re­search gen­er­a­tion mod­els and their APIs and fetch in­for­ma­tion about mu­sic videos (if needed).

get_bud­get: to check the re­main­ing bud­get.

gen­er­ate_im­age and gen­er­ate_video: the only tools that spend bud­get. The model can pick any FAL or Replicate model and pass its own pa­ra­me­ters.

run_­com­mand: a lo­cal shell with ffm­peg/​ff­probe avail­able, used to an­a­lyze au­dio, cut and con­cate­nate clips, and mux the fi­nal video.

Once the bud­get hits zero, paid gen­er­a­tion is re­fused, but the model can keep edit­ing. Every model mes­sage, tool call, charge, and er­ror was logged. The whole har­ness is open source at github.com/​her­shalb/​mu­sic-video-arena, so you can run it your­self.

The four videos

Each clip be­low is the mod­el’s fi­nal, self-as­sem­bled out­put.mp4, full length with the orig­i­nal song muxed in.

The num­bers

All four runs fin­ished on their own (none hit a step or time limit) and all four pro­duced a valid, full-length video with the orig­i­nal song muxed in.

Generation spend” is the me­tered FAL cost, which is what the bud­get caps. At $25 both mod­els nearly ex­hausted it. At $100 they spent $36.57 (Sol) and $48.60 (Fable), so more bud­get did trans­late into more footage. It does not in­clude the cost of run­ning the model it­self, which we add be­low.

Time to fin­ished video

What each model built with

Left to choose their own tools, the mod­els di­verged. Three of the four runs went pure text-to-video. Only GPT-5.6 Sol at $25 used an im­age-to-video pipeline (generating stills first, then an­i­mat­ing them). GPT-5.6 Sol at $100 mixed three dif­fer­ent video mod­els in a sin­gle run.

Prices are FALs listed rates, shown per sec­ond of out­put video un­less noted. Hailuo 2.3 Standard is priced per video (about $0.28 per 6s clip), and Seedance 1.0 Pro is to­ken-priced (~$0.62 per 5s 1080p clip, shown above as its ef­fec­tive per-sec­ond rate). Distinct clips gen­er­ated per run ranged from 46 to 80.

Tool us­age

How each run spent its tool calls (this counts at­tempts, in­clud­ing failed gen­er­a­tion calls).

Each run’s full tran­script, every plan, tool call, and com­mand, is here: Fable 5 · $25, Sol · $25, Sol · $100, Fable 5 · $100.

Errors along the way

Failed calls” are gen­er­a­tion re­quests that re­turned an er­ror (mostly tran­sient net­work fail­ures to the provider). They were not charged, but the model spent steps retry­ing them.

Token us­age

Total cost per run

The bud­get only me­ters gen­er­a­tion (FAL) spend. Adding the LLM to­ken cost for Claude Fable 5 ($10 / $50 per 1M in­put/​out­put) and GPT-5.6 Sol ($5 / $30), gives the to­tal cost of each run.

For Claude Fable 5, the to­kens alone ran $16.99 to $25.05, about 30 – 40% of each run’s to­tal. GPT-5.6 Sol’s to­ken cost stayed near $3 – 4 de­spite sim­i­lar to­ken vol­ume.

Method notes

Same in­puts for all four runs: song, a short text de­scrip­tion, and a time-stamped lyric tran­script. Each model chose its own gen­er­a­tion mod­els on FAL and did its own ffm­peg edit­ing.

Wall-clock time in­cludes the mod­el’s own re­tries and any wait­ing on provider queues.

Generation spend is a best-ef­fort es­ti­mate from a per-model price table.

Try it your­self

The arena is open source: github.com/​her­shalb/​mu­sic-video-arena. Point it at your own song and bud­get, swap in whichever mod­els you want to pit against each other, and see what they build. Issues and PRs wel­come, we would love feed­back on the setup.

Our take

None of the mu­sic videos were great, but watch­ing how the mod­els got there was pretty in­ter­est­ing and does show where gaps still clearly ex­ist for fron­tier-level mod­els. A few things notes:

Character and story con­sis­tency was a strug­gle for all four. Recurring char­ac­ters drift be­tween shots, and none of the videos hold a co­her­ent sto­ry­line from start to fin­ish.

The mod­els take lyrics very lit­er­ally. Make a dragon wanna re­tire, man” gets you an ac­tual dragon on screen. It’s in­ter­est­ing for a few shots, but got a lit­tle weird af­ter a while.

Tempo match­ing is weak. The cuts land on the beat (they all ran the ffm­peg beat de­tec­tion), but the mo­tion in­side the clips, danc­ing, cam­era moves, rarely matches the song’s tempo, so it of­ten feels a lit­tle off. An ex­am­ple line gotta kiss my­self I’m so pretty”, shows the main char­ac­ter mak­ing a kiss­ing mo­tion way too slowly.

GPT-5.6 Sol at $25 was the most in­ven­tive ed­i­tor. It over­laid text and an­i­mated still im­ages with video ef­fects, tech­niques none of the other runs tried. The rest mostly just stitched gen­er­ated clips to­gether. GPT 5.6 Sol $100 also tried mul­ti­ple video mod­els in­stead of just stick­ing with one like Fable did.

Nobody re­ally it­er­ated on the edit. Once clips ex­isted, the mod­els con­cate­nated and muxed, but rarely went back to re-cut or add ef­fects, and none se­ri­ously probed their own clips to con­firm they were any good. GPT-5.6 Sol’s $100 run shipped some gen­uinely low-qual­ity AI clips, while Claude Fable 5 hap­pened to pick a model with more co­her­ent out­put. Some of this is prob­a­bly a model lim­i­ta­tion, but the lack of self-re­view is no­table.

Neither model touched Replicate. Both FAL and Replicate keys were avail­able, but all four runs used FAL ex­clu­sively.

Claude Fable 5 was the pricier pick. It cost more per run (and the most over­all, at $73.65) de­spite fin­ish­ing faster than GPT-5.6 Sol. Subjectively, we slightly pre­ferred the Fable $100 video, though none blew us away.

$100 was prob­a­bly too much bud­get. Neither model wanted to spend near the cap, and both kept their step counts mod­est. With that head­room they could have, for ex­am­ple, gen­er­ated con­sis­tent char­ac­ter im­ages up front and an­i­mated from those, but nei­ther chose to.

We’ll see if mod­els can im­prove on more sub­jec­tive/​styl­is­tic tasks as they con­tinue to get smarter, but for now there’s still a lot of room for im­prove­ment.

Try it your­self

Every model men­tioned here is avail­able on TryAI with one ac­count, pay-as-you-go, no sub­scrip­tion.

Introducing LM Studio Bionic: the AI agent for open models

lmstudio.ai

Today, we’re tak­ing the biggest leap for­ward in LM Studio’s evo­lu­tion. Meet LM Studio Bionic, the AI agent made for open mod­els.

Bionic is the AI agent for get­ting real work done with open mod­els, in­clud­ing cod­ing, re­search, and com­plex work with doc­u­ments and files. You can use lo­cal mod­els or switch to open-source mod­els in the cloud for heav­ier tasks, all while stay­ing in con­trol of your pri­vacy and AI spend.

For all LM Studio Bionic users, we com­mit to Zero Data Retention and never train­ing on your data.

Bionic brings to­gether:

A Bionic agent that ex­cels at cod­ing and doc­u­ment work

Voice in­put with state-of-the-art lo­cal voice tran­scrip­tion

Flexible model ex­e­cu­tion: run lo­cally, con­nect through LM Link, or use the largest fron­tier open source mod­els through LM Studio Secure Cloud

Better cost con­trol by let­ting users choose the right model and com­pute en­vi­ron­ment for each task

Offline voice tran­scrip­tion

Use Bionic’s voice key­board with lo­cal tran­scrip­tion to speak through ideas, prompts, and ed­its - all en­tirely lo­cally on your de­vice, us­ing state-of-the-art lo­cal au­dio mod­els. For launch, we are ship­ping Voxtral by Mistral AI. Voxtral is a per­for­mant mul­ti­lin­gual re­al­time tran­scrip­tion model.

Use Bionic’s voice key­board to dic­tate into any app with lo­cal tran­scrip­tion.

Start the voice key­board from any app, and Bionic will be­gin tran­scrib­ing where your cur­sor is.

Bionic for Coding

Bionic sup­ports a wide range of cod­ing needs with­out giv­ing up pri­vacy and con­trol.

Bionic can in­spect lo­cal code­bases, ex­plain un­fa­mil­iar code, and help you make changes.

Create a Code pro­ject and point it to a lo­cal folder. Ask Bionic to in­ves­ti­gate, edit, or de­bug, and re­view its work as it goes. Inline diffs make every code change easy to in­spect, and with agen­tic code search, Bionic can quickly find rel­e­vant files, trace be­hav­ior, and ex­plain un­fa­mil­iar code.

Bionic works with pow­er­ful open mod­els like GLM 5.2 and Kimi K2.7 Code, so you can build more while keep­ing costs un­der con­trol.

Bionic for work­ing with docs, slides, and sheets

Bionic is also built for gen­eral pro­duc­tiv­ity and deep knowl­edge work.

Give Bionic doc­u­ments to work with, or ask it to gen­er­ate new doc­u­ments, decks, spread­sheets, and more from scratch.

Use Bionic across doc­u­ments, PDFs, decks, spread­sheets, and more. In a Work pro­ject, Bionic processes doc­u­ments in a sand­boxed en­vi­ron­ment, keep­ing the rest of your com­puter and files safe. It can or­ga­nize lo­cal di­rec­to­ries, edit files, sum­ma­rize ma­te­ri­als, and bring out­side con­text into your work­flow with na­tive web search. Automatic check­points let you safely re­view or roll back changes, while in-app pre­views keep your ma­te­ri­als and work­flow in one place. We’re con­tin­u­ing to add pre­view sup­port for more file types, so stay tuned!

Natively Local

Download and run lo­cal mod­els in Bionic.

Download the lat­est lo­cal LLMs di­rectly within the Bionic app, then use them for sim­ple chats or ad­vanced agen­tic tasks. Local mod­els in Bionic are pow­ered by the LM Studio run­time.

Cloud in­fer­ence with Zero Data Retention by de­fault

Bionic sup­ports the lat­est fron­tier open mod­els for your most com­plex tasks, run­ning on the LM Studio Secure Cloud.

Bionic is built for a world where open mod­els keep get­ting bet­ter. As fron­tier open source mod­els im­prove at cod­ing, rea­son­ing, tool call­ing, and long-con­text tasks, Bionic gives you a way to try them in LM Studio Secure Cloud. When us­ing cloud mod­els, your re­quests are processed tran­siently and are not re­tained af­ter the re­quest com­pletes.

Getting started

Download LM Studio Bionic.

Bionic is a new, sep­a­rate app from LM Studio. For ad­vanced low-level con­fig­u­ra­tion, you can con­tinue to use LM Studio along­side Bionic.

To use cloud mod­els, cre­ate an LM Studio ac­count to set up billing for your user.

From there, con­nect a pro­ject, choose a model, and start work­ing with the Bionic agent!

What’s next

We’ll keep im­prov­ing the ex­pe­ri­ence as open mod­els be­come more ca­pa­ble and as we learn from how peo­ple use Bionic in real pro­jects.

The Human-in-the-Loop is Tired

pydantic.dev

Yet an­other thought piece about LLMs. I know. Bear with me.

This is an at­tempt to put words around some­thing I think most de­vel­op­ers are ex­pe­ri­enc­ing right now but haven’t had time to make sense of. Programming with LLMs is gen­uinely use­ful and gen­uinely desta­bi­liz­ing. These two things co­ex­ist. If we pre­tend the sec­ond one is­n’t hap­pen­ing, we will all burn out.

At Pydantic, we build tools that de­vel­op­ers use to val­i­date data, build AI agents, and ob­serve what their sys­tems are do­ing in pro­duc­tion. We are, quite lit­er­ally, in the busi­ness of mak­ing LLM-powered soft­ware more re­li­able. And we are also hav­ing a weird time.

This is­n’t a think­piece about whether AI will re­place pro­gram­mers. It’s not a doomer es­say and it’s not a hype piece. It’s an hon­est ac­count of what it feels like to be a de­vel­oper right now, from some­one in­side it, and some thoughts on what might ac­tu­ally help.

Hands in the fab­ric

When I was first learn­ing to code in my early twen­ties, I re­mem­ber hav­ing this dis­tinct sen­sa­tion that pro­gram­ming let me dip my hands into the fab­ric of the uni­verse and shape it to my will. This was, of course, be­fore I’d hit too many com­pile er­rors. But that feel­ing of touch­ing some deep fun­da­men­tal layer of ab­strac­tion, of be­ing able to make things from noth­ing but logic, has al­ways stuck with me.

I’m not a Computer Science grad­u­ate. I’m a de­signer and a pro­gram­mer — for­mally trained in the first, self-taught in the sec­ond. I came to the for­malisms of soft­ware en­gi­neer­ing through painful ex­pe­ri­ence rather than aca­d­e­mic in­struc­tion. If any­thing, that made me take those prin­ci­ples more se­ri­ously once I un­der­stood them. When you’ve earned your opin­ions about ar­chi­tec­ture and code qual­ity the hard way, they feel less like text­book rules and more like scar tis­sue.

That pri­mal feel­ing of cre­ation? It’s the same promise that the low-code and no-code tools of the 2010s kept mak­ing but never quite de­liv­ered on. I’m old enough to re­mem­ber build­ing web pages in Dreamweaver, watch­ing Adobe spruik zero-code de­sign tools that gen­er­ated ab­solute spaghetti un­der the hood. It was al­ways al­most there, just good enough to hint at a fu­ture that was just around the cor­ner (if only you were smart enough to grasp it).

If you’re cyn­i­cal about the cur­rent wave of AI tools, I get it. We’ve been promised this be­fore. But this time the gap be­tween promise and re­al­ity has ac­tu­ally, fi­nally, nar­rowed to some­thing mean­ing­ful. And that’s ex­actly what makes it so un­set­tling.

What the code writes it­self” ac­tu­ally feels like

Yes the code (sorta) writes it­self, but the hu­man re­view­ing, di­rect­ing, and course-cor­rect­ing feels worse, not bet­ter.

I re­cently had a con­ver­sa­tion with my col­league Douwe, who main­tains the Pydantic AI frame­work and has been one of the most thought­ful peo­ple I know about in­te­grat­ing LLMs into open source work­flows. He de­scribed wak­ing up to thirty PRs every morn­ing, each one pulled overnight by some­one’s AI, and need­ing to make snap judg­ment calls on every sin­gle one. The temp­ta­tion to del­e­gate the re­view it­self to an AI was enor­mous. But, as he put it: at that point, what am I still do­ing here?”.

The hon­est truth is that in the last few months, there have been days when I have spent close to two full days writ­ing a plan for an LLM to ex­e­cute: ob­ses­sively clar­i­fy­ing, spec­i­fy­ing, re-spec­i­fy­ing, only to have it still do some­thing in­ex­plic­a­bly stu­pid. Port a React hook into a Storybook story file. Read from the wrong plan. Invent com­po­nents that don’t ex­ist. And these aren’t er­rors of ca­pa­bil­ity; they’re er­rors of co­her­ence. The mod­els are smart enough to pro­duce plau­si­ble code, but not al­ways smart enough to main­tain a co­her­ent in­tent across a com­plex change.

This cre­ates a pe­cu­liar new kind of fa­tigue, the fa­tigue of su­per­vi­sion: of hold­ing the in­tent in your head while the ma­chine gen­er­ates vol­umes of mostly-cor­rect out­put that still needs your eyes, your judg­ment, and your taste. Douwe put it well: he used to get a dopamine hit from col­lab­o­rat­ing with a real per­son on a cool fea­ture in open source. Helping some­one be­come bet­ter at their craft. Now, he said, everything I write goes into some AI black hole. There’s no per­son on the other side ac­tu­ally learn­ing any­thing.” That loss is real and it’s worth nam­ing.

The in­ten­sity trap

Simon Willison re­cently high­lighted a Berkeley Haas study which de­scribes how AI us­age in­creases the in­ten­sity of work. The con­stant pull of one more prompt at the end of the day, one more fea­ture that could make this per­fect.” I felt that one in my bones. I was up un­til nearly 2am re­cently, prompt­ing, be­cause I was so close to get­ting a plan right. Or so I thought.

Marcelo, an­other Pydantic col­league, when asked about his Claude Code ses­sion freez­ing said: just open 5 claude ses­sions. You’ll never no­tice be­cause you’re busy giv­ing feed­back to the oth­ers.” He was jok­ing. I think. But it cap­tures some­thing true about the cur­rent mo­ment. The par­al­lelism is ex­hil­a­rat­ing and kind of feral. The num­ber of things you can start has dra­mat­i­cally in­creased. The num­ber of things you can thought­fully fin­ish has­n’t changed at all, be­cause that part still re­quires the one re­source we can’t par­al­lelise: your brain.

Here’s a term for what I think is hap­pen­ing: the hu­man re­ward func­tion prob­lem. In ma­chine learn­ing, a re­ward func­tion tells an agent what good looks like. Writing code by hand was never easy, but it was full of small re­wards. Solving a prob­lem in your head. Understanding a gnarly bit of logic. Watching the code com­pile. The feel­ing of con­trol. LLM-assisted pro­gram­ming has au­to­mated much of the work that gen­er­ated those dopamine hits and re­placed it with the cog­ni­tive load of re­view and su­per­vi­sion. The sat­is­fy­ing part shrank. The ex­haust­ing part grew. And there are no new re­wards to fill the gap.

If you’re feel­ing like your work is si­mul­ta­ne­ously more pro­duc­tive and less sat­is­fy­ing, you’re not bro­ken. The feed­back loop is bro­ken. And I think we need to start treat­ing that as an en­gi­neer­ing prob­lem in its own right, not a per­sonal fail­ure.

It’s also, frankly, quite lonely. Programming with an LLM is an in­tensely soli­tary ac­tiv­ity.

You and the ma­chine, go­ing back and forth, re­fin­ing and prompt­ing and re­view­ing. The nat­ural mo­ments where you’d turn to a col­league to ask a ques­tion, to rub­ber-duck a prob­lem, to share the small vic­tory of some­thing fi­nally click­ing. Those mo­ments get qui­etly re­placed by an­other prompt. In a team with­out a strong ex­ist­ing cul­ture of col­lab­o­ra­tion, this has a ten­dency to fur­ther sep­a­rate peo­ple, to chill com­mu­ni­ca­tion at pre­cisely the mo­ment when you most need the re­as­sur­ance that other hu­mans are find­ing this hard too.

And it’s ad­dic­tive in a way that makes the iso­la­tion worse. Sometimes you get some­thing bril­liant, some­times garbage, and you never quite know which. Textbook Skinner Box. It can be gen­uinely hard to step back and re­mem­ber that you’re al­lowed to just… write code. But switch­ing be­tween LLM-assisted and man­ual work is jar­ring and un­com­fort­able, two very dif­fer­ent modes of think­ing, and it takes a kind of ma­tu­rity and con­fi­dence to give your­self per­mis­sion to switch.

Breakpoints

This mo­ment brings to mind the fear and angst caused by re­spon­sive de­sign. I was work­ing as a de­signer and fron­tend de­vel­oper at the time, fol­low­ing Ethan Marcotte and the Zeldman / A Book Apart crowd like every­one else, and I re­mem­ber how un­set­tling it felt to be told that the fixed-width lay­outs we’d all mas­tered were ba­si­cally over.

For the younger devs: there was a gen­uine cul­tural mo­ment around 2009 when web­sites moved from fixed, pixel-per­fect, mag­a­zine-style lay­outs to fluid, re­spon­sive ones. And de­sign­ers hated it. The loss of con­trol was ex­is­ten­tial for peo­ple whose en­tire iden­tity was built around pre­cise lay­outs and per­fect grids. You’re telling me the user might see my de­sign at any width? On any de­vice? That the lay­out I crafted would… flow?

Image de­sign by Jyotika Sofia Lindqvist

Image de­sign by Jyotika Sofia Lindqvist

The re­sis­tance was in­tense. And it was un­der­stand­able. People had built real ex­per­tise in a par­a­digm that was be­ing fun­da­men­tally dis­rupted. The de­sign­ers who thrived through that tran­si­tion were the ones who re­framed their skills. The eye for pro­por­tion still mat­tered. The un­der­stand­ing of hi­er­ar­chy still mat­tered. The craft did­n’t die, it evolved. What be­came less rel­e­vant was the ob­ses­sion with pixel-level con­trol. What be­came more rel­e­vant was un­der­stand­ing sys­tems, adapt­abil­ity, and de­sign­ing for un­cer­tainty.

I don’t want to over­sell this par­al­lel. Responsive de­sign played out over years. The cur­rent shift is mea­sured in months. Agencies lost clients and de­sign­ers lost gigs over the re­spon­sive tran­si­tion, but it did­n’t carry the same ex­is­ten­tial dread. The stakes are ma­te­ri­ally dif­fer­ent, and the pace is gen­uinely ex­haust­ing in a way that the re­spon­sive tran­si­tion never was. But the un­der­ly­ing pat­tern, of craft evolv­ing rather than dy­ing, of the core skills mat­ter­ing more not less, I think that holds.

Working with LLMs on code feels like a sim­i­lar in­flec­tion point. The skill is­n’t gone, it’s shift­ing. You’re not less of an en­gi­neer be­cause you did­n’t hand-write every line. But you do still need to know what good looks like, ar­guably more than ever, be­cause you’re now the qual­ity gate for a much higher vol­ume of out­put.

What sur­vives

In an era when any­one can pro­duce rea­son­able-look­ing UI and code that com­piles, the dis­tin­guish­ing mark­ers be­come: taste, nu­ance, ma­ture ar­chi­tec­tural opin­ions, and the con­trar­ian calls that come from gen­uine ex­per­tise rather than pat­tern-match­ing.

It’s no­tice­able to me that we are most suc­cess­ful guid­ing LLMs in the do­mains where we un­der­stand the code, the de­ci­sions, and the trade-offs most deeply. As we ven­ture into the shal­low ends of our skill sets, the out­puts be­come markedly more im­pres­sion­is­tic. Further from pro­duc­tion-ready. More plau­si­ble-look­ing, less ac­tu­ally cor­rect. The model does­n’t know what it does­n’t know, so it fills the gaps with con­fi­dence. Sound fa­mil­iar? It’s a very hu­man fail­ure mode, too.

But new skills are also emerg­ing. I’ve started run­ning what I call pre-mortems on com­plex plans: ask­ing a fresh LLM ses­sion to as­sume the plan has cat­a­stroph­i­cally failed and di­ag­nose why. It catches spec­i­fi­ca­tion gaps that I miss af­ter two days of be­ing too deep in the de­tails. One of our en­gi­neers built a tool that ex­tracts rules from thou­sands of his past code re­view com­ments to seed an AGENTS.md file, es­sen­tially en­cod­ing years of im­plicit en­gi­neer­ing judg­ment into in­struc­tions an LLM can fol­low. That’s not the death of ex­per­tise. That’s ex­per­tise be­ing dis­tilled.

The peo­ple who are find­ing their foot­ing right now seem to share a few traits: they have strong opin­ions earned through prac­tice, they can dis­tin­guish be­tween prin­ci­ples that still ap­ply and habits that were just band­width con­straints, and they’re will­ing to evolve their work­flow with­out aban­don­ing their stan­dards.

A view from in­side the loop

I don’t think the cur­rent wave of AI rep­re­sents the end of soft­ware en­gi­neer­ing as a pro­fes­sion. I do think it rep­re­sents a se­ri­ous con­trac­tion and a fun­da­men­tal re­shap­ing of what the work is. The fear of ob­so­les­cence is le­git­i­mate. The fear of skill rot is le­git­i­mate. And the fear that if you don’t go fast enough you’ll be left be­hind is — while of­ten over­stated — not en­tirely un­founded.

But the bot­tle­neck was never the code. It was al­ways the hu­man at­ten­tion, the en­gi­neer­ing judg­ment, the abil­ity to hold a co­her­ent vi­sion for a sys­tem. We just did­n’t no­tice be­cause writ­ing code felt like the hard part. Now that it’s be­ing au­to­mated, those hu­man ca­pac­i­ties are re­vealed as the ac­tual scarce re­source. And scarce re­sources are valu­able.

So if you’re feel­ing over­whelmed, desta­bi­lized, si­mul­ta­ne­ously more pro­duc­tive and less happy, know that you’re not alone. The team build­ing the tools you’re prob­a­bly us­ing to nav­i­gate this mo­ment is feel­ing it too. We’re de­bug­ging our re­ward func­tions in real time, same as you.

The code is chang­ing. What we do with it is chang­ing. How it feels is… a work in progress.

But the hu­mans are still in the loop. We’re just tired. And that’s worth talk­ing about.

We’re build­ing tools to make this less chaotic: Pydantic AI and Logfire. We’re also hir­ing.

Immersive Math

immersivemath.com

Preface

A few words about this book.

Chapter 1: Introduction

How to nav­i­gate, no­ta­tion, and a re­cap of some math that we think you al­ready know.

Chapter 2: Vectors

The con­cept of a vec­tor is in­tro­duced, and we learn how to add and sub­tract vec­tors, and more.

Chapter 3: The Dot Product

A pow­er­ful tool that takes two vec­tors and pro­duces a scalar.

Chapter 4: The Vector Product

In three-di­men­sional spaces you can pro­duce a vec­tor from two other vec­tors us­ing this tool.

Chapter 5: Gaussian Elimination

A way to solve sys­tems of lin­ear equa­tions.

Chapter 6: The Matrix

Enter the ma­trix.

Chapter 7: Determinants

A fun­da­men­tal prop­erty of square ma­tri­ces.

Chapter 8: Rank

Discover the be­hav­iour of ma­tri­ces.

Chapter 9: Linear Mappings

Learn to har­ness the power of lin­ear­ity…

Chapter 10: Eigenvalues and Eigenvectors

This chap­ter has a value in it­self.

Security Verification

www.ft.com

For help please visit help.ft.com. We apol­o­gise for any in­con­ve­nience.

The fol­low­ing in­for­ma­tion can help our sup­port team to re­solve this is­sue.

Just a moment...

www.smithsonianmag.com

Pebble Mega Update - July 2026

repebble.com

TL:DR;

#Pebble Time 2 Shipping Status

Since we started mass pro­duc­tion in late March, we’ve built over 23,000 Pebble Time 2 watches. We’re over 80% of the way through ful­fill­ing all the pre-or­ders we’ve re­ceived! But that means there are still some ul­tra pa­tient folks who haven’t re­ceived their watches yet. If you’ve placed an pre-or­der for PT2 and haven’t re­ceived it yet (including Batch 6 - August), here’s when we ex­pect to ship your watch out:

Pebble Time 2 - Black → July 31

Pebble Time 2 - Red → July 31

Pebble Time 2 - Grey → July 28

Pebble Time 2 - Blue → July 28

Coincidentally, this means that we’ll be in-stock’ with no wait very soon! If you’ve been hold­ing off plac­ing an or­der be­cause you did­n’t want to wait, now is the time to jump on it. This won’t last for­ever - first-come first serve. As soon as the cur­rent in­ven­tory is sold out, we’ll be back in pre-or­der mode wait­ing for the next ship­ment.

Order to­day on rePeb­ble.com/​watch.

Major props to our three per­son cus­tomer sup­port and lo­gis­tics team! Claudio, Trevor and Colin have an­swered thou­sands of your ques­tions and helped ship watches safely onto your wrist in 93 coun­tries. Have a ques­tion? Please check out our Help site first. If that does­n’t have an an­swer, please email us at [email protected].

Want an ex­tra Pebble charger? shop.repeb­ble.com now car­ries ac­ces­sories - full se­lec­tion of straps com­ing soon.

#Pebble Software - Progress and Roadmap

Over the last 6 months, the core four per­son Pebble soft­ware team built and shipped a met­ric ton of new Pebble open source soft­ware! Our im­prove­ments were cen­tered around these ar­eas:

Battery life

We’ve (well, mostly Gerard 🙂) worked ex­tra­or­di­nar­ily hard over the last few months, op­ti­miz­ing and re­duc­ing power con­sump­tion in PebbleOS. As pre­dicted, we boosted the me­dian bat­tery life of Pebble 2 Duo from 17 days (last sum­mer) to over 30 days. Pebble Time 2 me­dian is cur­rently around 21 days - more im­prove­ments in the works here too! The biggest con­sumers of power are back­light, watch­faces with a lot of an­i­ma­tions and health track­ing. If you want to hypermile’ your Pebble, try switch­ing to a low-an­i­ma­tion watch­face and the new Battery Saver back­light mode (Settings → Display → Backlight).

Apps and SDK

Together with the Moddable team, we’ve pub­lished sev­eral Pebble SDK up­dates in­tro­duc­ing new fea­tures like:

Touch Screen API (Calculator on your wrist any­one?)

Speaker API (useful for tun­ing your gui­tar, or feed­ing your Tamagotchi)

RGB Backlight API (try it in this wild lit­tle app Chinese Toy Phone)

Apps can now de­ter­mine how they were quick launched (ie by sin­gle press, long press)

Alloy (native JS apps)

FFI - run C code within Alloy JS apps (similar to Android NDK) and js de­bug­ger A bunch of new JS APIs peb­ble build –debug now de­fines PBL_DEBUG and launches XSBUG, a pow­er­ful JS de­bug­ger

FFI - run C code within Alloy JS apps (similar to Android NDK) and js de­bug­ger

A bunch of new JS APIs

peb­ble build –debug now de­fines PBL_DEBUG and launches XSBUG, a pow­er­ful JS de­bug­ger

Developers in the Pebble com­mu­nity have cre­ated 2,120 apps and watch­faces for Pebble Time 2 and Pebble Round 2 al­ready!

Index 01

The first ver­sion of all Index 01 func­tion­al­ity is up and run­ning in­side the Pebble mo­bile app. Don’t have an Index 01 yet? You can check out how it works and try the soft­ware in­ter­face in the Pebble app, just go to Settings → General → Enable Index feed.

All the main fea­tures are in, in­clud­ing sync­ing to iOS Reminders, Obsidian, Google Tasks, Calendar, Android mu­sic con­trol, MCPs and send­ing record­ings or tran­scrip­tions to your own server or app via Webhook. Optional en­cryp­tion (you own the keys) pro­tects op­tional cloud backup. And of course, it’s all open source (github.com/​core­de­vices/​mo­bileapp). We even built a lit­tle we­bapp that you can use to ac­cess your Index in­for­ma­tion from any­where → in­dex.rePeb­ble.com. Watch the pod­cast or read the blog post to learn more.

Stability

Thanks to help­ful bug re­ports from y’all, we’ve made hun­dreds of small im­prove­ments to PebbleOS and the Pebble mo­bile app. Please keep it com­ing!

I’ll dive into one spe­cific (and ul­tra tech­ni­cal) topic - re­verse PPoGATT (Pebble Protocol over GATT). Quick his­tory: dur­ing the first Pebble era, we con­fig­ured the Pebble mo­bile app to ex­pose a PPoGATT ser­vice, as means to work around the lack of IPC be­tween iOS apps. This setup is the op­po­site of how Bluetooth ac­ces­sories nor­mally con­nect to phones and caused a num­ber of weird prob­lems! Also this setup blocks us from us­ing iOS AccessorySetupKit (ASK), which is a pre­req­ui­site for us to im­ple­ment the new Notification Forwarding fea­ture (EU only) that will fi­nally en­able you to re­ply to no­ti­fi­ca­tions. Enabling ASK is go­ing to be tough - our iOS app must ei­ther use ASK or not, mean­ing that we need to up­grade the re­cov­ery firmware on all Pebble watches in the field to re­verse PPoGATT be­fore we can switch ASK on. Anyways, we have the first piece of the puz­zle in place (Pebble Round 2’s re­cov­ery firmware al­ready has the up­grade). This saga will take a while.

Community Contributions

Thank you to the dozens of de­vel­op­ers from the broader Pebble com­mu­nity who have con­tributed huge im­prove­ments to PebbleOS and the mo­bile app, in­clud­ing Apple HealthKit and Google health sync, im­proved light sen­sor al­go­rithms, no­ti­fi­ca­tion fil­ter­ing, many new lan­guage packs, and so many bug fixes. It’s so fun and very en­er­giz­ing to see so many tal­ented hack­ers push PRs! See the full list and thank you devs! Some ex­cit­ing new com­mu­nity built fea­tures are on the hori­zon: HRV, SP02, ex­pos­ing HRM via BLE, mic API, mul­ti­ple BLE clients and more

Software Roadmap

Your browser does not sup­port the video tag.

We keep im­prov­ing Pebble soft­ware pri­mar­ily be­cause we are Pebble users. We love us­ing the prod­ucts we make and con­tin­u­ally want to make them bet­ter! Here’s some of the things we’re ex­cited to work on next:

Send text app (Android only)

Find my phone

Beautiful new weather app for PT2 and PR2 (created by grim, a win­ner of the Spring Developer Contest)

Tweaking PebbleOS UI for Round 2

Improving the Pebble mo­bile app UI

WYSIWYG watch­face ed­i­tor - spir­i­tual suc­ces­sor to Pebble Canvas

Continue tran­si­tion to fully re­verse PPoGATT role to en­able ASK and (eventually) replies to no­ti­fi­ca­tions for iOS users (in EU)

See be­low for in­dex roadmap

#Pebble Time 2 - Problems You’ve Reported

Thank you all for re­port­ing any bugs or is­sues you’ve spot­ted! We test each watch at the fac­tory be­fore it’s shipped out, and we test each soft­ware re­lease in­ter­nally and with a grow­ing team of beta testers (want to join? Sign up at rePeb­ble.com/​ac­count). But these tests are not in­fal­li­ble and we will make mis­takes. We ap­pre­ci­ate your re­ports as they help us get more in­for­ma­tion to help us fix prob­lems!

Software Issues

We’re track­ing three big soft­ware is­sues with PebbleOS, and a mul­ti­tude of smaller prob­lems. While we are ac­tively work­ing on fix­ing these with a fu­ture soft­ware , we don’t have an ETA on when these will be fixed.

Step and sleep track­ing met­rics are not ac­cu­rate for some peo­ple

Accelerometer some­times stops work­ing

Touch screen some­times stops work­ing or reg­is­ters touches in wrong lo­ca­tion

It would be tough to list here the long-tail of soft­ware is­sues we’ve had re­ported. But please note that while we don’t re­ply to every­one, we do read every sin­gle re­port and look for pat­terns and clues that help us fix many is­sues with each soft­ware up­date (see the changelog for PebbleOS and Pebble mo­bile app).

Hardware Issues

You’ve all demon­strated in­cred­i­ble pa­tience wait­ing for your PT2 to ship. You’re ex­cited to try the first brand new Pebble in the last 10 years. That’s why we un­der­stand how painful and dif­fi­cult it could be if you un­box your brand new watch and dis­cover man­u­fac­tur­ing flaw, or use it for a few weeks and find the bat­tery is dy­ing too quickly or ac­ci­den­tally crack the glass. It sucks!

We feel your pain, even more than you can pos­si­bly imag­ine. That’s why every­one who has re­ported a hard­ware is­sue to our sup­port team has re­ceived a free re­place­ment (with free world­wide ship­ping) re­gard­less of whether their de­vice is un­der war­ranty or not.

To date, we’ve re­placed 330 PT2s (out of 17.82 mil­lion hours of us­age from 19,000+ watches in the field).

Mass pro­duc­ing a con­sumer elec­tronic prod­uct is labour in­ten­sive. Making stuff is still a very hu­man-cen­tric process. We make mis­takes. A worker may not as­sem­ble a part cor­rectly. A test may be ac­ci­den­tally skipped. The test re­sult could be read in­cor­rectly. Procedures can be put in place to min­i­mize mis­takes, but the cost will rise. As with all of hard­ware prod­uct de­vel­op­ment - it’s a trade­off 🤷.

The most fre­quent hard­ware is­sue we’re see­ing is very high power con­sump­tion (less than ~3 day bat­tery life). We’ve taken apart some units and found a va­ri­ety of is­sues. To com­bat this, we’ve im­ple­mented more strin­gent power con­sump­tion test­ing on the as­sem­bly line. If you en­counter this is­sue (regardless of your war­ranty el­i­gi­bil­ity), please send us a bug re­port in the Pebble app and we can help you out!

Next most fre­quent are prob­lems with the touch panel. At first, we thought this could be a hard­ware prob­lem and re­placed around 70 watches. After re­view­ing the units with our fac­tory, we now be­lieve this could be a soft­ware bug. We’re work­ing to fix these is­sues with a soft­ware up­date - if we can’t, we’ll re­place the af­fected watches (regardless of your war­ranty el­i­gi­bil­ity).

Next up is the front glass crack­ing. We’ve had 51 re­ports so far, and we’ve sent a free re­place­ment to each per­son af­fected. If your glass has cracked, send us a video (preferably, pic­ture is ok) in a bug re­port in the Pebble app. During the lead up to mass pro­duc­tion, we per­formed ex­ten­sive en­vi­ron­men­tal test­ing - in­clud­ing drop test­ing, tum­ble test­ing, but­ton press, strap stretch and bend, ther­mal cy­cling and many other tests. All test re­sults showed nor­mal dura­bil­ity com­pared to sim­i­lar smart­watches. But if your watch glass cracks, do you care what the fac­tory test re­sults were? Or that this has hap­pened to just 0.25% of all PT2s - or once every 30+ years of us­age? Of course not - your watch just broke. That’s why we will con­tinue re­plac­ing rea­son­able re­ports of glass crack­ing for free as long as we can. At some point, we will shift to of­fer­ing a re­place­ment at a highly dis­counted amount. We are also look­ing into sourc­ing ex­tra LCM mod­ules (the en­tire front as­sem­bly - glass, touch panel, dis­play, metal top cover and back­light) and mak­ing them avail­able for folks who choose to fix their watch them­selves.

The fi­nal big cat­e­gory of hard­ware is­sue are re­ports of but­ton prob­lems (32 so far). In some cases, a small in­te­rior clip is im­prop­erly as­sem­bled, caus­ing the but­ton to pop off. We’ve ad­dressed this is­sue with changes to the pro­duc­tion line process and hope that it be­comes much less fre­quent as watches as­sem­bled af­ter the change start mak­ing their way out into the world. If you en­counter this is­sue (regardless of your war­ranty el­i­gi­bil­ity), please send us a bug re­port in the Pebble app and we can help you out!

Then we’ve had a long tail of smaller is­sues that I’m mod­er­ately em­bar­rassed by, like a re­port of the watch miss­ing screws on the bot­tom, or the front falling off. I guess these things do hap­pen!

#Pebble Round 2 - Production Update and Timeline

My cur­rent favourite watch­face - Chronology II by Nicholas Jitkoff

I posted a mini-up­date on Pebble Round 2 in June - we weren’t able to start mass pro­duc­tion in May be­cause of a cos­metic prob­lem with the stain­less steel bot­tom case (an ex­tra in­den­ta­tion made by the CNC milling ma­chine). Since then the fac­tory has re­ceived a new ver­sion of the bot­tom case and things are look­ing much bet­ter! In par­al­lel, we’ve been run­ning ex­ten­sive en­vi­ron­men­tal test­ing (including drop test­ing).

At the be­gin­ning of July, we shipped out more Pebble Round 2 watches to lucky folks who signed up for the beta test. Thanks for your help find­ing and test­ing fixes for bugs in PebbleOS!

Our plan (as of to­day July 14 - sub­ject to change) is to start mass pro­duc­ing Round 2 watches dur­ing last week of July. We’ll start ramp­ing up pro­duc­tion slowly and care­fully. Roughly 14,000 peo­ple have pre-or­dered Round 2. It will take us about 2 months to build all pre-or­dered watches. We ex­pect to fin­ish ship­ping out all pre-or­dered Round 2 watches by the end of September.

If you pre­ordered Round 2 on rePeb­ble.com/​watch, we’ll send you an email roughly 2 weeks be­fore your watch is ready to ship ask­ing you to con­firm your ad­dress, add op­tional ac­ces­sories to your or­der and pay any ad­di­tional taxes due. If you haven’t al­ready se­lected your watch colour, please do so on or­ders.rePeb­ble.com.

Each Round 2 pre-or­der in­cludes a sil­i­cone watch strap and charger. We’ve also cre­ated beau­ti­ful cus­tom leather straps for PR2 ($20 – 30), in­clud­ing brown or black soft leather straps that feel very sim­i­lar to the straps we made for the orig­i­nal Pebble Time Round.

#Index 01 - Production Update and Shipping Timeline

Since our last up­date, we ex­panded our beta test and learned a lot from the hun­dreds of will­ing test sub­jects. Thank you for your ser­vice and bug re­ports!

Index 01 is now of­fi­cially in mass pro­duc­tion! We’ve as­sem­bled sev­eral thou­sand rings so far, and have grad­u­ally be­gun ship­ping them out. Schedule has slipped slightly from our last es­ti­mate (early August), we’re now aim­ing to ship out nearly all pre-or­ders by the end of August, ex­cept for a few un­lucky size/​color vari­ants that will ship in September.

#⚠️ Important Note For Index 01 Pre-orderers ⚠️

We’ve re­ceived re­ports from testers that Index 01 may feel every so slightly smaller than the ring siz­ers. Please take the time now to recheck your ring size with the ring sizer kit. If the ring sizer feels tight on your fin­ger, is hard to get on/​off, or if you can­not eas­ily clench your hand with the sizer on, please change your size to the next larger size. When in doubt, or­der a larger size. You can al­ways ad­just a larger Index 01 to feel smaller with a foam ad­he­sive or clip but you can’t make it larger!

If you pre­ordered Index 01 on rePeb­ble.com/​in­dex, we’ll send you an email roughly 2 weeks be­fore your ring is ready to ship ask­ing you to con­firm your ad­dress and pay any ad­di­tional taxes due. If you haven’t al­ready se­lected your Index 01 size and colour, please do so on or­ders.rePeb­ble.com.

Index 01 has changed my life. There’s no way I could go back to a world with­out ex­ter­nal mem­ory for my brain. And this is just the be­gin­ning, Index 01 soft­ware is im­prov­ing every sin­gle day. I ex­cited to hear what you think of it!

Competing speech streams are simultaneously represented in the human cortex during attention switching

journals.plos.org

Loading met­rics

Loading met­rics

Open Access

Peer-reviewed

Research Article

Emina Aličković,

Johannes Zaar,

Alejandro López Valdés  ,

Giovanni M. Di Liberto

Competing speech streams are si­mul­ta­ne­ously rep­re­sented in the hu­man cor­tex dur­ing at­ten­tion switch­ing

Sara Carta,

Emina Aličković,

Johannes Zaar,

Alejandro López Valdés,

Giovanni M. Di Liberto

x

Published: July 16, 2026

https://​doi.org/​10.1371/​jour­nal.pbio.3003876

Figures

Abstract

Successful speech com­mu­ni­ca­tion in multi-talker sce­nar­ios re­quires a skill­ful com­bi­na­tion of sus­tained at­ten­tion and rapid at­ten­tion switch­ing. While the neu­ro­phys­i­ol­ogy lit­er­a­ture of­fers de­tailed in­sights into the neural un­der­pin­nings of sus­tained at­ten­tion, there re­mains con­sid­er­able un­cer­tainty on how at­ten­tion switch­ing takes place. In this study, us­ing EEG record­ings from nor­mal-hear­ing adults in an im­mer­sive multi-talker en­vi­ron­ment, we mea­sured the neural en­cod­ing of two com­pet­ing speech streams amid back­ground bab­ble. Participants were cued to switch at­ten­tion be­tween streams every 15 – 30 s. Neural track­ing was as­sessed via Temporal Response Functions (TRF), con­firm­ing re­li­able de­cod­ing of at­ten­tional fo­cus. Our re­sults in­di­cate asym­met­ric dis­en­gage­ment and en­gage­ment processes dur­ing at­ten­tion switches, where the neural track­ing of the new tar­get stream emerges be­fore dis­en­gag­ing from the pre­vi­ous tar­get, re­veal­ing a tran­sient si­mul­ta­ne­ous en­cod­ing of two speech streams. That tran­si­tion was closely mir­rored by a re­duc­tion in EEG al­pha power, in­form­ing on the cog­ni­tive ef­fort dur­ing dif­fer­ent phases of the at­ten­tion switch. We then iso­lated cor­ti­cal ac­tiv­ity re­flect­ing lex­i­cal pre­dic­tion mech­a­nisms to de­ter­mine how lex­i­cal con­text is up­dated af­ter an at­ten­tion switch, com­par­ing four con­text-ac­cu­mu­la­tion strate­gies that were con­structed us­ing Large Language Models. Our find­ings elu­ci­date both the tem­po­ral and con­tex­tual mech­a­nisms un­der­ly­ing au­di­tory at­ten­tion shifts, point­ing to the pos­si­bil­ity that lis­ten­ers carry out a re­set in lex­i­cal con­text af­ter switch­ing at­ten­tion. By fo­cus­ing on dy­namic at­ten­tional re­al­lo­ca­tion, this study of­fers in­sights into the brain’s ca­pac­ity for flex­i­ble speech pro­cess­ing in com­plex lis­ten­ing en­vi­ron­ments.

Citation: Carta S, Aličković E, Zaar J, López Valdés A, Di Liberto GM (2026) Competing speech streams are si­mul­ta­ne­ously rep­re­sented in the hu­man cor­tex dur­ing at­ten­tion switch­ing. PLoS Biol 24(7): e3003876.

https://​doi.org/​10.1371/​jour­nal.pbio.3003876

Academic Editor: Manuel S. Malmierca, Universidad de Salamanca, SPAIN

Received: July 3, 2025; Accepted: June 12, 2026; Published: July 16, 2026

Copyright: © 2026 Carta et al. This is an open ac­cess ar­ti­cle dis­trib­uted un­der the terms of the Creative Commons Attribution License, which per­mits un­re­stricted use, dis­tri­b­u­tion, and re­pro­duc­tion in any medium, pro­vided the orig­i­nal au­thor and source are cred­ited.

Data Availability: All data sup­port­ing the find­ings re­ported in this man­u­script are freely ac­ces­si­ble with­out re­stric­tion. The EEG pre-processed dataset, the re­sult­ing analy­sis files, and the analy­sis code are pub­licly avail­able on the open repos­i­tory Zenodo (https://​zen­odo.org/​records/​20569817). The EEG record­ings are pro­vided fol­low­ing the Continuous-event Neural Data (CND) for­mat stan­dard. The as­so­ci­ated speech stim­uli can also be found in the same repos­i­tory, within the STIMULI folder.

Funding: S.C., A.L.V., and G.D.L. were sup­ported by the William Demant Fonden (https://​www.williamde­mant­fonden.dk/), un­der grants 21 – 0628 and 22 – 0552, and by Taighde Éireann — Research Ireland (https://​www.re­searchire­land.ie/) un­der grant No. 18/CRT/6223. G.D.L. ad­di­tion­ally con­ducted this re­search with the fi­nan­cial sup­port of Research Ireland at ADAPT, the Research Ireland Centre for AI-Driven Digital Content Technology (https://​www.adapt­cen­tre.ie/) at Trinity College Dublin [grant 13/RC/2106_P2]. The fun­ders had no role in study de­sign, data col­lec­tion and analy­sis, de­ci­sion to pub­lish, or prepa­ra­tion of the man­u­script.

Competing in­ter­ests: The au­thors have de­clared that no com­pet­ing in­ter­ests ex­ist.

Abbreviations: EEG, elec­troen­cephalog­ra­phy; EOG, elec­tro-ocu­log­ra­phy; EMG, elec­tro-myo­g­ra­phy; ERSP, event-re­lated spec­tral per­tur­ba­tion; iEEG, in­tra-cra­nial elec­troen­cephalog­ra­phy; FDR, false dis­cov­ery rate; fMRI, func­tional mag­netic res­o­nance imag­ing; ICA, Independent Component Analysis; IQR, in­terquar­tile range; LLM, large lan­guage model; MEG, mag­ne­toen­cephalog­ra­phy; PSD, power spec­tral den­sity; RMS, root-mean-squared; SE, stan­dard er­ror; SEM, stan­dard er­ror of the mean; SNR, sig­nal-to-noise ra­tio; SPL, sound pres­sure level; TRF, Temporal Response Functions

Introduction

To un­der­stand speech in multi-talker en­vi­ron­ments, lis­ten­ers sin­gle out the tar­get speaker from com­pet­ing sound streams [1 – 3]. The neu­ro­phys­i­ol­ogy of this se­lec­tive at­ten­tion process has been widely stud­ied with sim­u­lated cock­tail-party sce­nar­ios [4,5], shed­ding light on how our brains seg­re­gate a tar­get stream from com­pet­ing speech streams, and en­abling the trans­for­ma­tion of the tar­get speech into lin­guis­tic mean­ing. While the ex­tent to which masker speech streams are processed re­mains highly de­bated [6 – 8], there is no doubt that there are con­sid­er­able dif­fer­ences be­tween the pro­cess­ing of tar­get and masker speech, which have been mea­sured with var­i­ous tech­nolo­gies, such as non-in­va­sive elec­troen­cephalog­ra­phy (EEG) [1,9], in­tra-cra­nial elec­troen­cephalog­ra­phy (iEEG) [10], mag­ne­toen­cephalog­ra­phy (MEG) [3,11] and func­tional mag­netic res­o­nance imag­ing (fMRI) [12,13]. That work could pin­point pre­cise loci in the au­di­tory cor­ti­cal ar­eas where that seg­re­ga­tion emerges [14] as well as mea­sur­ing the sub­stan­tial (but not to­tal) sup­pres­sion of lin­guis­tic pro­cess­ing for the masker speech [1,15 – 17]. However, neu­ro­phys­i­ol­ogy lit­er­a­ture in this field has al­most en­tirely fo­cused on sus­tained at­ten­tion tasks [2,10], leav­ing con­sid­er­able un­cer­tainty on the neural un­der­pin­nings of at­ten­tion switch­ing.

Dynamic switch­ing par­a­digms have been widely used in the do­main of cog­ni­tive con­trol stud­ies to probe for cog­ni­tive flex­i­bil­ity and cog­ni­tive sta­bil­ity [18]. In those ex­per­i­ments, par­tic­i­pants are of­ten re­quired to flex­i­bly adapt their be­hav­ioral re­sponse de­pend­ing on new in­struc­tions, ini­ti­at­ing a task-switch [19 – 21]. For ex­am­ple, given a sin­gle digit, they are re­quired to clas­sify it ei­ther based on par­ity, i.e., whether it is even or odd, or based on rel­a­tive mag­ni­tude, i.e., whether the digit is greater than or less than 5 [22]. In these par­a­digms, the switch-cost is the in­crease in re­ac­tion time or er­ror rate when switch­ing from one task to the other. Similar be­hav­ioral par­a­digms have also in­volved sim­ple speech stim­uli in multi-talker set­tings [23 – 25]. However, the main in­ter­est of those tightly con­trolled ex­per­i­ments was to model the process of tar­get speech se­lec­tion as one par­tic­u­lar in­stance of a task-switch­ing prob­lem, i.e., tar­get stream se­lec­tion could ei­ther de­pend on spa­tial lo­ca­tion or voice iden­tity [23], rather than fo­cus­ing on the dy­namic as­pect of at­ten­tion re-al­lo­ca­tion per se in nat­u­ral­is­tic multi-talker sce­nar­ios. As such, very lit­tle is known on how a flex­i­ble re­ori­ent­ing of at­ten­tion might im­pact speech pro­cess­ing of con­tin­u­ous com­pet­ing streams.

In re­cent speech neu­ro­phys­i­ol­ogy re­search, ex­per­i­men­tal par­a­digms have started to in­clude switches of at­ten­tion as a tool to­wards tai­lored EEG/MEG method­olog­i­cal ad­vances in the do­main of at­ten­tion de­cod­ing [26,27], or to in­ves­ti­gate how sus­tained speech at­ten­tion un­folds for mov­ing au­di­tory ob­jects [28]. However, to the best of our knowl­edge, only one pre­vi­ous study has specif­i­cally fo­cused on the neu­ro­phys­i­ol­ogy of at­ten­tion switch­ing in multi-talker sce­nar­ios, re­lat­ing the neural en­cod­ing of speech dur­ing at­ten­tional re-ori­ent­ing with EEG al­pha ac­tiv­ity and pupil di­la­tion dy­nam­ics [29]. Those find­ings proved that the neu­ro­phys­i­ol­ogy of at­ten­tion switch­ing can be stud­ied non-in­va­sively. Building on that work, our study sheds light on the ex­act neural dy­nam­ics sup­port­ing the steer­ing of at­ten­tion be­tween two com­pet­ing speech streams, dis­en­gag­ing from the pre­vi­ous tar­get stream while en­gag­ing to the new one.

In this study, we mea­sure the neural en­cod­ing of speech us­ing a range of en­cod­ing win­dow lengths, as lis­ten­ers steer their at­ten­tion from one speaker to an­other. We test whether en­gage­ment with a new speech stream be­gins be­fore dis­en­gage­ment from the pre­vi­ous tar­get is com­plete, re­sult­ing in a brief pe­riod of si­mul­ta­ne­ous track­ing of both streams. Such an asym­me­try in the dis­en­gage­ment-en­gage­ment processes, even if tran­sient, could sup­port the abil­ity to ex­plore al­ter­na­tive au­di­tory streams while main­tain­ing at­ten­tion to a given stream [30].

The neural en­cod­ing of speech was mea­sured from nor­mal-hear­ing adult par­tic­i­pants us­ing EEG dur­ing an im­mer­sive multi-talker lis­ten­ing task. Participants were ex­posed to two com­pet­ing speech streams from TED talks, pre­sented via two front-fac­ing loud­speak­ers, while back­ground noise from a 16-talker speech bab­ble played from rear loud­speak­ers (Fig 1A). An on-screen ar­row cued par­tic­i­pants to at­tend to one of the two speech streams and to shift their at­ten­tion rapidly when­ever the ar­row changed di­rec­tion, ap­prox­i­mately every 10 – 30 s (Fig 1B). Neural track­ing of tar­get and masker speech was quan­ti­fied us­ing the Temporal Response Function (TRF), de­scrib­ing the lin­ear re­la­tion­ship be­tween each speech stream and the neural re­sponses. As an ini­tial val­i­da­tion, we con­firmed that the at­tended stream could be re­li­ably de­coded from the EEG, con­sis­tent with the ex­ten­sive lit­er­a­ture on sus­tained at­ten­tion [9,10,31]. This con­firms that the EEG re­sponses in this ex­per­i­ment re­flects dif­fer­en­tial en­cod­ing of tar­get ver­sus masker speech (Fig 1C).

Fig 1. Experiment overview and val­i­da­tion.

(A) Participants were pre­sented with speech from two loud­speak­ers placed in front of them with 60° of sep­a­ra­tion (30° left and 30° right), and with con­cur­rent 16-talker back­ground noise (B1–B4). In each trial, the screen pre­sented an ar­row point­ing to the tar­get speech stream. Participants were in­structed to switch at­ten­tion as soon as the vi­sual cue changes di­rec­tion. (B) Schematic di­a­gram of one ex­per­i­men­tal trial. The black area rep­re­sents blocks of at­ten­tion ei­ther to the left (L) or right (R) front streams. The red ar­rows in­di­cate the in­stants where the at­ten­tion cue switches side (six times per trial). Note that block du­ra­tion was ran­dom­ized and al­ways be­tween 15 and 30 s, with tri­als last­ing 3 min. (C) EEG data val­i­da­tion was car­ried out by run­ning an at­ten­tion de­cod­ing analy­sis. Progressively longer de­cod­ing win­dows were con­sid­ered (larger win­dows use more data, typ­i­cally lead­ing to more ac­cu­rate de­cod­ing scores). Binary clas­si­fi­ca­tion scores are re­ported ar­bi­trat­ing be­tween the tar­get and masker streams. The dashed line in­di­cates the 95th per­centile of a ran­dom dis­tri­b­u­tion cal­cu­lated by ran­dom­iz­ing the clas­si­fi­ca­tion la­bels. Statistically sig­nif­i­cant at­ten­tion de­cod­ing clas­si­fi­ca­tion scores were mea­sured for all the de­cod­ing win­dows con­sid­ered, with nu­mer­i­cal re­sults com­pa­ra­ble with pre­vi­ous stud­ies on se­lec­tive at­ten­tion [31,34,35]. Data sup­port­ing this fig­ure is avail­able at: https://​zen­odo.org/​records/​20569817.

https://​doi.org/​10.1371/​jour­nal.pbio.3003876.g001

We next ad­dressed two fun­da­men­tal ques­tions about the neural mech­a­nisms un­der­ly­ing at­ten­tion switch­ing in nat­u­ral­is­tic lis­ten­ing. First, we asked whether the processes of en­gag­ing with a new speech stream and dis­en­gag­ing from a pre­vi­ous one un­fold sym­met­ri­cally (Figs 2 and 3). To test this, we fit en­cod­ing TRF mod­els to EEG data, mea­sur­ing the neural track­ing of the two com­pet­ing speech streams over time. This al­lowed us to char­ac­ter­ize the av­er­age en­cod­ing dy­nam­ics sur­round­ing at­ten­tion switches, com­par­ing dis­en­gage­ment and en­gage­ment processes. The sec­ond ob­jec­tive was to un­der­stand how our brains up­date and use lex­i­cal con­text when switch­ing at­ten­tion (Fig 4). Building on pre­vi­ous work show­ing that speech com­pre­hen­sion is sup­ported by con­tex­tual pre­dic­tions [32,33], we for­mu­lated four com­pet­ing hy­pothe­ses re­flect­ing dif­fer­ent as­sump­tions about how lin­guis­tic con­text is pre­served, re­set, or se­lec­tively up­dated across an at­ten­tion switch. Using a state-of-the-art large lan­guage model (LLM), we de­rived quan­ti­ta­tive pre­dic­tions for each hy­poth­e­sis, re­sult­ing in four re­gres­sors for lex­i­cal sur­prisal and en­tropy, sep­a­rately, dif­fer­ing in their sen­si­tiv­ity to prior con­text and to the oc­cur­rence of the switch. Encoding TRF mod­els were then fit for each hy­poth­e­sis, al­low­ing us to com­pare al­ter­na­tive con­text-ac­cu­mu­la­tion strate­gies and iden­tify the model most con­sis­tent with the ob­served neural re­sponses. This study pro­vides sub­stan­tial new in­sights into the tem­po­ral un­fold­ing and con­tex­tual mech­a­nisms guid­ing at­ten­tion switch­ing, en­com­pass­ing both low and high lev­els of speech ab­strac­tion.

Fig 2. The at­ten­tion-switch­ing cue prompts a ro­bust dis­en­gage­ment from Speaker 1 and en­gage­ment to Speaker 2, and it is fol­lowed by a sig­nif­i­cant de­crease in the EEG al­pha ERSP.

Disengagement has longer tem­po­ral dy­nam­ics com­pared to en­gage­ment. (A) Left: Speech track­ing en­cod­ing for an at­ten­tion switch from Speaker 1 and 2. The tra­jec­tory in the panel rep­re­sents our null hy­poth­e­sis, where the dis­en­gage­ment and en­gage­ment processes progress in a sym­met­ric man­ner af­ter the switch-cue (vertical gray line). Right: Results for the neural track­ing of Speaker 1 and Speaker 2 across the switch­ing cue. EEG pre­dic­tion cor­re­la­tions (average across all chan­nels) ob­tained from a 4-s slid­ing-win­dow TRF model in­clud­ing Envelope (Env), Word Onset (WO) and Word Surprisal (WS) fea­tures. Coloured hor­i­zon­tal bars at the bot­tom of the plot in­di­cate the at­ten­tion in­struc­tion around the at­ten­tion switch­ing cue. The turquoise dot in­di­cates the en­cod­ing switch of EEG pre­dic­tion cor­re­la­tions based on Spk1- and Spk2- speech fea­tures. The piece­wise lin­ear model fit for dis­en­gage­ment and en­gage­ment is over­layed on the EEG pre­dic­tion cor­re­la­tion val­ues. Please note that the bro­ken-line-fit in this plot was per­formed on the grand-av­er­age cor­ti­cal track­ing curves here for il­lus­tra­tive pur­poses. Please find the es­ti­mates at the sin­gle-par­tic­i­pant level in Panel C. Hexagram shapes in­di­cate the start of the dis­en­gage­ment (blue) and en­gage­ment (yellow) processes, while di­a­monds rep­re­sent the end of the tran­si­tions. (B) Left: Diagram of ex­pected re­sults for al­pha-band ERSP (event-related spec­tral per­tur­ba­tion) across the switch­ing cue. Right: ERSP of the al­pha band (8 – 12 Hz) around the switch­ing cue (average of all chan­nels), com­puted with a 4-s slid­ing win­dow, as above. Scalp topogra­phies at se­lected time points re­veal a pat­tern of pos­te­rior neg­a­tiv­ity, which drops sig­nif­i­cantly fol­low­ing the in­struc­tion to switch (thick black lines in­di­cate a sta­tis­ti­cally sig­nif­i­cant change com­pared to pre-switch base­line). The red dot rep­re­sents the av­er­age of ERSP min­ima across par­tic­i­pants. The shaded area rep­re­sents the stan­dard er­ror of the mean (SEM) across par­tic­i­pants. (C) Left: Comparison of en­cod­ing switch of EEG pre­dic­tion cor­re­la­tions (turquoise bar) and al­pha ERSP min­i­mum (red bar) for a 4-s slid­ing win­dow. The al­pha ERSP reaches its min­i­mum sig­nif­i­cantly af­ter the Spk1-Spk2 en­cod­ing switch point. Right: Comparison of tem­po­ral dy­nam­ics for start and end points of dis­en­gage­ment and en­gage­ment processes, with start/​end tran­si­tion points es­ti­mated at the sin­gle-par­tic­i­pant level. Stars in­di­cate sig­nif­i­cant sta­tis­ti­cal ef­fects (paired sam­ple t-tests; *p ≤ 0.05; **p ≤ 0.01; **p ≤ 0.001). Data sup­port­ing this fig­ure is avail­able at: https://​zen­odo.org/​records/​20569817.

https://​doi.org/​10.1371/​jour­nal.pbio.3003876.g002

Fig 3. Comparing the start and end tran­si­tion points for the dis­en­gage­ment and en­gage­ment processes af­ter the at­ten­tions switch­ing cue.

The process of en­gag­ing to a new speaker be­gins and ends sig­nif­i­cantly ear­lier than dis­en­gag­ing from the pre­vi­ously at­tended speaker. (A, B) Start and end points of the tran­si­tion for the dis­en­gage­ment (blue) and en­gage­ment (yellow) processes over five TRF slid­ing win­dow lengths. Error bars rep­re­sent SEM across par­tic­i­pants. Stars in­di­cate sig­nif­i­cant ef­fects of process type (two-way re­peated mea­sures ANOVA; *p ≤ 0.05; **p ≤ 0.01; ***p ≤ 0.001). Data sup­port­ing this fig­ure is avail­able at: https://​zen­odo.org/​records/​20569817.

https://​doi.org/​10.1371/​jour­nal.pbio.3003876.g003

Fig 4. Investigating lex­i­cal pre­dic­tion mech­a­nisms dur­ing at­ten­tion switch­ing.

(A) Layout of the four con­text mod­els. Blocks coloured in black il­lus­trate sus­tained at­ten­tion ei­ther to the Left or Right stream, while or­ange ar­rows in­di­cate at­ten­tion switch­ing cues. The thick red ar­row in­di­cates the con­text used to guide word pre­dic­tions for the cur­rent block (B7, high­lighted in or­ange). (B) Average lex­i­cal en­tropy at words pre­ced­ing and fol­low­ing the at­ten­tion switch cue. Note that no value for en­tropy is dis­played in the Reset model for the first word af­ter the switch, due to the con­text be­ing fully re­in­stated. (C) EEG pre­dic­tion cor­re­la­tions for the four mul­ti­vari­ate TRF mod­els, only dif­fer­ing in their en­tropy fea­ture. Coloured dots in­di­cate the av­er­age across all elec­trodes and par­tic­i­pants. The gray area at the bot­tom rep­re­sents the av­er­age en­cod­ing ac­cu­racy of a mul­ti­vari­ate TRF with­out any se­man­tic in­for­ma­tion (Envelope + Word Onset). Stars rep­re­sent sta­tis­ti­cally sig­nif­i­cantly greater EEG pre­dic­tion cor­re­la­tions for the Reset model com­pared to the other mod­els (Significance lev­els: *p < 0.05, **p < 0.01, ***p < 0.001). Topographical pat­terns il­lus­trate the gain due to se­man­tic in­for­ma­tion (compared to the Envelope + Word Onset TRF) for the four mod­els. (D) (Left) TRF weights for the en­tropy fea­ture at time-lags be­tween −100 and 600 ms rel­a­tive to stim­u­lus on­set. Transparent shaded ar­eas rep­re­sent the stan­dard er­ror of the mean (SEM) across par­tic­i­pants. The hor­i­zon­tal black line in­di­cates the time win­dow em­ployed to com­pute the av­er­age TRF-N400 am­pli­tude. (Right) Boxplots rep­re­sent­ing the dis­tri­b­u­tion of the TRF-N400 am­pli­tude across par­tic­i­pants for the four con­text mod­els. The cen­tral line within each box rep­re­sents the me­dian, while the edges of the box in­di­cate the in­terquar­tile range (IQR). Whiskers ex­tend to the most ex­treme data points within 1.5 times the IQR from the quar­tiles. Outliers are plot­ted as in­di­vid­ual points be­yond the whiskers. Stars in­di­cate sta­tis­ti­cally sig­nif­i­cant dif­fer­ences (Significance lev­els: *p < 0.05, **p < 0.01, ***p < 0.001). Data sup­port­ing this fig­ure is avail­able at: https://​zen­odo.org/​records/​20569817.

https://​doi.org/​10.1371/​jour­nal.pbio.3003876.g004

Results

Behavioral per­for­mance

Following each trial, par­tic­i­pants were first pre­sented with a four-al­ter­na­tive forced-choice ques­tion about the con­tent of the at­tended speech stream to con­firm task en­gage­ment. Behavioral per­for­mance re­vealed that they were able to suc­cess­fully re­ply to con­tent-re­lated ques­tions, with an av­er­age ac­cu­racy of 86.3% (SEM 2.6%). Participants were also re­quired to in­di­cate their pref­er­ence be­tween left and right streams, which was found to be over­all bal­anced, with the left stream se­lected in 49.79% of the tri­als, on av­er­age (SEM 1.7%). Finally, per­ceived dif­fi­culty of the at­ten­tion switch for every trial was mea­sured by ask­ing par­tic­i­pants to rate it on a scale from 1 (very easy) to 5 (very hard). The av­er­age dif­fi­culty of the switch was judged to be 3.1 out of 5, with a SEM across par­tic­i­pants of 0.11 points. Due to tech­ni­cal is­sues, be­hav­ioral data for one of the 24 par­tic­i­pants was not avail­able, there­fore be­hav­ioral per­for­mance was com­puted based on the data from the re­main­ing 23 par­tic­i­pants.

Decoding of se­lec­tive au­di­tory at­ten­tion in a dy­namic switch­ing sce­nario

Participants’ at­ten­tion was de­coded with a back­ward TRF analy­sis, de­scrib­ing the re­la­tion­ship be­tween the EEG sig­nals and the en­ve­lope of the tar­get speech. For each left-out trial, the speech en­ve­lope re­con­structed from the tar­get de­cod­ing model was cor­re­lated with the en­velopes of both the left and right speech streams. Attention was clas­si­fied by de­ter­min­ing which speech stream’s en­ve­lope showed a higher cor­re­la­tion with the re­con­structed en­ve­lope. Since this was a dy­namic at­ten­tion-switch­ing sce­nario, the at­tended speech could al­ter­na­tively cor­re­spond to the left or the right stream. Classification was con­sid­ered cor­rect when the re­con­structed en­ve­lope cor­re­lated more strongly with the tar­get speech en­ve­lope than with the masker en­ve­lope. Classification ac­cu­racy was then com­puted as the pro­por­tion of in­stances where this cri­te­rion was met. To es­tab­lish chance per­for­mance, left and right la­bels were ran­domly shuf­fled 100 times for each de­cod­ing win­dow. As shown in Fig 1C, the longer de­cod­ing win­dows led to higher clas­si­fi­ca­tion per­for­mances. However, even with a 1-second win­dow, clas­si­fi­ca­tion ac­cu­racy was sig­nif­i­cantly above chance level, and all de­cod­ing win­dows yielded clas­si­fi­ca­tion rates sig­nif­i­cantly above the 95th per­centile of its chance dis­tri­b­u­tion (paired two-tailed t test, FDR-corrected for mul­ti­ple com­par­isons for win­dows of 1 s, 2 s, 4 s, 8 s, 16 s, 32 s, re­spec­tively: p = 0.47e−9; 0.53e−9; 0.27e−9; 0.24e−9; 0.24e−9; 0.24e−9). These find­ings align with pre­vi­ous work de­cod­ing sus­tained at­ten­tion or em­ploy­ing match-vs-mis­match clas­si­fi­ca­tion met­rics [9,31,36], and con­firm that a clas­si­fi­ca­tion based on the en­ve­lope re­con­struc­tion can re­li­ably track se­lec­tive at­ten­tion even dur­ing at­ten­tion switches.

Neural track­ing of com­pet­ing speech streams in a dy­namic switch­ing sce­nario re­flects the lis­ten­er’s fo­cus of at­ten­tion and is re­lated to changes in al­pha ERSP

A mul­ti­vari­ate TRF analy­sis was car­ried out to char­ac­ter­ize the neural track­ing of two com­pet­ing speech streams in a set­ting where par­tic­i­pants were in­structed to dy­nam­i­cally switch their at­ten­tion be­tween the two streams. Single-subject TRFs were trained on the tar­get stream and tested on both speak­ers (i.e., Spk1 and Spk2) us­ing a mul­ti­vari­ate speech rep­re­sen­ta­tion that in­cluded Envelope, Word Onset and Word Surprisal fea­tures (for more de­tails see Methods). EEG pre­dic­tion cor­re­la­tions were com­puted us­ing a slid­ing win­dow to cor­re­late true and pre­dicted EEG sig­nals over time, with a leave-one-out cross-val­i­da­tion pro­ce­dure and were av­er­aged across all EEG chan­nels. Importantly, be­cause these cor­re­la­tions are com­puted us­ing slid­ing win­dows, the re­sult­ing switch tim­ing de­pends on the slid­ing win­dow length. As such, the tem­po­ral dy­nam­ics de­riv­ing from our analy­ses do not re­flect the ex­act tim­ing of the un­der­ly­ing neural processes, and they should al­ways be in­ter­preted with the caveat of the slid­ing win­dow length.

In or­der to an­a­lyze ro­bust switch­ing dy­nam­ics, we se­lected 21 par­tic­i­pants dis­play­ing a re­li­able at­ten­tional bias over the course of the switch, based on an above-chance clas­si­fi­ca­tion ac­cu­racy cri­te­rion (>50%) over the course of the switch. In do­ing so, we re­moved par­tic­i­pants for whom the start and end points of the (dis)engagement could not be es­ti­mated (note that this ex­clu­sion is de­ter­mined be­fore iden­ti­fy­ing the start/​end es­ti­mates; in that sense, this is dif­fer­ent from an out­lier re­moval, which would ex­clude ex­treme start/​end val­ues in­stead).

Aligning with our ex­pec­ta­tion (Fig 2A), EEG pre­dic­tion cor­re­la­tions around the switch­ing cue re­flected track­ing of Spk1 and Spk2 streams con­sis­tent with the at­ten­tion in­struc­tions, such that Spk1 was sig­nif­i­cantly more tracked than Spk2 be­fore the switch, while the re­verse pat­tern was ob­served af­ter the switch (paired two-tailed t test of Spk1-Spk2 dif­fer­ence against zero, FDR-corrected for mul­ti­ple com­par­isons, p < 0.005).

As the at­ten­tion switch un­folds, also the grand-mean ERSP in the al­pha fre­quency band dis­played a sta­tis­ti­cally sig­nif­i­cant change com­pared to base­line (one-sample t test against zero, FDR-corrected for mul­ti­ple com­par­isons), re­veal­ing a pat­tern of oc­cip­ito-pari­etal neg­a­tiv­ity in the scalp topogra­phies (Fig 2B). This is con­sis­tent with our ex­pec­ta­tion of an im­pact of at­ten­tional re­ori­en­ta­tion on the EEG al­pha band, which has al­ready been shown to re­flect at­ten­tion switch­ing be­hav­ior in com­pet­ing speech lis­ten­ing sce­nar­ios [29].

EEG pre­dic­tion cor­re­la­tions for Spk1 and Spk2 con­verged, be­fore sig­nif­i­cantly sep­a­rat­ing again once the switch­ing process was con­cluded and, pre­sum­ably, the at­ten­tion was fully re­al­lo­cated. Here, we re­fer to the time point when EEG pre­dic­tion over­laps be­tween Spk1 and Spk2 as the en­cod­ing switch point. Given the ob­served sta­tis­ti­cally sig­nif­i­cant drop in al­pha ERSP, we asked how the tem­po­ral dy­nam­ics of this drop com­pared to those of the EEG pre­dic­tion cor­re­la­tions. To ad­dress this, for each par­tic­i­pant, we iden­ti­fied the time of the al­pha ERSP min­i­mum, and the en­cod­ing switch point, based on an en­cod­ing win­dow of 4s (Fig 2C). The choice of this par­tic­u­lar en­cod­ing win­dow for our main analy­sis is jus­ti­fied based on the clas­si­fi­ca­tion ac­cu­racy re­sults (Fig 1C), since it is a good com­pro­mise be­tween tem­po­ral res­o­lu­tion and clas­si­fi­ca­tion per­for­mance. However, the same pat­tern of re­sults holds when con­sid­er­ing mul­ti­ple en­cod­ing win­dows si­mul­ta­ne­ously (S1 Fig). A paired t test com­par­ing the tem­po­ral dy­nam­ics of the al­pha ERSP and the EEG pre­dic­tion cor­re­la­tions showed that the min­i­mum of the al­pha ERSP drop sig­nif­i­cantly fol­lows the en­cod­ing switch point (t(20) = 4.29, p = 3.59e-4, Cohen’s d = 0.94).

We then eval­u­ated mul­ti­ple en­cod­ing win­dow lengths, as­sess­ing the ef­fect of Metric (encoding switch ver­sus ERSP min­i­mum) and Window (1, 2, 4, 8 s) on the tim­ing of the en­cod­ing switch and the min­i­mum of the al­pha ERSP with a 2-way re­peated mea­sures ANOVA. The analy­sis re­vealed that the tem­po­ral dy­nam­ics of both en­cod­ing switch and al­pha ERSP min­i­mum be­came longer as the en­cod­ing win­dow length in­creased (F(1.68, 33.55) = 52.77, p = 2.3e−10, ηp2 = 0.72; a Greenhouse-Geisser’s cor­rec­tion ap­plied due to spheric­ity vi­o­la­tion), which is un­sur­pris­ing given the method­olog­i­cal con­straints we dis­cussed (see Methods). More in­ter­est­ingly for our ques­tion, a sta­tis­ti­cally sig­nif­i­cant ef­fect of Metric emerged (F(1,20) = 20.26, p = 2.18e−4, ηp2 = 0.5), with the al­pha ERSP min­i­mum oc­cur­ring sig­nif­i­cantly later than the en­cod­ing switch across a range of en­cod­ing win­dows (Holm-corrected post-hoc t test: t(20) = 4.5, p = 2.18e−4, Cohen’s d = 0.97).

Dissecting the tem­po­ral dy­nam­ics of at­ten­tional dis­en­gage­ment and en­gage­ment dur­ing at­ten­tion switch­ing

The at­ten­tion switch­ing cue prompts the lis­tener to re­al­lo­cate their at­ten­tion from the pre­vi­ously at­tended speaker, Spk1, to the newly at­tended speaker, Spk2. While this re-rout­ing of at­ten­tion ap­pears to be a sin­gle, uni­fied process, it is pos­si­ble to dis­tin­guish two sep­a­rate op­er­a­tions that are nec­es­sary for it to hap­pen: dis­en­gage­ment, which we de­fine as the de­crease in neural track­ing for the pre­vi­ously at­tended speech stream, and en­gage­ment, which we de­fine as the in­crease in neural track­ing for the pre­vi­ously un­at­tended speech stream. Our goal was to clar­ify the tem­po­ral dy­nam­ics of these two op­er­a­tions to un­der­stand whether they oc­cur fully in par­al­lel, se­ri­ally, or with a cer­tain de­gree of over­lap. It is worth not­ing that, due to the use of slid­ing en­cod­ing win­dows, the es­ti­mated tem­po­ral dy­nam­ics of en­gage­ment and dis­en­gage­ment do not re­flect the ex­act time course of the un­der­ly­ing neural processes and should be in­ter­preted as rel­a­tive, rather than ab­solute, tem­po­ral met­rics. As in the pre­vi­ous analy­sis, we first se­lected par­tic­i­pants dis­play­ing a re­li­able at­ten­tional bias over the course of the switch (see Methods). For this se­lec­tion of 21 par­tic­i­pants, we fit­ted a piece­wise lin­ear re­gres­sion on sin­gle-sub­ject EEG pre­dic­tion cor­re­la­tions, and found the op­ti­mal break­points, cor­re­spond­ing to the start and end time points of dis­en­gage­ment and en­gage­ment (Fig 2C). As above, we chose to fo­cus on an ex­am­ple win­dow of 4 s and later repli­cated our re­sults on a range of en­cod­ing win­dow lengths. To fur­ther char­ac­ter­ize the spa­tial pat­terns of en­gage­ment and dis­en­gage­ment processes, scalp topogra­phies of the EEG pre­dic­tion cor­re­la­tions at se­lected time points are shown in S2 Fig, in­di­cat­ing that the most pre­dic­tive chan­nels were pre­dom­i­nantly lo­cated over cen­tral-pari­etal re­gions. Disengagement and en­gage­ment processes were com­pared sep­a­rately based on their start times and end times, re­veal­ing con­sis­tently ear­lier tem­po­ral dy­nam­ics for the en­gage­ment com­pared to the dis­en­gage­ment. Engagement to the newly at­tended speaker started sig­nif­i­cantly ear­lier than the dis­en­gage­ment from the pre­vi­ously at­tended speaker (paired-sample t test: t(20) = 2.37, p = 0.03, Cohen’s d = 0.52), and fin­ished sig­nif­i­cantly ear­lier (paired-sample t test: t(20) = 2.35, p = 0.03, Cohen’s d = 0.39).

We then ex­tended our analy­sis to a range of slid­ing win­dow lengths and com­pared start times and end times for dis­en­gage­ment and en­gage­ment processes, in­clud­ing Window (1, 2, 4, 8, 16 s) and Process (disengagement ver­sus en­gage­ment) as main fac­tors in a re­peated mea­sures ANOVA. Regarding the start points (Fig 3A), our analy­ses re­vealed an ex­pected sta­tis­ti­cally sig­nif­i­cant ef­fect of Window (F(1.51,30.14) = 9.7, p = 0.001, ηp2 = 0.33; the as­sump­tion of spheric­ity was not met; hence, a Greenhouse–Geisser’s cor­rec­tion was ap­plied), with longer tem­po­ral dy­nam­ics cor­re­spond­ing to longer en­cod­ing win­dow lengths. More im­por­tantly, we also ob­served a sig­nif­i­cant main ef­fect of Process (F(1,20) = 5.48, p = 0.03, ηp2 = 0.21), with en­gage­ment to the newly at­tended stream start­ing sig­nif­i­cantly ear­lier than the dis­en­gage­ment to the pre­vi­ously at­tended stream (Holm-corrected post-hoc t test: t(20) = 2.34, p = 0.03, Cohen’s d = 0.54). The same sta­tis­ti­cal analy­sis was re­peated sep­a­rately on the end time points of dis­en­gage­ment and en­gage­ment processes (Fig 3B), re­veal­ing once again a main ef­fect of Window, whereby longer en­cod­ing win­dows yield longer tem­po­ral tran­si­tions (F(1.97,39.32) = 31.76, p = 7.2e−9, ηp2 = 0.61; the as­sump­tion of spheric­ity was not met; hence, a Greenhouse–Geisser’s cor­rec­tion was ap­plied). A sig­nif­i­cant main ef­fect of Process also emerged (F(1,20) = 4.46, p = 0.047, ηp2 = 0.18), re­veal­ing that the process of en­gage­ment to the newly at­tended speaker, not only starts, but also ends sig­nif­i­cantly ear­lier than the dis­en­gage­ment (Holm-corrected post-hoc t test: t(20) = 2.11, p = 0.047, Cohen’s d = 0.58).

A fol­low-up analy­sis in­clud­ing the three par­tic­i­pants with lower-than-chance clas­si­fi­ca­tion ac­cu­racy around the switch­ing cue con­firmed that these data points in­tro­duced noise to the es­ti­ma­tion of en­gage­ment and dis­en­gage­ment la­ten­cies. This was ex­pected, as the start and end tran­si­tion points can­not be de­ter­mined in those par­tic­i­pants. The pat­terns ob­served were qual­i­ta­tively sim­i­lar to the main re­sult re­ported above, with ear­lier tem­po­ral dy­nam­ics for the en­gage­ment com­pared to the dis­en­gage­ment, al­beit with weaker ef­fects be­low the sta­tis­ti­cal sig­nif­i­cance thresh­old (repeated-measures ANOVA; start point: F(1,23) = 2.69, p = 0.11, ηp2 = 0.1; end point: F(1,23) = 2.96, p = 0.1, ηp2 = 0.11).

Determining how lex­i­cal pre­dic­tions are built dur­ing at­ten­tion switch­ing

Reorienting at­ten­tion to a dif­fer­ent speech stream im­plies a change of con­text and, con­se­quently, dif­fer­ent se­man­tic pri­ors for lex­i­cal pre­dic­tions. We thus hy­poth­e­sized that in­cor­po­rat­ing this change of con­text into the struc­ture of our se­man­tic re­gres­sor in a mul­ti­vari­ate en­cod­ing TRF model would in­crease EEG pre­dic­tion cor­re­la­tions, as it would bet­ter re­flect the dy­nam­i­cally up­dat­ing neural track­ing of the com­pet­ing speech streams. We com­pared four al­ter­na­tive mod­els rep­re­sent­ing how con­text could be in­cre­men­tally ac­cu­mu­lated for per­form­ing lex­i­cal pre­dic­tions at one par­tic­u­lar at­ten­tion block (e.g., B7, in Fig 4A). A naïve Oracle model, which uses all avail­able con­text of pre­vi­ous blocks from the cur­rent stream, whether at­tended or un­at­tended, to pre­dict words from the cur­rent block, served as our base­line, since it was es­sen­tially a switch-un­aware con­tex­tual rep­re­sen­ta­tion. Speaker-Specific and Attention mod­els were in­stead switch-aware mod­els, as they only con­sid­ered pre­vi­ously at­tended blocks as part of the con­text for lex­i­cal pre­dic­tions. Speaker-Specific as­sumed a higher de­gree of stream seg­re­ga­tion, since its con­text only con­sisted of pre­vi­ously at­tended blocks from the same speech stream, while Attention in­cluded any pre­vi­ously at­tended block from both streams. The Reset model in­stead ig­nored all pre­vi­ously at­tended blocks from any of the streams and com­puted con­text only over the course of the cur­rent block of at­ten­tion, as if the pri­ors for lex­i­cal pre­dic­tions were re­set at each at­ten­tion switch (Fig 4A).

As lex­i­cal en­tropy is a proxy of un­cer­tainty for next-word pre­dic­tion, its val­ues should be im­pacted by a switch­ing cue, which de­ter­mines an abrupt change of con­text. Fig 4B shows the change of av­er­age lex­i­cal en­tropy val­ues in words pre­ced­ing and fol­low­ing the switch cue, which vary de­pend­ing on the con­text mod­els. It can be ob­served that the Reset model peaks with the high­est un­cer­tainty and slowly de­cays over the course of the next words, while the Attention and Speaker Specific mod­els have over­all sim­i­lar lex­i­cal en­tropy dy­nam­ics and more sta­ble val­ues. Consistently with its switch-un­aware na­ture, the Oracle model in­stead dis­plays en­tropy val­ues that are largely un­changed de­spite the switch. An ex­plicit com­par­i­son of the av­er­age en­tropy val­ues of the four con­text-ac­cu­mu­la­tion strate­gies re­vealed sta­tis­ti­cally sig­nif­i­cant dif­fer­ences (repeated-measures ANOVA, Greenhouse-Geisser cor­rec­tion due to spheric­ity vi­o­la­tion; F(1,19) = 39.57, p = 9.59e−10, ηp2 = 0.68). Post-hoc pair­wise tests (Holm-adjusted) in­di­cated that the Reset model showed an in­ter­me­di­ate av­er­age en­tropy, sig­nif­i­cantly higher than the Oracle model (t(19) = 5.75, p = 1.44e−6, Cohen’s d = 0.45), and sig­nif­i­cantly lower than the Attention (t(19) = 4.64, p = 6.28e − 5, Cohen’s d = 0.36) and Speaker-Specific (t(19) = 2.24, p = 0.04, Cohen’s d = 0.17) mod­els. As such, de­spite show­ing the high­est peak fol­low­ing the at­ten­tion switch­ing cue, the Reset model had over­all in­ter­me­di­ate en­tropy val­ues across the four lex­i­cal ex­pec­ta­tion mod­els con­sid­ered here.

Lexical sur­prisal and lex­i­cal en­tropy were used as se­man­tic in­for­ma­tion re­gres­sors for each con­text model and sep­a­rately in­cluded in a mul­ti­vari­ate stim­u­lus rep­re­sen­ta­tion to fit sin­gle-sub­ject en­cod­ing TRFs (Envelope-Word Onset-Word Surprisal and Envelope-Word Onset-Word Entropy). Resulting TRF weights and EEG pre­dic­tion cor­re­la­tions were then com­pared across con­text mod­els, with the hy­poth­e­sis that switch-aware and con­text-rich rep­re­sen­ta­tions (e.g., Speaker-Specific or Attention) would best de­scribe neural ac­tiv­ity in at­ten­tion-switch­ing sce­nar­ios.

Before com­par­ing the con­text mod­els, we first tested whether each of them yielded a sig­nif­i­cant en­cod­ing ac­cu­racy gain com­pared to the base­line model only con­sist­ing of acoustic fea­tures (Envelope and Word Onset). When us­ing en­tropy as a re­gres­sor for se­man­tics, all mod­els, with the ex­cep­tion of Oracle, showed a sta­tis­ti­cally sig­nif­i­cant gain, sug­gest­ing a ro­bust track­ing of se­man­tic in­for­ma­tion in ad­di­tion to the stim­u­lus acoustics (paired t-tests: Oracle ver­sus Acoustics: p = 0.2; Spk.Spec. ver­sus Acoustics: p = 0.04; Attention ver­sus Acoustics: p = 0.04; Reset ver­sus Acoustics: p = 0.002). Employing word sur­prisal as se­man­tic re­gres­sor yielded sim­i­lar re­sults, with all the mod­els show­ing a ro­bust en­cod­ing of se­man­tic in­for­ma­tion, apart from Oracle (paired t-tests: Oracle ver­sus Acoustics: p = 0.15; Spk.Spec. ver­sus Acoustics: p = 0.02; Attention ver­sus Acoustics: p = 0.02; Reset ver­sus Acoustics: p = 0.01). The non-sig­nif­i­cant gain of the Oracle model com­pared to the acoustic model was ex­pected, since Oracle was de­signed as a con­trol switch-un­aware model.

In con­trast to our ex­pec­ta­tion, the Reset con­text model was shown to yield higher EEG pre­dic­tion cor­re­la­tion val­ues when en­tropy was used as a re­gres­sor for se­man­tics (Fig 4C). A re­peated mea­sures ANOVA re­vealed a sta­tis­ti­cally sig­nif­i­cant ef­fect of the main fac­tor, Context Model (F(2.1,47.75) = 9, p = 4e−4, ηp2 = 0.28; with Greenhouse-Geisser’s cor­rec­tion). In the Holm-corrected post-hoc tests, the Reset model was shown to yield sig­nif­i­cantly higher en­cod­ing ac­cu­ra­cies than Oracle (t(23) = 4.99, p = 2.63e−5, Cohen’s d = 0.14), Speaker Specific (t(23) = 3.73, p = 0.002, Cohen’s d = 0.1), and Attention (t(23) = 3.28, p = 0.006, Cohen’s d = 0.09). We then as­sessed the dif­fer­ence of TRF weights for the en­tropy fea­ture across the four con­text mod­els (Fig 4D), av­er­ag­ing the weights’ am­pli­tude within a win­dow broadly cen­tered around the TRF-N400 la­tency (350 – 550 ms). A re­peated mea­sure ANOVA was run on the weights’ am­pli­tude val­ues, re­veal­ing a main ef­fect of Context Model (F(3,69) = 15.51, p = 8.2e−8, ηp2 = 0.4). Post-hoc tests (Holm-corrected) showed that weights for the Reset model had lower TRF-N400 am­pli­tude com­pared to Oracle (t(23) = −5.56, p = 2.4e−6, Cohen’s d = 0.45), Attention (t(23) = −5.84, p = 9.2e−7, Cohen’s d = 0.47), and Speaker Specific (t(23) = −5.24, p = 6.5e−6, Cohen’s d = 0.43).

When fit­ting a mul­ti­vari­ate TRF in­clud­ing lex­i­cal sur­prisal as a se­man­tic re­gres­sor, we ob­served a sta­tis­ti­cally sig­nif­i­cant dif­fer­ence in EEG pre­dic­tion cor­re­la­tions be­tween the four con­text mod­els (F(1.59,36.6) = 3.96, p = 0.04, ηp2 = 0.15, with Greenhouse–Geisser cor­rec­tion). Post-hoc analy­ses in­di­cated a sta­tis­ti­cally sig­nif­i­cant dif­fer­ence be­tween the Reset and Oracle mod­els (t(23) = 3.18, p = 0.013, Cohen’s d = 0.1), while all other post-hoc pair­wise com­par­isons did not reach the sig­nif­i­cance thresh­old (p < 0.05). Similarly, no sta­tis­ti­cally sig­nif­i­cant dif­fer­ence emerged when com­par­ing the TRF-N400 am­pli­tude of the mod­els’ TRF weights.

Discussion

Speech com­mu­ni­ca­tion in multi-talker en­vi­ron­ments re­quires a skill­ful com­bi­na­tion of sus­tained at­ten­tion and rapid at­ten­tion switch­ing abil­i­ties [5,30]. While the neu­ro­phys­i­ol­ogy of sus­tained speech at­ten­tion has been widely stud­ied [1,9,37,38], less is known about the neural mech­a­nisms of at­ten­tion switch­ing. Here, we fill this gap with a tai­lored EEG ex­per­i­ment ex­am­in­ing the neu­ro­phys­i­ol­ogy of at­ten­tion switch­ing across dif­fer­ent lev­els of speech ab­strac­tion. In do­ing so, we (1) demon­strated an ex­per­i­men­tal par­a­digm that can suc­cess­fully probe both sus­tained at­ten­tion and at­ten­tion switch­ing mech­a­nisms; (2) suc­cess­fully dis­sected dis­en­gage­ment and en­gage­ment processes with a high tem­po­ral res­o­lu­tion, iden­ti­fy­ing sub­stan­tial asym­me­tries in their tem­po­ral un­fold­ing and a tran­sient si­mul­ta­ne­ous en­cod­ing of two speech streams; and (3) pro­posed a neu­ro­phys­i­o­log­i­cally plau­si­ble ex­pla­na­tion of how our brains up­date and use lex­i­cal con­text when switch­ing at­ten­tion.

The find­ings in this study have sev­eral im­pli­ca­tions for our un­der­stand­ing of speech at­ten­tion switch­ing mech­a­nisms. The asym­me­try mea­sured be­tween dis­en­gage­ment and en­gage­ment processes high­lights the im­por­tance of study­ing the two processes sep­a­rately. That dis­tinc­tion was of­ten not con­sid­ered in pre­vi­ous stud­ies on sus­tained at­ten­tion, which of­ten fo­cused on mea­sures of at­ten­tion bias or clas­si­fi­ca­tion [10,31,34,39]. The ef­fec­tive­ness of such de­cod­ing met­rics has been a dri­ving force for re­search on brain-com­puter in­ter­faces such as cog­ni­tively-con­trolled hear­ing de­vices [40 – 43]. Our find­ing high­lights that en­cod­ing met­rics en­able a suf­fi­cient level of de­tail for dis­en­tan­gling how the en­cod­ing of dif­fer­ent streams evolves over time. Here, we mea­sured an asym­me­try be­tween dis­en­gage­ment and en­gage­ment processes dur­ing at­ten­tion switch­ing in a very spe­cific sce­nario. Indeed, it will be im­por­tant to de­ter­mine how that re­la­tion­ship is mod­u­lated by fac­tors such as cog­ni­tive load, ag­ing, cog­ni­tive abil­i­ties, hear­ing dif­fi­cul­ties, in­ter­est in the speech con­tent, fre­quency of at­ten­tion switches in a trial, among many oth­ers. Of course, fu­ture work should also scru­ti­nize how the spe­cific na­ture of the task might im­pact that phe­nom­e­non.

Sustained at­ten­tion tasks, where par­tic­i­pants fo­cus on a tar­get speech while ig­nor­ing the masker [2,44], in­volve a quite par­tic­u­lar sce­nario where lis­ten­ers have no in­cen­tive to mon­i­tor un­at­tended streams. In real-life sit­u­a­tions, how­ever, lis­ten­ers may have rea­sons to ex­plore al­ter­na­tive speech streams, for ex­am­ple, due to a lack of in­ter­est in the cur­rent speaker. Our ex­per­i­men­tal par­a­digm more closely mir­rors this sce­nario. Although the in­structed na­ture of the task makes it less re­al­is­tic, the par­a­digm in­cen­tivises mon­i­tor­ing the masker and be­ing ready to rapidly switch at­ten­tion, which con­trasts with sus­tained at­ten­tion tasks. While the asym­me­try ob­served may be spe­cific to this ex­per­i­men­tal par­a­digm, the re­sult in­di­cates that our brains can en­gage with a new tar­get even be­fore start­ing the dis­en­gage­ment from the pre­vi­ous one, lead­ing to a tran­sient si­mul­ta­ne­ous track­ing of the two streams, com­pat­i­ble with au­di­tory scene mon­i­tor­ing mech­a­nisms [45,46]. In other words, there is a brief pe­riod, fol­low­ing an at­ten­tion switch, where the track­ing of a new stream be­gins to emerge with­out al­ter­ing the track­ing of the pre­vi­ous stream. The en­gage­ment and dis­en­gage­ment la­ten­cies are win­dow-de­pen­dent and, as such, are not in­tended as ab­solute neural tim­ings. Nonetheless, the en­gage­ment-dis­en­gage­ment asym­me­try is ro­bust to the se­lec­tion of the slid­ing-win­dow length (Fig 3) and can­not be ex­plained by the tem­po­ral smooth­ing in­tro­duced by the win­dow or by trial- and par­tic­i­pant-av­er­ag­ing. The tem­po­ral smooth­ing could, in prin­ci­ple, tem­po­rally stretch the en­gage­ment-dis­en­gage­ment dy­nam­ics, but not gen­er­ate an asym­me­try. Future re­search could in­ves­ti­gate the vari­abil­ity across tri­als and par­tic­i­pants to bet­ter char­ac­ter­ize these tem­po­ral dy­nam­ics. Within the dor­sal–ven­tral at­ten­tion frame­work [47,48], at­ten­tion re­ori­ent­ing re­sults from the flex­i­ble in­ter­play of the goal-di­rected dor­sal net­work and the stim­u­lus-dri­ven ven­tral net­work. Our find­ing of an en­gage­ment-dis­en­gage­ment asym­me­try aligns with this view of an in­te­grated process of at­ten­tion re­lease and re­al­lo­ca­tion, with po­ten­tially over­lap­ping neural dy­nam­ics.

Intuitively, main­tain­ing a tran­sient par­al­lel rep­re­sen­ta­tion of mul­ti­ple speech sources dur­ing at­ten­tion switch­ing is an ef­fi­cient neural pro­cess­ing strat­egy. It al­lows the flex­i­bil­ity to switch back to the pre­vi­ous stream, if nec­es­sary, with­out fully com­mit­ting to the newly at­tended speech im­me­di­ately. This phe­nom­e­non sup­ports pre­vi­ous claims that our brains can process speech maskers be­yond the acoustic level, en­cod­ing lin­guis­tic prop­er­ties to some ex­tent [7,8,16]. Unattended speech streams are also rep­re­sented in hu­man cor­ti­cal ac­tiv­ity, with ev­i­dence for lower en­cod­ing strengths or longer time la­ten­cies than the tar­get stream [1,49,50], and with a gra­di­ent of at­ten­tional bias from pri­mary to non­pri­mary au­di­tory cor­tex [13,14], whereby the un­at­tended stream en­cod­ing tends to be sub­stan­tially re­duced or not mea­sur­able in higher-or­der cor­ti­cal ar­eas [51,52]. Prior re­search has shown that not only the speech en­ve­lope, but also other key fea­tures of the un­at­tended speech, such as acoustic on­sets, are neu­rally rep­re­sented [53,54] and, when not read­ily avail­able due to speech mask­ing, they are even re­stored at later tem­po­ral scales [55]. One in­ter­pre­ta­tion is that en­cod­ing a tem­plate struc­ture of the un­at­tended speech might be a use­ful strat­egy to sup­press it [53]. Other re­search found at­ten­tional fluc­tu­a­tions cor­re­spond­ing to the changes in Target-Masker rel­a­tive sound en­ergy, with ev­i­dence that our brains may en­code some pho­netic in­for­ma­tion of un­at­tended streams [56,57]. The en­cod­ing of such un­at­tended stream in­for­ma­tion may be one of the fac­tors fa­cil­i­tat­ing the rapid en­gage­ment dur­ing at­ten­tion switch­ing.

Using al­pha ERSP as in­di­ca­tor of lis­ten­ing ef­fort, this study re­lated per­cep­tual de­mands with at­ten­tion switch­ing dy­nam­ics. A large re­duc­tion in EEG al­pha-band power was mea­sured con­sis­tently about 4.5 s af­ter the at­ten­tion-switch­ing cue. The ERSP tra­jec­tory sug­gests that a strong lis­ten­ing ef­fort per­sists through­out the at­ten­tion switch, with a sub­stan­tial re­duc­tion near the end of the switch (Fig 2A). Interestingly, the trough of the al­pha ERSP ob­served in this study roughly cor­re­sponds to the mo­ment when the new tar­get stream be­comes fully tracked, i.e., when the en­gage­ment process is com­pleted, which is well be­fore com­ple­tion of the dis­en­gage­ment process. Since the at­ten­tion switch­ing process can be deemed com­pleted when cor­ti­cal track­ing mea­sure­ments re­turn to pre-switch lev­els for both streams, this re­sult points to a link be­tween al­pha power and the en­gage­ment process specif­i­cally. Another pos­si­bil­ity is that the al­pha ERSP dy­nam­ics re­flect a com­bi­na­tion of lis­ten­ing ef­fort while re­fo­cus­ing at­ten­tion on the new tar­get stream and ac­tive sup­pres­sion of the new masker stream. When the newly at­tended stream is tracked at pre-switch lev­els, a suf­fi­cient acoustic and lin­guis­tic con­text on that stream may have been ac­cu­mu­lated to fa­cil­i­tate the track­ing, re­leas­ing cog­ni­tive re­sources. Future stud­ies could ex­plore this pos­si­bil­ity by ex­am­in­ing how the switch dif­fi­culty in­flu­ences the cor­re­spon­dence be­tween cor­ti­cal track­ing asym­me­try and al­pha ERSP. This find­ing ex­tends prior re­search on the neural cor­re­lates of se­lec­tive at­ten­tion and lis­ten­ing ef­fort. Variations in al­pha-band ac­tiv­ity have been as­so­ci­ated not only with au­di­tory at­ten­tion ef­fort [58 – 62], but also with vari­a­tions of in­ter­nally- ver­sus ex­ter­nally-fo­cused brain states [63], and with the ac­tive sup­pres­sion of ir­rel­e­vant in­for­ma­tion in ac­cor­dance with be­hav­ioral goals [64 – 66]. Notably, cog­ni­tive load and the in­hi­bi­tion of ir­rel­e­vant stim­uli ap­pear to be even more strongly in­flu­enced by at­ten­tion re­ori­ent­ing than by main­tain­ing at­ten­tion on a sin­gle speaker [29,67], high­light­ing the in­creased cog­ni­tive de­mands of switch­ing at­ten­tion. While al­pha power has com­monly been linked to sub­jec­tive lis­ten­ing fa­tigue [58,60] or the sig­nal-to-noise ra­tio (SNR) be­tween at­tended and un­at­tended streams [61], it is less fre­quently as­so­ci­ated with neural mark­ers of speech track­ing [68,69]. In this study, we iden­ti­fied a link be­tween the tem­po­ral dy­nam­ics of neural speech track­ing and lis­ten­ing ef­fort, sug­gest­ing a po­ten­tially valu­able met­ric for fu­ture re­search into at­ten­tion-switch­ing chal­lenges.

While cor­ti­cal track­ing and al­pha ERSP met­rics can be used to in­ves­ti­gate how at­ten­tion is dy­nam­i­cally re­al­lo­cated be­tween com­pet­ing streams, they do not spec­ify how higher-level lin­guis­tic rep­re­sen­ta­tions are up­dated dur­ing the at­ten­tion switch. Considering the im­por­tance of con­text in speech com­pre­hen­sion, it is par­tic­u­larly rel­e­vant to in­ves­ti­gate how it is ad­justed while shift­ing at­ten­tion from one speech stream to an­other. Addressing this ques­tion re­quires fo­cus­ing on neural rep­re­sen­ta­tions with rel­a­tively ex­tended tem­po­ral dy­nam­ics, which can be mean­ing­fully com­pared across com­pet­ing mod­els, and with suf­fi­cient dis­tinc­tion from the speech en­ve­lope track­ing to en­able the iso­la­tion of re­lated neural sig­na­tures. Lexical en­tropy and sur­prisal, with their long-la­tency and widely stud­ied neural sig­na­tures, are an ideal choice for char­ac­ter­iz­ing the im­pact of con­text on at­ten­tion switch­ing. Other in­for­ma­tive speech prop­er­ties such as phonol­ogy or prosody would also be im­por­tant to ex­am­ine; how­ever, their fast tem­po­ral dy­nam­ics chal­lenge the iso­la­tion of their at­ten­tion-switch­ing dy­nam­ics from the speech en­ve­lope track­ing. We there­fore fo­cused on how se­man­tic pre­dic­tions are up­dated fol­low­ing an at­ten­tion switch, mod­el­ing whether lin­guis­tic con­text is main­tained, re­set, or up­dated dur­ing the process.

This study com­pared four con­text-ac­cu­mu­la­tion mod­els that var­ied in their sen­si­tiv­ity to at­ten­tion switches and ac­cess to prior con­text: an Oracle model (context-rich but switch-un­aware), Speaker Specific and Attention mod­els (both con­text-rich and switch-aware but dif­fer­ing in stream se­lec­tiv­ity), and a Reset model (aware of the switch but lim­ited to the cur­rent block’s con­text). For each model, a mul­ti­vari­ate TRF was fit us­ing a se­man­tic re­gres­sor aligned with the re­spec­tive con­text strat­egy. Our data in­di­cates that the Reset model best pre­dicted EEG data, out­per­form­ing mod­els that re­tained past con­text and chal­leng­ing the as­sump­tion that prior se­man­tic in­for­ma­tion aids com­pre­hen­sion dur­ing at­ten­tion switches. This find­ing was un­ex­pected but one of the pos­si­ble out­comes that we had hy­poth­e­sized, and it may sug­gest that lis­ten­ers re­set con­text and re­cal­i­brate their lex­i­cal pre­dic­tions dy­nam­i­cally when switch­ing at­ten­tion to a new stream, in line with find­ings in the episodic mem­ory and event-seg­men­ta­tion lit­er­a­ture [70 – 72].

Interestingly, the mul­ti­vari­ate TRF analy­sis re­vealed fine-grained dif­fer­ences among the four con­text mod­els when lex­i­cal en­tropy is used as the se­man­tic re­gres­sor, but not for lex­i­cal sur­prisal. This may re­flect the for­ward-look­ing na­ture of en­tropy, as op­posed to the re­ac­tive na­ture of lex­i­cal sur­prisal. Another con­sid­er­a­tion is that par­tic­i­pants ac­tively per­formed the at­ten­tion switch, there­fore ex­pect­ing to en­counter dif­fer­ent speech ma­te­r­ial, po­ten­tially damp­en­ing the sur­prisal. This was not the case for the LLM model, which did not re­ceive a switch cue. This pos­si­ble mis­match be­tween LLM and hu­man brain could im­pact sur­prisal but not en­tropy (as that re­flects the process of con­text-build­ing), pro­vid­ing a po­ten­tial ex­pla­na­tion of why the Reset model per­forms best only for the en­tropy re­gres­sor. For in­ter­pret­ing these re­sults, it is also im­por­tant to con­sider that LLMs like Mistral are op­ti­mized for next-word pre­dic­tion, with­out a re­quire­ment of be­ing neu­ro­phys­i­o­log­i­cally plau­si­ble. While one in­ter­pre­ta­tion is that our brain’s lex­i­cal pre­dic­tions are built af­ter re­set­ting the con­text, it is also pos­si­ble that Mistral LLM and our brains deal with these speech dis­con­ti­nu­ities in a dif­fer­ent way al­to­gether. With these caveats in mind, counter to con­sis­tent re­ports of the sim­i­lar­ity be­tween mod­ern LLMs with neu­ro­phys­i­o­log­i­cal ac­tiv­ity [73 – 75], the higher neu­ro­phys­i­o­log­i­cal plau­si­bil­ity of the Reset model sug­gests that prior con­text is not availed of by our brains in the way im­ple­mented by the com­pet­ing mod­els, Attention and Spk-Specific.

Other strate­gies mak­ing use of the prior con­text might also be in place. One pos­si­bil­ity is that switch­ing at­ten­tion prompts a dif­fer­ent use of con­text, for ex­am­ple sum­ma­riz­ing its ab­stract mean­ing, as the gist of the story [16]. As such, there could be value in ex­plor­ing dif­fer­ent strate­gies for con­text rep­re­sen­ta­tion, for ex­am­ple, by em­ploy­ing Large Concept Models [76], which are trained and op­ti­mized for sen­tence pre­dic­tion. This lat­ter pos­si­bil­ity is also sup­ported by re­cent work on the ac­cu­mu­la­tion of lin­guis­tic con­text in LLMs and the hu­man brain [77] while lis­ten­ing to con­tin­u­ous mono­logues, show­ing that LLMs with a lim­ited con­text win­dow (32 to­kens) and with ac­cess to a coarse sum­mary of the pre­vi­ous con­text pre­dict neural ac­tiv­ity bet­ter than LLMs with a higher to­ken-mem­ory.

In sum­mary, this study showed that the process of at­ten­tion switch­ing in a re­al­is­tic multi-talker sce­nario can be in­ves­ti­gated in terms of its en­gage­ment and dis­en­gage­ment com­po­nents, with a tran­sient par­al­lel rep­re­sen­ta­tion of the two streams. We high­light the im­por­tance of re­lat­ing met­rics of neural track­ing of speech with met­rics of lis­ten­ing ef­fort and demon­strate that the lis­ten­ing ef­fort starts de­creas­ing fol­low­ing suc­cess­ful dis­am­bigua­tion of the two streams dur­ing at­ten­tional re-al­lo­ca­tion. Finally, we in­tro­duce an ap­proach for mod­el­ing lex­i­cal con­text of dy­namic at­ten­tion sce­nar­ios, show­ing the sen­si­tiv­ity of trans­former-based lan­guage mod­els to sub­tle dif­fer­ences in con­text ac­cu­mu­la­tion strate­gies. These find­ings have im­pli­ca­tions for fu­ture in­ves­ti­ga­tions into the cor­ti­cal mech­a­nisms of at­ten­tion re-ori­ent­ing and can be em­ployed to high­light dif­fer­ences across di­verse pop­u­la­tions in terms of age and hear­ing lev­els.

Methods

Ethics state­ment

Written in­formed con­sent was ob­tained from the study par­tic­i­pants. The study was con­ducted in ac­cor­dance with the Declaration of Helsinki, and the pro­to­col was ap­proved by the School of Psychology Research Ethics Committee of Trinity College Dublin (ethics ap­proval num­ber: SPREC012023 – 08).

Participants and ex­per­i­men­tal pro­ce­dure

We re­cruited 24 young na­tive English speak­ers (between 18 and 39 years of age) to take part in the study. Participants had nor­mal hear­ing, as per a screen­ing pure tone au­dio­gram from 0.25 Hz to 8 kHz and re­ported no his­tory of neu­ro­log­i­cal or psy­chi­atric dis­or­ders and had nor­mal or cor­rected-to-nor­mal vi­sion.

The ex­per­i­ment sim­u­lated a multi-talker sce­nario (Fig 1A) with a cir­cu­lar ar­ray (1.50m ra­dius) of six loud­speak­ers sur­round­ing the lis­tener (at hor­i­zon­tal an­gles of ±30°, ±112.5°, and ±157.5° rel­a­tive to the par­tic­i­pant). Participants were in­structed to dy­nam­i­cally switch their at­ten­tion be­tween left and right speech streams in the fore­ground, fol­low­ing a vi­sual cue (left- or right-point­ing ar­row) in­di­cat­ing the to-be-at­tended side, which was dis­played at the cen­ter of a screen placed in front of them. While switch­ing their at­ten­tion be­tween the fore­ground streams, they were also asked to ig­nore a 16-talker noise played from the four loud­speak­ers in the back­ground (B1-B4, each of them de­liv­er­ing a 4-talker bab­ble). Frontal streams were pre­sented at 60 dB sound pres­sure level (SPL) each, while each of the noise bab­bles was de­liv­ered at a level of 54dB SPL, re­sult­ing in a 3dB SNR of the fore­ground rel­a­tive to the back­ground.

Participants were pre­sented with 20 tri­als (lasting 180 s each) and had to per­form 6 at­ten­tion switches per trial, oc­cur­ring at semi-ran­dom in­ter­vals (Fig 1B). For this rea­son, blocks of sus­tained at­ten­tion to one par­tic­u­lar speech stream var­ied con­sid­er­ably in du­ra­tion, span­ning from 10 to 30 s. For each trial, a dif­fer­ent male and fe­male speech stream was played from the left and right loud­speak­ers in the fore­ground, coun­ter­bal­anc­ing through­out the ex­per­i­ment for side of pre­sen­ta­tion and start of the at­ten­tion block (i.e., the ex­per­i­ment con­sisted of five sub-blocks with the fol­low­ing trial se­quence: Male Left — Attention Start: Left; Female Left — Attention Start: Left; Male Left — Attention Start: Right; Female Left — Attention Start: Right).

Each trial started with the vi­sual cue point­ing to­wards the to-be-at­tended side and back­ground noise only, fol­lowed by the two fore­ground speech streams start­ing si­mul­ta­ne­ously af­ter 5 s. At the end of each trial, par­tic­i­pants an­swered three mul­ti­ple-choice ques­tions. First, they were pre­sented with a four-al­ter­na­tive forced-choice ques­tion re­gard­ing the con­tent of the at­tended speech stream. As at­ten­tion al­ter­nated be­tween the left and right speech streams over the course of the trial, the ques­tion could be about ei­ther of the two com­pet­ing streams. The sec­ond ques­tion was a bi­nary choice as­sess­ing par­tic­i­pants’ pref­er­ence be­tween the two streams (left or right) based on per­sonal in­ter­est. Finally, a 5-point Likert-scale ques­tion (1: very easy; 5: very hard) was used to quan­tify the per­ceived dif­fi­culty of the at­ten­tion switch­ing task. The ex­per­i­ment flow was self-paced and, to min­i­mize fa­tigue, it in­cluded three manda­tory breaks, each last­ing no less than five min­utes, every fifth trial.

Speech streams were pre­sented at a sam­pling rate of 44.1 kHz, de­liv­ered through a Roland Octa-Capture 10 × 10 sound card (24-bit/192 kHz), and played through six PreSonus Eris 4.5BT loud­speak­ers. Participants’ EEG ac­tiv­ity was recorded us­ing a BioSemi ActiveTwo sys­tem at a sam­pling rate of 512 Hz, from 64 elec­trodes po­si­tioned on a stan­dard cap fol­low­ing the International 10/20 sys­tem. An ac­tive (CMS) and a pas­sive (DRL) elec­trode were used as ref­er­ence for all elec­trodes, and two ad­di­tional elec­trodes were placed on the mas­toids for of­fline ref­er­enc­ing. For 21 of our 24 par­tic­i­pants, we ad­di­tion­ally recorded elec­tro-ocu­log­ra­phy (EOG) and elec­tro-myo­g­ra­phy (EMG). Two elec­trodes were placed on the left and right tem­ples to cap­ture hor­i­zon­tal eye move­ments, and two elec­trodes were po­si­tioned above and be­low the left eye to record ver­ti­cal eye move­ments and blinks. To cap­ture EMG ac­tiv­ity re­lated to head ro­ta­tion, an elec­trode was placed on the left del­toid mus­cle. Please note that ac­tiv­ity from these ex­ter­nal elec­trodes has not been an­a­lyzed as part of this study.

Stimuli

The fore­ground speech stim­uli in­cluded 40 TED Talks cov­er­ing a range of top­ics, with 20 fe­male and 20 male pre­sen­ters, each speak­ing in a va­ri­ety of English ac­cents. All speech streams were root-mean-squared (RMS) nor­mal­ized to re­duce dif­fer­ences be­tween male and fe­male voices. Each of the 4-talker back­ground bab­ble sig­nals was ob­tained by sum­ming the au­dio sig­nals of four sep­a­rate TED talks. The long-term av­er­age spec­trum of the bab­ble noise was then ad­justed to align with the over­all spec­trum of both male and fe­male fore­ground speak­ers, to pre­vent in­con­sis­ten­cies in mask­ing.

EEG data pre­pro­cess­ing

Neural data were an­a­lyzed with cus­tom scripts in MATLAB soft­ware (MathWorks), based on pub­licly avail­able scripts and re­sources shared as part of the CNSP ini­tia­tive (Cognition and Natural Sensory Processing; https://​cn­sp­work­shop.net). Neural sig­nals were first band-pass fil­tered be­tween 0.5 Hz and 8 Hz, us­ing a zero-phase shift Butterworth fil­ters of or­der 4, and then down­sam­pled from 512 to 64 Hz. Spherical spline in­ter­po­la­tion was ap­plied to re­place chan­nels that were three stan­dard de­vi­a­tions away from the mean. EEG was then re-ref­er­enced to the av­er­age of the two mas­toid chan­nels.

Speech fea­tures

The cur­rent study aimed to char­ac­ter­ize the neural track­ing of a dy­namic multi-talker sce­nario by mea­sur­ing the re­la­tion­ship be­tween EEG data and var­i­ous fea­tures of the fore­ground speech stim­uli, re­lated to their acoustic and lex­i­cal prop­er­ties. To model the speech acoustics, the au­dios’ broad­band am­pli­tude en­velopes were ex­tracted by tak­ing the ab­solute of the Hilbert trans­form. In or­der to model the lex­i­cal prop­er­ties of speech, the tran­scribed stim­uli and their au­dios were first au­to­mat­i­cally aligned us­ing the WebMAUS Basic aligner [78 – 80], which iden­ti­fied time­stamps cor­re­spond­ing to the start and end of each word. The re­sult­ing au­to­matic align­ment was saved in the TextGrid for­mat and ad­justed man­u­ally, when nec­es­sary, us­ing the Praat soft­ware [81]. The time stamps were then used to build bi­nary word on­set vec­tors in MATLAB. While bi­nary word on­set vec­tors rep­re­sent in­for­ma­tion re­lated to word seg­men­ta­tion, they can also be mod­u­lated ac­cord­ing to each word’s sur­prisal or en­tropy value to rep­re­sent higher-or­der se­man­tic in­for­ma­tion. Word sur­prisal is a mea­sure of how un­ex­pected a word is given its pre­ced­ing lin­guis­tic con­text, and it can be com­puted us­ing Large Language Models (LLMs), as the neg­a­tive log­a­rithm of the prob­a­bil­ity of that word given the pre­vi­ous con­text. Word en­tropy, on the other hand, mea­sures how un­cer­tain or un­pre­dictable the next word is. Here, we used a pre­trained open-source LLM, Mistral-7B-v0.1 [82] to ex­tract word prob­a­bil­i­ties, and then com­puted lex­i­cal sur­prisal and lex­i­cal en­tropy val­ues for each word.

When con­sid­er­ing the dy­namic na­ture of the at­ten­tion switch­ing task, the de­f­i­n­i­tion of what con­text to in­clude for the cur­rent word pre­dic­tion be­comes a non-triv­ial prob­lem. From the ma­chine per­spec­tive, given a word w be­long­ing to, e.g., the left stream, the LLM would pre­dict it more eas­ily when pro­vided with all the avail­able lin­guis­tic con­text from the left stream. However, from the neural/​be­hav­ioral per­spec­tive, since par­tic­i­pants were flex­i­bly re-ori­ent­ing their at­ten­tion be­tween left and right streams, the op­ti­mal con­text would be im­pacted by the at­ten­tion switch and, po­ten­tially, store in­for­ma­tion of pre­vi­ously at­tended blocks. To com­pare these con­text-ac­cu­mu­la­tion al­ter­na­tives, we rep­re­sented con­text ac­cord­ing to four al­ter­na­tive rep­re­sen­ta­tions. A ma­chine-ideal model, Oracle, con­sid­ers as con­text all words pre­ced­ing the cur­rent word in one par­tic­u­lar stream, whether they were at­tended or un­at­tended. As such, this model is un­aware of the switch of at­ten­tion. Among more neu­rally-plau­si­ble and switch-aware con­text ac­cu­mu­la­tion mod­els, we con­structed the Attention model, which in­cor­po­rates as con­text any pre­vi­ously at­tended block from both left and right speech streams, and the Speaker Specific model, which dis­plays a speech stream bias, whereby only pre­vi­ously at­tended blocks of the same stream are in­cluded as con­text for lex­i­cal pre­dic­tion of the cur­rent block. Similarly to Attention and Speaker Specific, the fourth model, Reset, is switch-aware, but not con­text-aware. In fact, it does not keep track of any pre­vi­ous speech block, nei­ther at­tended nor un­at­tended, and in­stead re­sets the con­text fol­low­ing each at­ten­tion switch cue.

Temporal Response Function (TRF) and analy­sis pro­ce­dure

To add this web app to your iOS home screen tap the share button and select "Add to the Home Screen".

10HN is also available as an iOS App

If you visit 10HN only rarely, check out the the best articles from the past week.

Visit pancik.com for more.