raynebc

You can also use a tech note:
http://i15.photobucket.com/albums/a354/raynebc/chord%20with%20hopo_zpsn1vb0aic.jpg
 
The resulting XML shows that only the one note in the chord is marked with hammer on:

<chords count="2"> <chord time="1.125" linkNext="0" accent="0" chordId="0" fretHandMute="0" highDensity="0" ignore="0" palmMute="0" hopo="0" strum="down"> <chordNote time="1.125" linkNext="0" accent="0" bend="0" fret="1" 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"/> <chordNote time="1.125" linkNext="0" accent="0" bend="0" fret="2" hammerOn="1" harmonic="0" hopo="1" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="2" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <chordNote time="1.125" linkNext="0" accent="0" bend="0" fret="3" 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"/> </chord> <chord time="1.625" linkNext="0" accent="0" chordId="1" fretHandMute="0" highDensity="0" ignore="0" palmMute="0" hopo="0" strum="down"> <chordNote time="1.625" linkNext="0" accent="0" bend="0" fret="1" 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"/> <chordNote time="1.625" linkNext="0" accent="0" bend="0" fret="3" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="2" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <chordNote time="1.625" linkNext="0" accent="0" bend="0" fret="3" 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"/> </chord>

You must be using a version of EOF more than a month old. Old versions of EOF would make a fret value X (string muted) if you entered a fret value that was higher than the track's fret limit (Track>Pro guitar>Set number of frets/strings). Current hotfixes will automatically ask if you want it to increase the fret limit of a track if you input a fret value that is too high.

It's an EOF bug regarding downward slides. EOF is supposed to determine how many frets the slide "moves" by comparing the lowest used fret in the note/chord with the end of slide position. It was instead looking at the lowest used string's fret value.
 
So basically EOF was looking at the 16-18 double stop that unpitched slides to fret 1 and it figured that the chord slides down 17 frets (18 - 1 = 17), but applying this difference to the fret 16 note in that double stop caused the fret value to go to -1 (which is written as 255 when the number is interpreted as a non-negative number).
 
I've fixed this madness so that it works the way I intended: End of slide positions refer to where the finger holding the note's lowest fret ends up.

You can use "Track>Rocksmith>Fret hand positions>List" (or simply press CTRL+SHIFT+F) to bring up a list of all positions in the current track difficulty and generate/wipe them one track difficulty at a time or if you want to regenerate for all difficulties in the current track, you can use "Track>Rocksmith>Fret hand positions>Generate all diffs".

Thanks, I've fixed this. It looks like it would only happen if the base chord in an arpeggio/handshape had more than one non ghosted gem. As far as "previous_save" being appended during each save, this would probably only happen if you are opening the previous_save backup each time you load your project (meaning you are editing an old version of the project). The next hotfix changes the file extension of project backup saves, so it will be hard for people to do this on accident.

You would use "Track>Pro guitar>Set capo" and then change the fretting as appropriate. There's a trick where you can use "Track>Pro guitar>Set tuning" and tune up by the number of frets that represents the capo position, allow EOF to transpose the notes in the track, then go back and set the tuning back to what it was (and not have it transpose the notes this second time). If any notes were played open or using a fret lower than the capo position you'll have to figure out how to change those manually, and EOF will have highlighted such notes if you let it tranpose notes during the first tuning change step.

To remove dynamic difficulties in EOF, you'd want to go to the highest populated difficulty (the highest number that has an * on the tab) and use "Track>Rocksmith>Flatten this difficulty". The default distance for merging notes is probably fine unless the chart has some sync errors. Then on each of the lower difficulties, use "Track>Delete active difficulty" until you are left with the full arrangement (flattened difficulty) as the lowest difficulty level. You can then recreate any sections how you want them to be. DDC will add phrases automatically, but you can add those manually if you prefer.

Track>Pro guitar>Set capo

EOF has a function that removes the top-most gem on selected chords (Note>Simplify chords). You should be able to select all notes after you pasted them into the bass track and use this function 5 times to get the desired effect. You can then use the "Note>Pro guitar>Remove palm muting" function to remove that technique from selected notes.
 
