Hi, folks.

I'll be using this thread to maintain the latest versions of EOF in one place. To start, download and extract EOF 1.8RC13:
https://ignition4.customsforge.com/eof

You can keep that zip file handy to avoid downloading it more than once. When I release a new hotfix, all you have to do is replace the files from the above zip file with the ones from the hotfix.  The latest hotfixes get posted in the same place:
https://ignition4.customsforge.com/eof

*If you use a non QWERTY US English keyboard layout, and keyboard controls/shortcuts aren't working for you, please make a post describing what keyboard shortcuts aren't working, and what the Info panel says the "CODE" and "ASCII" values are after you use each of the keyboard controls in question.

I used to make Mac releases, but Apple dropped support for 32 bit applications so the user base dwindled away and I can't port the entire application to 64 bit at this time.  The latest Mac build (2-7-2025) is here:
https://ignition4.customsforge.com/eof/download/17
Unless you have oggenc and LAME installed (these don't come with the Mac build for licensing reasons), you won't be able to have EOF automatically convert from MP3 to OGG when you create a new chart. If you have trouble getting those set up on your system, here is a package that should get them installed and usable by EOF:
http://www.t3-i.com/apps/eof/downloads/eof_utilities.pkg

Please provide any and all feedback, including bugs and feature requests. If possible, also please review the included documentation (manual, tutorials) and let me know if you find any room for improvement there. Eventually I plan to add a Rocksmith authoring section to the pro guitar tutorial, but the community's knowledge of the Rocksmith songs' makeup changes pretty quickly so it's hard to know when particular features are considered fully known. For any features that ARE fully known (like anchors), please feel free to remind me if they aren't incorporated into EOF yet, in case I missed any information being passed around on this forum or the Google group.

Note: If you are reporting a bug, please specify which hotfix (date) you're using. I release hotfixes on a somewhat random schedule, sometimes more than once per day, so the issue being reported may have been fixed in a release you haven't tried yet.

@raynebc  Tookit is using UTF-8 for vocals xml.  If EOF is using Windows-1252 do you think toolkit should have/needs a Windows-1252 to UTF-8 converter for vocals.xml.  Presently there is no conversion and I have not seen any issues.  What do you think?

@@SmellsLikeMonkey If you mean chords inside of handshape tags aren't automatically broken up into single notes like they would be in arpeggios, it's been that way for a while.  If you apply "split" status to the chords in the handshape, does that achieve the effect you want?

 

@@cozy1 The "normal" RS vocal file EOF is creating is encoded as UTF-8 (extended ASCII characters are written as multiple byte Unicode characters).  An additional "RS2_EXT.xml" vocal file gets written in Windows-1252 encoding (extended ASCII characters are written as a single byte each) in case the author has any use for it.  Each XML file indicates the correct encoding in the "xml" tag though, the file I/O libraries the toolkit uses might honor that information, but I don't know if that's the case.

@@raynebc the handshapes works perfectly, the only problem now is that when a "new" chord appears in the phrase, it will be show up. I can't control that. This is a playthrough video i made, look at the minute 0:29

 

 

As you can see, after the single note on the E string, the G7/F shows up with all the gems. I just want to see the repetition box. In other examples is more notorious and the display is more annoying. Is really common to hold a position and alternate single notes and strumming, like this:

 

e|--------------------------------|

B|--------------------------------|

G|-------------------------------|

D|---5------5------5-------5---|

A|---5------5------5-------5---|

E|---3-3-3-3-3-3-3-3-3-3----|

 

Now is impossible to do this without showing all the gems of the G5 chord

If you apply "hi dens" status to that G7/F, or extend a handshape phrase over that entire section I think you'll end up with what you're wanting.

If you apply "hi dens" status to that G7/F, or extend a handshape phrase over that entire section I think you'll end up with what you're wanting.

Now it works! thanks a lot! the handshape phrase was already extended, but i didn't know the function of the "hi dens" status. It forces the chord to show it only as an empty box right?

It forces the chord to be "high density" (a repeat line instead of a chord box, which is a feature of a "low density" chord).

Hi, folks.  The latest hotfix (4-17-2017) is in the first post.  Changes are as follows:
*Improved the "Repair grid snap" function to check the active track's notes and display by how many milliseconds the most out of grid snap note is before any alterations are performed, allowing a way to judge note sync.  This millisecond value is the number that would allow the function to repair the grid snap of all notes in the track.
*Improved the Information Panel to indicate when the track's tuning is not reflected (Track>Pro guitar>Ignore tuning/capo) for the selected chord's automatic name lookup.
*Changed the tuning handling to allow tunings more than 11 half steps from standard, for use with Rocksmith 2014.  Phase Shift, Rock Band 3, Rocksmith 2011 and Bandfuse aren't expected to support this so their exports will have the string tunings translated to fit within the allowed range of 0 to 11 half steps (ie. a tuning of 13 half steps above standard is instead exported as 1 half step), which should preserve chart functionality with those games.
*Changed RS exports to no longer automatically place an "intro" RS section, as it had been indicated this isn't required by Rocksmith 2014.
*Added "Tapping" to the list of usable Rocksmith section names.  This section is not a known supported section in Rocksmith 2011, so RS1 export will omit this section name wherever it is present.

If anybody tests in Rocksmith 2011 and finds that game does require an "intro" RS section, let me know.  I'd also be interested in knowing if the "noguitar" section should continue to be added automatically to the RS XML files if it isn't manually authored in the chart.

Is there a changelog that we can keep track of to see what's being changed each month?

EDIT: Scratch that, didn't surf through the forum enough

I'd also be interested in knowing if the "noguitar" section should continue to be added automatically to the RS XML files if it isn't manually authored in the chart.

 

In ODLC the END phrase is accompanied by a noguitar section if that's what you mean. Speaking of which, EOF should probably place the END phrase on the first beat of a bar so that DDC won't move it.

@@Chlipouni Any other such DDC requirements EOF should take into consideration regarding the END phrase or the noguitar section? Should they also be placed at the same timestamp?

For DDC, a phrase or a section must start on the first beat of a measure. There are no other requirements.

I'm using this new version right now and i have this issue (it's the first time and i don't know how to solve this at the moment). When i select a note clicking on  the scroll wheel button, nothing happens. I need to transcribe manually a song.

And also when i launch eof: 

Warning: The abridged RS2 file export prference is enabled. XML files are only supported in Rocksmith Custom Song Toolkit 2.8.2.0. Ensure you have a new enough toolkit or disable this option in File<Preferences>Import/Export

Thank you for your help. Cheers!

 

EDIT

 

actually i'm using an old version and is working pretty good but i would like to solve that issue anyway. Thank you.

Middle click should bring the the edit pro guitar note dialog if you're clicking on a note in a pro guitar/bass track. Let me know if that's not working for you.

 

About the warning, you can click the "Don't warn again" option if you are certain you have updated to version 2.8.2.0 or newer of the toolkit. Otherwise you should disable the "Abridged Rocksmith 2 export" option in File>Preferences>Import/Export.

Middle click should bring the the edit pro guitar note dialog if you're clicking on a note in a pro guitar/bass track. Let me know if that's not working for you.

 

About the warning, you can click the "Don't warn again" option if you are certain you have updated to version 2.8.2.0 or newer of the toolkit. Otherwise you should disable the "Abridged Rocksmith 2 export" option in File>Preferences>Import/Export.

 

Exactly, that's not working (pro guitar note dialog display doesn't appear) eof1.8RC12+hotfix 17/04 but the middle wheel seems  responsive to make a  sustain.

