raynebc

This will mostly happen if the active track isn't one of the guitar/bass tracks with "real" in the name, as those are the only tracks that can contain Rocksmith arrangements. Use CTRL+Tab functions or Song>Track to change the track and let me know if those functions are still unavailable.

That file does not open in Guitar Pro 5, which instead gives a cryptic "Erreur E/S 998" error message. So the file is corrupt, but I don't have enough information to determine what length the note is supposed to be. EOF's logging suggests this problematic note is in the first measure of the first track. If you can post a screen capture, it might let me see what that track is supposed to have in it. In case I can't add workarounds for this corrupted file, there may be no way to import it directly into EOF. It's probably worth contacting Arobas support and explaining that their program is exporting a broken GP5 file. If they fixed that already, they may suggest upgrading to a newer version of their program.

That file seems to be in GPX format and not in GP5 format, so EOF won't be able to import it and I can't open it in Guitar Pro 5 to examine it. Please send me the GP5 file that EOF wasn't able to import.

I suppose. Although if this originated in Guitar Pro 6 or newer, a buggy export is probably the reason it won't import. Sometimes, the broken GP5 exports won't even open in Guitar Pro 5.

It's an error in the Guitar Pro file. The smallest note length that is allowed in GP5 specification is a 1/64th note, which is written as length 4. GP6 has been known to occasionally write buggy GP5 files with features not actually supported in Guitar Pro 5. Check to make sure the tablature doesn't use anything shorter than 1/64.

There may be specific scenarios where this kind of thing could happen, ie.: 1. If you create the waveform graph, then use "File>Load OGG" to load a different one, the waveform isn't recreated until you hide and show the waveform again (ie. press F5 twice). This is intentional behavior in case somebody wanted to load a drum stem, display its waveform and then load a different audio file while keeping the drum waveform shown. 2. If you have the project open in EOF and edit the chart audio outside of EOF, the change isn't immediately reflected because EOF loaded the audio into memory already. Re-loading the project would fix it.

If you mean you want to import the Rocksmith XML file and remove everything except the (edit: highest) difficulty, this should do it: http://customsforge.com/index.php/topic/21280-how-do-delete-dd-sections/?do=findComment&comment=166356

25920 is the correct delay value (note this is completely unrelated to the "AV delay" in that it only affects the active project) to set in Song>Properties in order to sync the first beat marker. After having a properly synced chart, you can change the AV delay value (which is a global setting that applies to audio/video sync during playback in EOF) to make it line up. To start, go into File>Settings and note what the AV delay is currently set to. If it's a number that is higher than 500 it is probably very wrong, and you should set it to 0 and see how the sync looks.

On my computer, when I open your project, the first bass note in the audio is where you drew the arrow in your screen capture. The delay defined in the project is wrong and should be changed to something like 25920. You can change this in Song>Properties and allow EOF to adjust the notes. Using that timing, make adjustments to the AV delay as necessary. If the waveform fails to generate, it says to check the log file for details. Open eof_log.txt from EOF's program folder while that message is being displayed and see what the cause of the error is cited to be (at or near the bottom of the log file).

There's not enough information for me to determine what's wrong. Unless this is the only chart you're having such problems with, a wrong AV delay value in File>Settings is likely. If this is the only chart you're running into this problem with, the chart audio is a likely problem. If you can send me the EOF project and guitar.ogg file I can test with it. When you said you were unable to generate a waveform for "longer" songs, instead of all songs, the memory limit is the most likely problem. Some people chart songs that are tens of minutes or even over an hour long, and decoding that much PCM to memory can be a problem. If you get any sort of error message/number when waveform creation fails, let me know.

I've never seen the waveform not sync with the audio. Whatever audio is loaded is what is used to create the graph. If you mean it's an AV sync issue in EOF, you can adjust that in File>Settings. If your song is super long, your computer may not have enough memory for EOF to create the waveform the way it does (decompress into memory as a WAV file). As a workaround, you can create a lower quality audio file to use for beat mapping (ie. monaural would cut the memory use in half, or you could lower the sample rate).

