Jump to content

Latest EOF releases (9-26-2020)


Recommended Posts

What version of Windows are you using? What model of laptop is this? Did any previous build of EOF work normally on this laptop?Windowws

Windows 7, Alienware M15X. I haven't tried any old versions of EOF; where would I be able to find them?

Link to post
Share on other sites

  • 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

Performance is bad in 6-12-2019, especially if you have ~3k notes on track. Scrolling back and forward my framerate goes from 100 in the beginning  to 30 at five minutes into the song. Even after changing eof window size to 640x480 still only 40 fps.

Link to post
Share on other sites

I had found a cause for that and fixed it. It was because of the 3D rendering logic I'd added to allow the tail from an off-screen crazy note to display even if the seek position is after the note it precedes and overlaps, which is kind of a niche issue for the performance hit it causes. I could probably make it work much faster, but it would convolute the 3D drawing code.

  • Like 1
Link to post
Share on other sites

Assuming mouse input is working, are you able to open/import a chart via the File menu? If so, does keyboard input at least work in the Windows file browser dialog that comes up to select a file for import?

 

Edit: I wonder, if you bring up the on screen Windows keyboard, does manipulating that virtual keyboard with the mouse while EOF is the foreground problem seem to send keyboard input to EOF?

 

Edit 2: Here is a keyboard testing program that comes with the Allegro 4 source code. Please give this a try and let me know whether it reports keyboard input:

https://www.mediafire.com/file/w0j0mjsf2x0oo2k/exkeys.zip/file

Link to post
Share on other sites

Assuming mouse input is working, are you able to open/import a chart via the File menu? If so, does keyboard input at least work in the Windows file browser dialog that comes up to select a file for import?

 

Edit: I wonder, if you bring up the on screen Windows keyboard, does manipulating that virtual keyboard with the mouse while EOF is the foreground problem seem to send keyboard input to EOF?

 

Edit 2: Here is a keyboard testing program that comes with the Allegro 4 source code. Please give this a try and let me know whether it reports keyboard input:

https://www.mediafire.com/file/w0j0mjsf2x0oo2k/exkeys.zip/file

I had deleted the program from my computer, and went to redownload it today to try your suggestions. I opened it up and the key functions worked.

It seems to have worked itself out. 

Thanks for all your suggestions.

Link to post
Share on other sites

Forced HOPO Off isn't working for me when I have a note in the auto-HOPO range of another note. Works with chords but won't work with single notes when I press H or try to toggle Forced HOPO Off.

"I am a thunder dragon! Hear me roar thunder and breathe lightning!"

Link to post
Share on other sites

Is this not working in EOF (EOF won't allow you to apply forced strum status) or not working in a particular rhythm game (the MIDI from EOF isn't working as wanted)? Either way, I'd probably need the EOF project file and details about which note can't be made force strum.

Link to post
Share on other sites

Is this not working in EOF (EOF won't allow you to apply forced strum status) or not working in a particular rhythm game (the MIDI from EOF isn't working as wanted)? Either way, I'd probably need the EOF project file and details about which note can't be made force strum.

Yeah, EOF (May 5 2019 revision and the latest revision) won't allow me to apply forced strum status. I'll redownload a fresh version of EOF and its latest hotfix, it worked.

 

The problem does not lie within the chart files but rather, the issue lied within EOF.cfg. I deleted it and while it reset all of my preferences, Forced Strums are working again. I was going to show you the settings I had in it but after I restored the file and closed EOF, my new preferences oversaved my restored old preferences (I wish I opened it in Notepad++ before that happened). =/ Can't really show you the differences in my old EOF.cfg vs a new default one since I quickly messed that up but at least I got it working again.

 

When in doubt when a feature isn't working for some reason, delete EOF.cfg and reconfig settings. :P

"I am a thunder dragon! Hear me roar thunder and breathe lightning!"

Link to post
Share on other sites

Could you further describe what the issue was? Would EOF not display the forced strum gems as being larger, or did the note retain the "h" or "(h)" notation below it even after you apply "Note>HOPO>Force off" on it? If you find a way to reproduce the issue, let me know. Did this happen in all non real guitar tracks? I see an issue where the 3D preview won't display forced HOPO notes with the correct smaller size in pro guitar tracks, but that didn't seem to apply to the 2D rendering.

 

