raynebc

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.

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

The easier thing to do would be to try to select part of the chart (use "Edit>Set start point" and "Edit>Set end point" to mark the current seek position) and use "File>Export chart range" to save that part of the chart (and audio) to another folder.

By now, a pre-bend tech note status is available to author this.

In case you still wanted to author these types of chords, EOF lets you do this now with the "disjointed" note status, which makes each gem in a chord have a separately editable length.

The slide ending is linked to the lowest fretted string in the chord, ie. in the above example, the A string slides from fret 3 to 5, and the G string slides the same number of frets (from 5 to 7).

For a long time now, EOF's default "Accurate TS" option (a per-chart setting in Song>Properties) is enabled for new charts and will adjust beat lengths to account for both tempo *and* time signature (which is correct) instead of just tempo. This means non #/4 time signature changes will have a notable effect.
 
To preserve your beat timings, you should be able to turn off the accurate TS song property, import the GP file, re-enable accurate TS and then take EOF up on its offer to alter the tempos to keep the beat positions intact. Please let me know if you find this doesn't work for your chart or if you can demonstrate that the beat lengths calculated based on a beat's tempo and time signature are not accurate.

"Track>Guitar>Set tuning>Preset"

I'd been more or less waiting for any other feedback from authors/developers, but since nobody brought up any concerns, I'll make that change.

If you can reproduce this problem without using DDC, please provide a simple example EOF project demonstrating it.

If your antivirus software is complaining that these old and well known OGG and MP3 encoding binaries are malware, it doesn't speak well of how many false positives it must get. Please send in false positive reports.

I'm not completely sure what you're asking, but if you just need to copy/paste repeated measures of notes, normal copy and paste does that and even keeps the notes grid-snapped. The key is that you have to move the seek position to the place where the first pasted note will go. Usually this means you should use the seek by beat functions (Pg Up/Dn) or seek by grid snap functions (CTRL+SHIFT+Pg Up/Dn while you have a grid snap size in effect instead of it being off, use , and . to cycle through the grid snap sizes or use "Edit>Grid snap>Custom" to define a grid snap of your own) to place the seek position appropriately.

Handshapes will appear as light blue rectangles in the piano roll. You can remove one handshape by selecting a note in the handshape and using Note>Rocksmith>Handshape>Remove. You can remove all handshapes at once from a track by select any note in the track and using "Note>Rocksmith>Handshape>Erase All".
 
You can remove a section marker from a beat by clicking on the beat in question ( --> ) and then using Beat>Events>Events to bring up the list of text events on the beat, ensure the one called "[section SECTION_NAME]" is selected, click the Delete button and click Done. Going into File>Preferences>Preferences and changing the "Top of 2D pane shows" setting to one of the two options including "RS sections" will make it easy to see which beats are the beginning of a section. The section names will display with white text and will include a number to indicate which instance of the section it is (ie. "intro 1").
 
Instead of looking for sections one at a time, you can also bring up a list of all of them by using "Beat>Events>All events" and change the radio button option to "RS sections". The list will then show the timestamp of each section, the letter 'S' to indicate that the event is a section marker, and then the name of the section itself. You can delete the event directly from this list or you can click the Find button to seek to it in the chart so you can manually review/delete the event.

Something very strange occurred with this project. If you use the "Beat>Events>All Events" function, it will show that there are 4096 text events defined. This is the limit of how many text events EOF allows a project to have, so it fails to create a default "noguitar" section after the last note in an arrangement, and the error is given. I don't know if a Rocksmith import malfunctioned or what happened to cause the project to have all of these events. It doesn't immediately look like any of these events have any text, so you should be able to just use "Beat>Events>Clear all events" and then the error goes away when you save the project.
 
If you can find a way to recreate this condition, such as by creating a new project and importing a particular Rocksmith XML file, I can see if there's something I can improve. Otherwise I think I can add logic to remove text events that have no text as a workaround.

According to Phase Shift's chart features page (http://dwsk.proboards.com/thread/404/song-standard-advancements) they have not implemented the tom+cymbal notation yet in-game. I'm pretty sure they suggested they eventually were going to, otherwise I would not have bothered to add this to EOF. It's probably worth asking on the Phase Shift forum if they would add this feature.

If you still have the Go PlayAlong XML file EOF won't import, please send it to me for testing. If it's like the previous one where it imports, but the beat timestamps aren't what you were expecting, it might still be that EOF imported it as written and there are sync problems in the Go PlayAlong project.

The easiest way to do this would be to change the time signature. The top number of the signature is how many beats are in a measure. So say the Intro section of your project is 10 beats in 4/4 before the Verse section begins, but you want the Guitar Pro file to have the Verse begin at measure 3. You can change the Time signature of the first beat marker to 5/4, which means each measure is 5 beats long. Then the Verse section would occur two measures into the project, and you can change the time signature at that beat marker to suit whatever you wanted. It's possible that the time signature makes a visible difference in-game, but I can't remember if it draws measure markers or anything like that.

Based on past reports, Xonar's EAX emulation (may be called something like "GX mode") isn't compatible, and disabling that feature may allow it to be used by EOF.

Give some of the EOF tutorials built-into the program on the Internet a try. You'll want to look at the parts where they describe "syncing" the chart to the audio, which will mostly involve either manually defining tempos on beat markers (-->) or clicking and dragging them to make adjustments. You can enable the waveform graph of the audio by pressing F5 to help line up the beats more easily.

I guess that has something to do with how some of the beats had to be dropped for having timestamps that were before 0 seconds. Here's a Windows test build if you would like to verify whether it allows you to import the GPA file as expected:
http://ignition.customsforge.com/eof/download/189
 
I keep hoping to get some time to finish the new pre-bend tech note status before formally releasing another hotfix, but life's been busy lately.

It's the intentional behavior that for auto-generated fret hand positions, EOF will use the extra time the player has during an open note to place the next fret hand position suitably for the notes that follow. If you want to delay the fret hand change to fret 2 until measure 45, you'll need to do some manual edits to the fret hand positions. You can have EOF generate them and keep them in the project (so you can edit them, instead of just automatically during save) by using "Track>Rocksmith>Fret hand positions>Generate all diffs", enabling the display of fret hand positions at the top of the piano roll (the "top of 2D pane" item in File>Preferences>Preferences) to make it easy to see where the position changes occur, and then use the set and list functions in the "Track>Rocksmith>Fret hand positions" menu to add or delete positions as you see fit.

I didn't see any import errors, but keep in mind that the GP5 file itself that Guitar Pro 7 created may have differences to the original tab. None of the bass notes were more than single notes, there were no chords, so EOF imported them all as single notes. EOF imported all of the rhythm guitar arrangement as 3 note chords, which is how they seem to be in the GP5 file. In the GP5 file, all notes and chords appear to be longer than quarter notes so it's expected EOF kept the sustain on all of them during import.

When I launch the 12-18-2017 hotfix of EOF, use File>New, select an MP3 file and opt to create a new folder in my defined song folder (File>Song folder), it creates the folder as expected, converts the audio to OGG format and creates an empty project file.
 
Please provide specific details about how you're using the new chart wizard, including what file format you're selecting for the source audio, what destination you're selecting for the project, what Operating System you're using and what version of EOF (Help>About) that you're using. Providing the eof_log.txt file (in the EOF program folder) after it has crashes may also reveal causes.

EOF does accept dots, triplets and generally what you see in GP5 is what you get in EOF except for exotic types of notation. If you can demonstrate otherwise, please provide a GP5 file demonstrating this.