Cài đặt Steam
Đăng nhập
|
Ngôn ngữ
简体中文 (Hán giản thể)
繁體中文 (Hán phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bungari)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (tiếng Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraine)
Báo cáo lỗi dịch thuật
There's three different tests you can do in audacity with one of the files.
1. Select a section after the first bit where it's unstable and select the effect "Pitch Change." It does an analysis to estimate the frequency of the note. It's not accurate on the low pitch files a2.ogg and below because it's detecting too much of the harmonics.
2. Add a new track along side the old one and generate a sine wave of the target frequency. That's those decimal values in tuning.config. If you generate 440 Hz (A4) next to the sound in a4.ogg, you'll hear a chord, not the two sounds merging together as one. You're going to need the volume to be the same for both sounds.
3. Measure the wavelength. It's most accurate if you do more than one period.
Number of periods / total length of time in seconds = frequency in Hz
Many applications that take sound samples like this assume C as the base note as it's typically regarded as the first note in an octave. It's the "do" in "do re mi fa so la ti do." This is why it was no surprise to me how simple the problem and solution are.
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=827912235
This only contains the tuning.config above.
EDIT: Now uploading to the Workshop.
EDIT 2: Uploaded.