I'm having difficulty charting a song with a capo and I'm hoping someone can help me figure this out.

 

The song is played with a capo on the 3rd fret, In EOF I've set the capo position to the third fret, and Rocksmith correctly has me install the capo during tuning. That's about as far as it works.

 

Chords appear correctly but are not listening for the right notes for open strings. For example, an Am-shaped chord like x02210 at the third fret appears in-game as xo443o (o being open strings) and should be listening for x35543. However, the game is listening for me to play x04430, as in playing the actual open strings WITHOUT the capo installed on the guitar.

 

I can remove the capo and play the song as indicated on the screen and it registers all the chords correctly but obviously sounds dreadful.

 

Chords without open strings work fine, and individual open string notes register correctly. Only chords with open strings fail to work properly.

 

I'm using the latest EOF and tooklit 2.6.0.0.

Maveth had problems with capo, but it was fixed, now you just set what fret become 0 with capo.As I understand: using capo on third fret turn powerchord G5 (3-5-5-(0)-(0)-(0)) to (0-5-5-(0)-(0)-(0))So try to put x35543 as x05540following this words..

anyways game shows

7ths fret, with no capo i can play it @ 7th and it works, OR i can play it at 9th and it worksopen string, with no capo fails if play open, works only if play the fret in capo.

 

 

 

 

BTW.. No Surprises by Radiohead are ok with capo on rhythm

 

 

 

Also uncheck property Track>Pro Guitar>Ignore TuningCapo

Edited April 22, 201411 yr by Alex360

If you didn't define the capo placement for the arrangement in the EOF project, the XML files it wrote will not be correct for using a capo. It's not as simple as just setting the capo value in the toolkit.

The _ 0 2 2 1 0 chord he mentioned (the first chord in the PART REAL_GUITAR_22 track, which has a capo on fret 3) is written in the XML as this:

  3...    ...                                                                  

If there is something specifically wrong with the XML, let me know what needs to change. Otherwise it wouldn't seem to be an issue with EOF. I believe this is how it was previously established that chords in capo arrangements needed to be written (open strings still are notated with a fret value of 0, otherwise all fret values have the capo position added to them so they indicate the guitar's native fret number instead of just the number of frets away from the capo).

I tried manually modifying the XML and changing all open strings from 0 to 3.

In game the chords work correctly, however the chord rendering is busted and instead of open strings it renders small note boxes

http://i.imgur.com/PSnqgSI.jpg?1

If there is official song with such chords and it works then it's not Rocksmith bug and it can be inspected for how it's supposed to look like. There was issue with open string sustains with capo but they fixed it a long time ago. Maybe @@Maveth can look at it.

DLCs like Matchbox Twenty's 3AM and Oasis' Wonderwall both have capo chords but I don't own them so I can't break them down to see how they work.

 

I opened the rs1compat file and looked at one song I knew needed a capo, Just Got To Be's Rhythm chart, but that doesn't use open strings in the chords. I'm not sure if there are any other songs in that file that use capos to look at.

 

BTW.. No Surprises by Radiohead are ok with capo on rhythm

 

 

This song doesn't work properly for me either.

 

Playing with the capo in place returns miss after miss, removing the capo and playing the open strings works without issue.

I purchased 3AM and have taken a look at the decompiled package and I may be on to something.

The XML files are the same, open strings are charted as 0 in the official files

 

However, when I look at the manifest/.json files I see something different:

 

