raynebc

You can click and drag beat markers if you want, but that affects all tracks in the project. This won't necessarily be a problem unless in certain circumstances such as if you're importing tablature after you synced the beat markers (the notes in the GP file may have a different number of lead in than what the project has) or importing tab from different files (the tablature between two different files is quite often not synchronized with each other).

If there are tempo changes, clicking and dragging several notes will usually cause notes to go out of grid snap because all notes are moved the same amount in milliseconds and not beats. If you need to re-align an entire imported GP track, it's better to select all of the imported notes (CTRL+A), copy them (CTRL+C), delete them, seek to where the first note should go (use the Pg Up/Dn related seek controls to seek by beat and grid snap) and paste the notes (CTRL+V). The notes will have been moved and will all retain their original positions within each beat.

I didn't see anything obviously wrong with it, maybe somebody else would be able to find a problem though.

If the first measure was manually synced in Go PlayAlong, it was already being imported correctly. The new logic covers the case of the first measure not being manually synced but otherwise being positioned either before or after 0ms. I only made special mention of the negative timestamp because that has the consequence of causing beats that are before 0ms to not be imported. EOF does not support negative timestamps for any items, so this was realistically the only way it could be made to work. The only way the measure numbering could be kept the same would be to insert extra beats to make up for the ones that are discarded from the GPA import, or you could just ensure measure 1 is always manually synced at 0ms or later and this problem would not occur. If any problems with the GPA import that I haven't addressed can be demonstrated, I will resolve them.

Hi, folks. The latest hotfix (r1310) is in the first post. Changes are as follows: *Improved the quick save function to export all files related to the project (MIDI, WAV, XML, etc), suppressing more prompts/warnings and by assigning it the CTRL+Q shortcut. *Fixed bugs in the "Note>Rocksmith>Generate FHPs" function. *Added cleanup logic that should prevent EOF from having multiple fret hand positions at the same timestamp of the same track difficulty. *Resolved a crash that could occur if EOF leaves foreground focus (ie. you use ALT+Tab or click outside of EOF) during time stretched playback. *Added logic to GPA import to handle the special case of the first measure not having been synchronized in Go PlayAlong. If the tablature is synchronized in a way where one or more beats are positioned with a negative timestamp (are before the start of the audio), those beats are omitted from import. This cannot be avoided if you synchronized the file this way, but the worst side effect would be that the imported notes won't begin at the same measure as notated in the original GP file.

I can understand your frustration, but I'm not going to disable a function by default or place extra warning messages on the off chance a function can be mis-used. Any function can be used correctly or incorrectly, and which of those it is depends entirely on the author's intentions, which isn't something EOF can judge. If you use the 'A' keyboard shortcut to anchor beats, it won't even be possible to add a beat on accident because you're not even opening the Beat menu.

This only matters if you're authoring multiple difficulties in EOF instead of using DDC, or if you leaving the difficulties named as they are by default and are authoring notes in the "BRE" difficulty, which won't export to XML. The reason for this is that when authoring charts for the Rock Band style of rhythm games, the "BRE" difficulty isn't used to author a playable difficulty, it's for notating things like drum fills and "Big Rock Endings" which is basically a bonus score button spam fest you can put at the end of songs. The act of removing the difficulty limit tells EOF that you are authoring for Rocksmith and not Rock Band so that difficulty can be treated like a regular track difficulty and have its notes exported.

You could also import the GP file into another track or instance of EOF and then copy/paste those notes into the track that has the fret hand positions defined (after clearing the existing notes out).

The way the GP import works, the imported track completely replaces the active track. I'm not sure why somebody would author fret hand positions before importing or authoring the tablature for the arrangement, is there a reason you prefer to do so? Also, if you have any suggestions for improving automated fret hand positions, let me know. There are limits to what can be done, but a lot of it comes down to user preference more than anything else and EOF may already have ways to accommodate that (ie. changing the fingering defined for particular chords).

If the notes are synced but the tempos are different between the two projects, "old paste" would work with the method you described (copy notes from one project to another when the tempos are different), but you may need to resnap some of the notes because they may be out of grid snap.

There's no status in EOF that allows for that (alter the start position of a note), but there's a technique to override the stop position of a note (which wouldn't help in this case). Even if you separate two notes by 1ms though, there have been some reports in the past that Rocksmith still wouldn't display two different notes when they were really close to each other. There may be some kind of threshold minimum distance the game requires between two notes or it could have been a toolkit issue or something. It would really be the easiest option to keep the double stops as chords and override the chord names with spaces if that's what you want.

Any two single notes at the same position have to be treated as a chord, Rocksmith requires this and so does EOF. All official RS songs that I've ever seen display double stops with chord panes. If you want them to show up as single notes, cstewart's suggestion is the most likely way to achieve it, but you're going to have a lot of manual changes to make to the chart. What Berneer and I are working on regarding tech notes is another matter.

Pressing A only toggles the beat marker as an anchor, it doesn't move it. If you pressed SHIFT+A however, the "Beat>Anchor beat" function would be triggered and you'd be promtped to enter a timestamp to which the selected beat is moved. The anchor functions in the Beat menu don't have hotkeys so you can't trigger them with ALT+B and the one more keypress. It's much faster and safer to just use the 'A' key to toggle the anchor setting for a beat. The time signature is optional. The XML files export assuming 4/4 time if no signature is placed. I disagree. This function serves a purpose.As mentioned though, none of these tempo map alterations can be performed if the tempo map is locked.

You can post the project file here or in a private message if you want and I can take a look at it.

Make sure the toolkit reflects that a capo is in use for the arrangement. If you can post the project file I'll take a look, but Rocksmith seems to have pretty glitchy support for capos as it is, or at least capo support is a little unstable for customs as a whole. That only affects the automatically-generated chord names and MIDI tone sound cues. I'm not sure what you mean. EOF does not import tempos during regular GP import. It's not really worth the effort to try to author a GP file to be perfectly in sync with the audio, that's what other programs like Go PlayAlong are better suited for. Usually it's enough to just import the GP file into EOF and then correct beat positions/lengths afterward.

Without seeing the chart, I don't know.

It would probably depend on the synthesizer in use whether it sounds like half the sustain or not.

At the beginning of whatever point you begin syncing the beat markers.

I don't see why there'd be a reason to keep sustains on palm mutes if sustains are being removed from staccato. A key characteristic of both types of notes is that the notes are played without sustain. Let me know if it looks like this change is acceptable after your testing.

I think I saw something like that happen before, I could probably put a check in EOF that thins out multiple fret hand positions that are at the same timestamp.

I'd probably have to see the Sonic Visualiser file and audio file to determine what's going on. If it doesn't give good results on the first try, you may have to try to have Sonic Visualiser try again wiith different settings.

If you're going to create lyrics, definitely use the same audio you have set up in EOF (guitar.ogg), which includes any leading silence you prefixed to the chart audio. Otherwise if you have to resync the lyrics, it causes extra work and you can run into issues like the one you mentioned with the lyric line markers (the blue backgrounds for the lyric text) need to be recreated.

Maybe DDC caused it, but maybe not. You can unpack your song package and import the XML files into EOF to see what's actually in it. I'm not sure what's preventing you from pasting into a post, both of those methods work for me.

If I made the change, I'd probably change the "GP import truncates short notes" preference so that the sustains from both palm muted AND staccato notes are dropped, since that would be more consistent. How does that sound?

Copy and pasting text in posts on this forum works for me. As far as ntoes disappearing, the only obvious reason is that's how the game works if the chart has dynamic difficulties. I don't see how it would be possible for notes in question to be visible at slow speed but missing at full speed in riff repeater.