Depending on your luck, Windows may have automatically made a backup "shadow copy" of the settings file. To check for this, right click on the EOF program folder, select properties and then select the "Previous versions" tab. If any older versions of the folder are listed there, you could open the backup copy and salvage the config file.

Link to post
Share on other sites

Could you further describe what the issue was? Would EOF not display the forced strum gems as being larger, or did the note retain the "h" or "(h)" notation below it even after you apply "Note>HOPO>Force off" on it? If you find a way to reproduce the issue, let me know. Did this happen in all non real guitar tracks? I see an issue where the 3D preview won't display forced HOPO notes with the correct smaller size in pro guitar tracks, but that didn't seem to apply to the 2D rendering.

 

Depending on your luck, Windows may have automatically made a backup "shadow copy" of the settings file. To check for this, right click on the EOF program folder, select properties and then select the "Previous versions" tab. If any older versions of the folder are listed there, you could open the backup copy and salvage the config file.

If I were to create a new note to Force HOPO Off away from another note, it will work the way it is placed but once I drag that note into another note's HOPO range, the Force HOPO Off status (big notes on the 2D editing plane) will turn off and revert back to an auto HOPO (normal sized notes) and it will only toggle between auto and forced on (small note) in an auto-HOPO range. And yes, I only tested this on non-Real Guitar tracks (Guitar Hero/Rock Band-styled tracks). During the "error", I noticed the notations would either be "h", "(h)", or "." (with consecutive HOPOs) but now that big notes (forced strum) show up on a new EOF.ctg, "(h)" doesn't show up any more (I think "(h)" meant auto-hopo).

 

