Jump to content


Rocksmith Custom Developer
  • Posts

  • Joined

  • Last visited

  • Days Won

  • Donations


Everything posted by raynebc

  1. Sorry for the delay, there was some work being done off and on with ignition but as of now the links work.
  2. Place an anchor on the beat where it begins being in sync. Then you'll have to use some other means to manipulate the tempo map. If there is any gap between the start of the song and the first beat, an easy option would be to use "Beat>Reset offset to zero", which will fill in that gap with one or more beats. Then you can move any beat other than the first without affecting the rest of the tempo map that is already correct. If the first beat already begins at the beginning of the song, then just leave it alone and move the other beat markers instead. You can add or remove beats if you want via the Beat menu.
  3. By default, repeated chords that are close enough to each other are written to display as repeats. You can force a repeat chord to display as the full chord box by applying "crazy" status to it (select the chord and press the T key to toggle that status). The black/white coloring of the fret number box in the editor panel will invert, and the 3D preview in EOF will reflect it being drawn as a chord instead of a repeat line.
  4. There may be some special case where the Rocksmith export is malfunctioning during save. Make sure you're using the latest hotfix (9-26-2020), and if the error still occurs during save, please send me the project (.eof) file for testing.
  5. When time permits, this is one of the next changes I want to tackle.
  6. If you want something really different, try the "2D render RS piano roll" option in File>Preferences>Preferences. It applies some editor style changes that were noticed in Rocksmith developer videos.
  7. It's not as convenient, but you can use the Song>Seek>Bookmark> menu. There are keyboard accelerators for each of these so you could use ALT+S, S, B and press a number key to jump to that bookmark (5 keystrokes).
  8. It shouldn't look very weird unless the song is actually designed to be not well-quantized. Just use grid snaps appropriately.
  9. EOF doesn't support that, but there's no reason the ability to do so is required. Just sync the beats before and after that 66BPM change and the problem is resolved.
  10. This was a design decision from the original EOF developer, where it was considered bad for security/privacy for the project file to define a full path to an audio file used in the project (in case you share your project file with other people). Having all audio files in the project folder is the best way to go for now.
  11. If notes got deleted for some reason while you're beat syncing, you can just import the tablature again and it will line up with the beat map. If you were note syncing instead then you made more work for yourself and are probably going to have to import the tab into a different track, then select all notes starting from where they mysteriously stopped up until the last note (click on the first missing note to select it, then use SHIFT+End to select all remaining notes), copy to the clipboard, seek to where the first missing note goes in PART REAL_GUITAR_22 and then paste the notes and continue working. If you import the tab again and find that the notes end sooner than expected, send me the GP5 file. Just know that Guitar Pro doesn't always convert to GP5 very accurately so EOF may actually be importing the file as it is defined.
  12. If you change the tuning of a string that is used by any notes in the track, EOF should offer to try to transpose that note up/down the string by however many frets the tuning changed. If you can reproduce steps where that isn't happening, please send me the .eof project file and specific steps (ie. change the tuning of string # to #). String 6 tuned down 4 half steps and all other strings at default tuning is the only "drop C" tuning EOF will recognize, so likewise if you can find a way to get EOF to not recognize it in that specific circumstance, let me know.
  13. As mentioned, this was most often a bug with Guitar Pro's export to GP5 format. If you can provide a GP5 file that is handled correctly in Guitar Pro 5 and not by EOF, then and only then is it a problem for me to fix with EOF.
  14. You may have to undo your Windows update to confirm whether that fixes it. In general I need more details.
  15. You might need to switch over to Clone Hero. Phase Shift is pretty much end of development.
  16. Hi, folks. The latest hotfix (9-26-2020) is in the first post. Changes are as follows: *Updated array.txt import to support explicit HOPO markers instead of threshold based HOPO by making "HOPO" the first line of the array.txt file, and by putting the letter H in front of the relevant notes' gem lane encoding. *Improved LRC import to ignore a defect commonly found in lyric files provided by Deezer where a past timestamp is repeated and accompanied with an empty line of lyrics. *Fixed a bug with the audio preview function where existing start and end timing tags aren't correctly replaced when the timings are redefined. *Improves "Queen Bee (multi)" import to look for any of 19 folder names (ie. "beatlines", "sections", "timesig", "bass_Expert", "lead_Expert", etc) at the same folder level as selected file's parent folder, offering a "GHOT import" automating the mass import of a chart's contents. *Improved the File menu handling to disable the "Export guitar pro" function if none of the pro guitar/bass tracks have notes in them. *Fixed a crash that would occur when changing to a pro guitar track difficulty with over 32,768 gems (would likely have to be a full album chart). *Fixed a bug where using "Track>Erase track" or "Track>Clone" functions did not remove existing track-specific text events. *Changed GH import so that star power and slider phrases aren't shortened if they end in the middle of a note. *Fixed a bug with MIDI import where if solo phrases are converted to star power phrases (an old Frets on Fire behavior, if there are fewer than two star power phrases), there is some data corruption that could cause undefined behavior until the project was saved and reloaded. *Improved the reliability of the "Import dialogs recall last path" import preference. *Clarification to RS export warnings that the "COUNT" phrase should be defined in all uppercase letters and the "noguitar" phrase should be defined in all lowercase letters. *Updated the warning during save about lyrics existing outside of defined lyric lines to offer to highlight the offending lyrics and cancel the save.
  17. You'll have to implement this via your computer. As long as you set up it up as the default MIDI device in the OS, it might work in EOF.
  18. Unfortunately there may never be Catalina support. Experienced Mac developers haven't been able to build EOF as 64 bit so if they can't, I don't have a way to do so. @@adrian142 What OS? What specific versions of EOF have you tried? Does accessing the menus via keyboard (ie. ALT+F to open the File menu) work? Does accessing the menus via mouse work? Does opening a file over command line (ie. drag and dropping a MIDI/XML/GP5 file on top of the eof.exe program) result in the file being imported? When a chart/file is loaded/imported, does the Information panel reflect when you press keys on the keyboard?
  19. I don't understand what you're trying to do. If you've reset the tempo, you can change the first beat's tempo in order to speed up or slow down the entire song, moving all notes earlier or later.
  20. Most of these things are made the default behavior in EOF if it would be appropriate in most cases. This preference also applies to notes marked as being played staccato as well (since those notes don't ring out).
  21. You can reset all beats to the first beat's tempo (Beat>BPM>Reset BPM). Then you can place other tempo changes as wanted.
  22. You're importing a chart with an unusually high number of phrases, sections or events. There's not immediately a workaround but if you send me the file I can manually import it for you. I hesitate to just largely increase the limit in EOF formally, because it will cause EOF to use more memory.
  23. You can look at two tracks at once, but adding more would be complicated to program. EOF does let you copy/paste large sections of notes, but it's not specifically measures' worth of notes, you'd have to manually select the content on the note level instead of beats/measures. You can define a custom window size and zoom level, but many of these options are based on limitations of what can easily be achieved due to Allegro's capabilities and EOF's design.
  24. You have to unzip the full build of EOF (1.8RC12) to a folder, then unzip the hotfix on top of it, replacing older files with the newer ones from the hotfix. You can't just download the hotfix and use it, it's not a complete EOF release.
  • 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