It's not as quick as a 1 click function, but should be quick enough (15 seconds or less). I tend to prefer functions that have a less specific effect, so they can be used in different combinations to perform the greatest variety of tasks.

The short answer is probably no, unless somebody else writes that program logic. In the mean time, you can use Shrubbery's Tux Guitar build, which has GPX support:
http://customsforge.com/topic/2235-guitar-pro-5/?do=findComment&comment=11971
 
You can then simply open the GPX file in Tux Guitar, save it as GP5 and use it in EOF.

There are lots of good threads in the tutorials section:
http://customsforge.com/forum/78-tutorials/
 
Here are some that I picked out by skimming thread names:
http://customsforge.com/topic/11242-how-to-get-dynamic-difficulty-work-like-official-dlc-by-using-catalog-and-phrases/
http://customsforge.com/topic/10520-creating-cdlc-tutorial-making-sections/
http://customsforge.com/topic/856-tutorial-for-proper-gp-tab-sync-sectionphrase-authoring-and-more/

After some thought, I'm leaning toward making it a global preference. It would be easy for people to turn that preference on before a GP import and turn it off again if they wanted.

If you're using the Windows build, it's built in automatically. If you're using Mac, you can install the "EOF utilities" package in the EOF thread's first post. If you're using *nix, it should be about the same as installing any other package from source distributions or what not.

Did you set the tuning to drop D in EOF (Track>Pro guitar>Set tuning)? For drop D, you'd just need to change the tuning value of string 6 to -2 (down two half steps) and EOF should say "Drop D tuning" in the dialog to confirm this is a known tuning, then click OK. EOF will offer to transpose the fret numbers for notes already in the track, but if they were already authored with drop D in mind, just decline this offer. Then all you need to do is save the project again and the XML file will reflect drop D tuning. Then you would have to recreate the custom song package in the toolkit, and it should be ready to go.

