Jump to content

Latest EOF releases (9-26-2020)


Recommended Posts

  • Replies 2.7k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

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.8RC12: http://www.mediafire.com/file/ih70h6p67iy77ka/eof1.8RC12.zip You

Hi, folks. The latest hotfix (r1378) is in the first post. Changes are as follows: *Improved GP import to process bend status for grace notes, it will apply a bend strength to the grace note correspo

Hi, folks. The latest hotfix (r1363) is in the first post. Changes are as follows: *Added a warning during save if any lyrics have extended ASCII or Unicode characters, as these aren't compatible wit

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

*Fixed a bug introduced in a recent commit that causes the wrong visible piano area to be set when right clicking on the mini piano when the vocal track is active.

*Improved the Song>Song>Beat/Measure dialog to allow B or M to be pressed to change the radio button to beat or measure.

*Added a "Note>Drum>Toggle cymbal" function that will toggle cymbal status for all selected yellow, blue or green (lane 3, 4 or 5) drum gems.

*Added logic that runs after loading a project that will automatically remove text events that have no text (ie. if a chart was handled oddly during import).

*Changed the MIDI export of forced HOPO on/off markers to only write the markers to be 0 delta ticks long, to better support the ability to have overlapping notes with opposing forced HOPO on/off statuses.

*Updated INI export to save a "charter" tag in addition to the old "frets" tag to identify the name of the chart author.

*Updated INI import to look for the "charter" tag and if both it and the "frets" tag are present, the "frets" tag is ignored.

*Fixed a bug with the loading of very old (9+ years) EOF projects that would corrupt the project's beat positions.

*Improved Feedback import to honor solo and soloend event markers in Expert difficulty instrument sections, which are used by Clone Hero.

*Added some additional guitar pro to drum track mappings: 40 (electric snare) is a lane 2 note, 50 (high t) is a lane 3 tom, 92 is a lane 3 cymbal, 48 (hi-mid tom) is a lane 4 tom.

*Added Guitar Pro drum mappings in the [other] section in the eof.cfg config file allowing the definition of how each type of drum note is to be translated into EOF (ie. lane 1 bass drum, lane 2 rimshot, lane 3 tom, lane 3 hi hat pedal, etc). For example, you can change a drum note 55 (splash cymbal) to import as a lane 4 cymbal instead of a lane 5 cymbal as is default. You can also define which notes, if any, will import into lane 6 and automatically activate the "Enable five lane drums" option for the destination drum track. To make changes to these mappings, open and close EOF at least once so the default values are added to the config file, and then while EOF is closed, edit the mappings by opening eof.cfg in a text editor, saving and closing the file. The changes will take effect the next time EOF is opened and you import a drum track from a Guitar Pro file. You can specify up to 50 drum note values for each mapping, and each note value must be separated by a space or a comma. To remove the mappings for a particular note type, enter the number 0 as the only value for the mapping. To revert to default mappings for a note type, delete the line containing the mapping definition (ie. deleting the line containing "gp_drum_import_lane_6 = " will cause EOF to reset to the default mapping list of nothing for lane 6 drum notes).

*Added logic to summarize the notation rendered at the bottom of the piano roll so that if two consecutive notes both have the same statuses (ie. slider+forced HOPO), the second note's notation is replaced with a period. Non-summarized notation will draw on top of periods and will avoid drawing off the left edge of the screen to in order to better remain visible.

*Added a track # field to the Song Properties dialog. The track number is automatically obtained during chart creation if it is defined within the selected MP3 or OGG audio file. If your project defined the track number in "Song>INI settings", make sure to remove it when defining it in Song Properties or it could get written to song.ini more than once during save.

Link to post
Share on other sites

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

*Added the %MOUSE_X% and %MOUSE_Y% expansion macros that display the given mouse X or Y coordinate, as well as the relative coordinate and name of whichever sub-window the mouse is in.

*Added the ability to set a custom screen resolution by defining a width and a height. EOF will try to revert to the previously used resolution if the new one cannot be set, but if that fails, use File>Display>Display to reset to one of the preset resolutions and try a new custom resolution. Panel widths (ie. 3D preview) are based on the height, so strange resolution where the width doesn't achieve at least the 4:3 aspect ratio may result in a 3D preview panel that isn't wide enough.

*Changed full height 3D rendering to stretch gems to be taller to make up for them looking flatter than normal.

  • Like 1
