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 see, I'm wrong again :(

 

I have never used tech notes for slides, I guess I will need to start :D

Sonic visualizer import fail if first element in points collection is "" (empty bpm) it'll be fine to drop it and import non-empty fields, idk why SV putting there empty one

Can you send me a sample file to test with?

@@raynebc, sure, here it is, also It's doubled markers for a reason I don't know, may be format a bit different?

https://drive.google.com/open?id=0B6zOE-7JCxwjTlVpWEllM1hPemM
(it's a folder for another proj, but you need a 321.svl)

by fail I mean it's left first BPM marker set to starting position of the first point and that's all.

I've improved Sonic Visualizer import, it is much more tolerant now of point tags that do not define a tempo.

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

*Fixed a bug with the previous commit that would cause the spectogram and waveform to be destroyed when performing undo or redo.

*Fixed some warning checks that are performed during save to not incorrectly warn about bend tech notes.

*Fixed a RS2 export bug where if a chord or single note had a length of 1ms and had bend or slide technique applied by a tech note, the corresponding chordnote or note tags would have a sustain of 0ms instead of 1ms.

*Fixed a GP import bug where hammer on or pull off technique from the current note wouldn't be handled correctly if the next note was in a different measure.

*Improved Sonic Visualizer import to ignore labeling data that do not define tempos, where previously the tempo would end earlier than it should.

*Improved the conditional selection functions to allow normal, mute and ghost gem type criteria to be specified when a pro guitar track is active.

*Changed chordify logic so that if a gem in an affected chord has any playable technique, it is written with an ignored single note with a minimum sustain of 1ms to ensure it displays appropriately in-game. The crazy and "high dens" statuses will now be able to force a chordified chord to export as low or high density regardless of the chord's contents (be aware that forcing a chord that has open notes and chordify status to be low density this way can cause graphical glitches in-game). Density changes the height of the chord box (high density -> shorter). Chords that have low density, no playing technique and no sustain status but have choridify status display notes that do not rotate as they approach the front of the screen in-game.

*Fixed a Feedback import bug that could allow drum notes to be given forced HOPO status.

Any chance of a new Mac build? It's been a while and there have been a lot of big changes in recent time. :)

@@th1rtyf0ur provided Mac builds for a while. If he has time, maybe he's willing to make a new one? I'd offer to cross-compile a Mac build from Windows or Ubuntu but it sounds like it would be complicated to get it to work correctly.

Hi,

 

this came up again

 

https://drive.google.com/file/d/0B2oZs0ta32KyU2FNbjFoTHFzUjA/view?usp=sharing

 

I believe it must be because the chord is accented.  The exact same chart without accent staus on that C#m does not produce it.

 

 

 

Thanks :D

 

 

Edit - scratch that, I took out accents and it still does it

 

https://drive.google.com/file/d/0B2oZs0ta32KyZk1nTFdSdFdfd1k/view?usp=sharing

 

https://drive.google.com/file/d/0B2oZs0ta32KydXk3THRScjlzdE0/view?usp=sharing

 

I can't understand it, I had earlier test versions that did not do this.

 

What are the rules on it again?

 

I am using straight RC11 (no hotfix, sorry I will get around to it) and there is no handshape sustain on the C#m in EoF.

 

 

Cheers :D

@PC Plum

 

Change the muted chords into C#m marked as muted (and regenerate fret hand positions)? If your intention was to have the muted chords appear in the same position.

No, I wanted them where they are.

 

I am confused because it worked fine through like 3 test builds, then I accented the last C#m and it done that.  I took off the accent and it still does it.  I can't think of anything else I did that would cause it.

 

 

Thanks for the input though :D

Yeah, I wasn't sure about that. If that was my custom I would try applying crazy status on the first muted note, but I'm not sure if that's what you want either.  :P

I'll wait and see what raynebc thinks.  I thought this issue was addressed previously, and in all honesty I'm fully expecting me to be at fault :D

@PC Plum the problem is that the handshape is stretch to include the muted chord that appear as repeat box. If you want the handshape to be at a controled value, apply the crazy status to the next chord and you can also use the "hi. dens" parameter in the note panel to avoid having the whole chord appearing to keep the same appearance that you have now at the exception of the handshape extension.

@@firekorn thanks I'll give it a try :D

 

@@iminashi sorry for not believing you :D

Well thanks, Crazy status worked a treat.

 

I know what I did.  There were actually string muted A0s between the C#m and the first muted F# chord in my test builds, but I removed them.  The open string would have "reset" auto handshape generation in my test builds.

 

 

I knew it would be my fault :lol:

I've been having trouble with the Leading silence function in the last couple hot fixes (error 47). Any chance on a patch, or possibly something I'm doing wrong myself?

I used it recently and it was working. Check EOF's log as well as the oggenc log in EOF program folder's "temp" subfolder.

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

*Changed GHWT export so that forced strum notes export with a marker 9 lanes higher than lane 1 to reflect user testing.

*Fixed a bug in RS2 export where a palm/string muted note would lose its sustain even if it should have been kept due to having linknext or sustain status.

**Fixed a bug in RS2 export where single notes may not correctly export for a chord with chordify status.

*Improved editor logic so that when adding linknext status to a note, it is prevented from being given a length that would go beyond the end of the chart.

*Added a check (if RS2 export is enabled) during save so that a warning is given if a note crosses an RS phrase or section boundary, as this can cause problems with dynamic difficulty.

*Fixed a Feedback import bug that could cause the drums and double drums tracks to be combined into one resulting drum track during import. Now the double drums track will be imported to the Phase Shift drum track if it is defined.

The first post is still 4-21-2016?

The forum glitched and didn't save my edits to the first post. Should be updated now.

A new Mac build has been posted, courtesy of th1rtyf0ur.

Thanks, @@raynebc and @@th1rtyf0ur

@@raynebc, 4-24 has a bug at copy\paste, it's CTD because of frets\lanes limit
Ii copied notes from higher difficulty and paste to main 0 difficulty(not hangs if paste to same diff, but will hang in another eof? probably kind of array copy opt) and CTD if i paste it in older EOF it will say "Tracks fret limit is exceeded by pasted note's fret value of 47, continue?" + "...tracks higher number... with a gam on 8 lane.." aaand it's paste nothing

something differently wrong :D

4-21 works just fine, notes.eof to play with : https://drive.google.com/folderview?id=0B6zOE-7JCxwjTlVpWEllM1hPemM&usp=sharing

@@Alex360 I couldn't immediately reproduce the crash. Is there a particular set of steps I can use (ie. select all notes in a particular track difficulty, copy, seek to a particular position in another particular track difficulty and paste)?

 

There have been some changes to the clipboard format somewhat recently, so going back or forward very far with the same clipboard files can cause unexpected behavior.