安裝 Steam
登入
|
語言
簡體中文
日本語（日文）
한국어（韓文）
ไทย（泰文）
Български（保加利亞文）
Čeština（捷克文）
Dansk（丹麥文）
Deutsch（德文）
English（英文）
Español - España（西班牙文 - 西班牙）
Español - Latinoamérica（西班牙文 - 拉丁美洲）
Ελληνικά（希臘文）
Français（法文）
Italiano（義大利文）
Bahasa Indonesia（印尼語）
Magyar（匈牙利文）
Nederlands（荷蘭文）
Norsk（挪威文）
Polski（波蘭文）
Português（葡萄牙文 - 葡萄牙）
Português - Brasil（葡萄牙文 - 巴西）
Română（羅馬尼亞文）
Русский（俄文）
Suomi（芬蘭文）
Svenska（瑞典文）
Türkçe（土耳其文）
tiếng Việ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.