Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Widget: Audio Add TTS Support to match Dashboard 1.0 Functionality #1560

Open
kd9lsv opened this issue Dec 24, 2024 · 3 comments
Open

Widget: Audio Add TTS Support to match Dashboard 1.0 Functionality #1560

kd9lsv opened this issue Dec 24, 2024 · 3 comments
Labels
feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do

Comments

@kd9lsv
Copy link

kd9lsv commented Dec 24, 2024

Description

Discussed on #52.
@bartbutenaers pointed to create issue to not lose track.

Functionality was missing from #1506
Didn't include the Text to Speech functionality in new 2.0 node.

Pictures from Dashboard 1.0
image
image

No hurry on additional functionality.

Have you provided an initial effort estimate for this issue?

I am no FlowFuse team member

@kd9lsv kd9lsv added feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do labels Dec 24, 2024
@bartbutenaers
Copy link
Contributor

@kd9lsv
Thanks for doing the administrative work!

Reminder for myself: the frontend code for TTS in the old dashboard can be found here.

If I remember correctly, there was one issue with that implementation: you have a dropdown in the ui-audio's node config screen, that allows you to select which language needs to be spoken. But that "TTS voice" dropdown contains the languages available on the server running Node-RED, not the device running the frontend dashboard in the browser. So you can select a supported language in the config screen, but might not have speech in that language in your dashboard (if the client device doesn't support that particular language)...

Don't think we can solve that problem. But need to add it at least to the documentation.

@bartbutenaers
Copy link
Contributor

Perhaps it is better to call it "preferred" TTS voice, to lower the expectations...

@bartbutenaers
Copy link
Contributor

@Steve-Mcl
Since I developed the ui-audio node, you can assign this one to me (after Chistmas eve whenever you have more time).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do
Projects
Status: Backlog
Development

No branches or pull requests

2 participants