raynebc

It doesn't matter what grid snap is in effect when you import, EOF only uses the note positioning in the GP file and the timing of the beat map.

There are no known problems with triplets no importing correctly, please send me the file so I can check it out. "Triplet feel" notation as it is called in Guitar Pro isn't supported yet. The reason for this is because Guitar Pro doesn't actually notate the notes as triplets, it notates them normally and they have to be interpreted differently.

As mentioned on the other forum, EOF no longer creates the showlights files because the toolkit does. If the toolkit is complaining that the files are missing, you would need to get a newer version of it.

I gave a more elaborate explanation here: http://customsforge.com/topic/841-how-to-make-cdlc-full-in-depth-tut-completed/page-5?p=18796&do=findComment&comment=18796 I tested the changes to the quick save function and it works nice, in the next hotfix, all project related files (MIDI, XMLs, WAV, etc) will be created when using the quick save function, will rotate out the ".backup.eof" save of the previous saved copy of the project, will do the strong verifications to ensure the project save succeeded, etc.

They're already working on the forum's download system, which will have these features.

Something I should note about quick save is that it doesn't create the backup save project file or write any files besides the project file itself (ie. no XML files). I'll probably have to have it use the more thorough save function's code, except switching the prompts off. There's no way to copy and paste both types of notes at once, that would take somewhat elaborate changes and I probably won't get to it for a while. I always recommend against clicking and dragging notes after a Guitar Pro import, you should click and drag beat markers to sync the tablature to the audio. If you do this, the tech notes and regular notes will both be moved together.

Only the first time stretched playback for an editing session of a project will take a couple seconds to process the song. Subsequent time stretched playbacks should start without delay, but as mentioned it can cause your computer to lag. I've tried this on multiple fast computers and it stayed pretty much perfectly synced even when I changed speed during playback.

If you can demonstrate an example of this problem it will get fixed. I made a test Guitar Pro 5 file and here are the results:Natural harmonic: Imports as a natural harmonicArtificial harmonic: Imports as a natural harmonicTapped harmonic: Doesn't import with any techniquePinch harmonic: Imports as a pinch harmonicSemi harmonic: Imports as a pinch harmonicI could make the tapped harmonic import as a natural harmonic if that's what people want, but otherwise it looks like it's working as expected.

Hi, folks. The latest hotfix (r1308) is in the first post. Changes are as follows: *Fixed a bug where clicking and dragging beats so that notes go over what was the previously the end of the chart would cause the notes to be deleted, now the chart's length is extended to retain the notes at their new positions. *Improved error handling with Rocksmith lyric import. *Updated Guitar Pro import to recognize when the selected XML file is a Rocksmith XML file rebuilt by the toolkit, which omits the XML declaration tag. *Improved GP import by allowing two consecutive bend points of the same strength to be imported instead of just the first of them. *Fixed a bug where the "Track>Rocksmith>Fret hand positions>Generate all diffs" function didn't correctly create undo states. *Fixed bugs that would occur if tech view was enabled for a track: Manually or automatically generated fret hand positions would be incorrect, the exported MIDI wouldn't contain the right notes. *Added a quick save function to the File menu. This saves the project without all of the prompts and warnings that the Save and Save as functions present. *Added a function (Track>Rocksmith>Fret hand positions>Delete effective) that deletes the fret hand position in effect at the current seek position, if there is any. This function is assigned the SHIFT+Del shortcut. *Improved the fret hand positions display preference by having it also draw a red line across the fret board to indicate its position, so it's easier to tell whether or not they line up exactly with notes. *Changed the "Track>Pro guitar>Ignore tuning/capo" option to be enabled by default for pro guitar/bass tracks in new projects. *Improved the labeling of difficulty tabs to display (*) if tech notes are present in the track difficulty but are hidden from display because tech view is not enabled. *Improved the populated indicator for the tracks in Song>Track, which will now display an asterisk when the track has no normal notes but has one or more tech notes. *Added a function (Note>Rocksmith>Generate FHPs) that generates fret hand positions for the selected notes, removing only the existing fret hand positions that already exist anywhere within that range of notes in the active track difficulty. I'm giving the Mediafire account a try, hopefully the download stats work this time around.

