• If you do not recieve your confirmation email within a few hours, please email haloutau@gmail.com with your username for manual validation. Your account should be activated within 24 hours.
    You may also reach out via any other listed contact on Admin Halo's about page: https://utaforum.net/members/halo.194/#about
Resource icon

How to Create Base OTOs (Part 3)

FelineWasteland

Feral Catboy
Defender of Defoko
FelineWasteland submitted a new resource:

How to Create Base OTOs (Part 3) - Comprehensive guide on creating base otos. This section covers creating them w/ regular expressions.

A comprehensive guide on writing base configuration files (otos) for Classic UTAU and OpenUTAU. Also applicable to DIY synths that use the same configuration parameters. This resource assumes at least a basic knowledge of UTAU.

This tutorial is crossposted from my website. Part 1 covers making bases from scratch and...

Read more about this resource...
 

Kiyoteru

UtaForum power user
Supporter
Defender of Defoko
Excellent resource! Just a couple notes I want to add.

For newlines, there's two standards: CRLF (Windows) and LF (Unix). These correspond to \r\n and \n respectively, so using \r only doesn't really exist.

For pattern matching sequences of longer consonants and vowels, I prefer specifying the exact numerical count of characters over wildcard extensions. For example, if I'm expecting 1-2 characters for a consonant and exactly 1 character for a vowel, I'll use this pattern.

Code:
(.{1,2})(.)
 
Last edited:

FelineWasteland

Feral Catboy
Defender of Defoko
Thread starter
Excellent resource! Just a couple notes I want to add.

For newlines, there's two standards: CRLF (Windows) and LF (Unix). These correspond to \r\n and \n respectively.

For pattern matching sequences of longer consonants and vowels, I prefer specifying the exact numerical count of characters over wildcard extensions. For example, if I'm expecting 1-2 characters for a consonant and exactly 1 character for a vowel, I'll use this pattern.

Code:
(.{1,2})(.)

I'll add a note about the Unix standard; I wasn't aware there were differences.

Also, specifying exact counts is probably a more intuitive way to handle it; I will likely update that as well then. Thanks for the suggestions!
 
  • Like
Reactions: Row 4

Similar threads