iminashi

Thanks for feedback.  Please try latest beta 1.3.1.1 and let me know results.  You should not have to create any folders or files.  CFSM should do all the work.

 

"the max 5 repair always seems to remove vocals no matter which options I select."    Thanks for finding and reporting this bug.  Should be fixed now.  Could you please recheck Max5 repair with an original unrepaired CDLC that has known vocals/showlights?

I tried it and it works, vocals are no longer removed.

There's a new permission problem in 1.3.1.0 I didn't get before:

[9.4.2017 10.15.37]:  - Repair failed ... Access to the path 'C:\Program Files (x86)\CustomsForgeSongManager\tmp' is denied.

Apropos of nothing, the max 5 repair always seems to remove vocals no matter which options I select.

2. The section names need to conform to a list of specific names. "Tapping" seems to be the only new section since RS1.

It is already supported by the toolkit:

                    SectionUINames.Add("fadein", "$[34276] Fade In [1]");
                    SectionUINames.Add("fadeout", "$[34277] Fade Out [1]");
                    SectionUINames.Add("buildup", "$[34278] Buildup [1]");
                    SectionUINames.Add("chorus", "$[34279] Chorus [1]");
                    SectionUINames.Add("hook", "$[34280] Hook [1]");
                    SectionUINames.Add("head", "$[34281] Head [1]");
                    SectionUINames.Add("bridge", "$[34282] Bridge [1]");
                    SectionUINames.Add("ambient", "$[34283] Ambient [1]");
                    SectionUINames.Add("breakdown", "$[34284] Breakdown [1]");
                    SectionUINames.Add("interlude", "$[34285] Interlude [1]");
                    SectionUINames.Add("intro", "$[34286] Intro [1]");
                    SectionUINames.Add("melody", "$[34287] Melody [1]");
                    SectionUINames.Add("modbridge", "$[34288] Modulated Bridge [1]");
                    SectionUINames.Add("modchorus", "$[34289] Modulated Chorus [1]");
                    SectionUINames.Add("modverse", "$[34290] Modulated Verse [1]");
                    SectionUINames.Add("outro", "$[34291] Outro [1]");
                    SectionUINames.Add("postbrdg", "$[34292] Post Bridge [1]");
                    SectionUINames.Add("postchorus", "$[34293] Post Chorus [1]");
                    SectionUINames.Add("postvs", "$[34294] Post Verse [1]");
                    SectionUINames.Add("prebrdg", "$[34295] Pre Bridge [1]");
                    SectionUINames.Add("prechorus", "$[34296] Pre Chorus [1]");
                    SectionUINames.Add("preverse", "$[34297] Pre Verse [1]");
                    SectionUINames.Add("riff", "$[34298] Riff [1]");
                    SectionUINames.Add("rifff", "$[34298] Riff [1]"); //incorrect name in some adverse cases
                    SectionUINames.Add("silence", "$[34299] Silence [1]");
                    SectionUINames.Add("shifts", "$[34308] Shifts [1]");
                    SectionUINames.Add("slides", "$[35872] Slides [1]");
                    SectionUINames.Add("solo", "$[34300] Solo [1]");
                    SectionUINames.Add("tapping", "$[34305] Tapping [1]");
                    SectionUINames.Add("taps", "$[34313] Taps [1]");
                    SectionUINames.Add("transition", "$[34301] Transition [1]");
                    SectionUINames.Add("vamp", "$[34302] Vamp [1]");
                    SectionUINames.Add("variation", "$[34303] Variation [1]");
                    SectionUINames.Add("verse", "$[34304] Verse [1]");
                    SectionUINames.Add("noguitar", "$[6091] No Guitar [1]");

That list does have a few names that don't belong there: "shifts", "slides" and "taps". In the game data there is also a generic "Phrase" that looks like it does belong to the same list of section names, but it's apparently not used in official content so forget that I mentioned it.  :) "Tapping" however is used.

3. In ODLC there is an empty phrase ("countoff", "default" etc) without an accompanying section at the beginning. What I meant was that there doesn't have to be a section called "intro" anywhere in the arrangement.

Chords that have been named " " in EOF to display without a name in the game are not handled properly by DDC 3.3.

displayName=" " chordName=" " 

Becomes:

chordName="displayName"

And the chord will have the name "m" in the game.

The update hasn't worked for me either in a long time. Now that I looked at it, it downloads the new version correctly (latest_test.zip is downloaded to the toolkit folder) and the files are extracted to the temp subfolder, but the files of the old version are not overwritten at all and the temp files are not deleted.

Turning off Windows Defender and running the Toolkit as administrator makes no difference.

Well " obviously has to be converted, and ' doesn't have to be. About the others, I don't know if it is absolutely necessary convert them. The characters & < > probably aren't used in ODLC by the way.