EOF can't determine how much leading silence to add to cause the audio to line up a specific way, but if you determine how many milliseconds are needed, you can add that much leading silence. As far as the chart audio, EOF requires the use of an OGG file internally. It's been this way since it was first created and changing it now would probably cause too many problems. If you want though, you can create the WAV file yourself outside of EOF and set the preference for EOF to not create a Rocksmith WAV file. Just beware that if you add leading silence to the chart in EOF, you'll have to manually replicate such changes to the WAV file because EOF won't be altering files external to the project.

WebTabPlayer corrupts Guitar Pro files, see this post: http://forums.smithyanvil.com/viewtopic.php?pid=95854#p95854 EOF's manual talks about this as well, to get it to open at all in either Guitar Pro or TuxGuitar, you have to edit the file in a hex editor. EOF makes this alteration automatically if you try to import one of these broken GP files, but sometimes that's not enough and the import will still fail because other parts of the GP file are also corrupted. In that case, editing it to remove those three bytes (EF BB BF) from the start of the file, saving the changes, opening the edited file in TuxGuitar and then re-saving it to GP5 format usually seems to make the file work in Guitar Pro and EOF. I contacted WebTabPlayer support multiple times about this in the past several months, but it doesn't sound like they ever did fix it.

Do chords where all chordnotes have hammer on or pull off technique still score correctly? Is there a need for EOF to try to write "-nop" chord templates?

It's created something along the lines of every 10 undo states. There's no way to trigger this backup save manually except by continuing to edit the project. If you're fine with accessing a "quick save" function from the File menu, I could probably add that to my to do list. It would even have a keyboard shortcut so you'd be able to activate it in a few keystrokes (ie. ALT+F, Q). This is expected behavior. If you open any project file, all changes are saved to that project file and any backups that are made of it reflect the base file's name (ie. notes_backup.eof). If you want to replace your original project with the backup, you could use "File>Save as" to save over the other project file, or just rename the old project to something like notes_old.eof and the backup project file to notes.eof. As MadMaxx indicates, you can work on multiple project files in the same folder (ie. to author more than 4 arrangements for a song), although you need to be careful because one project will overwrite the other project's XML files without warning if the tracks have all of their default names. If you use Track>Rename you can set a unique name for each track and the XML files that are created will reflect this name so saving one project won't overwrite the XML files from the other project.

The way EOF is designed, it has to store the audio files in the project folder. Allowing it to store files elsewhere would make it too easy for file paths to be invalidated, and it would require the path to be stored in the project file, something the original EOF author wanted to avoid in case people share project files to work on together. Importing what? Loading audio doesn't cause the beat positions to change unless it's the MIDI delay value tied to another OGG file you loaded previously and gave a different first beat position. The author needs to set the position and length/tempo of the first beat before using the leading silence to add a specific number of beats worth of silence. Having EOF guess all of this automatically would probably lead to mediocre results. In the past, it seemed like some kind of distortion being added to the chart audio and this was a bug with either LAME or oggenc. Is this distortion first being introduced when you select an MP3 file when creating a new chart, or when you add leading silence to a chart? If you add leading silence, the default option is to move the first beat marker position accordingly. The beat positions aren't automatically synced to the music, although you could try having Sonic Visualiser attempt to do so (See the manual description of the "File>Sonic Visualiser Import" function for more details). Otherwise I'll need more information about what behavior you're expecting.

To me it seems like Rocksmith will automatically determine what mastery percentage to start you off with on a new song, and it may round up. So if it thinks you're capable of playing 75% mastery, and you go to play a song with only 3 difficulty levels, it may skip level 2 (we can estimate this as being 66% mastery) and round you up to the next available mastery level (100%).

What does the "-nop" suffix do for chords?

EOF is designed so that fret hand positions are supposed to automatically move when you click and drag beat markers, in the same way that the notes do. It shouldn't matter whether or not the fret hand positions are defined on beat marker positions. If you have a project where clicking and dragging a particular beat doesn't cause the fret hand positions to move, please send it my way with instructions for reproducing the problem and I'll try to fix it. The prompts usually offer to cancel save so you can address a particular problem, so it's generally OK to answer no to those questions in order to carry out the save. If the save actually fails, EOF should give an error message to that effect. I could consider a quick save function, but there might not be a good keyboard shortcut to assign to it. Due to most user preferences, both CTRL+S and F2 perform the save function, as they have for years, and if I re-assign one of them to a different save function it might annoy some long time users.

EOF's Rocksmith XML import code is well over a thousand lines of code. Thinking about how many more might have to be written for Guitar Pro 6's format makes my head hurt. Shrubbery posted a Windows build of the latest TuxGuitar source, and that works for converting GPX to GP5. That's the best solution for now.

