Identifying visual prosody : where do people look?

Simone Simonetti, Jeesun Kim, Chris Davis

Research output: Chapter in Book / Conference PaperConference Paperpeer-review

1 Citation (Scopus)

Abstract

Talkers produce different types of spoken prosody by varying acoustic cues (e.g., F0, duration, and amplitude), also making complementary head and face movements (visual prosody). Perceivers can categorise auditory and visual prosodic expressions at high levels of accuracy. Research using eye-tracking trained participants to recognise the visual prosody of two-word sentences and found that the upper face is more critical for determining prosody than the lower face. However, recent studies using longer sentences have shown that untrained perceivers can match lower and upper faces across modalities. Given these, we aimed to extend the eye-tracking research by examining the gaze patterns of untrained participants when judging prosody with longer utterances. Twelve participants were presented questions, narrowly focussed, or broad focussed (neutral) utterances for a 3 alternative forced-choice identification task while eye gaze was recorded. Identification accuracy was high (81-97%) and did not differ among expression types. Participants gazed at eye regions longer and more often than mouth regions for all expressions. They gazed less at the mouth region for questions than for broad and narrow focussed statements. These results are consistent with the early research indicating the importance of the upper face for determining visual prosody.
Original languageEnglish
Title of host publicationSpeech Prosody 2016, May 31 - June 3, 2016, Boston, MA, USA
PublisherBoston University
Pages840-844
Number of pages5
Publication statusPublished - 2016
EventSpeech Prosody -
Duration: 31 May 2016 → …

Conference

ConferenceSpeech Prosody
Period31/05/16 → …

Keywords

  • gaze
  • visual perception

Fingerprint

Dive into the research topics of 'Identifying visual prosody : where do people look?'. Together they form a unique fingerprint.

Cite this