raynebc

You can name tones pretty much anything you want, provided you only use regular ASCII characters (ie. avoid accented or Unicode characters). You need to author tone changes referring to at least two different tone names, otherwise the arrangement only uses one tone and no tone changes are really needed, the one tone would just need to be defined in the toolkit. If your arrangement does use multiple tones, one has to be specified as the default, which means it will be in effect automatically when the song begins. The issue where tones stop working is usually involved with one or more tones not being correctly defined in the toolkit. For lyrics, EOF has a vocal tutorial in the help menu. You can also import various lyric formats in the File menu. For Rocksmith, most people seem to prefer a lyric editor called "Ultrastar Creator". You don't need to worry about setting vocal pitches for the lyrics, this information isn't used in a meaningful way in Rocksmith 2014. Just the timing of each lyric is important, as well as defining the "lyric lines" (the start and end position of each line of lyrics) since Rocksmith 2014 displays lyrics one line at a time compared to just scrolling them from start to finish like in the first Rocksmith game. The warning messages mean exactly what they say. Typically, there is a sort of default phrase and section that are usually in official charts. EOF will try to place these where they would normally go, but if you have defined other phrases or lyrics on those beats, EOF warns they won't export properly because only one phrase and one section can be in effect on a beat. You can ignore the warnings if they don't cause problems in-game, maybe Rocksmith 2014 has less need for them than Rocksmith 1, but I haven't had any requests to change the behavior so I'm just assuming they should still be included with every chart. Rocksmith events were used in Rocksmith 1, but I don't know if they are well supported in Rocksmith 2014.

The toolkit is no longer writing timestamps to three decimal places. That's not numerically wrong, but it's inconsistent with official lessons and charts. I'll add handling for this.

Until then, all you should have to do in order for EOF to import the XML file is to add count="1"inside the tag. The number could really be any valid whole number greater than 0, EOF doesn't do anything with that attribute except ensure that it's there and defines a number of beats greater than 0.

If the toolkit doesn't require the count attribute, I'll have EOF not require it during import since it doesn't care what the count is anyway. I'll still have it export that attribute though.

The beat timing format hasn't changed between RS1 and RS2, you would want to compare those between the original and unpacked XML files.

http://www.theriffrepeater.com/rocksmith-2014-dlc-311-singles-female-fronted-bands-heart-flyleaf-halestorm/

I opened it in Guitar Pro 5, and no repeats are shown to be authored into the file. Would you please double check that it shows up for you in the actual file?

The EOF thread has a Mac release. It has the latest release candidate, but the Mac binary doesn't get updated as often though since I only use Windows, so I have to bug the other EOF developer to build EOF for Mac.

Usually all I need is the .eof file. If you send it to me, please send some details about the issue and how to reproduce it.

Depending on what we can make work, you may want to author it as an arpeggio instead. With arpeggios, I imagine it's often implied that each note rings out until another note on the same string is played.

If you send me the GP file I can look into it.

The EOF releases thread includes a Mac installer for tools to decode MP3 (LAME) and encode OGG (oggenc). If you want to use the "stream copy" leading silence feature, you also have to put the Oggcat program in EOF's program folder. Oggcat is part of the OGG Video tools (http://www.streamnik.de/files.html), but they don't provide Mac binaries so you'd have to build it from source or find it someplace. This depends on the notes you are pasting. If you are pasting notes so that the first note goes on a beat line, you can skip the grid snap seeking functions and just seek by beat marker (Pg up and Pg dn) instead.

It's not that they're too close together, the way EOF is writing that to XML may not be something Rocksmith supports, I posted to an ongoing ticket about it to see what the toolkit developers think. I may have to have EOF do something more unusual here and convert the multiple linked notes into a one long single note if they overlap any other notes, just so it will work in-game.

Looking at the full XML file you sent me, it looks like I'd expect: I think it would be up to the toolkit developers to say if Rocksmith is unable to display that example properly. I think they'd mentioned that Rocksmith doesn't like two single notes that start at the same position, and if they can confirm that, I may be able to come up with a workround (ie. if a chord is broken up into single notes because the previous note had linknext status, the linked chordnotes can be moved by a millisecond or so so that the broken up chord notes are at different timestamps).