I'm trying to redownload again --> same bug

Well, at the moment i'm happy to complete the custom with the old one eof. Eventually i could wait for the new one or maybe i don't know, is possible to share an eof folder (without projects) so i can test it? It's ok, thanks for your help. Cheers! ^_^

The middle button click in that hotfix works for me, did it work for you in previous releases of EOF? Since the middle click logic hasn't changed anytime recently, I wonder if it's a problem with the mouse itself. Please verify your mouse is working by middle clicking in another program (ie. Firefox, Chrome or Internet Explorer, each of which should turn the mouse pointer into a scroll function).

 

Middle click is not required to author, you can get to the same dialog by selecting it (left click) and pressing the N key.

The mouse is perfectly working (scroll function included).

The middle button worked very well with all the previous release. Strange fact: Also using N key on the new eof doesn't work. 

Make sure you're in a pro guitar/bass track (the name of the track will include "REAL_GUITAR" or "REAL_BASS"), otherwise this is expected behavior.

Make sure you're in a pro guitar/bass track (the name of the track will include "REAL_GUITAR" or "REAL_BASS"), otherwise this is expected behavior.

 

 

So, apparently i was sleeping. :lol: Thank you so much!

@@raynebc,

 

  I have just tried the new "Allow RS2 extend ASCII lyrics" preference, and it works fine.

  As a minor improvement, it would be nice to suppress the warning message about non ASCII characters when this preference is activated ...

 

Thank you

I could probably suppress that warning if RS2 is the only format being exported.  Does anybody know if RS1 supported extended ASCII?

In my memory I did create french accentued lyrics in RS1 but it was a long time ago (in a galaxy far far away) So I can't assure you that it is working.

Anyway who is using RS1 anymore ? I think if something broke the user will tell you that it's not working anymore.

Does anybody know if RS1 supported extended ASCII?

 

It does, "Gobbledigook" and "Icky Thumb" use extended characters in RS1.

Hi raynebc,

 

  What is the exact purpose of the "PART VOCALS_RS2_EXT.xml" file ?

 

  For me, only the "PART VOCALS_RS2.xml" works fine with accented characters (RS2014, RST and text editors).

  When I try to use the "_EXT" file, accented characters are not displayed in the game.

 

Thanks

As per the previous changelog it's just the RS2 lyric file encoded in Win-1252. It's not obvious if this is useful for anything besides importing back into EOF (EOF can't import Unicode lyrics but it can import extended ASCII).

  For each character it displays in the game the following informations :

  - ASCII code

  - the character itself

  - [ND] tag if the character isn't displayed in the game (with no crash)

  - [NV] tag if the character is special and hasn't a visible symbol

 

 

I am interested to know how you built the .psarc with these characters in?

 

It seems to me that the toolkit is filtering out some characters during the build process.  Was the toolkit behaviour amemded after your testing, using the results?

 

 

Thanks :D