You could import the first GP track into one track in EOF (ie. PART REAL_GUITAR). Then for each of the other GP tracks:
1. Import into a separate EOF track (ie. PART REAL_GUITAR_22).
2. Seek to the first imported note in that track (CTRL+Home).
3. Select all notes and copy to clipboard (CTRL+A, CTRL+C).
4. Without seeking, change to the track where you imported the first guitar part (ie. PART REAL_GUITAR).
5. Paste the notes (CTRL+V).
6. If the imported track (back in PART REAL_GUITAR_22) has tech notes (the difficulty tab would have (*), you can enable tech view with F4 and repeat steps 2 through 4, just also enable tech view for the track you're pasting the notes into. Keep in mind the next EOF hotfix will fix a bug related to pasting notes in tech view.
7. You may have to recreate some things that won't copy/paste with the notes, such as tremolo sections. You can enable the secondary piano roll Shift+Enter and set it so you can see both tracks at the same time to recreate anything that's missing (use CTRL+Enter to swap between editing the first and secondary piano roll, the one that is available to edit is always displayed on top).
 
Tone changes are placed (on a per-track basis) by seeking to the desired part of the chart (ie. at/before where the different guitar part comes in) and using "Track>Rocksmith>Tone change>Add". You can use the "List" function in that menu to get an overview of where all the tone changes currently are. Also make sure to go into the "Names" function to see a list of all the tone changes in use to verify none of them are mis-spelled (If you have one called "solo" and one calld "soloo" they will be treated as different tones) and to make one of them the default (the one in effect automatically when the song begins).
 
Make sure to delete the contents of the track you're importing the guitar parts into temporarily (you can use "Track>Erase track" if you want) or EOF will create an XML file for it when you save and it probably wouldn't be one you want to use in-game since it's not a complete arrangement.

Often, the arrangement may have only had one difficulty authored so moving that to the Expert difficulty level involves inserting lower difficulty levels in front of it.  You can do this with the "Track>Rocksmith>Insert new difficulty" function and specify to insert a difficulty below the active difficulty.  Assuming only one difficulty was present after import, use the insert new difficulty function three times and then the one imported difficulty will now be the 4th difficulty (like Expert in Rock Band authoring).
 
Optionally, you can then also disable the "Track>Rocksmith>Remove difficulty limit" option to return it from numbered difficulties to named difficulties, but unless authoring certain things that's only a matter of personal preference for Rock Band authoring as it won't affect the export of the notes to MIDI.  One example of where it would matter whether you changed the difficulty limit is if you wanted to use tremolo phrases in the Rock Band chart.  In Rocksmith, this is authored on a per difficulty basis, so if you re-instate the difficulty limit, you would notice EOF would hide any tremolo phrases that were imported from the XML file.  You would have to re-author each phrase by selecting the notes that should go in the phrase and using Note>Tremolo>Mark.
 
If you want to author EMHX, you can use "Edit>Paste From" functions on each lower difficulties to copy the highest difficulty if you want, and make any edits you like to simplify the lower difficulties.  If you're authoring all difficulties, it's usually best to copy from Expert to Hard, simplify, copy Hard to Medium, simplify, copy medium to Easy and simplify that.
 
To reset the offset to zero, you can use the function of that name from the Beat menu.  Usually the option to use equal sized beats (same size as the current first beat) is usually best, but the first beat will often end up being smaller in size to fill up whatever space was left and that may cause its tempo to go outside the range Rock Band likes.  You can play around with selecting a beat and using Beat>Delete to combine two beats into one to work around that, or use the "Beat>Fix tempo for RBN" function to try to automate this process on the whole chart.
 
Then as long as the "Save separate Rock Band files" preference (File>Preferences) is enabled, EOF will create the appropriate files during save.

I took a look at it.  It's authored as a set of legato slides, so it doesn't surprise me that EOF would have removed the note that follows the slide.  This was behavior that was programmed before the linknext status was implemented in EOF.  I agree with you that it's probably more accurate for it to keep the note and mark the previous note (the one with the slide status) with linknext status.  I'll work on adding this change.

Yes, the user has to define the tones themselves in the toolkit.

Try it in the latest EOF hotfix, it should be working better now.

One of the leading silence options is to "pad" the leading silence to a certain amount. For example, you can pad it to 4 beats then reset the offset and it will fill the gap in with beats of the same tempo. If you do this, it's better to use the re-encode leading silence option though, because stream copy doesn't give to-the-millisecond precision and you can end up with one tiny beat after this process.

There's not really a single easiest way of doing this, it's the most tedious part of authoring. You can try:
 
*Using Sonic Visualizer to estimate the beat map (details are in the "Menu functions>File>Sonic Visualizer Import" section of EOF's manual).
*Using Go PlayAlong to synchronize the tablature with the audio (this isn't a free feature of the program though, but the demo functionality should let you decide if you think it's worth buying).
*Enabling EOF's waveform graph (F5) and using the peaks in the audio to help you find where the snare drum hits are. Typically beat lines should line up with the beginning of the normal on-beat snare and bass drum hits. Enabling EOF's metronome (M key) and playing back the chart (Spacebar) will help you tell if the ticking is in rhythm with the song. You can also enable the claps feature (C key) so that playback will also make a clap noise each time a guitar/bass note is reached and that can help you tell if the notes are positioned correctly.
 
There are various tutorials around the forum that should discuss one or more of these types of methods.

The last hotfix did make such a change. Before, you could just move the mouse over an input field and it would give that field focus, now it requires a click. It wasn't intended to make it so that no fields have focus when a dialog is launched though, so I'm going to try to figure out how to fix that.

After studying the GP5 spec a little it seems I can determine which instrument type the user selected for each track (ie. "Distortion Guitar" or "Electric Bass (pick)"). I think I can add some logic to offer to change the arrangement type from/to bass without too much difficulty.

The issue was that the file was encoded with a Unicode mechanism called a Byte Order Marker (BOM), which is basically a sequence of 3 bytes at the beginning of the file. The next EOF hotfix will check for and ignore this sequence, but until then you can fix the lyric file by saving it in a text editor with no BOM (Windows Notepad ought to do the trick if you save it as ANSI instead of Unicode, or you can use a more fully-featured text editor like EditPad Lite or Notepad++ to save as UTF-8 without the BOM).

Same as the previous post. If you send me the Go PlayAlong XML file and the Guitar Pro file I'll see if I can find the problem.