So I'm trying to recover some work from a compiled package. The .eof file is lost on a crashed hard drive.

 

I'm running the latest toolkit  v2.6.1.0

I'm able to extract the xml file. However, when I try to import the xml file, I get an error and this shows up the in the eof log:

642:  Processing line #630642:    Processing <chordTemplates> tag on line #630642:  Error reading chord name on line #632.  Aborting

 

 

Looking at the XML file on line ~632, and deleting chordtemplates until it errors out at a later step (missing chordid) it looks like its not accepting this:

  <chordTemplates>    <chordTemplate displayName="C#5/A" chordName="C#5/A" fret0="-1" fret1="-1" fret2="7" fret3="6" fret4="4" fret5="4" finger0="-1" finger1="-1" finger2="-1" finger3="-1" finger4="-1" finger5="-1">      <ChordId>0</ChordId>    </chordTemplate>  </chordTemplates>

But it does accept this:

  <chordTemplates>    <chordTemplate ChordId="0" displayName="C#5/A" chordName="C#5/A" fret0="-1" fret1="-1" fret2="7" fret3="6" fret4="4" fret5="4" finger0="-1" finger1="-1" finger2="-1" finger3="-1" finger4="-1" finger5="-1"/>  </chordTemplates>

So it doesn't like the nested chordid value in the chordtemplate. Is this a bug?

I think its Toolkit Issue, you should remove all 0,but better  just uncheck "Extract Song xml" at unpacker options (this one for official DLC or cdlc repacked without xml files included)

 

All CDLC should include xml files, use import package feature to quick project-like unpacking and filling dlc.xml template :)

Thanks. Unchecking that box worked. I guess it is labeled a bit counter-intuitively. Perhaps it should be renamed to "extract official dlc song xml"? or something.

@@bob64, I'll handle that.

I don't recall that any official XMLs use a sub-tag. Is this something the toolkit is going to continue to use when it recreates the XML file (if it's missing)?

I'll handle that issue, folks its just something that rubbishing xml