Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in. Login to AccountCreate an Account
Learn & Play Rocksmith!
Want to play the songs you love? Registration and the use of this website is 100% free.
The only thing you need is a legal copy of Rocksmith 2014 w/ a cable. Click here to buy it.
Having trouble logging in or registering? Please click "Support" below.
@RedLionhead I'm not able to reproduce the error. Plz delete the >My Documents>CFSM folder and subfolders and try again. If CFSM still throws the errror then plz send me a link to the complete >My Documents>CFSM>debug.log file. Thanks
@Milo6485 Odd, that version works for me. I got the same error message you got only if I try to run the application from inside the disk image. Give this one a try and let me know if you get it working. It is a new Rocksmith Tools for Mac AIO that was just released which includes the latest version of all tools.
"could someone point me to a tutorial?" CFSM has a genereal help (tutorial) button (see top tool strip) and then each of the features have additional help buttons (see feature menu strip) and tooltip popups. You just need to try exploring CFSM on your own a little. You can always look here and search for anything you are having trouble with. Look here for help with repairs.
"where is the cdlc back up folder?" >My Documents>CFSM>Backups, Quarantine, or Remastered folders. Open the >My Documents>debug.log file in any text editor. The log file will also tell you about why certain files where quarantined or any errors.
"can i change the volume of the songs?" Yes. CFSM>Song Manager>pick a song and Select the checkbox>Right Click>Edit Song Information>Song Editor>Song Info tab (change the song volume)>Save>Exit
"the tones?" Yes. CFSM>Song Manager>pick a song and Select the checkbox>Right Click>Edit Song Information>Song Editor>Tones tab>(select the tone to change)>ToneEditor>(change the tone info)>OK>Save>Exit
"why Win10 doesn't see me as the administrator for this app?" Because your are not a real admin and/or your AV does not like the app. Have a look here for how to check your admin status, and how to whitelist the app correctly in your AV.
@raynebc So in new version of EOF I see Song>Track>PART_REAL_GUITAR_BONUS and I see new Track>Rocksmith>Arrangement type> BOnus and Alternate.
I am a little confused. What is the purpose of PART_REAL_GUITAR_BONUS if any track seems like it can be specified as BOnus or Alternate using Track>Rocksmith>Arrangement type>? Seems like PART_REAL_GUITAR_BONUS is not needed.
Would it be possible to have EOF set the arrangement element values as follows according to how the new Track>Rocksmith>Arrangement type> BOnus and Alternate are used?
Default : Represent = 1, Bonus = 0
Alternate : Represent = 0, Bonus = 0
Bonus : Represent = 0, Bonus = 1
Toolkit can handle the rest.
EDIT: after second attempt the new EOF version actual seems to be working the way I had asked for/described above. I am still unclear as to the use of PART_REAL_GUITAR_BONUS firekorn explained the useage to me in PM. Now time for me to tweak the toolkit to accommodate the changes.
Looking at the toolkit code for section naming you will not find any special characters or punctuation used in ODLC. For consistency it may be best to apply this validation to phrase naming as well (so no underscores, hyphens, etc).
The problem was solved by going to the EOF's Ver. 1.8RC12 5-23-2017 - import/export preferences and disabling the "Abridged Rocksmith 2 export", re-saving the EOF projects (Customs) and then using the new XML files when repacking with the toolkit. Like raynebc suggested. I new it had to be a real simple thing causing the problem, but frustrating when a simple mis-setting drives you crazy for a few days. Luckily if someone else see's this problem show up here's the cure. I also installed the Toolkit 18.104.22.168 (rev 3d133c61), which is fantastic. Thanks for all the extra new features in it. All is good again.
Downgrading solves absolutely nothing. Provide your project files that caused the chord issue using the newest beta toolkit and newest version of EOF, or have your comments accepted for what they seem to be ... 'rage and banter' that require no further response from the developers.
Since the XML file names are arbitrary, I don't know if they can really be counted on. If you're willing to parse the file to validate it as being a lyric file, checking for the presence of a <vocals> tag as the first non-comment tag should be enough to tell for sure.
I actually thought of doing that too (parse the file to validate it as being a lyric file), and then realized there is only one of me.
Whats a UTF file, is it something normal EoF users can get?
By using the PART VOCALS_RS2.XML file you are already using a UTF file.
The vocals XML file is encoded in UTF-8 (Unicode) whereas the _EXT file is encoded in Windows-1252. You don't need to worry about that. Just know that the _EXT file does not work properly with the Toolkit.
ã is not in the default lyrics font so it will not work. Since it's written into the UTF lyrics file, it would seem that EOF's character filtering is not working correctly.
For the _EXT file the filtering does work properly; ã is filtered out.
The + characters for line breaks are not being written into the _EXT file.
So @raynebc seems EOF and toolkit are strictly correct because as @iminashi has pointed out, ã is not an ODLC vocal character list. We could add it to the vocals validation/filtering in EOF and toolkit and see if it works in the game.
EDIT: I have added ã to the latest toolkit beta list of approved lyric characters for testing.
Sheryl Crow Soak up the Sun is a LaceyB charted CDLC. Start with an original copy of the CDLC. You need to apply the Max5 Bug repair and check the box to Remove Bonus arrangements ... in addition to other repairs. If you check the CFSM logs you will see that this CDLC gets flagged as a Max5 and moved to (.max) backups if you don't select the repair Max5 options. Max5 Bug CDLC are known to crash the game.