peak_checker (BMS wav checker)

example:

D:\yamajet_is_sugoi>peak_checker
BMS wav checker
checking directory D:\yamajet_is_sugoi

  parsing v_o.wav...
    8bit 22050Hz/s Stereo Peak:L=-6.0206 db/R=-6.0206 db/M=-6.0206 db
  parsing v_n.wav...
    8bit 22050Hz/s Stereo Peak:L=-6.0206 db/R=-6.0206 db/M=-6.0206 db
  parsing v_foon.wav...
    8bit 22050Hz/s Stereo Peak:L=-8.99783 db/R=-8.99783 db/M=-8.99783 db
  parsing v_f.wav...
    8bit 22050Hz/s Stereo Peak:L=-6.0206 db/R=-6.0206 db/M=-6.0206 db
  parsing ohh.wav...
    8bit 22050Hz/s Stereo Peak:L=-17.6299 db/R=-11.0447 db/M=-13.7276 db
  parsing kick.wav...
    16bit 44100Hz/s Stereo Peak:L=-0.003977 db/R=-0.003977 db/M=-0.003977 db
  parsing clap.wav...
    8bit 22050Hz/s Stereo Peak:L=-6.08899 db/R=-6.29746 db/M=-6.1926 db
  parsing bass.wav...
    8bit 11025Hz/s Stereo Peak:L=-8.80797 db/R=-8.17434 db/M=-8.48538 db
Statistics[Global Group]:
  Available:8
  Max Peaks:L=-0.00 db/R=-0.00 db/M=-0.00 db(kick.wav)
  Min Peaks:L=-17.63 db/R=-11.04 db/M=-13.73 db(ohh.wav)
  Avg Peaks:L=-6.36 db/R=-6.00 db/M=-6.18 db
  Med Peaks:L=-4.95 db/R=-3.88 db/M=-4.40 db

Writing statistics...
Thank you for using

About grouping: peak_checker parses the format of the output file name of Edison and/or Slicex.

E.g. “drum - 01.wav”, “drum - 02.wav”, “pad - 01.wav”, “pad - 02.wav”

Result: [Global Group], [drum Group], [pad Group]

Katakana on the web

<span aria-label="developer">デベロッパ</span>
<span aria-label="developer">デベロッパー</span>
<span aria-label="developer">デベロッパァ</span> <!-- Excite: DEBEROPPAA -->
<span aria-label="developer">デヴェロッパ</span> <!-- Excite: DEVEROPPA -->
<span aria-label="developer">デヴェロッパー</span>
<span aria-label="developer">デヴェロッパァ</span> <!-- Excite: DEVEROPPAA -->
<span aria-label="developer">ディベロッパ</span>
<span aria-label="developer">ディベロッパー</span>
<span aria-label="developer">ディベロッパァ</span> <!-- Excite: DIBEROPPAA -->
<span aria-label="developer">ディヴェロッパ</span>
<span aria-label="developer">ディヴェロッパー</span> <!-- Excite: DIVEROPPA -->
<span aria-label="developer">ディヴェロッパァ</span> <!-- Excite: DIVEROPPAA -->

<span>開発者</span> <!-- Excite: Developer -->

iBMSC's bug?

番号が01に置き換わるbugがあるそうですが、再現手順が分かりませんでした。情報提供を求む！

備忘録

  • Can't we encode WebVTT as Base64? (Failed: Blink, Firefox, IE11)
  • Amaya and old Lynx cannot parse HTML5 charset

  • Ellipsis#In_Japanese, Japanese_punctuation#Ellipsis, エリプシス（ellipsis）と三点リーダ

    font-family: sans-serif;

    この段落には、前述のCSSを指定している。“……”

    Midori 0.5.9 (Windows 8.1):

    例示した文章に対し、欧文書体と繁体字が適用される。句読点は中央に位置し、くさかんむりは中途で途切れ、三点リーダーは下線として描画される。

    Traditional Chinese font (“PMingLiU”) is applied to Japanese text. Generic font-families are not useful.

  • Firefox 36 (released on ) or later supports CSS unicode-range.

    [about:config] layout.css.unicode-range.enabled → true

    @font-face {
    font-family: 'EllipsisJa';
    src:
        local('Hiragino Kaku Gothic ProN'),
        local('Yu Gothic'),
        local('Yu Gothic Regular'),
        local('IPAexGothic'),
        local('Meiryo'),
        local('MS Gothic');
    unicode-range: U+2026;
}

