ashleymo2025 commited on
Commit
01e9b24
·
verified ·
1 Parent(s): 33a7320

Upload README.md with huggingface_hub

Browse files
Files changed (1) hide show
  1. README.md +67 -0
README.md ADDED
@@ -0,0 +1,67 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ language:
3
+ - sw
4
+ - pcm
5
+ - yo
6
+ - tl
7
+ - hi
8
+ - es
9
+ - en
10
+ license: cc-by-4.0
11
+ task_categories:
12
+ - automatic-speech-recognition
13
+ tags:
14
+ - code-switching
15
+ - conversational
16
+ - diarization
17
+ - spontaneous-speech
18
+ - asr
19
+ - speech
20
+ - low-resource
21
+ pretty_name: Code-Switching ASR
22
+ size_categories:
23
+ - 100K<n<1M
24
+ ---
25
+
26
+ # Code-Switching ASR
27
+
28
+ Code-switching ASR is a speech dataset of code-switching between English and medium to low resource languages. Samples include en-sw, en-pcm, en-yo, and en-tl but we can deliver any of the languages listed here: https://huggingface.co/datasets/liva-ai/yapdo-convo
29
+
30
+ Samples are full verbatim with speaker diarization and audio tags (e.g. [laughing], [phone buzzing], etc.). Transcripts are either AI-generated and then human reviewed, or fully human generated, depending on customer request.
31
+
32
+ ## Audio
33
+
34
+ All audio is collected in-house from our own pool of human contributors. The audio is fully channel separated.
35
+
36
+ ### How We Collect Data
37
+
38
+ The difference is in how we collect the data. We collect it through our internal consumer platforms, where people socialize with friends, whereas other providers typically create environments where contractors are paid to speak with each other as strangers. We've learned that this makes a huge difference in the naturalness of the interactions.
39
+
40
+ Our apps have users around the world, which has allowed us to capture various low-resource languages, mixed languages (e.g. Sheng), and code-switching as they naturally occur in the wild, which are all areas where ASR models can improve greatly.
41
+
42
+ ### Technical Analysis
43
+
44
+ | Property | Value |
45
+ | -------------------- | ------------------------------------------ |
46
+ | Sample rate | 48 kHz |
47
+ | Bit depth | 16-bit PCM |
48
+ | File format | WAV |
49
+ | Mean SNR | ~33 dB |
50
+ | Median RMS | -26 dBFS |
51
+ | Average speech ratio | 0.35 |
52
+ | Spectral centroid | ~0.66 kHz |
53
+ | Frequency content | 3.3 kHz (averaged over 10-30 second clips) |
54
+
55
+ ## Transcripts
56
+
57
+ All transcription is done in-house. Transcripts can follow a specific style guide (e.g. verbatim vs. non-verbatim, overlapping vs. non-overlapping timestamps, specific audio tags, etc.). We can provide transcripts for any of the languages listed here: https://huggingface.co/datasets/liva-ai/yapdo-convo
58
+
59
+ ### Transcription Process
60
+
61
+ All transcripts go through at least two full human review passes.
62
+
63
+ **First pass:** A native-speaker transcriber reviews and revises an AI-generated transcript or writes the transcript from scratch using our custom-built transcript editor. Transcribers are provided the conversation as channel-separated audio, which enables precise speaker diarization correction and makes it easier to identify and label each speaker accurately. They work through the entire audio file to produce a full verbatim transcript with precise timestamps down to the millisecond, labeled speaker turns for diarization, and audio event tags for non-speech sounds such as [phone buzzing], [laughing], or [door closing]. Native fluency allows transcribers to accurately capture code-switching, overlaps, disfluencies, colloquialisms, and other conversational details that are difficult to capture without deep familiarity with the speakers and language variety.
64
+
65
+ **Second pass:** Once the first pass is complete, the file is handed off to a senior reviewer with a proven track record of producing high-quality transcripts. The senior reviewer listens through the full audio file again and manually corrects any remaining transcription errors, spelling issues, timestamp inconsistencies, speaker label issues, or missed audio events. In addition, a senior native project lead performs rigorous spot checks across completed files to monitor quality, enforce consistency, and identify any recurring issues that need to be corrected across the project.
66
+
67
+ **Transcriber quality:** Transcribers are initially screened through a rigorous four-step process, involving both automation and human scoring, and are continuously monitored for attention and quality throughout every transcription project. Transcribers are promoted to more senior positions after delivering consistent quality work for weeks and continue to be monitored by Liva AI staff for attention to detail and quality.