I constantly get this error. What does it mean and how can I fix it?

 

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

@@Kiscsak98,

 

I've been having the same problem.  If you've got tone changes in your song, go into EoF and name the tones whatever the name of the tone you are going to use, i.e. Metallica-Distortion.  Or change the name of the tone in RS Toolkit to match the tone name in EoF.  If none of that works, with your songs open in EoF, delete all your .xml files for that song, then save your song in EoF.  Load the new arrangements (.xmls) that were just saved in EoF back into RS Toolkit and create your song.  I've had this same problem for about a week and this has always fixed it.  Hope this helps.  Good luck.

Are you using custom tone or standard fuzz tone?  If you post link to arrangement xml, audio, and tone files I will have a look and see if there is a bug in the toolkit.

Recently, whatever tone name you are using in EoF must match the tone name in RS Toolkit or you get that error.  RS Toolkit also saves a second copy of all the .xmls, not sure why.  The only way I've been able to correct it is as stated above.

"RS Toolkit also saves a second copy of all the .xmls, not sure why." 

 

We were testing saving user modifications to the XML file in the toolkit.  The new feature allows you to save last minute changes to the song information from the toolkit so that you do not have to reauthor in EOF.  The feature is fully active now an the secondary XML copy is no longer created.

 

"whatever tone name you are using in EoF must match the tone name in RS Toolkit" 

 

I am not an EOF expert.   If you are referring to the feature in EOF toolbar, Track, Rocksmith, Tone change, add, Tone key name then we probably need to ask @raynebc fpr guidance as to what the proper "Tone key names" are that are compatible with Rocksmith.   I have never used this feature in EOF.

I don't know of any specific requirements for tone names in Rocksmith, although it wouldn't surprise me if there had to be no spaces or special characters.

So is the tone naming tool function in EOF similar to phrases and sections where the user is just defining a point in time in the arrangement to apply a specific tone?  If so then the user still needs to define these tones in toolkit.

 

Use the PackageCreator, Edit Tone feature in the toolkit to define the tones that were named in EOF before clicking Generate should solve the problems.

Yes, the user has to define the tones themselves in the toolkit.

I used to be able to name the tones whatever I wanted in EoF, i.e. clean, distortion, a, b, c.  As long as you didn't give the tones numbers for names, you were fine.  Then in Toolkit, you just subbed in your pre-made tone into the slot, names didn't need to match.  Now, I get the same error as above (undefined tone name: "tone you named in EoF") if they are not named exactly the same.

 

Not that big of a deal, just adds a few extra steps, but will probably stump a bunch of people when they get that error in Toolkit.

 

Thanks for all the work you guys put in, much appreciated.

Bookmarked, gonna add tracking issue at GH.

@manchot66  Please post a link to an EOF arrangement XML file that you are having this problem with. 

@@Alex360 I found section of code that could generate this error.  I will fix when user posts link to EOF xml file to make sure I have the right area of code to apply fix.

All you need to do is  create empty track(or place there some notes) with tone changes, then apply steps above, I think it's general issue, not single file related

@@cozy1, I have it already, I can attach one of my, let's say 46&2 from tool, lead part:
https://copy.com/tkZuXhE9dkXyyxGx?download=1

@@cozy1, there is a lot of tone changes and full tones set, have you tried it to reproduce issue? C:

@@Kiscsak98, can I have same error screenshoot again from you using last build?

Here's an .xml that's giving the error.  Let me know if you need anything else.  Thanks, guys.

@@Kiscsak98, can I have same error screenshoot again from you using last build?

@@Alex360 Here it is. Same error, latest build

 

http://i.imgur.com/5OTHUex.png

@@Kiscsak98, great! now I know it's doesn't work(force english at exeptions), I think it'll be fixed soon so one issue will gone, 99 left xD

I really need to list all toolkit features down...

Should be fixed in the latest beta build if you want to give it a try.  Don't forget you still need to fully define these custom tones that you insert in EOF.  Otherwise it is not going to sound very good.  Use the toolkit "Edit" Tones to do this..

Will try beta. 

 

Thanks@@Alex360 & @@cozy1

We aim to please! :) Remember if we break it, we may fix it eventually.