Link to post
Share on other sites

@@Chlipouni About the issue you mentioned earlier (http://customsforge.com/index.php/topic/1529-latest-eof-releases-6-7-2018/page-119?p=282934&do=findComment&comment=282934), I think EOF is forcing a new handshape because of the use of the unpitched slide status (forces low chord density). To confirm, EOF should extend the first chord's handshape to encompass the chords that were split up into single notes?

 

Also, could you provide a sample RS XML file and steps to reproduce the duplicate note issue you mentioned in that post?

Link to post
Share on other sites

@@raynebc,

 

  Let's take the following example with two C5 chords :

  EOF - screenshot

 

  I obtain the following XML code :

    <level difficulty="0">
      <notes count="0"/>
      <chords count="2">
        <chord time="5.352" chordId="0" >
          <chordNote time="5.352" string="1" fret="3" leftHand="1" />
          <chordNote time="5.352" string="2" fret="5" leftHand="3" />
          <chordNote time="5.352" string="3" fret="5" leftHand="4" />
        </chord>
        <chord time="6.443" chordId="0" highDensity="1" >
          <chordNote time="6.443" string="1" fret="3" leftHand="1" />
          <chordNote time="6.443" string="2" fret="5" leftHand="3" />
          <chordNote time="6.443" string="3" fret="5" leftHand="4" />
        </chord>
      </chords>
      <fretHandMutes count="0"/>
      <anchors count="1">
        <anchor time="5.352" fret="3" width="4.000"/>
      </anchors>
      <handShapes count="1">
        <handShape chordId="0" startTime="5.352" endTime="7.534"/>
      </handShapes>
    </level>

  The two chords are generated and the handShape includes both of them.

 

  If I add a LinkNext status on the first chord, the XML code becomes :

    <level difficulty="0">
      <notes count="0"/>
      <chords count="1">
        <chord time="5.352" chordId="0" linkNext="1" >
          <chordNote time="5.352" string="1" fret="3" sustain="2.182" leftHand="1" />
          <chordNote time="5.352" string="2" fret="5" sustain="2.182" leftHand="3" />
          <chordNote time="5.352" string="3" fret="5" sustain="2.182" leftHand="4" />
        </chord>
      </chords>
      <fretHandMutes count="0"/>
      <anchors count="1">
        <anchor time="5.352" fret="3" width="4.000"/>
      </anchors>
      <handShapes count="1">
        <handShape chordId="0" startTime="5.352" endTime="6.443"/>
      </handShapes>
    </level>

  Only one chord is generated and it includes the second one with its sustain (OK for me).

  But the handShape doesn't include the second chord anymore.

 

  If I add a split status on the second chord, the XML code becomes :

    <level difficulty="0">
      <notes count="3">
        <note time="6.443" string="1" fret="3" sustain="1.091" />
        <note time="6.443" string="2" fret="5" sustain="1.091" />
        <note time="6.443" string="3" fret="5" sustain="1.091" />
      </notes>
      <chords count="1">
        <chord time="5.352" chordId="0" linkNext="1" >
          <chordNote time="5.352" string="1" fret="3" sustain="2.182" leftHand="1" />
          <chordNote time="5.352" string="2" fret="5" sustain="2.182" leftHand="3" />
          <chordNote time="5.352" string="3" fret="5" sustain="2.182" leftHand="4" />
        </chord>
      </chords>
      <fretHandMutes count="0"/>
      <anchors count="1">
        <anchor time="5.352" fret="3" width="4.000"/>
      </anchors>
      <handShapes count="1">
        <handShape chordId="0" startTime="5.352" endTime="6.443"/>
      </handShapes>
    </level>

  The second chord is generated as single notes as expected, and the first chord has a sustain that includes the single notes.

  In this third case, the handShape only includes the first chord.

 

  Finally, If I replace the split status with a slide, I obtain the same behaviour about the handShape.

 

  In conclusion, when I use the LinkNext status, EOF doesn't generate a handShape for the second chord and it omits to include it in the existing one.

 

  PS : About the second issue (single notes duplicated), I can't reproduce it with freshly created files.

 

Thanks

Link to post
Share on other sites

@@raynebc,

 

  I tried the beta release with the following example :

  EOF - Chords - HandShapes 2

 

  The XML code is :

    <level difficulty="0">
      <notes count="3">
        <note time="6.443" string="1" fret="3" sustain="1.088" slideTo="7" />
        <note time="6.443" string="2" fret="5" sustain="1.088" slideTo="9" />
        <note time="6.443" string="3" fret="5" sustain="1.088" slideTo="9" />
      </notes>
      <chords count="2">
        <chord time="5.352" chordId="0" linkNext="1" >
          <chordNote time="5.352" string="1" fret="3" sustain="1.091" linkNext="1" leftHand="1" />
          <chordNote time="5.352" string="2" fret="5" sustain="1.091" linkNext="1" leftHand="3" />
          <chordNote time="5.352" string="3" fret="5" sustain="1.091" linkNext="1" leftHand="4" />
        </chord>
        <chord time="7.534" chordId="1" >
          <chordNote time="7.534" string="1" fret="7" leftHand="1" />
          <chordNote time="7.534" string="2" fret="9" leftHand="3" />
          <chordNote time="7.534" string="3" fret="9" leftHand="4" />
        </chord>
      </chords>
      <fretHandMutes count="0"/>
      <anchors count="1">
        <anchor time="5.352" fret="3" width="7.000"/>
      </anchors>
      <handShapes count="2">
        <handShape chordId="0" startTime="5.352" endTime="7.531"/>
        <handShape chordId="1" startTime="7.534" endTime="8.080"/>
      </handShapes>
    </level> 

  The first handShape tag includes correctly the second chord, so this problem is solved.

  

  As you can see, I added a third chord that starts on the 7 fret. This new chord is not fully included in the current anchor tag, but EOF doesn't generate a new anchor tag for it.

  Instead of that, EOF displays this warning : "This note is specified as using the index finger, but the first hand position is on a different fret....".

  

  Is it normal ?

  If yes, how can I solve this ?

 

  If I remove the linkNext status on the first chord, the new XML code becomes :

    <level difficulty="0">
      <notes count="0"/>
      <chords count="3">
        <chord time="5.352" chordId="0" >
          <chordNote time="5.352" string="1" fret="3" leftHand="1" />
          <chordNote time="5.352" string="2" fret="5" leftHand="3" />
          <chordNote time="5.352" string="3" fret="5" leftHand="4" />
        </chord>
        <chord time="6.443" chordId="0" >
          <chordNote time="6.443" string="1" fret="3" sustain="1.088" slideTo="7" leftHand="1" />
          <chordNote time="6.443" string="2" fret="5" sustain="1.088" slideTo="9" leftHand="3" />
          <chordNote time="6.443" string="3" fret="5" sustain="1.088" slideTo="9" leftHand="4" />
        </chord>
        <chord time="7.534" chordId="1" >
          <chordNote time="7.534" string="1" fret="7" leftHand="1" />
          <chordNote time="7.534" string="2" fret="9" leftHand="3" />
          <chordNote time="7.534" string="3" fret="9" leftHand="4" />
        </chord>
      </chords>
      <fretHandMutes count="0"/>
      <anchors count="1">
        <anchor time="5.352" fret="3" width="7.000"/>
      </anchors>
      <handShapes count="3">
        <handShape chordId="0" startTime="5.352" endTime="6.440"/>
        <handShape chordId="0" startTime="6.443" endTime="7.531"/>
        <handShape chordId="1" startTime="7.534" endTime="8.080"/>
      </handShapes>
    </level>

  In this specific case, EOF creates a new handShape to manage the second chord, but it should be able to reuse the previous handShape (because they both have the same chordId).

 

Thank you

Link to post
Share on other sites

I could only get that to occur if I both had applied chord fingerings so that the index finger is used for the third power chord and had also manually defined a fret hand position to suit the first two power chords (ie. fret 3). Since there is a fret hand position defined during save, EOF skips creating automated positions and then complains that the third power chords fingering implies the fret hand position at its timestamp should be 7 instead of 3. If I remove the fret hand position and allow EOF to place it automatically during save, it places a position of 3 at the first power chord and a position of 7 at the third power chord. Let me know if this doesn't address your concern or if there's any other problem to address.

Link to post
Share on other sites

  • 2 weeks later...

Hello Im a Mac osX High Sierra user,

I just downloaded EOF (06-07-2018).app and eof_utilities.pkg.

When I try to launch EOF I get an error.

 

NO - Song      Error opening log file for writing.  Move EOF to a file path without any special (ie. accented) characters if applicable.

 

Here is the content of the log file.

 

320: Logging started during program initialization at Fri Jun 29 19:14:16 2018

320: EOF v1.8RC12 (6-7-2018)
320: Logging level set to normal
320: Importing chord shape definitions
320: eof_load_chord_shape_definitions() entered
320: 54 chord shape definitions imported
320: eof_set_display_mode() entered
320: eof_window_create() entered
320: eof_window_create() entered
320: eof_window_create() entered
320: eof_window_create() entered
320: eof_window_create() entered
320: eof_load_data() entered
 
 
Please Help Me
Link to post
Share on other sites

  • 2 weeks later...

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

*Changed the recent MIDI export logic where HOPO on/off markers are 0 delta ticks so that this only occurs for notes with crazy status, without which the note can't overlap with other notes and this workaround isn't needed.

*Added some RS2 export logic to allow a chord's handshape to extend over the single notes created from a repeated chord due to split or linknext status.

*Adjusted the 3D image scaling when the full height 3D preview option is in use.

*Added functions to select/deselect notes that do or do not have a specified number of gems exactly.

*Added logic to validate the user specified width when setting a custom window size, and to offer different widths if the specified one isn't a multiple of 4 as required.

*Added a function to seek by a percentage of one screen (defaults to 5%, but can be specified by changing the eof_scroll_seek_percent setting in eof.cfg while EOF isn't running) by holding ALT and using the mouse's scroll wheel.

*Added new logic to Feedback import that will automatically resnap notes that lose grid snap due to floating point math errors during the import's timing conversion.

*Fixed bugs that prevented the clone to/from clipboard functions from working properly in some scenarios (ie. for tracks that have tone changes or slider sections).

*Fixed a bug with the MIDI export where the quantize logic would incorrectly use the project's native tempo map if the project had a stored TEMPO track from MIDI import. The quantize logic will now only run if there is no stored tempo track in the project.

*Changed MIDI import so that EOF only offers to store the imported file's tempo map into the project if Rock Band file export is enabled, as this feature is only meant to be used for authoring pro guitar upgrades for charts in Rock Band and the original tempo map must be used.

*Updated Feedback import to support Clone Hero formatted lyrics (encoded in either ASCII or Unicode), which use text events to define lyrics (without pitch or duration) and lyric lines.

  • Like 1
Link to post
Share on other sites

  • 3 weeks later...

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

*Fixed a bug with Feedback import where mid-beat tempo changes would cause a text event to import onto the wrong beat marker.

*Improved the "Imports drop mid beat tempos" handling to only delete the first of consecutive beats inserted due to consecutive mid-beat tempo changes.

*Improved MIDI import's handling of charts with lyrics incorrectly defined as text events, by not importing those events as text events in addition to importing them as lyrics.

*Corrected the chord name validation during save to reflect that Rocksmith export allows chord names to include parentheses.

*Changed the metronome so that by default, a lower pitched tick sound is used for beats that have a time signature in effect and aren't the first beat in a measure. This can be disabled by unchecking the "Use multi-pitch metronome" checkbox in "Song>Audio cues".

*Changed the slider mechanism to be usable in the keys track, for use in Clone Hero.

*Fixed some bugs in "Beat>Reset offset to zero".

*Added handling for the close window control.

*Returned the CTRL+SHIFT+R shortcut to "Resnap to this grid" and assigned ALT+R to "Resnap auto".

*Improved the error handling for when a custom window size couldn't be set.

*Added CTRL+ALT+Y/G/B shortcuts to toggle cymbal+tom status for selected cymbals in the Phase Shift drum track.

*Improved Guitar Pro import of drum tracks to be able to apply cymbal+tom status to notes imported into the Phase Shift drum track if they are defined to have both a tom and a cymbal at the same place. If the destination of the import includes the normal drum track, a message is displayed warning that cymbal+tom status is only applicable for the Phase Shift drum track.

*Improved file imports so that if a file named drums.ogg, rhythm.ogg or song.ogg is selected as the chart audio, that file is copied to the project folder if necessary and used with its original file name instead of being renamed to guitar.ogg.

  • Like 3
Link to post
Share on other sites

  • 2 weeks later...

When charting vocals using the Feedback input mode and piano tones are on, if a note is selected then pressing up/down to seek will play the pitch of the selected note as well. It looks like it might be a bug since up/down in the other input modes just change the note and should play the new one.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    No registered users viewing this page.


×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. - Privacy Policy