安装 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.