Jump to content

raynebc

Rocksmith Custom Developer
  • Posts

    2,899
  • Joined

  • Last visited

  • Days Won

    8
  • Country

    United States
  • Donations

    0.00 USD 

Everything posted by raynebc

  1. That radio button is a bit complicated in how it works, it only allows the status to be applied if all gems in the note are already marked as string mutes. Use the "mute" checkbox next to each gem instead, or use the CTRL+X (remove fret number and apply string mute status) or SHIFT+X (keep existing fret number and apply strnig mute status) controls.
  2. Creating a version of the chart with only one difficulty (ie. don't use DDC in the toolkit) will simplify the chart, so it's worth seeing if that version crashes in-game.
  3. That means the first sync point occurs after the first beat, and based on the timing it would put one or more beats before 0 seconds. The best way to avoid that would be to sync the first beat marker at or after 0 seconds. If you sync the tab to audio, and then edit the audio afterward by inserting silence to the beginning, it will no longer be in sync with the tab. You can click and drag the first beat marker in EOF (or manually adjust the delay value in Song>Properties, which is measured in milliseconds) to sync it up again. If you insert silence before you sync the GPA file, this shouldn't be an issue you need to correct for after importing it into EOF.
  4. The input method only affects how you place/remove notes in the chart, it won't change how the project's contents export to XML.
  5. I'm guessing a legato slide (pick the string once and then slide the fretting finger to another fret) is what you want.
  6. Authoring certain things requires some more complex mechanisms like "tech notes", which are basically a second set of notes where you apply various statuses/techniques to individual notes in a chord. There's a pretty thorough tutorial about their use here: http://customsforge.com/topic/890-tech-notes-tutorial-authoring-complex-bends-and-more/ Keep trying with the custom though, sometimes it takes some troubleshooting to figure out why a chart doesn't work in-game.
  7. You'll probably have to try something like placing an open B note at the next G13 note, placing a tech note on top of the first open B note and giving the tech note linknext status.
  8. Make sure you have the latest hotfix of EOF installed. Sometimes, antivirus software can interfere with programs, so whitelisting EOF may be necessary.
  9. If you find that a GP5 file doesn't import into EOF the way it's reflected in Guitar Pro 5 itself, let me know. Otherwise as mentioned, Guitar Pro's export to older versions of the format can be a bit buggy. Reporting the bugs to its developers is probably the best way to ensure it gets fixed someday.
  10. I'm not sure why it's that way, I could look into it again, but the last time I did, it wasn't obvious why it didn't work consistently. Edit: It's better now.
  11. In most cases, you're going to have to make tempo corrections throughout a chart because the musicians are not as accurate as machines. To copy multiple notes, select a range of notes by clicking one, seeking to another note, holding SHIFT and clicking that note. You can also add/remove a note to the selection by holding CTRL when you click. There are also many other selection/deselection functions in the Edit>Selection menu.
  12. Due to some requirements for handshapes in EOF (reflecting the almost universal usage of them in Rocksmith), making a handshape for a single note will involve using ghost notes (which won't affect gameplay). Place a gem AFTER the single note in question, with it being the only note selected, use "Note>Pro guitar>Toggle ghost" (or press CTRL+G) and the note's fret value will be put in parentheses. Select that ghost note and the single note for which you wanted to add the handshape and use Note>Rocksmith>Handshape>Mark (or press CTRL+SHIFT+H). A blue rectangle will be drawn across the span of the notes in the new handshape and the single note will have a ghost note added to it because as per common Rocksmith usage, handshapes apply to chords and not single notes. If you want to control which finger the handshape says to play the single note with, you can select the note and use "Note>Rocksmigh>Edit frets/fingering" (or press F) and define the finger number in the finger field for the string having the played note. The values range from 0 (for thumb, you can also use the letter T) to 4 (pinky). As far as alternatives, there aren't really any. Even for authoring pro guitar in Rock Band 3, there was only one user created editor apart from EOF, developed by ZiggyXNAMVP ( It hasn't had any code changes in about 6.5 years though, and there's probably not much of any usage guides or videos for it. Rocksmith authoring is reasonably complicated, you're going to want to read some of the guides and probably watch some videos as it's not something you can reasonably learn from scratch without many complications. You can also skim through EOF's pro guitar authoring tutorial in the Help menu. It pertains to Rock Band 3, but much of it is relevant to Rocksmith authoring. If you get stuck you can also pop into the CustomsForge Discord: https://discord.gg/cf
  13. Generally, EOF selects whichever the "default" MIDI device is in the OS, but I don't know how that would be defined in *nux. From some Googling it sounds like a limitation with Allegro and the distro's sound system. The top post at https://bugs.launchpad.net/ubuntu/+source/overgod/+bug/311833 suggests you may be able to just define a symlink so midiC0D0 points to your correct sound device name. May be worth a try.
  14. Did you ask the developer for a link to download the old version?
  15. You need to legitimately buy the software, in which case the developer of the software can provide support.
  16. After troubleshooting this in the Allegro IRC channel for a while, it seems this is a problem with how Allegro is defined in Arch Linux's package manager or something like that. I was told that you can install asp, then do "asp checkout allegro4", then do "makepkg -si" to properly build Allegro 4 and then it should work better when you build EOF. Ie. these steps: sudo pacman -S asp; asp checkout allegro4; cd allegro4/repos/community-x86_64/; makepkg -si
  17. By any chance would you have enough time to kill to try to debug where the crash is occurring (ie. set a breakpoint within set_window_title() and step through until the system driver eventually gets called? This would probably involve re-building with the -ggdb option so GDB can work fully when debugging it.
  18. I'm not sure why GCC with the same compiler and linker options would result in a crashy executable in one Linux distro and a normal executable in another.
  19. @@Mricco89 EOF can't open GPX files, you'll need to have Guitar Pro export them as GP5 files. If you don't have the Guitar Pro program, you can use the free Tux Guitar program (http://www.tuxguitar.com.ar/) to do so. @@Kicker0429 If it's crashing in one of Allegro's functions, there's nothing I can directly do about it. EOF is only calling set_window_title() with constant strings or with arrays with properly-formed C strings. It cannot be getting called with a NULL pointer or anything like that. You might try changing the makefile to build without optimization and see if that gets rid of the problem, then we can work from there.
  20. I'm still guessing it's a GCC issue with it behaving differently than on other platforms. That compiler warning in Append() looks like another false positive. It might not be understanding my malloc_err() wrapper function that guarantees the string is large enough to append the two input strings together. I guess you could check eof_log.txt and see how far it gets. You could also open eof.cfg when EOF isn't running and change the eof_log_level value to 2 or 3 to increase the amount of logging performed and possibly better identify how far the program gets before entering the normal loop waiting for user input.
  21. That first warning is technically true in terms of code style, but it's ultimately a false positive since the destination buffer (eof_chord_shape[num_eof_chord_shapes].name) is in fact allocated to store strlen(name) + 1 bytes nine lines of code earlier. I'll adjust that line to better reflect this and sooth the compiler's warning. The second series of warnings about strncpy seem like they're all false positives. Almost like the compiler doesn't know what strncpy() really is, since it guarantees no overflow when the last parameter specifies a size that isn't larger than the first parameter's buffer size. And the string being copied into the destination buffer is never larger than 2 characters while the destination buffer can accommodate 5 characters. So those compiler warnings are not relevant, but it's weird that a segfault is happening. I've been sticking to an older version of MinGW since at some point the gcc compiler had a drastic optimization change where it could remove NULL pointer checks depending on code style. You might try adding the -fno-delete-null-pointer-checks compiler flag to see if that helps. Otherwise I haven't tested this in Linux in a while but the last time I did in Ubuntu it did not crash on launch. Also, the line numbers cited in the warnings seem wildly different from the line numbers in the current version of the source code. Are you building off the latest git version of it?
  22. Keep in mind that MIDI import is meant to import a rhythm game MIDI, not a generic MIDI file, although you can import the time signatures and tempo changes. You're going to want to import a Guitar Pro file instead in order to bring the tablature into EOF. That error is not a problem with MIDI import specifically, but a problem with where EOF is installed or third party software interfering with EOF (ie. antivirus or cloud syncing programs).
  23. There's no harmonies support in EOF. It's been on the to-do list for a while, but so have a great number of things. I'll basically never run out of features to work on.
  24. I have nothing against it. Knock yourself out.
  25. The "Makefile" file isn't one I ever use. The only one I've ever tested in *nix is makefile.linux in the /src folder. I've updated the link in the Wiki article.
×
×
  • 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