Hi, folks. The latest hotfix (1-15-2019) is in the first post. Changes are as follows: *Corrected the SP pathing logic's scoring of partial points for disjointed chord sustains. *Added a "Beat>Validate tempo map" function that will check if any beats' timestamps aren't accurately reflected by the tempo changes in the project, and if so, offers to correct the tempo changes to resolve this. This check is now automatically run when the project is loaded and at the end of the "Anchor measures" functions. *Improved the automatic resnapping that occurs if a note loses grid snap during MIDI import due to number rounding so that it can resnap to the beat marker after it if that's the closest grid snap position. *Fixed a minor bug where the difficulty tab highlighting wouldn't immediately update if using the , or . keys to change away from a custom grid snap and notes in the track using that grid snap became highlighted for being out of grid snap (for the built-in grid snap intervals). *Improved the accuracy of EOF's capability to test a note's grid snap status or recover grid snap positioning during paste by having EOF now checking all intervals from 1/2 through 1/96 beat instead of just the default, built-in grid snap sizes. This should allow better recognition of strange intervals like 1/20 as being grid snapped. *Added a "Phase cancellation" feature (ie. to remove center-panned vocals) for chart playback that can be toggled by using ALT+P or via the checkbox in File>Settings. A %PHASE_CANCELLATION% macro was added to allow this to be tracked. *Changed the key to add vocal percussion notes from backspace to the 0 key (the normal one, not the number pad key), since some Mac keyboards don't have a true backspace key. *Changed the Mac build so that the backspace key is treated as the delete key when no dialogs are open. This allows delete key shortcuts to be used on Mac keyboards that don't have a true backspace key. The copy and clone clipboard formats have changed. Make sure to to re-perform copy or clone to clipboard before pasting or cloning from clipboard again or it will malfunction.

You buy the song. Official DLC is not made available for download on this forum.

What build are you using? Do you see the | line move around in the piano roll to reflect where the mouse is? Does clicking on a beat marker select it? In "Classic" input mode, you have to use number keys (1 through 6) to enable placement of a gem the next time you right click. Do you have any gems visible that move around with the mouse pointer in the piano roll? In "Piano Roll" input mode, the gem that is placed only depends on which lane the mouse is in and you don't have to use number keys, just right click. If you set that input mode, are you able to add/remove notes? I wouldn't expect that unzipping EOF again to get a fresh copy would do anything more than just renaming/deleting/moving the eof.cfg file in EOF's program folder in order to revert to all default settings.

Can you post a screenshot of what EOF looks like after you open it on the laptop? It may be some particular graphics hardware/etc. that EOF isn't able to get along with.

Is that the whole log file? These kind of issues have generally been interference by security software (sandboxing, antivirus, etc). EOF does work fine in Windows 10 x64.

That means you have at least one lyric that is outside of a lyric line.

Make sure to skim through the pro guitar tutorial in the Help menu. It was designed for authoring guitar arrangements for Rock Band 3, but most of that is applicable to Rocksmith authoring too.

So far as I've heard, the latest Mac builds are working in High Sierra and Mojave. Let me know if you find otherwise.

