iminashi

 Periods "." are not valid in sortable fields.

They are actually. This can be easily fixed by filtering out the periods somewhere. Here, for example.

Represent is either 1 or 0. If it's 1 then it's the main arrangement for the path (rhythm, lead, bass) and its stats will be the ones displayed in the Learn a Song list and elsewhere.

The "represent" attribute would be used for that.

 

I was just thinking the other day that I knew there was something broken and weird with ignores, but I couldn't remember what.

 

So this issue aside, there is no problem with using ignores (in relation to them messing up scores or the percentage when completing the song)?

One thing what I find weird about ignores is that the game won't display "miss" but may display "late".

Hopefully all the bugs with ignore are fixed. The issue where any ignores you would cause wrong mastery was fixed a long time ago and a while back, I fixed another bug that had to do with calculating the total notes in a song, but I don't know if that one actually caused any problems in practice. In any case it should match ODLC now so any possible updates to the game shouldn't break things either.

Bump. This is still an issue.

EOF should definitely export 23rd and 24th fret notes with an ignore status automatically.

Uploaded a new version that fixes an issue of some characters not being included in the font because they were considered linguistically equivalent by the default string comparer, e.g. ー and 々.

Using two (or more) fonts in one song is possible, I've been planning on trying it out sometime.

As for overlapping vocal parts, I don't think that there's anything that can be done.

Just to make sure we're looking at the same thing, could you send me a project file to test with? There may be special circumstances for either problem.

Here, although there's nothing special in it.

https://drive.google.com/open?id=1wqEb5GnWk66v80yUrxkRX-o_5KNctDXt

At 02:13 in the lead arrangement there is a split double stop which causes the previous handshape to be extended to cover it.

*Added some RS2 export logic to allow a chord's handshape to extend over the single notes created from a repeated chord due to split or linknext status.

It doesn't make sense to extend the handshape with slides such as this:

The handshape is also incorrectly extended when an unrelated split chord follows a chord, e.g.:

While I'm talking with myself, here's a new custom build of the toolkit. The one before could produce poor quality cover images.

Uploaded a new version with a quick fix for incorrect character spacing when using "accurate inner rects".

When you save a font, in addition to the DDS file, a glyphs.xml file is also saved. This file is required, so don't delete it. If you rename the DDS file, you must rename this file too.

If you install a new font while the program is running, you must restart it in order to see it in the list.

Using the Font in the DLC Builder

The custom font can be added when selecting a vocals arrangement.

When adding a Japanese vocals arrangement, if the filename contains "jvocals" (or "jlyrics"), and the project folder contains a file called "lyrics.dds", the custom font will be applied automatically.

Using the Font in the Toolkit

Edit a vocals arrangement, click the "..." next to the arrangement type to open the window where you can set the path to the custom font.

Word Spacing

As far as I know, you cannot change the space between words. The space character in the custom font is only used if it is included in the lyric itself. For example, in this picture "exist as it is" is a single "word":

Colors

In the texture file red means white/light gray and blue means black. The lyrics seem to be monochrome so different colors cannot be used. You could invert the colors but in that case the blue karaoke highlighting of the current syllable would be on the shadow:

Unicode Combining Characters

You should avoid combining characters and use precomposed characters if possible. If you have a combining character like "o̺" and also have a regular "o" in the lyrics, the game seems to pick the regular o.

This can be made to work by making changes to the lyrics file itself and I will add support for it if there is need.

Requirements:

• Windows (or wine)
• .NET Framework

v1.2

Download at GitHub

@@Rockfirstlast

You can ignore them, it's just adjusting the gap between two handshapes to be at least a 32nd note, which I believe is the closest handshapes can be in ODLC.

Released v1.1 with a few minor changes.

I decided to make a cross platform version to see how hard it would be (It wasn't too bad). The UX is not as good as the Windows version, but the core functionality is the same.

It seems to me that there's only three heights the note tail can be in and the height for anything beyond a whole step bend is the same as a whole step bend.

There is a bend like this in "Sloe Gin" and the situation is the same.

It's clearly not split since it has that double stop panel thingy.

Well, I have a custom where this (bending up from whole step to 1.5 steps) wasn't working even before Remastered.

I think that's a limitation of the game itself.

You know any DLCs that have this situation?

No, don't know if I've come across any.

You could also use ignore to make it work:

As for frethand mutes that start a handshape, the Toolkit currently makes files that would look different if you were to play them in the non-Remastered RS2014. The first frethand muted chord would be displayed as a full chord whereas in Remastered it would be a repeat panel.

This could be easily changed though.

It's not utilized in RS1 either? I wonder what it was actually supposed to be then.

@@I)ark_Seph

Funny, when I try the program in a Ubuntu VM, the Configuration works, but Help crashes the program. (Edit: Because I forgot to install corefonts  :ph34r:)

An actual Mac version would be quite a bit of work I imagine.

In any case, I do plan on releasing the source code eventually™.

@@Yojimbo1989

Here it is.