DRAFT GUIDELINES FOR REVIEWING RECORDINGS Thank you to all the Community Members that took part in developing the guidelines. The guidelines are now available on Common Voice . For support in localising the page please read this comment. . - From @heyhillary [Edited to include comments up to 2 Apr…

So we should be refusing voice samples that don’t pause for commas? That’s a lot of them. There should be an information video for both submitting and validation that tells people this.

So it’s better to reject such sentences as they will cause the engine to have a invalid knowledge of commas. I don’t think it is common for speech recognizers to actually listen to speech timing (prosody) to determine punctuation, it is more commonly done as a post-processing step based solely on…

[image] cjbaker: I don’t think it is common for speech recognizers to actually listen to speech timing (prosody) to determine punctuation, I agree, but we have to think of the future not the present when creating the data set. In addition, keeping one limited application in mind (Deep Speech…

Hi all, what about question marks and the like at the end of sentences? I often hear speakers not respecting them (for instance, to the text “you go first?” they would not raise the tone at the end of the recording, thus making it into a text that would rather look like “you go first !”). Should I s…

@Bloubi I think you should accept that. There’s a lot of variety between different nationalities, and a rising tone does not always go with a question mark. Also, sentences like “Well, are you coming?” when said in a cross voice doesn’t have a rising tone.

I’ve updated the draft at the top of this thread to include the various comments made so far. More feedback from the specialists would be welcome though. Pinging @nukeador , @kdavis , @josh_meyer , @mbranson , @gregor , @mkohler . I agree that we don’t want to scare off new contributors off by presentin…

[image] Michael_Maggs: I agree that we don’t want to scare off new contributors off by presenting the guidelines up-front as an off-putting wall of text that they have to read. A light-touch way to have them available would be to add to the recording validation page a short line such as: Unsure…

Something to add to the list would be ambiguous sentences. An example from the current corpus would be: I only read the quotations. The sentence has no errors but it’s still unclear what the correct pronunciation is.

@dabinat I would think that is an issue that the algorithm simply has to cope with. It’s an annoying feature of the English language that can’t be avoided.

Discussion of new guidelines for recording validation

Common Voice

Michael_Maggs (Michael Maggs) March 13, 2019, 3:55pm 13

I’ve edited the draft above to make it clear that we don’t want computer-synthesized voices. See What if people are using text-to-speech to record?

Topic		Replies	Views
Single Sentence Record Limit feature release Common Voice announcements	18	3121	June 13, 2022
✅ Die Juni-Validierungskampagne - alles was vor dem 22. Juni validiert wird, landet in der neuen Version des Datensatzes Deutsch (de)	14	1843	June 22, 2020
Discussion of new guidelines for uploaded sentence validation Common Voice sentence-collection	37	9564	September 25, 2020
"Listen" Guidance Common Voice feedback	8	2134	March 3, 2020
[RFC] Critères d'acceptation pour la validation d'enregistrements Français (fr) participation	21	2766	January 8, 2024

Discussion of new guidelines for recording validation

Related topics