raynebc

Having an option for EOF to automatically delete all lower difficulty levels during an import could lead to some serious bugs if it was programmed wrongly, when otherwise flattening an arrangement to one difficulty level with existing functions takes only a matter of tens of seconds. Having an option to hide all non Rocksmith relevant tracks could also be messy to implement. As for @@I)ark_Seph saying that the "Remove difficulty limit" removes notes, I'm not sure what he means. By design, the difficulty limit being enabled/disabled determines whether the BRE difficulty (#4) is merely a Rock Band mechanism instead of a playable difficulty, and determines whether that difficulty will export to MIDI (it will if the difficulty limit is active) or XML (it will if the difficulty limit is disabled).

I don't understand what it is you're asking for.

I could probably make a change so that if neither Rock Band nor FoF/Phase Shift exports are enabled, but Rocksmith 1 or 2 export is enabled, the difficulty limit for pro guitar/bass tracks is removed by default. This would make removed the named difficulties for those tracks and apply numbered difficulties instead. For this to take effect, you'd have to disable the FoF and Phase Shift export preference (which is enabled by default in File>Preferences>Import/Export), but let me know if this would be helpful.

A gem whose fret number is in parentheses is a ghost note. This is used for different purposes, but the chords won't show up in game this way. To make them normal chords, you can select them and toggle the ghost status with CTRL+G (or use "Toggle ghost" or "Remove ghost" from the "Note>Pro guitar" menu).

The /Applications folder may have permissions troubles. Try using "File>Song Folder" to define a place for new charts that are created in the song folder root. Alternatively, if you create a folder with your chart audio before-hand, you should be able to tell EOF to "Use source audio's folder" to create the project file in that folder.

You can also use , and . to cycle through the preset grid snap sizes. The Information panel will display what size is currently in effect. Alternatively, you can use a higher grid snap than you need, and just increase the note length (ie. placing a 1/16 note and using ] or scroll wheel up will increase it to a 1/8 length).

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.

Is anybody having problems with the latest Mac build of EOF?

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).

Wouldn't this work? EOF will output that as 3 single notes, with the two of them on the A string linked together: <note time="0.500" string="1" fret="3" sustain="0.500" linkNext="1" ignore="0" slideTo="-1" slideUnpitchTo="-1" bend="0" hopo="0" hammerOn="0" pullOff="0" tap="0" mute="0" palmMute="0" harmonic="0" harmonicPinch="0" accent="0" leftHand="-1" pluck="-1" slap="-1" tremolo="0" vibrato="0" pickDirection="0" rightHand="-1" /> <note time="1.000" string="1" fret="3" sustain="0.500" linkNext="0" ignore="0" slideTo="5" slideUnpitchTo="-1" bend="0" hopo="0" hammerOn="0" pullOff="0" tap="0" mute="0" palmMute="0" harmonic="0" harmonicPinch="0" accent="0" leftHand="-1" pluck="-1" slap="-1" tremolo="0" vibrato="0" pickDirection="0" rightHand="-1" /> <note time="1.000" string="3" fret="5" sustain="0.500" linkNext="0" ignore="0" slideTo="7" slideUnpitchTo="-1" bend="0" hopo="0" hammerOn="0" pullOff="0" tap="0" mute="0" palmMute="0" harmonic="0" harmonicPinch="0" accent="0" leftHand="-1" pluck="-1" slap="-1" tremolo="0" vibrato="0" pickDirection="0" rightHand="-1" />

Can you post a picture of the guitar tablature depicting this, just so I make sure I understand the scenario you're describing?

Unless anything's changed, you should be able to author this as a sustained note, add linknext status to it (from the "edit pro guitar note" dialog) and then place another note on the same string where the slide begins. Define the slide status and slide end position on the latter note.

It's probably just a cosmetic issue, but I'll get it fixed.

I'm looking into getting a cheap refurbished Macbook so I can actually test the Mac build for these kinds of bugs, but if you can keep a list of bugs you find it will be handy. If you browse into the EOF app folder, into Contents, into Resources, into eof, does an eof.cfg file get written at all after you exit EOF?

