raynebc

If you download the tab in GP5 format, the file is corrupted and won't open in Guitar pro 5 or Tuxguitar. I tried it again before posting just to make sure.

I think ignore tech notes have a good chance of working in this scenario.

The popup messages used to work perfectly in Rocksmith 1, but I don't think it's been figured out if/how they work in Rocksmith 2014.

Based on what you describe, that looks correct for tone changes. Are they not working in-game? Did you define the settings for each tone in the toolkit?

That's because EOF doesn't support GPX (the format used in Guitar Pro 6) files. I used to recommend WebTabPlayer to convert it to GP5 format (something the free version of GP6 won't do), but that site has been broken for months now (it corrupts GP files). The development version of Tux Guitar supposedly can open and convert GPX files, but you'd have to compile it yourself since they haven't uploaded a binary for it in a long time.

If you can find a way to reproduce CTRL+F not changing back or activating another function, let me know, I can't cause such problems to happen. There's not a list of ALL keyboard commands, but eventually when keyboard shortcuts become user-definable, they'll probably be listed in one place.

Usually that means it's not really a GP5 or older file, ie. it's a GPX file. If you provide the related files (XML and Guitar Pro file) I can check it out. It already imported the tremolo phrases, but it could import them different (track-wide or difficulty specific) depending on various conditions.

Make sure you didn't put EOF in a protected location like anywhere inside either of the "Program Files" folders. Windows has a security feature that will interfere with programs' abilities to write files in such places. If you still run into problems you may have to re-extract the 1.8RC9 files, since it comes with all of the related conversion tools, maybe the ones in your EOF installation got removed or something.

Your project file has extended ASCII or Unicode characters in its file path. The lyric export uses standard C libraries which don't support those, ie. it cannot write a file named c:my_söng.txt, but it can write one called c:my_song.txt (without the umlaut). If you close EOF and rename the project file/folder so that it doesn't include such special characters (or if you move it to a folder without such characters), EOF should be able to create the lyric file.

In many cases, using automated fingering and fret hand positions should be fine, unless you want to have fine control over how something looks in-game. If you decide to permanently add some to the project though, there are a couple of things you have to take into consideration. For example, if you have Rocksmith 1 export enabled, all fretted notes have to be at or within the next (higher) three frets of the current fret hand position or else they'll draw outside the highlighted lanes and chord boxes in the game, because Rocksmith 1 doesn't allow the "anchor" size to go larger than 4 frets. Also, if you define a chord to use the index finger, EOF expects the fret hand position to reflect that (ie. don't say the fret hand position is on fret 1 if you define a power chord shape where the index is at fret 2) or else it will complain.

Although it's not the same thing as how Guitar Pro automatically plays a synthesized version of notes each time you alter them, if you have MIDI tones enabled, you can click on a note and EOF will play it through your configured MIDI device. The next hotfix will allow you to middle click to launch the edit pro guitar dialog. I have no desire to abandon all of the other supported rhythm games, but even if I did, EOF almost certainly couldn't become the only tool needed/wanted by every author. It's not feasible to make EOF do everything the best compared to supplemental programs (ie. digital audio manipulation, MIDI synthesizing, etc), so I like to focus on what I can make it do well. Some day down the line when EOF is ported to Allegro 5, more possibilities will open up. For now, there's not much that can be done. The latest release candidate (RC9) has added instructions in the regular tutorial (Help>Tutorial) that describe how to use Sonic Visualiser to automated beat syncing. It's not exhaustive but it should get people started enough to see if they like the feature. If you know any other tricks to improve the accuracy of Sonic Visualiser's results, let me know and I can add them.

I just fixed a bug that causes this, it should work correctly in the next hotfix. Why not just declare the section with a section marker instead of beat text? The more elaborate a beat text system gets, ie. "tone:songname_distortion:section:intro:phrase:intro1", the harder it would be for people to use. I don't see why this would be considered easier or faster than just defining the sections in EOF. As you said, an external text file defining sections would have to have timestamps in it, and then EOF would have to look for errors in the file and handle that gracefully, such as by fixing timestamps by finding the closest beat marker, etc. Doing something like this right would be a fair amount of programming work but I can't see what the benefit would be. That keyboard shortcut changes to a full screen style 3D view. Doing the same will return to normal, or alternatively, right clicking on the screen gives that option. Exiting out would have still prompted you whether or not to save changes, so there's no reason you couldn't have done that.

No progress yet, there are still bigger problems to deal with. It isn't really that much work to just sync the beat markers since if you do it all manually, it's still the same amount of work regardless of whether you're paying attention to time signatures.

That technique is known as an "unpitched slide".

Adding leading silence will move all chart content, including lyric sections. If you mean you added leading silence and then made lyrics using audio that didn't have the leading silence, you may be better off re-syncing your lyrics in whatever external lyric authoring program you used.

The 1/3 into the note is just a default timing applied to older style bend notes (ie. how they were authored in Rocksmith 1, with no tech notes to define specifically where the bend occurs). I believe slides start immediately, taking the right slope to end at the end of the note that has the slide technique. You can use linkNext status as cstewart suggests if you want to include some non sliding sustain before or after the slide part of the note.

Try "Rex Mundi" input mode (you can set this in File>Preferences). Then you just mouse over where you want to place a note and then press the 1, 2, 3, 4, 5 or 6 number key to add a note to that lane (lane 1 is the bottom-most string). Right click will bring up a context menu, but the edit pro guitar note function is a couple levels deep into that. I'll see if I can make middle click (ie. clicking down on the scroll wheel) can bring up the edit pro guitar note dialog for selected or moused over notes. But that will only work if your mouse has a scroll wheel and Allegro can reliably detect it. I probably won't add support for an external text file just for this, but I may reconsider beat text, but it would have to be formatted pretty specifically (ie. "tone:[tone name here]").

I love the Mass Effect series. It's too bad you didn't get into playing ME3 before the online community for it died down, multiplayer in that game is an absolute blast as long as you're not dealing with the usual lot of cheaters.

Adding special GP text notations for stuff that is easy to add in EOF seems like it would be more complicated than it has to be, and it would make the GP import code a little messier than it already is. I'd rather improve EOF's internal functionality by making it easier to author tone changes. What would you suggest to improve that, would adding a "copy" button (which copies the selected tone change to the selected beat) to the tone change list and names dialogs help? I still plan to add functionity that copies all tone changes from one track to another, I haven't forgotten about that one. It's possible, but that changes my workflow for posting a hotfix. The 7zip format overall is better than zip, but the number of bytes saved is probably negligible. Is there a functional reason you don't want .exe in the filename (ie. virus scanners flagging it more easily)? Most of the time a hotfix includes just an updated exe file, it only has other ones if I've changed them since the last release candidate. I prefer zip for EOF releases because all modern operating systems pretty much support that compression format out of the box without having to install third party software.

Go into "Track>Pro guitar>Set tuning" and set the tuning values to -2 -2 -2 0 0 -2 and it should show the tuning for each of the strings to reflect DADFAD.

I think the toolkit will let you look at the tone settings of another CDLC file, but it's possible you may have to unpack it and look at some of the extracted files. I haven't tried to do that myself, so I'm not sure.

If you have Guitar Pro or a VST generate audio for the tablature, you should be able to use the chart audio and import the GP track into EOF with good results. Unless you have non #/4 time signatures, you probably won't have to even mess with the tempo map beyond exporting the MIDI from Guitar Pro and importing that into EOF to get any tempo changes you placed in the tablature. And if you have non #/4 time signatures, it would probably take a few minutes of dragging beat markers around, but it should be pretty easy work.

If you use the 17 fret guitar or bass tracks and want to use fret numbers higher than that, you may need to increase the fret limit with the "Track>Pro guitar>Set number of frets/strings" function. If you are importing a Guitar Pro file, it will automatically raise the fret limit.

Repost from SA: Yes, just click and drag the first beat marker and the entire chart will move with it. Or if you know the exact number of milliseconds you want to move it, you can open Song>Properties and type that value into the "Delay" field. This "MIDI delay" is a mechanism from the Frets on Fire era that was used to define where the chart starts in relation to the audio.

Prone to user error? It depends on how much practice you've had working with the editor. If you find that EOF doesn't behave as described, let me know.