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.

I'm not sure how helpful it would be overall for EOF to write a separate file of preferences/instructions to be picked up by the toolkit. I'm not sure I understand all of your examples though.

@@raynebc

 

Basically adding another line next to "Bonus arrangement", for an "Alternate arrangement". As for Bass Picked, you can just make it a check/uncheck option when your in a Bass track. It will be greyed out if your in a guitar track.

How is an arrangement defined as being an alternate arrangement in the XML file? Bonus arrangements have the bonusArr attribute, but there's not such an obvious one for alternate arrangements.

If memory serves and not being in fromt of my computer, there is no alternate attribute in XML. For my MacGyver CDLC I had “alternate lead” show up in-game simply due to the fact that I labelled two arrangements in the toolkit as lead without calling them bonus arrangements.

 

Probably doesn’t help anything here. But in case it did I thought i’d Share. If ever you need me to check that custom I can do so.

 

I think my metronome arrangements were labeled as alternate... prior to Remastered Max5 requirement.

 

Cheers

Alt arrangement are determined by their order in which they are in the toolkit, i don't think there's any attribute outside of that so that's quite impossible to manage from EOF as far as i'm aware.

The "represent" attribute would be used for that.

But the represent attribute set by EOF in the xml is ignored by the toolkit as far as i'm aware. You can try it yourself, set 2 lead path, the one at the top is the bonus arrangement the other is not a bonus arrangement, you'll end up with a bonus and an alt but no default arrangement while the standard arrangement have the represent tag set to 1.

According to this (at least based on the comments, without studying it very closely):

https://github.com/rscustom/rocksmith-custom-song-toolkit/blob/master/RocksmithTookitGUI/DLCPackageCreator/DLCPackageCreator.cs#L626

 

If the "represent" and "bonus" attributes are both 0, it's considered an alternate arrangement. I can make that change in EOF (that if the author specifies the arrangement is alternate, both of those attributes are written as 0) if the toolkit developers will confirm that the toolkit does or would be made to honor that. Then I'd just need to know what information EOF needs to get from the author (ie. does a represent attribute value of 5 mean it is alternate arrangement number 5)?

Represent is either 1 or 0. If it's 1 then it's the main arrangement for the path (rhythm, lead, bass) and its stats will be the ones displayed in the Learn a Song list and elsewhere.

@@cozy1 If EOF writes the arrangementProperties tag of an arrangement XML file so that the represent and bonusArr attributes are both zero, will the toolkit consider it as an alternate arrangement or would the user still have to configure that in the toolkit?

@@raynebc I thought you've guys talked about eof-toolkit xml thing when you have created this lightweight xml support? I'm sure that toolkit is able to read any propeties you'l fed it but sng\lib and gui part are separate so we "patch" xml files with tone names for autotone switch could work and such

I just need to know whether if EOF defines the properties as described, the toolkit will reflect that the imported arrangement is an alternate arrangement. If that's the case, I'll make the changes in EOF so the chart author can specify that a track is an alternate arrangement.

As far as i am aware, the toolkit will alter the represent argument depending on the position/order in the arrangement list.

@@raynebc This section of the code seems to address what you are asking about:  https://github.com/rscustom/rocksmith-custom-song-toolkit/blob/78afe484d5451687c8ee33fcd0af5f4f7cc0636c/RocksmithToolkitLib/DLCPackage/DLCPackageCreator.cs#L550

Short answer:  Yes the toolkit considers it an alternate arrangement when both represent and bonus are set to "0".  :)

 

OK. I'll need to figure out how to present this in EOF, probably something like a submenu where you pick "Normal", "Bonus" or "Alternate". I'm not sure what to call such a submenu though, since there's already an "Arrangement type" one to specify bass, rhythm, etc. Should that latter submenu be renamed to something like "Arrangement path" or something similar?

@@raynebc The toolkit use arrangements as you have described and then each arrangement can be designate as a  'Bonus Arrangement' via a user checkbox.  If you keep the EOF arrangement structure the way it is now and add  new bonus arrangements, .e.g Lead_Bonus_RS2.xml, Bass_Bonus_RS2.xml, etc.  The toolkit will decode the xml based on the 'arrangementProperties' element 'bonusArr=' and 'represents=' condition.