I was hoping to be able to recover the "corrupted" configuration file but trying to show Previous Versions in the properties any files I wanted to revert back to but that Windows 10 feature never ever worked for me for any saved files I was hoping to recover for anything. :( Like anything else on my computer, Windows 10 didn't back up EOF.ctg's previous saved versions.

"I am a thunder dragon! Hear me roar thunder and breathe lightning!"

Link to post
Share on other sites

(h) does mean auto HOPO. I couldn't find a way to reproduce the issue as you've described, and I can't immediately think of any user preference that would have this kind of effect on HOPOs. Even if I use the preference to make all new notes forced strum automatically, place a note and move it right next to an existing note, it's retaining HOPO status for me.

Link to post
Share on other sites

  • 1 month later...

Hi, folks. The latest hotfix (8-21-2019) is in the first post. Changes are as follows:

*Fixed a bug with MIDI export where lyrics containing Unicode characters would be written incompletely.

*Updated GH3/GHA import to interpret the HOPO threshold as a fraction of a quarter note length instead of a fraction of a beat length, since FCPREMIX suggests this is how Guitar Hero handles it.

*Corrected Guitar Hero import to reflect that notes that start at the end of a slider (tap) phrase do not have that status applied to them.

*Added logic so that the main menu is rendered correctly when x2 zoom is in use.

*Fixed a bug with Feedback import where if events were defined out of chronological order, they may not import correctly.

*Removed the previous change to 3D render logic regarding crazy note tails. Resolving this superficial problem causes too much of a performance hit on track difficulties with several thousand notes.

*Improved the trill, tremolo and slider remove functions to only create one undo state when used on multiple selected applicable notes.

*Fixed the GH import logic that prompts for which type of star power phrase to import when both normal and battle phrases are present.

*Fixed a bug where seeking to the chart or audio end during playback could result in the seek position exceeding the end position of the audio.

*Fixed a bug with GPA import where time signatures on beats synced to precede 0 seconds would be incorrectly applied to the beats that are kept.

*Improved GH import to be able to read sections from GH3 format chart files.

*Added a "File>Import>Guitar Hero sections" function to import just the section names from a Guitar Hero file (ie. *.pak.ngc) into the active project. Each imported section is assigned to the beat immediately at or before the section's timestamp.

*Corrected the GH import logic's ability to read the section names from one file and the section instances (ie. timestamps) from the main chart file. This seems necessary for GHA charts, where if you extract the chart's text.qb.ngc file from the game disc's qb.pak.ngc file, you can provide that text.qb.ngc to EOF when it offers to load the section names from a different file.

*Changed the 2D rendering of cymbals in the piano roll to work around Apple's changes to OS X (at least as far back as High Sierra) which broke the ability to draw filled triangles.

*Added CTRL+Space and CTRL+SHIFT+Space playback shortcuts to the Mac build, since the CMD+Space shortcut that had been assigned invokes the Operating System's search feature.

*Fixed the handling of the optional background image so that it is retained when importing a file via command line or when changing the program window size.

*Fixed a bug that could cause pro guitar notes to 3D render with the wrong size (ie. reflecting wrong hammer on or pull off status).

*Added a "Track>Offset" function that will move the track's contents (excluding text events) forward or backward a specific number of milliseconds, such as to correct the sync of lyrics after lyric import. It's been said that Guitar Hero Smash Hits automatically offsets the lyric timings by some amount of milliseconds from how they're defined in the chart file, so offsetting the vocal track after importing a GHSH chart appears necessary.

*Fixed a bug with GH import that would prevent sections from being loaded from a few specific songs due to their inclusion of hex strings of multiple opposing section definition methods.

*Corrected MIDI import to better handle open notes that overlap other notes.

*Changed the MIDI export of crazy open strum notes to end the open strum Sysex marker 1 delta tick after it begins instead of extending it across the entire open note, to improve compatibility with Clone Hero.

*Fixed a bug where accent drum note status was not correctly applied when using "Paste from difficulty", "Paste from catalog" or "Clone from track".

*Fixed a bug where accent drum note status was not correctly retained when vertically reflecting notes.

*Corrected the behavior of the Note>Drum>Accent>Toggle and Clear functions, which weren't actually toggling or clearing those statuses.

*Changed the Note>Drum>Accent>Toggle and Clear functions so they don't force the status to match on notes outside the active track difficulty.

*Added the ability to define ghost status for drum notes (which is used in some Guitar Hero charts), for potential future use in Strikeline and Phase Shift, which will render with a white background in the piano roll at the letter 'G' below the note at the bottom of the piano roll. Ghost status is applied appropriately by Guitar Hero import for Warriors of Rock chart files. When the MIDI is exported during save, a "drum_ghost_threshold = 1" INI tag is written to reflect that the velocity value of 1 is being used to define ghost gems. The G menu accelerator in the Note>Drum menu was re-assigned to the new Ghost submenu, since "Toggle G cymbal+tom" already has a keyboard shortcut. If a drum gem is defined as having both accent AND ghost status at the same time, it will export to MIDI as a ghost gem, as this is the conflict resolution observed in at least one Guitar Hero chart that does this.

*Added a "Prefer MIDI friendly grid snaps" preference that is enabled by default which causes the "Highlight non grid snapped notes" and "Repair grid snap" functions to only honor grid snap sizes that will quantize properly when saved to MIDI. For example: In 4/4 meter, 480 ticks is divisible by 4 so 1/4 beat works well. However 480 ticks is not divisible by 25, so 1/25 beat can't be written so that many consecutive 1/25 beat notes are equal distances from each other.

*Changed the length threshold for drum rolls in GH import to 160ms based on the in-game behavior of some charts.

*Improved MIDI export so that if a note is within 1ms of a quantized MIDI timing, it is exported at that quantized position, reducing timing problems introduced by math rounding limitations depending on the tempo map.

*Added some fault tolerance to the project save logic (also applies to creating undo/redo state) so that if the file can't be opened for writing (ie. if it was blocked by the OS or antivirus), EOF will delay 1ms and retry to open the file up to 4 more times in case the interference ends and EOF can then write the file.

*Corrected the behavior of the track cloning functions to correctly reflect the sharing of the phrases between the normal and Phase Shift drum tracks.

*Improved the auto adjust logic to update the timing of Phase Shift drum track phrases even if that track is currently reflecting the normal drum track's phrases (the phrasing is being shared).

*Added logic to rebuild the program window before prompting to exit (by pressing Esc or clicking the close button at the top right of the EOF program window), in case the display stopped rendering properly due to use of Remote Desktop or the computer going to sleep/hibernation. The close button click should be able to be detected as long as a dialog window wasn't left open, but in case a dialog was left open, you should be able to press Esc a couple times to close the dialogs and trigger the display to be redrawn.

*Improved Queen Bee import to be able to import a text file that defines a time signature or star power phrase. Queen Bee exports one such definition per file.

*Added a "File>Import>Queen Bee (multi)" function that has you browse for a Queen Bee format array.txt file and imports all .txt files in that file's folder.

*Added a "Don't auto edit new lyrics" preference that suppresses the prompt to provide lyric text when a new lyric is placed in the vocal track.

  • Like 1
Link to post
Share on other sites

  • 2 weeks later...

Hey! I noticed fairly recently there was an update for when loading an ogg it defaults to the project folder rather than having to navigate specifically there, which saves me some notable time on every project, thanks! I thought about requesting this at some point but felt it might be too niche to put time into, so it was a very pleasant surprise when it happened on its own.

 

Some fairly niche requests I would like to make, as someone who does the majority of their tabbing out in EoF:

-It's common for me to hit Ctrl+Shift+H to create a handshape and for it to create an arpeggio marker instead. This isn't a huge deal, hitting it again on the same area DOES create a handshape the second time and then I just have to hit T to remove crazy from the notes, but it does throw off my flow a bit.

-Dead notes (both the Shift+X and Ctrl+X kind) don't change in fret number when you select them and hit +/- or Ctrl+Scroll Wheel. A lot of times I'll be tabbing something out and realize 'Oh that's actually a string higher/lower' and move the riff to the string and adjust the fret values as necessary with a quick scroll wheel, but then again I have to hit Shift+X for any dead note and scroll wheel, then hit Shift+X again to toggle back to the actual riff. (Ctrl+X dead notes probably don't need to change because I imagine anyone using that is intentionally setting the fret value to zero, but Shift+X saves the specific fretting so)