From Ghost:

        "ChordTemplates": [          {            "ChordId": 0,            "ChordName": "G",            "Fingers": [              2,              1,              -1,              -1,              -1,              3            ],            "Frets": [              6,              5,              0,              0,              0,              6            ]          },

Notice that the open strings are marked with fret 0.

 

Now, from 3AM:

        "ChordTemplates": [          {            "ChordId": 0,            "ChordName": "G#",            "Fingers": [              2,              1,              -1,              -1,              3,              4            ],            "Frets": [              4,              3,              1,              1,              4,              4            ]          },

The song is played with a capo on 1, and in this case the open strings are marked with a fret number equal to the capo.

 

Unfortunately, I haven't had any luck yet in manually modifying the json file and recompiling, but I'll keep at it.

Just played No Surprises (Rhythm).  The capo works correctly during the intro when it's just single notes.

 

Then I played a section that uses open chords in riff repeater.  If the capo is on, I miss just about all the notes.  If the capo is off, I don't miss anything.

Yeah, I've had the same experience. Open strings work fine for single notes but just fall apart during chords.

 

I've scoured the rest of the files and I can't find any other references to chords or finger positions. Only place I've found them is in the manifests/ .json and songs/arr/ .xml files.

 

I've manually modified the .json file and recompiled the package but the arrangement plays the exact same. At this point I'm stuck again. Clearly there is a mismatch between how the toolkit is handling capos and how the official songs do, but I'm not quite sure where else to look.

Okay, I've noticed another discrepancy between the .json files.

 

The official has a rather large section before "ChordTemplates" simply named "Chords" and it's nearly 1000 lines long in this particular song. I won't post the whole thing due to the sheer size but it goes on like this:

        "Chords": {          "7": {            "0": [],            "1": []          },          "8": {            "0": [              16            ],            "1": [              16            ],            "7": [              16            ],            "13": [              16            ],            "18": [              16            ]          },          "9": {            "0": [              13,              16            ],            "1": [              13,              16            ],            "2": [              13,              16            ],            "3": [              13,              16            ],            "4": [              13,              16            ],            "5": [              13,              16            ],            "6": [              13,              16            ],            "7": [              13,              16            ],            "8": [              13,              16            ],            "9": [              13,              16            ],            "10": [              13,              16            ],            "11": [              13,              16            ],            "12": [              13,              16            ],            "13": [              13,              16            ],            "14": [              13,              16            ],            "15": [              13,              16            ],            "16": [              13,              16            ],            "17": [              13,              16            ],            "18": [              13,              16            ]          },-snip-

Now I'm guessing that this may have something to do with chords for different difficulty levels since it seems to repeat so many times but that's just a blind guess.

Interesting, I'll keep my fingers crossed that the toolkit developers can determine the necessary changes.

1st. Json file is not used in the playing mode only on menus and song info, so, any changes on json file will be affect only this sections, not during playing.

 

2nd. Chords and Techniques fields in json are not discovered by the toolkit team until this time and how we can generate this values for rs2024 cdlcs, but don't worry, it will be affect only chord and technique list on song information screen and any custom song have this sections.

 

3rd. Playing a song is affected only by .sng binary file that's generated by .xml file from EoF. Is simple, if xml have fret 0 on first string in a chord, it will write this value on the .sng file, so if you need different fret on a chord with capo, I believe that this frets need to be modified on xml (by the EoF). You can try to do the changes manually to test.

Aquilae tried that and listed the results in post 5 (http://customsforge.com/topic/5030-capo-chord-support/?do=findComment&comment=33673). The pitch detection worked in that case, but the game rendered the open notes as notes at the fret on which the capo is placed instead of as open strings. If this graphical issue can't be figured out, it's probably something people can live with since it's better than having the pitch detection not work. Let me know if I should go ahead and change EOF to write open notes in chords as notes played at the capo'd fret.

Good, so it should work. What needs to be done is to author same chord which appears in official song and then compare original and custom SNG, particularly chord template and hand shape data

Maybe the chordNotes and chord template have to be different to avoid the graphical issue, ie. one would define the open strings as fret 0 and the other defines them as the fret number at which the capo is placed?

Maybe the chordNotes and chord template have to be different to avoid the graphical issue, ie. one would define the open strings as fret 0 and the other defines them as the fret number at which the capo is placed?

I think so, chord template and hand shape adjusted to capo and chord notes with true fret values.

If people can test and make sure that both scores and displays correctly, with sample edited XML code to confirm the way it had to be done, I'll make that change in EOF.

What effect would the Update SNG checkbox have on recompiling packages? Would that throw out any changes I was making to the XML or JSON files? I haven't manually re-compiled any SNG files yet, but I'll keep the Update SNG checkbox clicked when repacking.

 

Experiment 1:

I took a package that had been decompiled where the open fret values were 0 in the XML. I modified those open string values to 3 in the XML and checked the .json file where fret values for open strings were still 0. Then I recompiled the package.

Result: Notes are registered correctly. Same as simply compiling the XML with open string values of 3, get weird boxes instead of strings.

 

Experiment 2: I manually modified the XML files and changed the open strings to equal the capo fret, I compiled the package from scratch (used source files), decompiled the package, modified the .json file so that open strings are played as fret 0, recompiled.

Result: Notes are registered correctly. Instead of open strings the game renders full note boxes at the third fret instead of the small graphic. Basically appears like the notes are simply placed right outside the fret hand position.

 

Experiment 3: Same as above, unchecked Update SNG checkbox.

Result: Same as above.

 

Question: Does the game have any setting in the files somewhere that indicates how long an open string graphic is? Is it possible that for some reason something is being set where the string has a length of of 0 or whatever instead of stretching the length of the hand position? If you look closely at the image posted earlier with the odd dots you will notice that it is actually the open string graphic, but it's just floating at the 3rd fret and aligned vertically.

 

1 and 2 had the same values in the XML & JSON but I got around to them differently and ended up with different results. I must be overlooking something in the way I'm modifying these packages in this order:

 

1: Toolkit -> Unpack, Extract Song XML.

2: Modify XML, JSON

3: Toolkit -> Packer, Update SNG

 

When I did the following I got different results:

 

1: Manually modify XML

2: Toolkit -> Generate Package from source materials

3: Toolkit -> Unpack, Extract Song XML

4: Modify JSON

5: Toolkit -> Packer, Update SNG

@@Aquilae, just chart song as normal and then modify xml parameter for capo (set it correctly), you will get full notes at capo place, but I got oasis wonderwall and there notes with capo created by same technique as we do now, but there was also events written to sng, maybe there something important.no, events are nothing..

So are you saying ignore the EOF setting for capo and export the XML and then modify the XML to enable the capo before compiling the package?

Well if it works with no problems that way - just use it instead of current.

I'll try to keep an eye on this issue, but if you guys find out a way to alter the XML so that capo chords with open strings work and show correctly, please make sure to get my attention because I don't want to miss improving the capo support.

3AM song rhythm, first chord:

 

METADATA

CapoFretId=1

 

ARRANGEMENT_SECTION Arrangements[7] Notes[0]

chordId=13

chordNotesId=1

 

CHORD_SECTION

Frets: 4 3 0 0 -1 -1

Fingers: 2 1 -1 -1 -1 -1

Notes: 44 48 51 56 -1 -1

Name: G#

CHORD_NOTES_SECTION NoteFlags: 0 0 4 4 0 0

 

NOTE_MASK_OPEN = 0x04

 

@@raynebc @@Aquilae can I have SNG for this chord produced by EOF+toolkit to confirm this? I think wrong MIDI values will be generated

 

BTW as far as we know only SNG data matters, JSON manifest is probably used for chord book

Take a look at these files, maybe they'll help.

 

In EOF I charted that G chord as 3200xx and set the capo to 1.

 

The first set of files I kept the XML as-is and used the SNG 2 XML feature in the toolkit.

http://rocksmith,silvite.com/4300.sng

http://rocksmith,silvite.com/4300.xml

 

In these last two files I modified the XML so that the open notes = the capo value, the way that correctly registers in game.

http://rocksmith,silvite.com/4311.sng

http://rocksmith,silvite.com/4311.xml