Arpasing VB Tutorial 1.2

How to record and OTO an Arpasing voicebank

  1. Kiyoteru
    Kanru Hua has formally released the Arpasing standard for English UTAU voicebanks. You can read about it on his website at these links.
    0.1.0: https://webhost.engr.illinois.edu/~...6/introducing-arpasing-for-english-utauloids/
    0.2.0: https://webhost.engr.illinois.edu/~khua5/index.php/2017/05/09/arpasing-standardscriptplugin-update/

    This tutorial will explain how to record and OTO an Arpasing bank yourself.

    While you can use whatever you like to record, it will be much, much easier to use OREMO. If you're currently unfamiliar with how to use it, see this as an opportunity to learn how. If you plan to do sample processing, you'll have to do it after recording.
    Official download: OSDN
    Wine wrapper for macOS: UTAForum
    Mac native English translation: UTAForum
    (I recommend the wine wrapper, because the mac native version doesn't have the comment box.)

    If for some reason you absolutely cannot use OREMO, you will have to refer to the proposal PDF in the Arpasing download from Mr. Hua's website. Scroll down to the chart for the reclist, and name each file according to the corresponding number.

    To begin, download the latest default reclist from here: http://utaforum.net/resources/arpasing-reclist-directory.299/
    The folder contains three reclist files, OREMO comment file, and index file.
    The core list is numbers 000 to 119, n gram coverage is 220 to 319, and isolated vowels are 320 to 334.
    The OREMO comment file allows you to see the actual phonemes or words that correspond with each number.
    The index file is for moresampler to reference when generating the OTO.
    If you're using any reclist other than the default, it will likely include the same set of reclist, comment, and index.

    Set up a folder for your voicebank, and copy+paste index.csv and OREMO-comment.txt into your new folder. In OREMO, open the core list as the reclist. (After you finish this list, switch to the n gram list, and then the vowel list.) Set the destination folder to your new folder.

    You can record with or without guideBGM. If you want to use guideBGM, I recommend using a short one made for CVVC reclists, such as the CVVChinese BGMs or the VCCV English BGMs.

    The comment file will tell you how to pronounce it approximately using words, and precisely in arpabet phonemes. This short article will explain how to read and pronounce arpabet. It's actually pretty straightforward!
    Other than vowel strings, each string only has 1 type of vowel. All three syllables will rhyme.

    Sing the 3 syllables consecutively, as if recording VCV. If at any point there is a "q" in the phonetics (or an apostrophe in the words) it means a brief pause (a glottal stop).
    For reference, you can download existing voicebanks from the voicebank directory.

    FOR MULTIPITCH: In the main voicebank folder, there must be a pitch that has no suffixes in the OTO. All other pitches with suffixes should be in their own subfolders. Don't add suffixes to the file names, or else the index.csv will be incompatible.

    Onto OTOing! Simply drag and drop the folder onto moresampler.exe to do so.
    Enter 3 to choose arpasing. When prompted on renaming duplicates, enter y or yes. Whenever there are multiple of the same diphone, such as [s t], this will add a numeric suffix to the end of additional copies. This serves to distinguish each one from the other, as they may sound different based on the context of nearby phonemes in the string. You can also choose whether or not to include a suffix. It's not possible to use characters such as arrows or kanji, so you will have to use suffixes such as "S" or "A#3".

    If you are using Mac or Linux, you will have to use wine to run Moresampler. Open terminal in the folder that moresampler.exe is in, and type "wine moresampler.exe /path/to/voicebank". If you're unable to do this, transfer your files to a windows computer, or ask a friend with Windows for help to generate it.

    Now that your base OTO is generated, it's time to refine it. Every entry of the OTO is a diphone, meaning that there are only two phonemes or two sounds. In general, the first one is a connector to the previous note, while the second one is the main phoneme for the current note. To OTO, first find the section corresponding to the first phoneme, then find the section for the second phoneme.

    First Phoneme

    This covers the blue offset and overlap.

    [-]
    The amount of overlap really doesn't matter for this one, because these notes always come at the beginning of a phrase, right after a rest. The only important thing is that it covers an area of silence.
    [​IMG]

    [c]
    Unvoiced plosives (p t k)
    If this is the first phoneme in the string, move the offset such that the overlap ends up about 15msec before the consonant.
    If there are other phonemes before this one, move the offset to where the previous one ended. Make sure you can't hear the previous one. Place the overlap about 15msec before the consonant.
    [​IMG]

    Voiced plosives and affricates (b d g ch jh)
    If this is the first phoneme in the string, move the offset such that the overlap ends up where the consonant begins.
    If there are other phonemes before this one, move the offset to where the previous one ended. Make sure you can't hear the previous one. Place the overlap where the consonant begins.
    [​IMG]

    Fricatives, nasals, and liquids (f v th dh s z sh zh hh m n ng l r)
    Move the offset to where the consonant begins. For 'r' in particular, you may want to refer to the glides section for help.
    [​IMG]

    Glides (y w)
    These consonants can be difficult to see on a normal waveform. By clicking on the S button, you can switch to spectrogram view, which gives you another way to visualize the audio. The bright areas are the loudest frequencies. These consonants show up as a change in frequencies over time.
    Move the offset to where the consonant begins, then place the overlap where it's consistent before the change. The preutterance will end up after the change.
    [​IMG]
    [​IMG]

    [v]
    By default, the overlap for these samples should be at a decently high amount. If it's absurdly small, moving it to around 50msec should be good.
    Move the initial offset so that the area between it and the overlap is at a consistent level.
    [​IMG]

    Second Phoneme

    For all cases, the preutterance should be placed where the first phoneme ends and second phoneme begins. This also covers the pink area, white area, and blue cutoff.

    [c]
    Stops (p b t d k g ch jh)
    There should be a small bit of silence or near silence just before the consonant. Move the pink where the silence begins, and the cutoff to where the silence ends. Yes, we're not including the consonant itself. That's because, in a UST, this note would be followed by another note that DOES have the consonant. This allows for a smooth transition without an awkward double consonant sound.
    [​IMG]

    Fricatives (f v th dh s z sh zh hh)
    Cover the entire consonant with pink until just before the end. Bring the cutoff to the same place, leaving a tiny gap. Without this gap, resamplers won't be able to render it. However, we don't want these consonants to be stretched.
    [​IMG]
    If there is silence after the consonant, have the white area be silence instead.
    [​IMG]

    Nasals, liquids and glides (m n ng l r y w)
    Move the pink to where the consonant starts being stable and consistent. Use the cutoff to remove where the consonant ends or fades out. These consonants are safe to stretch.
    [​IMG]

    [v]
    Move the pink to where the vowel starts being stable and consistent. Use the cutoff to remove where the vowel fades out. The white area will be the sustained part of the note, which ensures that it will sound good.
    [​IMG]

    [-]
    Cover everything with pink, such that everything in white is silence.
    [​IMG]

    And just like that, your voicebank is already done. Have fun, good luck! Feel free to ask any questions in the discussion thread.
    rmL, ㅤㅤㅤ, Dane and 8 others like this.