-Tech notes have no 'select like' options. Both internet tabs and myself have a bad tendency to exaggerate bends to twice their amount. I've been trying to right this recently, but I've found with a full tab if I try to select like on any tech note, it selects every tech note, making it a daunting task to manually correct. I think this might have come up before and it was an oddity of how tech notes are done, apologies if so.

 

Nothing huge, I still remain amazed at the program's stability and versatility.

 

EDIT: Oh in addition to dead notes, increasing/decreasing slides would be nice (pitched and unpitched) when changing the fret value for a selection of notes. I know changing tunings changes these values, and I think I personally routinely run into wanting to change slide values with the fret than just wanting to change the fret value (especially with pitched slides, wherein I often change the fret value for the start of the slide and the end of the slide it's linknexted to with shortcuts, but I forget to get the slide so all the slides look wonky in first test).

I've always got the multitracks.

Link to post
Share on other sites

Are you sure you're not hitting CTRL+SHIFT+G sometimes? That is the keyboard shortcut to mark an arpeggio, and the letter is right next to H so that's a possibility. The next time this has just happened, please check the Information Panel to see if the value listed for the last ASCII character input read was "103 ('g')" or if it is stated to be 'h' instead.

 

As you suggest CTRL+X defines a Rock Band 3 style string mute (no defined fret number). For this reason, these notes are prevented from having their fret value incremented/decremented with those controls. I've gone ahead and changed it so that muted notes with a fret value (ie. defined with SHIFT+X) can have their fret values incremented/decremented with these controls.

 

For the tech note selection issue, try "precise select like" (SHIFT+L), which will only select notes with a matching lane number AND statuses.

 

For incrementing/decrementing slide endings automatically, I can't assume that's a behavior everybody would like. If you like, could make a user preference for this (you'd have to enable it once and it would stay enabled permanently until you make a new EOF installation, reset your settings to default, etc). Let me know if that would work for you.

 

Edit: This preference would probably be limited to only affected slide endings directly applied to selected notes (ie. if you select a normal note and increment its fret value, a slide ending applied by tech note won't be altered, since the normal and tech notes are kept separate intentionally). It would probably allow you to select a tech note and use the increment/decrement function on it directly to affect the slide though, so it could still be convenient in that way.

  • Like 1
Link to post
Share on other sites

Re: Handshapes: Unfortunately I can't screenshot that it's showing h because it reads Print Screen as I press it, but I can confirm that it's saying "104 ('h')" and still creating arpeggio markers. In one file I was working on (A RB3 Pro chart I was updating) so far it ALWAYS becomes an arpeggio without fail, before that one it seemed to be somewhere about one in three or two times in other projects (but I'd simply tap the same key again while holding down CTRL+SHIFT so I'm pretty confident I was hitting h every time). I am someone who very often uses the Rock Band .mid's as starting points (for beatmap and lyrics), if that might be relevant to pinpointing this issue.

 

Re: Tech Note Selection: Similarly, I have tried SHIFT+L when in tech note view and it still selects every tech note in the file for me, regardless of lane or status.

 

Re: Slide Preference: I would very much like that slide preference if it's not a hassle to introduce; as mentioned none of these make anything impossible for me, they'd simply be more convenient.

 

EDIT: Addendum: Tried handshapes and tech notes in a project that wasn't started from an imported .mid (I do have some of those!) and both worked as intended as far as my testing went. So likely this is some oddity created from importing the .mid from a GH or RB3 file. It's a niche case so unless you think it's simple to solve or related to some deeper problems that need fixing probably isn't a priority.

I've always got the multitracks.

Link to post
Share on other sites

As with your case, I can't reproduce the arpeggio issue on a blank chart. If you can reliably cause the arpeggio marker to be created with minimal steps such as opening a project file (or immediately after importing some file), selecting specific notes and pressing CTRL+SHIFT+H, please send me the file and steps in question so I can try to reproduce the issue.

 

Same for the tech note selection, I can't reproduce this on the current hotfix. One thing to keep in mind though is that select like isn't so picky that it will differentiate a tech note that slides up to fret 5 from a tech note that slides up to fret 6. From its perspective they are both slide up tech notes.

Link to post
Share on other sites

http://www.cdlc.wit-n-wiz.com/RamblinMan/

 

For me, this notes.eof should demonstrate both of these issues I was having if one tries to create a new handshape or precise select like in tech note view. As I realized after some testing, it seems like it might be exclusive creating a notes.eof from a GH/RB notes.mid than any created from New. This is how I personally do most of my charts, but I imagine I'm in a very select minority that does so nowadays.

 

EDIT: For clarity, I mean I'm importing from notes.mid from projects that ripped GH/RB songs to formats for FoF and Phase Shift.

I've always got the multitracks.

Link to post
Share on other sites

 

Some fairly niche requests I would like to make, as someone who does the majority of their tabbing out in EoF:

-It's common for me to hit Ctrl+Shift+H to create a handshape and for it to create an arpeggio marker instead. This isn't a huge deal, hitting it again on the same area DOES create a handshape the second time and then I just have to hit T to remove crazy from the notes, but it does throw off my flow a bit.

 

Same here, but I might not be updated.  I'll update and give an example in a bit.

It's not an everytime thing, but sometimes I have to Ctrl+Shift+h twice to get a handshape instead of arpeggio.

 

BTW I start from scratch without importing  mids or tabs.

  • Like 1
Link to post
Share on other sites

For incrementing/decrementing slide endings automatically, I can't assume that's a behavior everybody would like. If you like, could make a user preference for this (you'd have to enable it once and it would stay enabled permanently until you make a new EOF installation, reset your settings to default, etc). Let me know if that would work for you.

 

I sometimes wish that if you selected notes/chords and there are FHPs at exactly same position, those would also be inc/dec automatically. Would this be an easy thing to do? I think this could be tied to the same preference.

Link to post
Share on other sites

I think I fixed the arpeggio marking issue, it looks like it would happen if you add a handshape that is earlier than existing handshape/arpeggio phrases in a track.

 

@@theSG Would it only be appropriate to automatically increment/decrement a FHP if it was the same timestamp as and was the same fret value as one of the gems in a note being affected? Should this functionality be lumped in with the preference to increment/decrement slide endings?

  • Like 1
Link to post
Share on other sites

Only same timestamp matters no need to have same fret value

  • chords 99% of time will have same value anyway
  • for single note auto inc/dec wouldn't work mostly in cases where you probably should use ctrl+(F)1-9 anyway
  • would work perfectly when you want to edit long selection of notes (like move up/down to a different string)

Should this functionality be lumped in with the preference to increment/decrement slide endings?

I don't know. I would want them both on, so it would work for me.

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