Instead of having every combination of normal/bonus/alternate and combo/rhythm/lead/bass, I'll probably just add the normal/bonus/alternate as a "sub type" in a lower half of the arrangement type menu.

@@cozy1 Except that it's possible in the actual toolkit to get no default arrangement and only a alt and a bonus one for a given path even though the represent is set to 1 for what will become the alt arrangement.

 

Just do the following :

 

Bonus is the first arrangement and the second arrangement should be the default as he have the represent set to 1 but in game, you end up with no default :

 

But only a bonus and an alt :

@firekorn  Plz give me link to that CDLC.  I would like to see what you did and how it looks in the other toolkit screens.  Thks

RS1 XML doesn't have a bonusArr attribute, but it has a "represent" attribute. I can't remember if that game had alternate arrangements, but if it does, will the toolkit classify an RS1 arrangement with a represent value of zero as an alternate arrangement?

@@raynebc "will the toolkit classify an RS1 arrangement with a represent value of zero as an alternate arrangement?"

Yes

Sounds good, I'll update RS1 export too. If somebody RS1 exports a track that is marked as a bonus arrangement, I guess I should make it export as an alternate track since it's not the representative track.

@@raynebc,

 

  I don't remember if "Import/Lyrics" works with accented characters.

 

  If my input lyrics file contains "é", it is not imported correctly in EOF. If I directly type it in EOF, it is correctly displayed.

 

  Do I need to use a special encoding setting for my input file ?

 

Thanks

I think it's most likely to work if you use Windows-1252 (extended ASCII) encoding instead of Unicode encoding for the file before importing it into EOF. If that's not the case, please send me the lyric file in question for testing.

Hi, folks. The latest hotfix (9-28-2018) is in the first post. Changes are as follows:

*Updated copy/paste, clone to/from and auto adjust logic to preserve disjointed status.

*Updated the save logic to not warn about gems in the same disjointed chord being too close together to enforce the minimum note distance.

*Added a "Save separate Guitar Hero files" export preference that will specify whether ghwt_drum.array.txt, notes_gh3.mid and note_ghwt.mid are created when the project is saved.

*Corrected an issue where the new MIDI import logic (for handling disjointed chords) could cause some notes to incorrectly detected as auto HOPO notes until fixup logic redetects that they are not auto HOPOs.

*Updated MIDI import to treat "PART GUITAR COOP GHL" and "PART RHYTHM GHL" as GHL tracks.

*Updated MIDI import to read the GHL track difficulty tags ("diff_bassghl" and "diff_guitarghl").

*Updated MIDI export to write the GHL track difficulty tags even when PART RHYTHM or PART GUITAR COOP are renamed to define the GHL guitar or bass track.

*Added a message that is displayed at the end of MIDI/Feedback import if the "Imports drop mid beat tempos" preference is enabled and leads to any beats being removed during the import, which could affect the grid snapness of notes.

*Changed RS2 export to automatically add ignore status to any gem that uses a fret number higher than 22, to ensure the game correctly handles this note, which it would otherwise not score but would count against the player's mastery percentage for the song.

*Changed the border color for selected lyrics' note rectangles to red instead of white to make them more visible.

*Fixed a bug with the recent Feedback import logic (to process toggle HOPO and slider markers at the end of each track difficulty's import) that could cause notes/chords with W3 to be deleted from charts with multiple difficulties.

*Updated RS2 export to only write the first 32 bend points for each note/chordnote, since having more of them would cause the game to crash. The warning given during save was updated to reflect that this action is taken.

*Added options to the "Track>Rocksmith>Arrangement type" menu to specify whether the arrangement is the normal one (whose play stats are the one listed in learn a song and other places), a bonus arrangement or an alternate arrangement, for use in Rocksmith 2014. RS1 export will write any track that is marked as a bonus or alternate arrangement as an alternate arrangement since RS1 doesn't support bonus arrangements.

*Added a "Track>Rocksmith>Picked bass" function that will specify that exported bass arrangements for RS1 and RS2 are picked bass instead of fingered bass.