@font-face {
    font-family: 'DoubleQuote';
    src:
        local('Consolas'),
        local('Trebuchet MS'),
        local('Times New Roman');
    unicode-range: U+201C-201D;
}

@font-face {
    /* for Antique Gothic */

    font-family: 'AntiqueJa';
    src:
        local('Hiragino Mincho ProN'),
        local('Yu Mincho'),
        local('Yu Mincho Regular'),
        local('IPAexMincho'),
        local('MS Mincho');
    unicode-range:
        U+2047-2049,   /* Double punctuation for vertical text */
        U+3001-3002,   /* Ideographic Comma / Full Stop */
        U+3041-3096,   /* Hiragana */
        U+3099-30FF,   /* Dakuten, Katakana */
        U+31F0-31FF,   /* Katakana Phonetic Extensions */
        U+FF01,        /* Fullwidth Exclamation Mark */
        U+FF1F,        /* Fullwidth Question Mark */
        U+FF65-FF9F,   /* Halfwidth Katakana */
        U+1B000-1B001; /* Kana Supplement */
}

@font-face {
    font-family: 'GothicJa';
    src:
        local('Hiragino Kaku Gothic ProN'),
        local('Yu Gothic'),
        local('Yu Gothic Regular'),
        local('IPAexGothic'),
        local('Meiryo'),
        local('MS Gothic');
}