I did some testing and I couldn't get fret hand positions to not automatically move with notes when I clicked and dragged beat markers. If you are able to produce this issue, let me know. Looks like this was a bug in EOF and a bug in something else (ie. the toolkit). The number of lyrics in the XML file is given as 0 (instead of just being omitted, like the toolkit is now doing for guitar/bass arrangements that are unpacked), as EOF's special handling didn't quite handle this condition so it crashed. EOF now ignores the count attribute and will import the lyrics, effective next hotfix. The short answer is no, EOF doesn't support that at this time. There's some more discussion on the matter starting at this post:http://customsforge.com/topic/2355-author-sustained-chord-with-a-hammer-on/page-2?do=findComment&comment=16011And a proposed solution here that would need some experimental testing:http://customsforge.com/topic/2355-author-sustained-chord-with-a-hammer-on/page-3?do=findComment&comment=16942

Notepad is probably the least user friendly way to edit XML files, there are probably tons of better XML editors or even text editors that have color formatting (Notepad++ is a likely candidate). I use EditPad Lite, but I don't really do much with XML files except peek at them. If I was in the habit of making lots of manual edits I'd probably spend more time looking for a program more specifically suited to the task. You're right that chord ID #33 is the last one defined in the templates, since the chord IDs are numbered starting with 0. As you say, the chordNote tags do define the fingering of the chord (the lefthand values), but I don't know what would happen if the chordNote fingerings contradicted the ones defined in the chord template, ie. if you edited the fingering for the chordNote for that chord instance, whether they would override the fingering in the template and show what you wanted it to show. It used to be that EOF only wrote chordNote tags for chord changes or for chords that had certain techniques, but the community determined that more problems were resolved by having chordNote tags be written for every chord. If it would actually work, I could just have EOF define the individually defined fingerings on a per-chord basis instead of just using the ones in the chord template. I'd like multiple people to test that out before I changed the code though, just to make sure it doesn't cause any wild problems with Rocksmith. The handshape tags also have an effect on chord boxes, it would probably take some testing to know for sure whether the chordNote fingering takes precedence over the fingering in whatever chord template the handshape invoked. EOF does overwrite the XML files every time you save the project, so it is a hassle to have to re-edit them after each save. So it's best to only edit to test stuff out, and then when finished, make edits then if you want to. Usually this would only be necessary in very specific circumstances if you wanted it to behave differently than EOF would allow, like different fingerings for the same chord, or combining multiple consecutive, linked notes into a single note.

In Audacity, you should be able to use the Silence function from the Generate menu, it will insert the specified amount of silence at the current seek position (ie. make sure you seek to the beginning of the song with the Home key first). After this, re-open the project and you should be able to manually click and drag the first beat marker to match the change to the chart audio, or you can just open Song>Properties and add the number of milliseconds of silence you inserted to the value in the Delay field. The delay value in song.ini is the same as the delay value in Song Properties, but it is only used by EOF if you re-import the MIDI file. This isn't recommended because it will lose some timing accuracy and lots of notation that isn't supported in the rhythm games that use MIDI formatted charts.

If individual arrangements can be marked as "complete" (ie. is accurate, works in Riff Repeater, has tone, etc), it may be good for people that can't or don't want to author all arrangements.

I tested it out on my computer just to make sure it wasn't a problem with leading silence, and when I added a measure of silence, the time stretch playback still was synced to the adjusted chart. The time stretch playback is a lot more processor intensive than normal playback. It's possible that it's causing EOF to lag during playback, so it may lose sync with the graphics until you seek or pause and resume playback. My development computer is kind of low powered compared to my lab computer that I use for fun stuff like playing Rocksmith PC, emulating Wii games, doing video capture, etc, so depending on what other programs I have running, it can cause EOF to lag. Some things will cause more lag than others, ie. having Audacity open seems to cause extra CPU cycles to be drained on my computer. You could try going into Task Manager and giving EOF "above normal" process priority (go to processes tab, find eof.exe, right click on it, select Set Priority and change the priority from normal). If you have a multi-core processor, EOF only has one thread so it can only use up to one core, so increasing the priority may be the best thing you can do to help it. It's best not to give it any higher than "above normal" priority though, in case EOF hangs it could make the rest of your computer less responsive until you terminate EOF.

I was listening to this when I happened upon this thread:

I don't have any other examples at this time.