Non-alphanumeric characters that definitely do appear in lyrics in ODLC include:

- ' , . ! ? " _ ( )

. , are generally not used, but they do appear.

_ is used in the RS1 DLC Nickelback - "How You Remind Me" and is obviously a mistake.

( ) only appear in the copyright notice at the end of Jimi Hendrix - "Voodoo Child (Slight Return)".

To quote myself:

This is the default font for the lyrics: http://i.imgur.com/jdTyZdK.png

 

So the characters that can be used are:

 

!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_abcdefghijklmnopqrstuvwxyz{|}~¡¢¥¦§¨ª«°²³´¶·¸¹º»¼½¾¿ÀÁÂÄÅÆÇÈÉÊËÌÎÏÑÒÓÔÖØÙÚÛÜÞßàáâäåæçèéêëìíîïñòóôöøùúûüŒœŠšž„…€™␀★➨

That should be all of them, unless I've missed some. I tested them all in the game and, as expected, they work. To be able to use other extended characters, one would have to create a custom font.

Found a couple more.

ODLC Name: Ritchie Valens - La Bamba

Special Characters Used in Lyrics: í é

ODLC Name: Rupert Holmes - Escape (The Piña Colada Song)

Special Characters Used in Title: ñ

Special Characters Used in Lyrics: ñ

ODLC Name: U2 - Vertigo

Special Characters Used in Lyrics: ó á

ODLC Name: The White Stripes - Icky Thump

Special Characters Used in Lyrics: ñ

Completely forgot about "Gobbledigook". It uses: Þ ú æ í á Ó ó ö ð.

"A Tout Le Monde" uses À in the lyrics (but not in the song title).

The artist and title fields use a different font which allows for some more extended characters to be used compared to the lyrics font. (See this thread).

This is the default font for the lyrics: http://i.imgur.com/jdTyZdK.png

So the characters that can be used are:

!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_abcdefghijklmnopqrstuvwxyz{|}~¡¢¥¦§¨ª«°²³´¶·¸¹º»¼½¾¿ÀÁÂÄÅÆÇÈÉÊËÌÎÏÑÒÓÔÖØÙÚÛÜÞßàáâäåæçèéêëìíîïñòóôöøùúûüŒœŠšž„…€™␀★➨

From my quick testing it looks like the showlights are causing the crash.

As an aside, you might want to set those 24th fret notes as 'ignore' in order to get correct mastery in Remastered.

'I got this error adding and editing vocals on the template, for all the song that I try to make.'   It looks like there is a problem with the songs tuning (may not be defined properly).  Please check the tuning for each arrangement (highlight  an arrangement, press the 'Edit' button and check the tuning.  PM me your EOF project files if you can not fix this error.  May have nothing to do with vocals.

It looks like that error happens on all vocals and showlights arrangements when you click edit.

Updated to fix an error.

Uploaded a new version that has 8 more shapes.

I've divided it into sections and added comments so if you want to find a specific chordshape, it should be a bit easier now.

Testing would be appreciated. Let me know if you find a chord that gets a wrong/weird fingering or a common chord that doesn't get a fingering automatically.

(Updated 2021-03-31, contains 159 chordshapes)

Download the file (the download button is in the top right corner) and move it to the EOF folder, overwriting the old one.

A chord using the thumb (0) doesn't get applied correctly.

When asked to automatically apply fingerings, they are not applied to frethand-muted chords, though I think they probably should be. At least it would save me some time. 

Couldn't you do it like this?

Unpack the custom, edit the numbers in "DynamicVisualDensity" in the manifest file for the arrangement and then repack it.

I did some quick testing. One problem that's immediately obvious for not having an empty phrase at the beginning (doesn't matter if it's called "COUNT" or "default" or whatever) is that the first phrase will be invisible:

http://i.imgur.com/AhUNnG0.jpg

The END phrase controls where the note highway cuts off. The ODLC "Yasashiku Naritai" doesn't have it in the rhythm arrangement, and the note highway doesn't cut off as the song fades out. However, in the two tests that I did, it does cut off right at the end of the audio.

Also, EOF gives a warning if there is no intro section, but that is not needed either.

Yep, same thing with handshapes.

There is a FHP defined at the middle of the arpeggio. This will break it.

http://i.imgur.com/LnHC9IQ.png

Personally I don't see what would be the downside of that.

In "Painkiller" all those notes have the ignore status.

The notes are completely ignored all right, the crux of the problem is this:

Unless they are also marked as 'ignore', accuracy will not equal mastery.

Which was not the case before Remastered.

I've made a test case that has half notes <22nd fret and half notes >22nd fret, without the ignore status. Hitting all of the notes (though you only have to hit half of them) gives you 100% accuracy and 50% mastery. 

"Holy Wars... The Punishment Due" has notes on the 23rd and 24th frets and they all have the ignore status.