.test20150222 {
    font-family:
        EllipsisJa,
        DoubleQuote,
        AntiqueJa,
        GothicJa,
        sans-serif;
    font-size: 1.5em;
}

    この段落には、前述のCSSを指定している。“……”

    IE11 & Firefox 36+, Blink (Iron 40), Midori 0.5.9:

    例示した文章に対し、和文書体が適用される。句読点は左下に位置し、三点リーダーは中点として描画される。

    • Hiragana, Ideographic Comma, Ideographic Full Stop: “Yu Mincho”
    • Alphabet, Kanji, Horizontal Ellipsis: “Yu Gothic”
    • Double Quotation Mark: “Consolas”
    Firefox 35.0.1 (ja-JP, Windows 8.1 // unicode-range is not supported):

    例示した文章に対し、和文書体が適用される。句読点は左下に位置し、三点リーダーは中点として描画される。

    “Yu Gothic Regular” is applied to all characters.

    Safari 8:

    例示した文章に対し、和文書体が適用される。句読点は左下に位置し、三点リーダーは中点として描画される。

    • Hiragana, Ideographic Comma, Ideographic Full Stop: “Hiragino Mincho ProN”
    • Alphabet, Kanji, Horizontal Ellipsis: “Hiragino Kaku Gothic ProN”
    • Double Quotation Mark: “Trebuchet MS”

  • Firefox 38.0a1 supports HTML5 ruby element (CSS Ruby).

    <!DOCTYPE html><html><head><meta charset="utf-8"><title>Ruby test</title>
<style>
/* Above-mentioned CSS @font-face rules, and */
.v {
    /* for IE5.5–11 */
    writing-mode: tb-rl;
}

html:root .v {
    -webkit-writing-mode: vertical-rl;
    -webkit-text-orientation: mixed;

    /* for Fx36+ (Nightly Build only) */
    writing-mode: vertical-rl;
    text-orientation: mixed;
}
</style>
</head>
<body>
<p
>&#xFF62;<ruby>&#x524D;<rp>&#xFF08;</rp><rt>&#x305C;&#x3093;</rt><rp>&#xFF09;</rp></ruby
><ruby>&#x4E16;<rp>&#xFF08;</rp><rt>&#x305B;</rt><rp>&#xFF09;</rp></ruby>&#xFF63;&#x306E;<br
><ruby>&#x8A18;<rp>&#xFF08;</rp><rt>&#x304D;</rt><rp>&#xFF09;</rp></ruby
><ruby>&#x61B6;<rp>&#xFF08;</rp><rt>&#x304A;&#x304F;</rt><rp>&#xFF09;</rp></ruby>&#x306F;<br
>&#x3042;&#x308A;&#x307E;&#x3059;&#x304B;&#xFF1F;</p
><p
><ruby>&#x87FB;<rp>&#xFF08;</rp><rt>&#x30AD;&#x30E1;&#x30E9;</rt><rp>&#xFF09;</rp></ruby
>&#x306B;&#x2026;<br
>&#x306A;&#x308B;<ruby
>&#x524D;<rp>&#xFF08;</rp><rt>&#x307E;&#x3048;</rt><rp>&#xFF09;</rp></ruby
>&#x306E;</p>

<div class="test20150222 v">
<p
>&#xFF62;<ruby>&#x524D;<rp>&#xFF08;</rp><rt>&#x305C;&#x3093;</rt><rp>&#xFF09;</rp></ruby
><ruby>&#x4E16;<rp>&#xFF08;</rp><rt>&#x305B;</rt><rp>&#xFF09;</rp></ruby>&#xFF63;&#x306E;<br
><ruby>&#x8A18;<rp>&#xFF08;</rp><rt>&#x304D;</rt><rp>&#xFF09;</rp></ruby
><ruby>&#x61B6;<rp>&#xFF08;</rp><rt>&#x304A;&#x304F;</rt><rp>&#xFF09;</rp></ruby>&#x306F;<br
>&#x3042;&#x308A;&#x307E;&#x3059;&#x304B;&#xFF1F;</p
><p
><ruby>&#x87FB;<rp>&#xFF08;</rp><rt>&#x30AD;&#x30E1;&#x30E9;</rt><rp>&#xFF09;</rp></ruby
>&#x306B;&#x2026;<br
>&#x306A;&#x308B;<ruby
>&#x524D;<rp>&#xFF08;</rp><rt>&#x307E;&#x3048;</rt><rp>&#xFF09;</rp></ruby
>&#x306E;</p
></div>

</body></html>
    Internet Explorer 11.0.9600.17631:
    Before: “MS PGothic” base, but U+2026 is “Arial”. After: “Yu Mincho” base, Kanji characters are “Yu Gothic”. Perfect.
    Firefox 35.0.1 (unicode-range, writing-mode, and ruby are not supported):
    (About the same as Opera 12.17):
    After: “Yu Gothic” base. Before: “MS PGothic” base.
    Firefox 36 (writing-mode and ruby are not supported):
    After: “Yu Mincho” base, Kanji characters are “Yu Gothic”.
    Firefox 38.0a1:
    Before: “MS PGothic” base. After: “Yu Mincho” base, Kanji characters are “Yu Gothic”. Baseline is upset by ruby elements (maybe).
    Blink (Iron 40.0.2150.0, Opera 27.0.1689.69, Vivaldi 1.0.94.2):
    Before: “MS PGothic” base. After: “Yu Mincho” base, Kanji characters are “Yu Gothic”. Vertical 'HALFWIDTH LEFT/RIGHT CORNER BRACKET' are not rotated…
    Midori 0.5.9:
    Before: “PMingLiu” base, but U+2026 is “Arial”. After: “Yu Mincho” base, Kanji characters are “Yu Gothic”. Vertical texts are not rotated…
    Lynx 2.8.6rel.4THjp:
    “MS Gothic” base. 'HALFWIDTH LEFT/RIGHT CORNER BRACKET' are replaced to U+0022 'QUOTATION MARK'.
    Amaya 11.4.7 (unicode-range, writing-mode, and ruby are not supported):
    Before: “Cyberbit” base, but U+2026 is “Arial” (maybe). After: font-size 1.5em is applied.
    Windows XP + Internet Explorer 8.0.6001.18702 (unicode-range and multiplex src syntax are not supported):
    Before: “MS PGothic” base, but U+2026 is “Arial” (maybe). After: “MS (P)Gothic” base. Baseline is upset by ruby elements (maybe). U+2026 is set to baseline as “Arial”.
    Windows XP + Internet Explorer 6 (unicode-range and multiplex src syntax are not supported):
    Before: “MS PGothic” base. After: “MS (P)Gothic” base.

  • Default font on IE11 (ja-JP locale):

    • [UTF-8] unspecified font-family = “Times New Roman” applied to U+2026 (vertical-align: baseline; Ellipsis: Circle;)
    • [UTF-8] specified sans-serif = “Arial” applied to U+2026 (vertical-align: baseline; Ellipsis: Square;)
    • [UTF-8] sans-serif + lang="ja" = “Meiryo” applied to U+2026
    • [Shift_JIS] unspecified font-family = “MS PGothic” applied to U+2026
    • [Shift_JIS] specified sans-serif = “Meiryo” applied to U+2026
    • [Shift_JIS] sans-serif + lang="en" = “Arial” applied to U+2026
  • Firefox changes applied default-fonts by lang attribute value.

  • 藤原竜也変換ツールJS版: This Dakutenizer dies on vertical texts.

    alt by ruby (<ruby>！<rt>゛</rt></ruby>):
    ど゛う゛し゛て゛な゛ん゛だ゛よ゛お゛お゛ぉ゛お゛！゛！゛！゛ん゛あ゛あ゛あ゛あ゛あ゛ぁ゛ぁ゛あ゛あ゛！゛！゛！゛！゛
    alt by U+3099 (！&#x3099;):
    どゔじでな゙ん゙だよ゙お゙お゙ぉ゙お゙！゙！゙！゙ん゙あ゙あ゙あ゙あ゙あ゙ぁ゙ぁ゙あ゙あ゙！゙！゙！゙！゙
    alt by img:

    (Vibrated voice start)

    ど゛う゛し゛て゛な゛ん゛だ゛よ゛お゛お゛ぉ゛お゛！゛！゛！

    (Vibrated voice end)

    alt by img (failed):
    vertical text, but image's alternate text rendered as horizontal text

DTXMania 101 + DTXCreator 028 ()

DTXMania101と099c, DTXCreator028をリリースしました。

Player application “DTXManiaGR.exe” and editor application “DTXCreator.exe” supported Unicode (UTF-16) together. Furthermore, *.config files were changed to UTF-8 encoding.

Quotes from DTXCreatorSetting.config:

  <RecentUsedFile>
    <string>C:\Users\yyagi\Documents\Visual Studio 2008\Projects\dtxmania4\trunk\DTXManiaプロジェクト\bin\x86\Debug\samplesongs\omens\DTXFiles.CASIOPEA VS THE SQUARE\omens\omensoflove_ext_HD_60fps_6mbps.dtx</string>
  </RecentUsedFile>

My monitor is narrow... I want to tooltips (or text-overflow: ellipsis) ...

Memo: LR2 timegates

LR2 timegates (According to 803832's report, in milliseconds)
#RANK 0 (Very Hard) 1 (Hard) 2 (Normal) 3 (Easy)
PGreat8151821
Great 23 <= x < 27 28 <= x < 31 40 <= x < 42 60 <= x < 64
Good 38 <= x < 42 60 <= x < 61 98 <= x < 101 120 <= x < 123
Bad200200200200
Great (approximation)25304060
Good (approximation)4060100120
Survey method:

1秒毎にノーツを置く→適当に遅ズレさせながら叩く→判定タイマーと曲開始タイマーのズレを見る (要スキン編集)

According to Bluvel's additional research:
LR2 timegates (in milliseconds)
#RANK 0 (Very Hard) 1 (Hard) 2 (Normal) 3 (Easy)
PGreat8151821
Great24304060
Good4060100120
Bad200200200200

BMSE v iBMSC performance comparison table

  • iBMSCに関するdocumentが少ないなか、詳細に調べてくださっていて頭が下がります。有難うございます。
  • 私に時間ができたら、BMSC/GDAC2も比較してHTML化してみたいけど、3月あたりまで無理かな…… [追記] BMSC/GDAC2/BMSE/iBMSCを比較してHTML化しました。

  • 私はいくつかの項目について補足することができるかもしれません。

    • BMSEはcustomizable skinsを持ちます(“bmse\theme\xxx.ini”)。Fontも変更できます。例:

      [Main]
Key="BMSE"
Language="Japanese"
;Font="MS UI Gothic"
;FixedFont="ＭＳ ゴシック"
Font="Meiryo UI"
FixedFont="MeiryoKe_Console"

      ただしBMSEは、外観を変更するためのUIを持ちません。また、私はWindows以外のplatformをtestできないので、WineなどでFontを変更できるかどうかについては知りません。

    • iBMSCは“BMSE ClipBoard Object Data Format”を部分的に解釈できるので、woslicerII.exeやBmWhはiBMSCの上で働くことができます。ただしmultiline BGM notesに対するcopy/pasteはうまくいかないかもしれません。

      私の環境では“woslicerIII\OggVorvis.dll”がAnti-Virus Softwareに検出されてDownloadすら阻害される状況なので、BMHelperやmid2bmsの連携に関しては確認していません（複数行BGMのClipBoard情報が必要なので、おそらくうまくいかないような気がします）。

      [追記] の更新において、woslicerIIIもBMHelperと連携できるようになったようです。

    • iBMSCは複数音声のDrag-Drop-Definingが可能です（すくなくともWindows XPとWindows 8.1では）。

      Non-audioは#WAV listから除外されます。

BMS Upload & Preview Tool BMS Preview Uploader (仮)

We know web apps which combined BMS chart uploader and BMS previewer already: “k-bms : append BMS and BGA archives” (mention in my old diary). We may regard the position of this “BMS Upload and Preview Tool” as Python/SVG edition of an aforementioned tool. Both outward appearances aren't similar, because this tool respects (about appearance and features) to TexTage.

Quotes from SVG version #000:

000 One quadruple measure requests at least 50 line elements. If song has #100 measures, at least 5200 element nodes are requested. (ドット絵におけるsvgのパフォーマンス検証)

Using Compounding paths

  • Adding black rectangle (for quote/print)
  • Adding shape-rendering attribute/style (for clear lines)
  • Drawing vertical-lines first (for beautiful barlines)

  • Replacing from lines to Compounding paths, and classifying:

    1. <line  x1="20.5"  x2="20.5" y1="600.5" y2="456.5" style="stroke-width: 1;" stroke="#eeeeee" />
<line x1="280.5" x2="280.5" y1="600.5" y2="456.5" style="stroke-width: 1;" stroke="#eeeeee" />
    2. <path stroke-width="1" stroke="#eee" shape-rendering="crispEdges"
  d="M  20.5, 600.5 v -144
     M 280.5, 600.5 v -144" />
    3. <style type="text/css">/*<![CDATA[*/
    path  {shape-rendering: crispEdges; }
    .vert {stroke-width: 1; stroke: #eee; }
/*]]>*/</style>
<path class="vert" d="M20.5 600.5v-144M280.5 600.5v-144" />

000 Element nodes decreased from 52 to 8. When there are about 10 path elements (i.e. classes), SVG can draw all grids of BMS charts.

The style element is convenient, but when users invalidate style sheets, even styles of SVG comes off. (Case IE: Via the menu toolbar, choose: “View” > “Page Style” > “No Style”) ...This behavior may be unsuitable for the intuition as the image format.