raynebc

If you can send me the entire log after importing the drum track and the Guitar Pro file in question, it would be helpful. Keep in mind that after the import, I don't believe it will automatically change the active track to PART DRUMS if you imported a drum track instead of a guitar track. Open Song>Track and see if PART DRUMS or PART REAL_DRUMS_PS has an asterisk next to its name (which would indicate the track has contents).

Both of those are likely problems with the naming/permissions of the folder where EOF and/or the project are located. Make sure your EOF installation is someplace with no Unicode or extended ASCII characters (ie. C:\EOF\ ) and make sure your project is not located in a write protected location (ie. within either "Program Files" folders). The eof_log.txt file may also show the reason for the failure immediately after the error(s) are given, but note that the log is overwritten every time you re-open EOF.

Short answer: You're probably wrong and shouldn't fear monger. If you want to be more productive, send the binaries to one of the few AV products that claimed it was malware and ask them to confirm it's not a false positive. If they check it manually and still consider it malware, that would have significantly more weight than an automated scan which could have flagged it just because it had a particular string of byte values.

Ever hear of a false positive? For both of those, around one tenth of the antivirus products claim to see malware, but nine times as many other antivirus products see the toolkit as clean. Several thousand people use the toolkit and don't report problems. You're going to have to draw your own conclusions about whether you'll use the toolkit, but you shouldn't take a small minority of AV products as gospel about a program's safety. Some will flag programs as suspicious for no reason other than them not being digitally signed, or for other arbitrary reasons not involving the presence of malware.

There should be an eof.cfg file in the same folder as eof.exe, that's the one with EOF's settings. The contents of the Information Panel suggest you're on a version of EOF that's over a year old though, you should probably apply the latest hotfix and then check to see whether anything still isn't working. I still have no idea what kind of Guitar Pro related message you're talking about though, or what "sctk" refers to.

If you can give more information about the message you're citing, I could give more guidance about what it's for. If EOF can't save anything, it's probably something outside of EOF interfering like antivirus or you're trying to save in a restricted portion of your file system (ie. within "Program Files"). If you installed another EOF instance, make sure you apply the hotfix. Notes will display differently depending on what they are (ie. cymbals display as triangles, forced strums display with large circles, vocal notes display as rectangles with no circles). The means of inputting notes differs depending on the input method you have in use (File>Preferences). "Piano roll" (where you use the right mouse button to toggle notes) is the default, and some but not all input methods use the right mouse button. The ability to click and drag notes can be disabled "Song>Disable click and drag", and if this is in effect, the title bar will say so. If you can provide a screen capture of EOF, and provide the eof.cfg file of the EOF instance you're having trouble with, I can point out many of these settings that may be causing the behaviors you mentioned.

As far as I know, Xenia still doesn't support microphone input, and this cable would have similar requirements.

String muted notes in general do work, there may have been something unusual with those particular ones.

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.

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.

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.

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.

I'm guessing a legato slide (pick the string once and then slide the fretting finger to another fret) is what you want.

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.

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.

Make sure you have the latest hotfix of EOF installed. Sometimes, antivirus software can interfere with programs, so whitelisting EOF may be necessary.

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.

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.

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.

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

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.

Did you ask the developer for a link to download the old version?

You need to legitimately buy the software, in which case the developer of the software can provide support.

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

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.