bug report Only the first two messages in the queue are played

[damiendier]

In this program only the first two are played

import pyttsx3
import time


def do_it():
    print("done")


engine = pyttsx3.init()
#voices = engine.getProperty('voices')

#engine.setProperty('voice', voices[1].id)
engine.connect(topic="finished-utterance", cb=do_it)
engine.say("I will speak this text")
engine.say("I will speak this text")
engine.say("I will speak this text")
engine.runAndWait()
time.sleep(10)

python version 3.12.4
on Windows 10

[MAC-GH]

This issue (only the 1st say() is spoken) happens too with other Python versions + Windows 11. Works by manually adding sleep() after say() but that defeats the purpose of runAndWait().

[cclauss]

I confirm on an M1 macOS PowerBook.

[romartyn]

This is how I overcome the problem, just delete engine every time:

import pyttsx3

def get_enginge():
    engine = pyttsx3.init()
    rate = engine.getProperty('rate')
    engine.setProperty('rate', rate + 100)
    return engine

with open("text.txt", "r", encoding='utf-8') as file:
    content = file.read().split('\n')
    for line in content:
        if len(line):
            print(f'{line = }')

            engine = get_enginge()
            engine.say(line)
            engine.runAndWait()
            engine.stop()
            del engine

[damiendier]

it seems to be a different bug when I do "say" and then "run and wait" it works as many times as I want

[damiendier]

I solved the problem simply by implementing my own queue
and also as I needed to do other things while it was saying the messages and to be able to stop them I put it in its own process that I can terminate if necessary

[eivl]

git bisect told me that this commit was the change that broke this.

f9bd477

WARNING: This MAY BREAK OTHER ENGINES!

maybe this is something @willwade can comment on?

I helped a guy online asking about this issue on discord, had him downgrade version and i became curious to what commit broke it.

i testet by doing a git checkout on this commit and on the one before to test it out.

I can write a new issue if that is needed, just let me know!