raynebc

I can push as many code commits as I want, it's completely simple. Sometimes there are several commits between hotfixes. My making fewer, larger commits is a personal preference to keep the revision number from bloating up too quickly instead of a reflection on how easy or difficult SVN is to use.

The toolkit will want the XML files EOF created, and that is the chart data that DDC will be working with. The "Lock tempo map" feature only affects the project while you have it open in EOF, it won't have any effect on DDC.

I had to re-post the hotfix because I forgot to include the updated eof.dat file, which has a new font glyph for the "stop" status.

In the new EOF hotfix, you can use stop tech notes to author cstewart's example: http://i15.photobucket.com/albums/a354/raynebc/linknextwithstoptechnotes_zps8b48e431.jpg The linkNext status will still be applied to the notes on the G string to ensure that it is played as a single long note that slides from fret 4 to 6 and then back to 4 before being picked a second time at the end of the example. Stop tech notes are placed at the start position of the open notes on the A string, which will force them to export with no sustain at all. The new linkNext handling will ensure that the chords are exported properly as single notes instead of chords. In theory, this should work absolutely as expected, without any uncertainty as with last time. Here's what the XML looks like: <note time="0.250" linkNext="1" accent="0" bend="0" fret="4" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="6" string="3" sustain="0.247" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <note time="0.500" linkNext="0" accent="0" bend="0" fret="0" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="1" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <note time="0.500" linkNext="1" accent="0" bend="0" fret="6" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="3" sustain="0.497" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <note time="1.000" linkNext="0" accent="0" bend="0" fret="0" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="1" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <note time="1.000" linkNext="1" accent="0" bend="0" fret="6" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="3" sustain="0.247" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <note time="1.250" linkNext="1" accent="0" bend="0" fret="6" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="4" string="3" sustain="0.247" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <note time="1.500" linkNext="0" accent="0" bend="0" fret="0" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="1" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <note time="1.500" linkNext="0" accent="0" bend="0" fret="4" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="3" sustain="0.247" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <note time="1.750" linkNext="0" accent="0" bend="0" fret="4" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="3" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/>

Hi, folks. The latest hotfix (r1300) is in the first post. Changes are as follows: *Improved GP import to ignore section markers with no name instead of importing them as text events. *Improved handling of linkNext tech notes so that they will cause a chord that follows to be exported as single notes, just as when normal notes have linkNext status applied. *Changed GP import logic so that whether a tremolo phrase imports to be specific to the active track difficulty depends on if the "GP import replaces active track" preference is disabled or if the track's difficulty limit has been removed. If either of those conditions is true, the tremolo phrase is made difficulty specific (Rocksmith style tremolo authoring) and will only be visible when the track difficulty limit is not in effect. Otherwise the phrase applies to all track difficulties (Rock Band 3 style tremolo authoring). *Added a new "stop" status that can be applied to tech notes. A stop tech note defines the end position of the affected string of the note it overlaps, allowing you to author chords with notes that have different lengths. If the stop tech note is at the start position of the note it affects, that note is exported with no sustain.

You don't have to manually sync every single beat marker unless the musicians are really that far out of tempo at a certain part of the song, usually you can do alright by just syncing one beat marker every measure or two for most of the song. Also, adding leading silence isn't necessary unless the guitar/bass part of the song begins RIGHT at the beginning and the player wouldn't get at least a couple seconds of warning before the notes are reached when they start the song.

It can make things easier to do it that way, but the often a note is auto-adjusted by moving a beat, the more out of sync it can potentially get (since they are stored in whole milliseconds and beats are stored with higher precision). Syncing the beats and then importing the tab makes it easier to avoid that, but even then it's nothing a resnap couldn't fix.

I'll take a look at it. The way EOF calculates the beat timings makes the negative timestamps a bit troublesome, but I'll see what can be done. The timing is probably corrected at the first non negative sync point. I often work on several things before I commit the changes, but the next revision will probably be up very soon. I wanted to get the stop tech note status implemented first. I'll have to try it myself to see. I'll look into it.

The phrases are optional, DDC will create them on its own if you don't, but if you place them you may be able to get better control over how the difficulty levels are created. The sections are required to be hand-placed though, and you would do that before using DDC. To do so in EOF, just click on the beat marker where one should go (ie. the first beat in a verse) and use the function in the Beat>Rocksmith menu to place an "RS section" (or press the given keyboard shortcut) with the appropriate text (ie. "verse"). When you synchronize tablature that you import, the best method is to click and drag the beat markers (-->) to line up with the drummer, which is better than syncing to a guitarist because the drums will be more consistent among all of the guitar/bass parts of the song. When you move beat markers, the notes will be automatically adjusted as long as you don't disable that feature in the preferences. To use DDC you should just have to author a single-difficulty chart with sections. It will create DD (dynamic difficulties) for you.

I can't make any guarantees, but if you can send me an example GPA file that has a negative timestamp, I'll see if there's a good way for EOF to handle that. If not, I can ensure EOF complains about it more overtly.

This is kind of a "wish list" item I have, but it would take so much work it's not likely that it will get added. There's a preference that has the existing 3D preview window more closely reflect how the notes and chords will export to Rocksmith, ie. it will display which chords show up as repeat lines.

Double post because the forum didn't seem to allow me to make a big post with this included with the previous one: There is no good way to make that maximize button work, complications involved with the Allegro game library that EOF uses. I haven't seen a way to have the x2 feature crash. Are you sure the program crashes or EOF just says that it couldn't set the display size and it reverts back? Your computer's screen resolution will have to actually be big enough to fit the entire EOF window or else EOF won't be able to set the window size and will revert to the previous size. You may have to set the default screen size of 640x480 and go from there, trying to set the x2 zoom, then trying to set a custom window width to use up more room on your screen. There's also no easy way to do this. EOF isn't developed with graphical libraries that make this sort of thing easy. That said, you can enable the secondary piano roll, which would allow you to display the regular notes in the bottom piano roll and the tech notes in the top one. This is intentional behavior. You won't be able to play back the audio in two different EOF instances at the same time, unless you're using multiple computers or something. If you wanted though, you could load a different OGG file as the chart audio (File>Load OGG) and play the chart back, so you can see what the tablature would look like with that audio. The tutorial covers the foundational concepts of working with and manipulating notes, and the pro guitar tutorial covers the jump into real guitar arrangements. Those two should get you started.

The standard behavior for chords with slide technique in EOF is for all of the fretted notes to slide the same number of frets. You would have to use tech notes to manually set the end slide position of strings if you wanted to override this. I'm not sure if there's a good way to "fake" authoring something like this in Guitar Pro or TuxGuitar, it would probably be more complicated than just adding the arpeggio notation in EOF. Like what? The biggest one I can think of right now is that as of the current revision, EOF won't allow you to define a chord where the strings have different sustain lengths. I'm working on another status that will allow you to place tech notes to define the stop position of individual strings in a chord. I suppose with things like grace notes or trills, Guitar Pro doens't define the notes you hear during playback in the tab, they're just techniques that are applied. I'd prefer not to have EOF add notes that aren't explicitly defined. Just what's in the EOF manual. You set the capo position and then EOF handles the rest. This is most likely the option to ignore the tuning/capo setting that forces chords to be named as if the guitar was in standard tuning with no capo. Some musicians prefer this. If you see the C=# indication at the left edge of the piano roll, then the capo is in effect. I'd probably have to see the XML file, it may not be correct.

You can't turn off the chord name lookup, it is a mandatory feature of pro guitar/bass tracks because of requirements in Rock Band 3. If you want, you can just name all notes with one space character " " and then just manually define names for chords as desired.

If you can post the XML, GP and audio files I'll take a look at it.

Do you mean the bar graph at the top of the screen? That might not work correctly unless the chart has dynamic difficulties authored, otherwise it will just look like a rectangle (all phrases/sections have the same maximum difficulty level).

