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.

 

Which menu functions are not available/working for the bonus track?

 

@@firekorn

Did you still find this to be the case?

@@raynebc Thanks for the release! To make DMGs, open up Disk Utility and hit Create New Image. Select the EOF.app and save it somewhere. Once its done, drag the EOF.app into the image window. Also, it will be easier and convenient if you make a little alias of the Applications folder, drag it into the image window so people can simply install EOF.app just by dragging it into the Applications.

 

Few bugs that I report. It doesn't save anything when you try to set your preferences. You have to do it every time you open EOF.

 

Here is what happens when I try to set the display size.

 

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

 

Then here is the second error that is pulled off, and when hitting "OK", it goes back to the default display size.

 

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

 

Anyways, thanks for the release! :D

@@raynebc Must have been in an older released that it was case.

 

I'll be sure to give the mac version a test ride this weekend :)

Here's a new Mac build:

http://ignition.customsforge.com/eof/download/155

 

It should fix the issue with preferences not saving, and also as a side effect setting the display size works.  There's possibly more stuff that's broken in Mac (let me know what you find) due to how differently it runs under the hood from Windows or even Linux.

@@raynebc Well, that fixed both of those problems. I should have told you this before releasing 3-15, but I'm in a rush right now.

 

When you set the path of song folder of where you want to save your CDLCs, it doesn't set it at all, instead it just makes it in the directory where EOF.app is installed no matter where if you set your song folder path or not. That's all I guess. Can't really test out more things since I got to get up early and work til 4 tomorrow.

@@I)ark_Seph I can't reproduce that issue.  When I open a clean copy of EOF, the default song folder is within the application bundle.  I set it to a folder on my desktop, re-opened EOF, created a new song with the "Create new folder" option and that song folder was created within the folder on my desktop.

 

In the same EOF instance, I changed the song folder to be back in the EOF application bundle, and without closing EOF I created a new chart with the "Create new folder" option and it created the folder within the application bundle as expected.

 

The starting point of the folder browse dialog that is presented when you set your song folder reverts to the default path in the application bundle, seemingly every time it is launched.  It does not reflect the previously defined song folder.  The dialog start folder isn't ideal, but to me the feature seems to be working otherwise.  Please check whether the song folder is honored when you create a new project, and whether this dialog behavior was just misleading you.

@@raynebc, any input on why when I change spectrogram parameters and show\hide it It's still the same? even redraw didn't help
I think handler is missing for this case? I'm changing just note range(which could be a slider( but I need to go above spectrum to have nice wrapp t osee higs and lows at crossover ;) )

I did some quick testing and it seems to update any time I change any of the spectrogram configuration parameters. Just make sure the checkbox next to "note range" is checked or it will probably not redraw the graph to reflect the given range of pitches.

@@raynebc, missed that little bastard somehow >__
thanks It works  as intended, just noticed yesterday it didn't saved my changes so I guessed it was somehow related to cfg issues that was recently

The config file issues were only with the Mac platform. If you can reproduce a problem with the current Win/Mac binary or current Git repository version on any platform, let me know.

@@I)ark_Seph @@firekorn Did either of you happen to reach a conclusion about whether the new Mac build works well enough to replace the nearly 11 month old Mac build on the Ignition EOF page?

@@raynebc sorry I haven't been able to mess with it for a few days. Tomorrow I'm off work so I can try it out.

@@raynebc I gotten to fiddeling around with (3-15-2017). Everything works like its expected. Preferences, display set, import/export, and everything else from the past hotfixes on windows. Even though you updated EOF ignition page for adding the latest build on mac, you didn't update the forum post about the new build. Thanks and time for release! :D

I wanted to make sure it was deemed working. The new Mac build is officially in the first post now.

Hi raynebc,

 

  Is there a way to import a Rocksmith Lyric file in EOF ?

 

  I am working on existing CDLCs to improve their quality and I would like to modify the existing lyrics.

 

Thanks

File>Import>Lyric ought to do it.

File>Import>Lyric ought to do it.

 

 It seems that EOF doesn't support accented characters anymore ?

 I'm trying to define lyrics in french language and all accented characters are not saved in the result file.

 

 If I add them by myself in the XML file they are displayed correctly in the game.

 

 Any idea ?

Extended ASCII (ie. accented) characters are omitted from exported XML files, to ensure game stability.  It's been this way for a while now (just over a year).  In order to change this, I'd want assurances that multiple developers tested and confirmed extended ASCII is allowed in lyrics.

I have never had any issues with ASCII extended characters (at least for those commonly used in the French language).

A few years ago, I made several french CDLCs and they continue to work fine in the last releases of the game.

 

As an example, I have just tried with the following special characters at the beginning of the song : "æ ß Ø — ¼ © ® þ ÷".

Only some of them are displayed : "æ ß Ø ¼", and the CDLC works fine.

 

As a second try, I used the following sequence : "àáâãäåæçèéêëìíîïðñòóôõöùúûüýÿÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑ".

Here is the result in the game :

Any developers opposed to me relaxing EOF's restrictions to allow (printable) extended ASCII characters for Rocksmith lyrics?

@@raynebc,

 

  Extended ASCII characters work fine for the song informations (artist, album and title) and the lyrics.

  The only issue I remember is the fact that they don't have to be used in the file path (path and file name).

This is the default font for the lyrics: http://i.imgur.com/jdTyZdK.png

 

So the characters that can be used are:

 

!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_abcdefghijklmnopqrstuvwxyz{|}~¡¢¥¦§¨ª«°²³´¶·¸¹º»¼½¾¿ÀÁÂÄÅÆÇÈÉÊËÌÎÏÑÒÓÔÖØÙÚÛÜÞßàáâäåæçèéêëìíîïñòóôöøùúûüŒœŠšž„…€™␀★➨

@@iminashi - Would you expect this to be relevant for the toolkit develepors as well (regarding what can and can't be put into the Artist, Song title, and other similar slots)? If so, it might be worth bringing this to their attention.

The artist and title fields use a different font which allows for some more extended characters to be used compared to the lyrics font. (See this thread).

Any developers opposed to me relaxing EOF's restrictions to allow (printable) extended ASCII characters for Rocksmith lyrics?

I'd say, show me an ODLC that uses extended characters before considering adding them to lyrics.  Toolkit and EOF have been rock solid since we adopted ODLC character standards.  :plus1: