raynebc

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.

It shouldn't matter where the tech note is on the tail unless you are applying bend or stop status. Both notes are at the same timestamp, I'm guessing it's a side effect of Rocksmith's display system that it looks like they are at different timestamps because one note is drawn higher (vertically) than the other one. Next hotfix will correct a bug so that linknext will also cause the chordnote's sustain to export. Otherwise you will probably have to apply sustain status to the first chord until then. You can assign as many statuses with one tech note that you want. It's hard to tell what's going on in the pictures, but I don't know why there's a chord box in there. That shouldn't be in the XML file since linknext will remove the chords and replace them with single notes. Applying the sustain status to the first chord should correct the sustains being missing on the first notes.

Looks like it's only available in Javascript or .NET, I wouldn't know where to start to try to integrate it with EOF.

The fret values of tech notes are ignored completely, you don't have to change any of those unless you have that dialog open and want to expand the tech note to include any other strings at that time stamp. In the previous example, hammer on was applied with a tech note, because if you applied it to the 11-9-9 chord, that technique could end up being applied to the A and D strings. I don't know how that would look in-game considering the notes are linked to the previous ones on those strings. The example in your last post looks like it will work to make a regular sustain on the B string that coincides with a note on the G string that hammers on and them pulls off.

"Select like" only compares the fret values and strings used, so "fret 8 on the E string" and "fret 8 on the E string that also slides" would both be considered a match. "Precise select like" requires the techniques to be the same, so "fret 8 on the E string" and "fret 8 on the E string that also slides" would be considered different. The paste issue you're talking about isn't a problem with paste, it's the behavior of clicking and dragging multiple notes across tempo changes. All notes are moved the same number of milliseconds instead of each one being grid snapped, so notes will fall out of grid snap when you do this. That's why you need to seek to the appropriate position before pasting in order to avoid this. There's a resnap command in the Note menu (and a shortcut is given), but this function can be destructive and should be used carefully: If two notes are moved to the same grid snap position during resnapping, they are merged (EOF will warn you if this happens, so you can undo the operation). Or if the grid snap value you have is too large (small denominator value), notes may snap to a position that you don't want simply because they're closer to that grid snap based on the current grid snap value. About the key list, it's a text file that EOF displays in a simple text box. You can open it up in a text editor or program of your choosing though, it's the keys.txt file in EOF's bin folder. If I ever have enough spare time to come up with a master list of all keyboard shortcuts, I'll probably make it an HTML help file that launches in your default web browser, and that would allow the best formatting.

EOF is probably a long way from proper Unicode lyric support, so definitely don't wait on it if you are able to build that functionality.

There are no shortcuts for this, I couldn't come up with any available ones that would make sense. All left/right/up/down/Pg up/Pg dn related keyboard shortcuts are in use. You can bring up lists of phrases or sections and use those the included seek controls though. If you can come up with any I could see if they are available for such functions, otherwise I'd just have to add them to the menu without them. "Track>Rocksmith>Manage RS phrases" (CTRL+SHIFT+M) will list all phrases in the active track, and automatically select the one that the seek position is in. Keyboard focus starts in the list part of the dialog so you can immediately use the up/down arrows to go to an adjacent section and press S to seek to it, then Enter or Escape to close the dialog. "Beat>Events" will list all events, but it has a filter that can be set to show only RS sections. This function does not automatically select the one immediately at or before the seek position, but I put it on my to do list to add that capability.

It's intentional. Fully string muted chords are appended to the previous chord's handshape tag as long as there aren't any single notes separating them. You can force a string muted chord to start its own handshape by applying "crazy" status (ie. select the note and hit the 'T' key). Thanks, I'll check this out. This is expected behavior, although the grid snap setting isn't being lost, it just isn't lining up with the grid snap positions if the seek position isn't grid snapped when you perform the paste. The first note is pasted starting at where the seek position currently is, like with copying and pasting text into a document. Feedback input mode seeks based on the current grid snap, but the other input modes do not. Even then, that's why I made those seek controls available via the Pg Up and Pg Dn keys. This is the best way to provide the most flexibility to everybody. If you can verify a problem and reproduce it on demand, let me know. Fret hand positions aren't something that you can manipulate this way. Fret hand position errors would only be given if the track had some permanently stored into the project but the position wasn't considered suitable based on a chord's fretting or fingering. You would either need to delete the hand positions so they get regenerated automatically during save, or edit/generate the positions manually after changing the chords. There could be all sorts of reasons such as the toolkit not being given the updated XML files, or the new song package not replacing the old one in your Rocksmith song folder. Only if the XML file doesn't contain your changes would it be considered a bug in EOF. If you have time to spot check the XML file to see if it doesn't reflect the project, let me know if you find any discrepancies. The edit pro guitar note dialog behavior hasn't changed recently. However if you find that the XML files between the two different versions don't match even though the project file is the same, let me know.

As long as it has at least two notes left, EOF will export it as a chord. You can manually name any note to anything you like by typing the name in the edit pro guitar note menu, or if you wanted to apply the same name to several non-identical notes that are selected, you can use the "Note>Edit name" function instead. You could try placing a tech note with "Accent" status on top of the note you want to emphasize. It should cause Rocksmith to display the note larger and more brightly than the regular notes (indicating it is to be played more strongly). I posted a solution in mrmaton's thread, give it a look and let me know if that doesn't do what you're wanting. If you author regular chords in EOF, they will each display with either a chord box or a chord repeat line. In case I misunderstood what you're wanting to author from your earlier post, you may want to consider authoring an arpeggio, that way you can author just the notes that are being played and they won't show up as new chords. Here's an example:http://i15.photobucket.com/albums/a354/raynebc/arpeggiowithaccents_zpsffdffadc.jpg In this example, the note on the D string isn't played at the beginning of the arpeggio, but it is played strongly throughout the duration of the arpeggio. You could just as easily have any notes authored within the span of the arpeggio and in game it can still display with whatever chord name you define.

Interestingly, a set of steps similar to this is given in EOF's tutorial. But wow, one of my charts gets pretty crappy beat detection when using the default "Complex domain" detection function, and "Broadband energy rise" works quite a bit better for it. Do you find that it seems to work better than the other detection functions for most songs?