Picroft aborts speeking since 19.02 update

@forslund, same here, just updated my picroft to 19.2.2 and tried to upgrade gtts, but it says it is current with version 2.0.3

Error still there for longer sentences. Though it seems that output is a bit longer than before. Strange.

I’ve pushed a longshot. For mimic and mimic2 the tts thread will now sleep until the audio has played. It’s unlikely to be the solution since it wouldn’t affect gtts.

If anyone is able to test if it makes any difference run

git fetch
git checkout bugfix/aiy-cutoff

And then restart mycroft.

thanks for the tip, just tried it, but I have problems with “read timed out” to api.mycroft.ai, could have been there already

on holidays from tomorrow, will check again later

The read timeouts are unrelated (Ongoing backend issue). Thanks for trying!

The read time outs should be resolved. I’ve updated the branch slightly so do a git pull next time you try.

The Picroft updated to 19.02.3. Should that be enough to get the updated code?

No change on the aiy-cutoff attempt.

Thanks wiggins. Back to the drawing board I guess.

Running 19.2.12 freshly updated from the stable image and still seeing the same thing (AIY hat build).

@forslund: I made a interesting observation today on my Picroft with AIY voice kit:

When - again - Mycroft aborted speaking I pressed the LED-button on top and suddenly Mycroft continued to speak the whole text (for several minutes as it was a very long text).

1 Like

I’ve been trying to look at the aiy-skill to see what that could mean but I see no real reason here. A short press should send the mycroft.stop signal, which should abort the speech by killing the aplay process… So this is definitely weird.

Do the setup for tha aiy voice kit use aplay or paplay for audio playback?

playback: it is aplay (in /etc/mycroft/mycroft.conf)

I am just wild guessing here: maybe audio output of the AIY-voice-hat gets muted for some reason and pressing the button un-mutes it again?

You’re probably right about the mute but what is causing it?

Btw @steve.penrod pushed a new unstable image this morning, it might be worth a shot to see how well that image is working.

Talked with Steve today and he actually added a google aiy specific fix for chopped audio: https://github.com/MycroftAI/enclosure-picroft/blob/stretch/home/pi/auto_run.sh#L328

Would be great to have some feedback on this.

1 Like

commented out load-module module-suspend-on-idle in `/etc/pulse/default.pa´

…Woo-hoo - wikipedia star wars followed by continue - Picroft talks and talks and talks…

Thanks.

2 Likes

Confirmed fixed here, too. Just to be clear, you have to make the change mentioned by @Dominik.

When I followed the link from @forslund and then the link on that page (See:) The last line in the thread says

This should be fixed on the latest SD card image.

I thought that meant it would be fixed in the image on the Picroft GitHub page (Picroft Stable 2019-07-10 image) but was wrong.

1 Like

Yes! This worked for me! I had to upvote in some way :slight_smile:

1 Like

N00b here, downloaded and used the .zipped image hosted by Mycroft on Google Drive, linked from that Github page, and am experiencing this same problem.

Is it Picroft Stable 2019-11-10 image you downloaded?
The old coments mentions older version of the Picroft image, and as far as I can tell it is fixed in the latest. 2019-11-10

Yes, I downloaded and installed it last week.