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.

Hi, folks.  The latest hotfix (5-18-2016) is in the first post.  Changes are as follows:
*Improved GP import so that if the chosen track has notes in both voices, EOF asks which of the voices to import.
*Fixed a bug where fret hand position warnings may be incorrectly given if tech view was in effect during save or when the "Check fret hand positions" function is used.
*Adds functions to select/deselect notes based on whether or not they are highlighted.
*Added a Note>Highlight menu with functions to apply or remove highlighting to selected notes.  The functions to transpose selected notes have been moved into a Note>Transpose menu.  The H menu hotkey has been re-assigned to the Highlight menu and O has been assigned to the HOPO menu.

For some reason with the latest hotfix, when I import a GoPlayAlong xml (which I know works as I already have a working copy) no notes show up in any of the difficulty tabs. 

 

I haven't changed my routine to starting a new project, other then I am on Windows 10 now. :/

 

Here's a pastebin of my log if that helps. http://pastebin.com/bqikAvMV

Thanks, I've fixed this.

 

Hi, folks.  The latest hotfix (5-19-2016) is in the first post.  This release fixes a bug with the previous hotfix where GP files with only one populated voice wouldn't import correctly.

Thanks, I've fixed this.

 

Hi, folks.  The latest hotfix (5-19-2016) is in the first post.  This release fixes a bug with the previous hotfix where GP files with only one populated voice wouldn't import correctly.

Fast fixing fingers! Works now :D

 

This GP file should cover a few examples of ways of I've seen things authored in GP that end up being weird in game.

Regarding the first example (vibrato on a bent note), are you wanting it to import the linked note as a pre-bent note that has vibrato?

 

@@albatross213 Any thoughts?

@@raynebc - Sorry, I missed the first time you asked. I'd say in nearly all cases I've seen the pre-bend and hold is intended for the part of the note with vibrato, so that sounds right.

 

Another thing I noticed with GP imports is that tremolo notes don't import with sustain if they're under 1/4 note long (which sometimes happens in songs with lower BPMs). Would it be possible to make it so notes marked with tremolo always import with sustain?

I was testing that example out and found that if I formally author the tie note as a pre-bend and release in Guitar Pro, it imports nicely in EOF so that the bend is held at the end of the first note and is released near the end of the tie note. Getting EOF to automatically assume this would be complex because it counters the logic that separates tied notes into linked notes when there are technique changes between the two. For now I think it's going to be best to leave it as is and have the author put in the pre-bend in Guitar Pro (or make the minor changes in EOF).

 

Another thing I noticed with GP imports is that tremolo notes don't import with sustain if they're under 1/4 note long

I've fixed this and another tremolo import issue that was related to the recent change allowing either/both instrument voices to be imported from Guitar Pro files.

Hi, folks.  The latest hotfix (5-25-2016) is in the first post.  Changes are as follows:
*Fixed a GP import bug where tremolo technique wouldn't import correctly.
*Improved GP import to not remove the sustain from tremolo notes if the preference for GP import to truncate short notes or chords is enabled.
*Fixed a bug in RS export where a chord with chordify AND crazy AND "hi dens" statuses would export as low density instead of the expected high density.
*Fixed a crash that could occur if Rocksmith or Guitar Pro imports fail when no project is open.
*Fixed a bug where RS import would fail when parsing a 6 string chord.

Hi, folks.  The latest hotfix (5-27-2016) is in the first post.  This release improves GP import so that if the selected track is a percussion track, EOF offers to import it into one or both drum tracks.

Hi, folks.  The latest hotfix (5-27-2016) is in the first post.  This release improves GP import so that if the selected track is a percussion track, EOF offers to import it into one or both drum tracks.

Awesome work dude :)

Hi, folks.  The latest hotfix (5-27-2016) is in the first post.  This release improves GP import so that if the selected track is a percussion track, EOF offers to import it into one or both drum tracks.

Awesome work dude :)

 

Whoops , double post due to excitement

I have a problem with eof when I open it you see only a white screen, I have tried to delete the folder and extract all again but always the same problem, what happened?

 

http://s33.postimg.org/93j93nu4f/Cattura.png

If you've been able to use EOF on this computer before:  What was the last version of EOF you used without this issue?  Any major changes to your computer since then?  Any changes after rebooting the computer?  Does RC11 without any hotfixes work?

 

If this is the first time you've used EOF on this computer:  What OS are you using?  Does any antivirus software on your computer indicate that it's doing anything like quarantining EOF or any of its files, running it in a sandbox, or anything else?

Sorry for the inconvenience has now returned to work after I uninstalled avg tune up that had probably changed something in my system.

Is EOF able to use usb audio cards? I can make it to work only with integrated, any advice?

EOF should use whatever is your default audio playback device at the time it is launched.  I've heard from people that they have used USB headphones with EOF without issue.

@@raynebc, I found what become a problem with my asus usb card, it seems EOF doesn't like gx option which enable eax support(emulated or not idk) so it won't play audio at all, if i disable it and change mode, than relaunch EOF it works like a charm, any thoughts how it could be fixed inn EOF's code? for now I'll limit usage of gx mode, thx :)

That's mentioned in EOF's "common problems" portion of the manual and is a limitation of Allegro 4 and or 5.  There's not anything I can do about it unfortunately.

Hi, folks. The latest hotfix (6-19-2016) is in the first post. Changes are as follows:

*Fixed a bug with GPA import where section/phrase markers (depending on user preferences) weren't imported.

*Added a "eof_db_import_suppress_5nc_conversion" setting (which can be set to 1 by manually editing eof.cfg while EOF is not running) that will prevent 5 note chords from being converted to open notes during Feedback import.

*Makes proposed changes to the chordify mechanism. Now, when single notes (those that require sustain) are exported for the affected chord, the related chord tag is exported with linknext status and the beginning of the single notes are moved ahead by 1ms.

@@raynebc, is it important to warn user aout this http://imgur.com/G66rvzn even it have no section\phrase at this arrangement but it its st another one? or it's just a bug?

 

just place tailed note sowhere, add PS marker across that note at another arrangement and you'll reproduce it, using recent and before eof's

I think it's just a bug by not taking into account specific section for single track.

Or could it be unsnapped notes and a tail is going 1 or 2 ms into the next section?

Having an example project file will help.  Phrases and sections can be specific to one track, but only if you designate them to be this way.  Otherwise I can only assume the note reaches/exceeds the phrase/section's position.

here https://mega.nz/#!2cwhCJbJ!SWn3llnLSvsZ20mmRqzCW42o3UHZ4VAma96mVYmXHXk

Thanks, I've fixed a bug with that warning as it should not have been triggered by that note. It is still triggered by the chord at measure 126 in the Rhythm track though (crosses an outro section and phrase change) and this seems to be correct.