šŸ—£ Feedback needed: Languages and accents strategy

Hi, Iā€™m a bit late to the party here, but Iā€™d like to offer a linguistā€™s point view.

TLDR; we should not crowdsource these definitions. Incorporate academic resources instead.

  1. Writing is a technology that has to be invented recently.
  2. Native speakers universally acquire their native language.
  3. A natural language has an internally consistent phonology.
  4. Spoken variations for continuums; division into ā€œlanguagesā€ are sometime political or historical.
  5. The official version of a language is often highly codified, constructed, and ā€œunnaturalā€ (far from spoken varieties).

Example: Norwegian is a language group, the varieties are largely mutually intelligible with each other, and with Swedish. The two formalised standards are BokmĆ„l (which half-jokingly is a koineized version written in Danish), and Nynorsk (an imaginary proto-version), both of which no-one ā€œreally speaksā€.

Comparable situation with Finnish. The official version that has a standard is an invention by amalgamating features from natural varieties, itā€™s highly constructed (though can be spoken).

Example: dialect continuum.

Consider:
ENGLISH: I am the son of my father and my mother.
SCOTS: A am the son o ma faither an ma mither.
FRISIAN: Ik bin de soan fan myn heit en myn mem.
DUTCH: Ik ben de zoon van mijn vader en mijn moeder.

Consider:
The Balkan example mentioned above.

What are the recommendations then?

  • For high-resource languages that have standard bodies, the meta-data should designate speaker status of whether they are producing the standardised variety, e.g. a ā€œnativeā€ English speaker, who can either use the General American, or Standard Southern British

  • For regional varieties, the meta-data should designate native speakers of a variety, as defined by widely established dialectology.

  • Non-native speech should be labelled as such. There are varying levels of ā€œaccentednessā€, from highly consistent L1-interference (in this case, you may say that the speaker has created a merged internal phonology in the process), to rampant lexical errors (e.g. using wrong tone or quantity as a result of having no control over phonemic contrast).

Now in terms of ASR, conventionally there are two models: the acoustic models and the language model. At some point it may be helpful to also have a separate phonology model: e.g. which phonemes can occur together, how they change into allophones in different contexts, or in the case of non-native phonology, substitutions etc.

1 Like

In practical terms, what crowdsourced questions would be useful for describing the speech production itself. I imagine independent of the language/variety designation, we can get meaningful self-reported information along several axes:

Stable-Unstable
ā€œWhen you speak this language, how stable is your accent over time?ā€
This goes from a native variety-speaker, to say, cosmopolitan Finns who speaks convincing TV English, but the accent varies widely from week to week.
Cf. https://www.phonetik.uni-muenchen.de/~jmh/research/papers/harrington00.nature.pdf

Convincing-Accented
ā€œHow do others (especially native speakers) perceive your accent?ā€
This only applies when you are aiming for an idealised target, e.g. an actor in a film playing a speaker of some other variety. Note: here ā€œaccentedā€ may be a bit misleading, since ā€œconvincingā€ is relative to the selected target, for example, when there is a consistent L1-mediated non-native phonology, the actor can put on a convincing ā€œRussian accentā€ in English.

Regional-Koineized
ā€œAre you speaking a variety that is used when regional locals talk to each other?ā€
When Glaswegians talk to Glaswegians, the production may be different from when they talk to New Zealanders.

1 Like

Do you have any empirical evidence that people are not able to self-classify their accents and that the subsequent classifications are not useful for the task of producing targetted speech recognition?

1 Like

This is more or less the right approach.

A post was split to a new topic: New to the community

@ftyers sometimes. Ferragne_2010_JPho.pdf has a British Isles English accent map, sort of. (1.3 MB)

Sorry everyone for taking so long to provide an update here.

We have been analyzing all your feedback, as well as consulting with more linguistic experts, both online and in person.

We are currently getting agreement on the final proposal, that Iā€™ll share here as soon as itā€™s ready. Itā€™s currently leaning towards a less restrictive approach (as lot of you asked for).

Thanks for your patience.

1 Like

October update:

We are still waiting to have a few more conversations with linguistics (sorry, this is taking way longer than we expected) and we have also have been trying to balance the current proposal so we bring value to both product and linguistic researchers using our dataset.

A lot of this project has been learning as we go, and the complexity of providing value to everyone is higher than we initially though.

My plan is to be able to come back with a recommendation by the end of this month.

Thanks all for your understanding!

Hi @txopi
Itā€™s the same with Kabyle language.

When I met some members from the Garabide foundation we talked about the different dialects and accents. They donā€™t correspond to the administrative repartition. Itā€™s the same with Kabylia.

Thanks for the lesson!!
Nice to know that

Hey everyone,

I know we havenā€™t published this yet, but getting to an agreement is taking a lot of time since Iā€™m scheduling personal conversation with different stakeholders.

My goal is to get green light from Deep Speech and legal team this week so we can share it here.

Cheers.

Update: As we have expressed here, we are definitely considering a more location-oriented metadata strategy to understand how people is likely to sound (as an improved version of the May proposal posted here)

We are right now evaluating with our legal team the requirements and limitations. Weā€™ll share it as soon as we have agreement.

1 Like

December update:

We have been working with our legal team about this proposal in the past month. Having in mind the current development focus is on infrastructure and we wonā€™t have the bandwidth to implement any changes on the site as a result of this proposal until at least February 2020, we agreed that weā€™ll give the legal team more time to finish the review and come back with recommendations.

Ideally this will happen mid/late-January so we have clarity to start planning on implementation by February.

Iā€™ll keep you posted and share the final proposal after the legal recommendations are out.

Thanks for your patience!

1 Like