Hi, folks. The latest hotfix (r1304) is in the first post. Changes are as follows: *Fixed a bug that could cause alternate endings to not import. *Improved the "Edit bend strength" dialog to start with the input focus on the bend strength field. *Improved the "Seek to beat/measure" dialog to empty the number field when launched and fixed a minor issue where escape may have to be pressed multiple times to cancel the dialog. *Fixed a bug where tempo changes that lead to some of the chart running past the end of the chart audio caused such content to get removed from the project. *Fixed a bug with RS2 export where linknext status didn't force chordnotes to keep their chord's defined sustain length unless the chordnote also had bend or slide status. *Fixed a bug where keyboard input from various dialog windows or prompts could leak and activate other keyboard shortcuts after the dialog was closed. *Fixed a crash that would occur if a track had more tech notes than regular notes. *Fixed a bug where auto-adjust would lose the manually defined name of affected notes and the text of lyric entries. As a side effect, this would cause pitchless lyrics to be deleted because a lyric with both no text and no pitch is discarded. *Fixed bugs with Feedback input mode where the "edit pro guitar note" and "edit frets/fingering" dialogs couldn't be launched for the note at the seek position without explicitly selecting the note first. *Fixed a bug with Feedback import where if a note began at the same position as a star power phrase, it could combine with the previous note instead of being imported as a separate note.

The error message was wrong (I've fixed it), it's actually about the tag. The "count" attribute is not there even though it's required. Do you find that ALL custom songs you unpack with the toolkit have this defect? If so, it's probably a bug with the toolkit, in which case would you please open a new issue about it here?https://github.com/rscustom/rocksmith-custom-song-toolkit/issues

Shrubbery recently built the latest version of TuxGuitar from source and posted it on the forum: http://customsforge.com/topic/2235-guitar-pro-5/?do=findComment&comment=11971 I tried it out and it converted a GPX file to GP5 perfectly. I think the only catch is that you may have to have Java installed on your computer.

I've fixed this issue.

The XML looks incomplete, I'd probably have to have the project file in order to test with it. On the first 9-9 double stop in the picture, the note on the G string won't sustain because it doesn't have the sustain status applied to it, the tech note only adds that status to the B string. You can apply the sustain status to the regular chord instead of with tech notes. The same issue applies to second to last chord in the picture.

That's expected behavior at this time. Having copy examine the tech notes affecting the copied notes is kind of like having the delete function remove both, or clicking and dragging a note move both. There are several functions that would have to be changed to allow all of that to happen.

This kind of thing could get complicated fast. At a bare minimum are chord names, then what fingering to use, then what fret and string the chord is at. EOF can't properly compete with a program that is designed for creating guitar tablature and nothing else, when you compare some of the really specialized features like the chord creator in Guitar Pro.

You can author chords inside of an arpeggio and EOF will export them as single notes. I've been told that Rocksmith doesn't like having multiple single notes authored at the same position in some cases, but I don't know if that would apply to arpeggios or not, since that's how official arpeggios seem to be authored (the chord at the beginning of the arpeggio is authored as single notes at the start position of the arpeggio hand shape instance).

I guess I'd have to see the project file in order to tell what was going on. Depending on how it was authored, each chord being displayed as a chord box could be expected behavior.

I could probably do something like that, but maybe only if the difficulty limit for the track has been removed and the difficulties are displayed by number instead of by name. The difficulty tabs themselves aren't wide enough (ie. "(*Supaeasy)" would go over the edge of the tab). If I went with just displaying this for the numbered difficulties, it could go something like "*1(*)" for a difficulty that had both regular and normal notes or "1(*)" for a difficulty that only had tech notes. How does that sound? I couldn't reproduce this. If you find a way to do so, please let me know. I don't know if I'd want to implement this, at least not without making it a user preference. If you wanted to remove everything in a track difficulty, the "Erase track difficulty" function is more suitable.

I'll leave the popup export logic in EOF alone, pending any further progress with this. If you find they should export to XML differently than they do now, let me know.