Hi, folks. The latest hotfix (11-1-2018) is in the first post. Changes are as follows: *Changed the border color for selected lyrics' note rectangles to blue instead of red so the highlighting is visible for notes that are out of the piano roll's focus. *Fixed a Feedback Import bug that prevented extended sustains from importing correctly. *Fixed a bug where adding a gem to an existing note while "Classic", "Piano Roll" or "Hold" input modes are in use could cause the wrong note to become selected. *Fixed a MIDI export bug where if two consecutive forced hopo on/off notes were authored one or two ms apart, the HOPO marker could be changed to 0 deltas long and the MIDI events for it could be written out of correct order to result in a MIDI violation where a note off occurs before the corresponding note on event. *Fixed a bug with the recent Feedback import logic (to process toggle HOPO and slider markers at the end of each track difficulty's import) that could cause GHL notes after a W3 to not import with the correct HOPO status. *Fixed a bug with Feedback import's automated resnapping that could cause toggle HOPO markers to not be handled correctly in some cases. *Added a Song>Seek>Note>Index function that will seek to the specified note number in the active track difficulty, if it exists. Notes are numbered starting from 0, so note index 1 is the second note in the active track difficulty. *Added error checking during warn if some of the project content fails to be written during save, such as if disk space runs out on the drive EOF is running from. File>Load was updated to be able to handle projects that have this problem. *Added a Clone Hero panel (File>Display>Notes panel>Clone Hero) that displays messages about missing features (like solos, star power, loading phrase, preview start time), warns about compatibility problems like using a chart offset and gives various statistics and other information relevant to authoring Clone Hero charts. *Added a "Track>Find optimal CH star power path" function to determine the optimum star power use for the active track difficulty based on Clone Hero scoring rules, reporting the maximum possible score, average multiplier and stars awarded. Also reported is the maximum percentage of notes that can be played during star power, to help the author decide if there are enough star power sections. The new Mac build might work in versions of OS X newer than Sierra, let me know if you find otherwise.

I don't know why old builds would work differently in Mojave, but the original EOF developer was making the Mac builds then. I'll see if he can make a new build.

EOF can't run on versions of OS X newer than Sierra. As a test, I wonder if you could check whether either of these happen to work in Mojave: The super old 1.71 build: http://www.t3-i.com/pages/download.php?id=12 Or the old 1.8RC10 build: http://ignition.customsforge.com/eof/download/13

As I mentioned, I am going to improve that preference that requires a click to change cursor focus in dialogs. The original Allegro menu logic was to move focus to wherever the mouse was, so when I added that preference, I designed it with one dialog item in mind (text input fields that only accept certain characters, such as the number fields). I need to write some logic for each dialog object type (ie. radio buttons, checkboxes).

The focus for those dialogs does default to the input field, but if you had accidentally moved the mouse over any of the other controls, it would have moved the focus. I verified this happens in the 9-28-2018 hotfix with default settings, please let me know if you find otherwise (ie. select the note, set the mouse aside and don't move it, then use keyboard controls to bring up the functions, such as CTRL+Up, CTRL+U, CTRL+B ).

It seems there isn't a consensus on this yet. If it's confirmed whether I should change the export a specific way (ie. have timings all start from 0s and use the offset to correct for the real timings), let me know.

I'll work on expanding the scope of the "Click to change dialog focus". The other functions you mention automatically set the cursor focus in the input fields. I'll see about setting the default cursor focus to the last-placed gem (if applicable) when pulling up the edit pro guitar note dialog.

If you enable the "Click to change dialog focus" preference, you don't have to worry about the mouse movement taking focus away from the fret number field you're editing. Or at least that's how it's meant to work. I'm seeing that dialog controls that aren't text input fields can still steal focus when moused over, so I have some work to do to improve that. Using the "Edit note frets/fingering" function (pressing F instead of N) may be more helpful in your case since the controls that can steal focus are further away from the fret number field. I could also see how hard it would be to automatically have this function give focus to the fret number field of whichever string was just toggled on.

You'd have to save into an older Guitar Pro format (5 or earlier). Newer Guitar Pro formats are completely different, so I'd have to add thousands of lines of new code and it would be way too much of a headache.

It probably wouldn't be very hard for me to change the RS export behavior so that the first beat starts at 0s and the offset tag is written. Let me know if it's actually useful for me to do this for the toolkit's sake though.