Hi, folks. The latest hotfix (12-20-2018) is in the first post. Changes are as follows: *Fixed a bug with the %CH_SP_SEEK_SP_PATH_STATUS% macro so that it correctly reports the deployment's timing when the seek position is within the scope of a star power deployment. *Greatly improved the performance of the %TRACK_SOLO_NOTE_COUNT%, %TRACK_SOLO_NOTE_STATS% and %TRACK_SP_NOTE_STATS% macros used in the Clone Hero panel. *Added logic to remove duplicate star power sections that may have been added when importing multiple difficulty Feedback charts, as they define star power notes per difficulty. *Added a %EOF_FPS% macro to display the number of frames per second rendered in the main loop of EOF (ie. doesn't update when dialogs are open, etc). This has been added to the Information panel. *Added a warning when disabling GHL mode on a track with W3 single note gems that those gems are converted to 5 note chords. *Added tracking for the resulting star power meter level after playing each note during star power path evaluation, and added a macro to display this in the Clone Hero panel. *Added a "Song>Seek>Next CH SP deployable note" function that will seek to the next note (after the current seek position) at which there is enough star power to deploy in Clone Hero (the SP meter is at least 50% full). *Added more stats about slider notes to the Clone Hero panel. *Added the function to toggle the display of the secondary piano roll to Rex Mundi input mode's context menu. *Added information to the Clone Hero panel about the length and effective notes per second rate reflected by the current grid snap setting at the current seek position. *Added the NPS rate of currently selected notes to the Clone Hero panel. *Added a red backgrounded warning to the Clone Hero panel if the active track difficulty has a solo without any notes. *Added a yellow backgrounded warning to the Clone Hero panel if the active track has any solo that starts less than one second after a previous solo, which could cause the earlier solo's bonus score to be removed too quickly to be reasonably seen in Clone Hero. *Improved the - and = keyboard controls (which alter the tempo of the anchor at/before the seek position) so that the dynamic highlighting (for "Seek>Highlight non grid snapped notes") updates immediately. *Updated the Info panel to display the number of highlighted notes in the active track, ie. to display how many notes are highlighted by "Song>Highlight non grid snapped notes". *Added the ability to use SHIFT+click to set the start and end points to reflect the portion of the chart from the previously-selected beat to the start position of the newly-selected beat. *Changed the "Set start point" and "Set end point" functions to not mark the chart as modified. *Organized several of the Beat menu's BPM manipulation functions into a BPM submenu. *Added "Copy tempo map" and "Paste tempo map" functions to the Beat menu, allowing parts of a tempo map to be applied in another part of the chart, a separate chart or a separate EOF instance. To use this feature, use the "Set start point" and "Set end point" Edit menu functions (or select a beat marker and use SHIFT+click to select another beat marker) to select a part of the chart containing one or more beat markers and then use "Copy tempo map". Then select a beat marker to indicate the first beat that will be altered by the copied tempo map and use "Paste tempo map". The tempo and time signature of the applicable number of beats starting from the selected one will be updated accordingly. You can now copy/paste a portion of the tempo map to another area, project or EOF instance. If you see the framerate listed in the Information panel drop significantly under certain circumstances (ie. using a particular Notes panel, changing to a track with a high number notes of a particular special status, etc), let me know so I can see if it can be improved. For now, it's known that the Note Counts panel can be slow on tracks that have tens of thousands of notes due to the type of processing needed.

In a future update, not necessarily the next.

The consensus has generally been that people don't like to be prompted for something all the time versus enabling a setting once and having it stick. Whether tech notes copy/paste automatically along with normal notes would probably be one of the checkboxes you could set in the preferences.

Exactly. As long as you didn't change the beginning of the audio and you only deleted something from the end of guitar.ogg, your chart retains the same sync it had. You would have to delete the WAV file EOF creates so it recreates it to reflect the shortened guitar.ogg file though.

"Set start point" and "Set end point" are used to select a portion of the chart for certain operations such as defining the preview audio or exporting part of the chart to another project. I don't recall if Rocksmith supports a way to force the chart to end the chart before the audio ends, maybe one of the developers or authors here can clarify that. Otherwise I think you may have to edit the chart audio (ie. guitar.ogg) outside of EOF (with a program like Audacity) to delete some of the audio to force it to end sooner.

Tech notes don't copy automatically when you're copying normal notes. It never did this, but I could eventually add the ability for EOF to do that. Some other functions (ie. click and drag to move notes will move the tech notes accordingly). If you can reliably reproduce a scenario where copying a chord and pasting it results in the pasted chord having the wrong fret numbers, let me know. If the fret numbers can't be retained because the source track has higher fret numbers than the destination track is set to allow, EOF will display a warning about this and the affected gems of the pasted note will have their fret value set to 0.