Finish reading message before going to new message

[imesmer]

Right now if a person sends me at texts and the app is reading it, and I receive another text right after that, it won't finish the previous text and it will just jump to the new one. It would be great if it would allow it to finish and put new notifications on hold until the current one is complete. Thank you

If this feature is added would you please have it updated in automatically because it's not something I would go back and forth checking for. It would be great if it's already active and I will notice it by hearing the difference. Again thank you in advance.

[pilot51]

It should already be queuing messages without interrupting speech or removing queued messages.

I just tested by setting Ignore Repeats to 0 and rapidly tapping Test 5 times. It spoke all 5 notifications one after the other without interruption.
Could you do the same test to be sure you can reliably reproduce the issue?

Also check the Notification Log. That should show a short descriptive yellow message on any notification that was interrupted during speech. If you see that, please let me know what it says.

What device and TTS engine are you using?
It's possible that the engine might not be properly queuing messages as requested (QUEUE_ADD where speak is called).

[imesmer]

Thank you for the quick response. I changed the setting and test just made the noise but no other sounds are coming through so I'll ask someone to send me to three texts one after another

…

On Sun, Oct 20, 2024, 6:53 PM Mark Injerd ***@***.***> wrote: It should already be queuing messages without interrupting speech or removing queued messages. I just tested by setting Ignore Repeats to 0 and rapidly tapping Test 5 times. It spoke all 5 notifications one after the other without interruption. Could you do the same test to be sure you can reliably reproduce the issue? Also check the Notification Log. That should show a short descriptive yellow message on any notification that was interrupted during speech. If you see that, please let me know what it says. What device and TTS engine are you using? It's possible that the engine might not be properly queuing messages as requested (QUEUE_ADD <https://developer.android.com/reference/android/speech/tts/TextToSpeech#QUEUE_ADD> where speak is called <https://github.com/pilot51/voicenotify/blob/v1.3.1/app/src/main/java/com/pilot51/voicenotify/Service.kt#L344> ). — Reply to this email directly, view it on GitHub <#144 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALRXB6IU56Y7Q7CDDHU32ELZ4RNCXAVCNFSM6AAAAABQIVFSHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRVGM4TMNJUHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[pilot51]

The Notification Log is a very useful troubleshooting feature which should always show why a notification was interrupted or not spoken, as long as the Voice Notify service is enabled. There would be red text if the notification was not spoken at all or yellow text if it was interrupted while speaking.

Could you run the test and check the Notification Log and let me know what the red or yellow text says if it doesn't make it clear how to resolve the issue?