Swedish voice in Wavenet not pronouncing words correctly [179397314]

Assigned

Bug

Status Update

No update yet.

Description

pe...@kattalo.com

created issue #1

Feb 5, 2021 09:12AM

Problem you have encountered:
"Jag" is pronounced "Ja" (which also means "yes")
"Och" is pronounced "å" (changed recently and was previously correct)

What you expected to happen:
"Jag" should end with a "g" sound.
"Och" should end with a "k" sound.

Steps to reproduce:
Both words sound incorrect independent if they are in a sentence or on their own.

Other information (workarounds you have tried, documentation consulted, etc):
"Jag" sounds better if sent as "Jagg" to Wavenet. No workarounds for "Och" as of now.

Comments

ro...@google.com <ro...@google.com> #2Feb 5, 2021 02:04PM

Hello,

Thank you for reaching out.

This issue was forwarded to our product team. Please keep in mind that this issue has to be analyzed and considered by the product team and I can't provide you ETA for it to be delivered. However, you can keep track of the status by following this thread.

Kind Regards

pe...@kattalo.com <pe...@kattalo.com> #3Feb 5, 2021 02:11PM

Is there any update on this issue?

ro...@google.com <ro...@google.com> #4Feb 5, 2021 02:55PM

Assigned to gc...@google.com.

Hello,

Thank you for your patience.

Our product team is currently working on it. Once there will be an update it will be shared in this thread.

Kind Regards

se...@google.com <se...@google.com> #5Mar 5, 2021 09:15AM

Reassigned to gc...@google.com.

Are there any alternative solutions or workarounds that would allow us to access the pipeline run id? This functionality is useful for us to be able to correlate our predictions with the pipeline runs that created them. And that in turn can help analysis/troubleshooting.

pe...@kattalo.com <pe...@kattalo.com> #6Mar 5, 2021 10:09AM

Hello,

Thank you for reaching out. Our internal team is handling the case. Unfortunately there are no updates about it. For now, please stay tune to this thread for updates.

Regards,

pe...@devcube.se <pe...@devcube.se> #7Jun 1, 2021 07:56PM

Hello,

Quick update about this. Our team mentions that for Vertex Pipelines, we have a different set of placeholders, the currently implemented ones are names and uuids. Here's an example of using them: https://github.com/kubeflow/pipelines/blob/master/sdk/python/kfp/v2/compiler_cli_tests/test_data/pipeline_with_placeholders.py

Let me know if this helps you with your case.

Regards,

pe...@devcube.se <pe...@devcube.se> #8Jan 3, 2022 01:22PM

Hello

Quick update, this has been delayed. Please stay tune for further for updates.

Regards

pe...@devcube.se <pe...@devcube.se> #9Jan 3, 2022 01:22PM

As a workaround, you can specify a run ID when you invoke the pipeline and then additionally pass that run ID as an input parameter to your pipeline so that you can access it.

ew...@google.com <ew...@google.com> #10Jan 4, 2022 12:10PM

Hello

Thank you for providing the workaround, I will forward that to the google team. Please stay tune to this thread for updates.

Regards,

pe...@devcube.se <pe...@devcube.se> #11Jan 5, 2022 08:16AM

Are there any plans to add phonemes for Swedish any time soon? It seems like that would solve this problem (and many more!).

sj...@google.com <sj...@google.com> #12Jan 11, 2022 09:46AM

Reassigned to sj...@google.com.

Hello Pether,

I have forwarded your last request to engineering team. Please keep looking at this thread for updates.

Regards,

sj...@google.com <sj...@google.com> Jan 20, 2022 12:31PM

Reassigned to gc...@google.com.

Issue 179397314

Description

Issue summary

Comments

ro...@google.com <ro...@google.com> #2Feb 5, 2021 02:04PM

pe...@kattalo.com <pe...@kattalo.com> #3Feb 5, 2021 02:11PM

ro...@google.com <ro...@google.com> #4Feb 5, 2021 02:55PM

se...@google.com <se...@google.com> #5Mar 5, 2021 09:15AM

pe...@kattalo.com <pe...@kattalo.com> #6Mar 5, 2021 10:09AM

pe...@devcube.se <pe...@devcube.se> #7Jun 1, 2021 07:56PM

pe...@devcube.se <pe...@devcube.se> #8Jan 3, 2022 01:22PM

pe...@devcube.se <pe...@devcube.se> #9Jan 3, 2022 01:22PM

ew...@google.com <ew...@google.com> #10Jan 4, 2022 12:10PM

pe...@devcube.se <pe...@devcube.se> #11Jan 5, 2022 08:16AM

sj...@google.com <sj...@google.com> #12Jan 11, 2022 09:46AM

sj...@google.com <sj...@google.com> Jan 20, 2022 12:31PM

Add comment

Issue metadata