"Named" is whenever the difficulty limit has not been removed. If you remove the difficulty limit, "Amazing" difficulty becomes difficulty number 3, and the imported tremolo phrase will be visible. I had to make this phrase type able to applied to an individual difficulty instead of the entire track because that's how Rocksmith allows it to be used. In Rock Band, phrases like that apply to the same time range of all difficulties in the track. I don't understand the question. Rocksmith doesn't support that as a specific techniq, you'd have to author all of the hammer ons and pull offs manually. Guitar Pro allows you to author these as slides into or out of a note. However, since Rocksmith requires more information than that (ie. the end position of the slide), EOF has to put something in there so it will default to one fret in the appropriate direction if the position is not given. I'm not aware of any. If anybody identifies a relevant technique EOF has missed, let me know. In Guitar Pro, you can select a note/chord and use the Effects>Slide menu to specify that the note/chord slides in from above/below or to slide out and upwards/downwards. This is the equivalent of unpitched slides in Rocksmith. However since Rocksmith doesn't support an unpitched slide in, EOF converts that as a slide from a lower note.

Seems to be related to the toolkit instead of EOF. Renaming/moving.

EOF is actually importing that as a difficulty-specific phrase, ie. it won't show up when the difficulty limit is in effect (ie. the difficulties are named instead of numbered), but if you remove the difficulty limit, it should show up. I'm not sure if it would be better or worse to change this behavior, it depends entirely on how the author is using GP files, some author each difficulty in Guitar Pro, some author only the full transcription. Ghost notes should import from GP files, but they will not export to XML because it's not a supported technique. Grace notes don't import from GP files, but that's not a supported technique in RS either. Without checking all of them right now, I'm pretty sure just about every technique that Rocksmith supports is imported from GP files. That is expected behavior. CTRL+X indicates all strings are muted and have no specific fret value. You can use the "Toggle string mute" function (SHIFT+X) to preserve the fret values of the note. It probably isn't something I'd be able to get around to doing for a while. The to do list is pretty huge.

The lag in the MIDI tones option depends a lot on your computer, you can try changing the "MIDI Tone Delay" in File>Settings, but it's pretty much guaranteed to never sync as well as the metronome and clap sound cues.

Hi, folks. The latest hotfix (r1299) is in the first post. Changes are as follows: *Improved RS2 export to support sustain tech notes. *Fixed a crash that could occur when performing a chord name lookup on a fully string muted chord. *Updated the "Correct chord fingering" function to alter the regular notes instead of tech notes. *Disabled the ability to apply fret or finger definitions for tech notes, since they don't use those values. *Fixed a bug where tech view wasn't disabled when importing a Guitar Pro track, which would cause the import to malfunction. *Updated Guitar Pro import to create tech notes for any complex bends defined in the imported track. In an effort to enrage the community, I have gone back to SendSpace. But really, MediaFire wasn't working right in the current stable release of Firefox, and the download counter doesn't work so that's two strikes against it, I'll round up to three just because I already disliked it. Plans for hosting EOF on something besides SendSpace are in the works.

I don't understand what you mean. Could you provide a Guitar Pro file whose phrases/sections import incorrectly? Go into File>Preferences an enable the option to save separate Rocksmith 2 files. Showlights XML files are not created anymore, the toolkit does that.

It looks like you authored the arrangement without a capo and then just changed the capo value in the toolkit, doing that won't work correctly. You need to define the capo in EOF because then the fret values will be increased accordingly. Even though EOF treats the capo position as the nut, Rocksmith does not, it expects the absolute fret numbers for each note and not those that are relative to the capo position. GetTheLedOut is right, it is actually EOF's chord lookup that defines the name of each chord, Rocksmith has no known built-in capability to do that. Calling the open E chord shape an A chord when there's a capo on fret 5 is musically accurate, but some musicians prefer to designate the chord shape as if there was no capo at all since that's easier. EOF will allow you to get this behavior by using "Track>Pro guitar>Ignore tuning/capo". It will then disregard the tuning and capo and name all chords as if the arrangement was in standard tuning with no capo.

EOF wants to put the default intro RS section where you defined that other section. If you only have one section in the whole arrangement, it may be better to use the "intro" section over any of the other ones.

Or you can just create an entirely silent audio file, such as in Audacity, and use that as the chart audio in EOF.