Skip to content
This repository has been archived by the owner on Mar 31, 2023. It is now read-only.

Speechmarks missing playerOffsetInMilliseconds #3

Open
jayeheffernan opened this issue Sep 16, 2019 · 1 comment
Open

Speechmarks missing playerOffsetInMilliseconds #3

jayeheffernan opened this issue Sep 16, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@jayeheffernan
Copy link

I'm trying to modify these examples to be able to sync an animation on a Raspberry Pi to the voice of an Alexa Echo. I am receiving the speech data, but is seems to be missing some of the data required to sync. The documentation for the speechdata interface (linked to in your README, here) suggests:

To determine how to sync speechmark data to Alexa's speech, use startOffsetInMilliSeconds minus playerOffsetInMilliseconds.

The packets I am receiving look just like the example in the README:

# Speechmark
{ {'payload': {'speechmarksData': [{'value': 't', 'type': 'VISEME', 'startOffsetInMilliSeconds': 708}]}, 'header': {'namespace': 'Alexa.Gadget.SpeechData', 'name': 'Speechmarks'}} }

They have a startOffsetInMilliSeconds, but no playerOffsetInMilliseconds. Any idea how to sync an animation to the speech data without this value?

@vartakr
Copy link
Contributor

vartakr commented Sep 23, 2019

Hi Jaye,

Thank you for reaching out to us. We are currently looking into this issue, and we will get back to you as soon as we have an update regarding this.

@vartakr vartakr added the bug Something isn't working label Sep 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants