raynebc

@@cozy1 If EOF writes the arrangementProperties tag of an arrangement XML file so that the represent and bonusArr attributes are both zero, will the toolkit consider it as an alternate arrangement or would the user still have to configure that in the toolkit?

According to this (at least based on the comments, without studying it very closely): https://github.com/rscustom/rocksmith-custom-song-toolkit/blob/master/RocksmithTookitGUI/DLCPackageCreator/DLCPackageCreator.cs#L626 If the "represent" and "bonus" attributes are both 0, it's considered an alternate arrangement. I can make that change in EOF (that if the author specifies the arrangement is alternate, both of those attributes are written as 0) if the toolkit developers will confirm that the toolkit does or would be made to honor that. Then I'd just need to know what information EOF needs to get from the author (ie. does a represent attribute value of 5 mean it is alternate arrangement number 5)?

How is an arrangement defined as being an alternate arrangement in the XML file? Bonus arrangements have the bonusArr attribute, but there's not such an obvious one for alternate arrangements.

That's a scam, I occasionally get that on various forums. I assume this is usually because of compromised advertisement objects/scripts on the site or something.

I'm not sure how helpful it would be overall for EOF to write a separate file of preferences/instructions to be picked up by the toolkit. I'm not sure I understand all of your examples though.

Honestly it's not clear if or when EOF will ever work on High Sierra. Apple announced that they're going to remove OpenGL support, so by the time EOF ever gets ported, it may have lost compatibility with OS X again. It would depend on whether Allegro adopts Vulkan, which doesn't even have first party support in OS X (it's provided by a third party library called "MoltenVK").

EOF doesn't actually work natively in OS X High Sierra because Apple removed support for some old graphics library stuff. If it works well in Wine on OS X, that's good for me to know.

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.

Just to make sure we're talking about the same thing, you want better highlighting for selected lyrics in the piano roll area? The lyric text area above that? Both?

That preference should help for item 1. As for highlighting, would you think it's better to change the text color or apply a background color for the lyric text (ie. white background with black text to make it stand out)?

If you change audio devices while EOF is running, restarting EOF should be all you need to do for it to output to your newly-assigned default device.

Hi, folks. The latest hotfix (9-13-2018) is in the first post. Changes are as follows: *Fixed a bug with recent Feedback import changes that could cause forced strum notes to import as forced HOPO notes. *Corrected RS1 export to not write "disparity", "ignore" and "solo" attributes for phrases. *Greatly improved the "Imports drop mid beat tempos" import preference to remove or combine mid beat tempo changes only where it results in a beat being a normal tempo (ie. within 15% of the length of the last complete beat). *Added a "Render mid beat tempos blue" import preference that, if enabled during Feedback or MIDI import, will keep track of which beats were inserted due to mid beat tempo changes. It will also change the color of anchor markers (the down arrow above the beta line) to blue to make it easy to tell where these beats are. *Added the ability to author "Disjointed chords" for button guitar/keys tracks, allowing different gems in a chord to have different lengths, for use in Clone Hero. This status can be added/removed by using the functions in the "Note>Clone Hero>Disjointed" menu. Notes that have this status will have the letter D display beneath them in the piano roll, and they will also gain crazy status as a side effect. Feedback and MIDI imports should add disjointed status where appropriate, and MIDI export will write each gem of a disjointed chord with its appropriate length. Project files that use disjointed status will not open in older builds of EOF, anybody sharing a .eof file between multiple computers will need to have them all update to this release of EOF.

The per-tuning preferred chord fingerings may be doable, but the FHP generation logic is really complex and making changes to it is difficult. Manually setting the fingering for the double stops in question (you can do this one at a time or several at once if you use "Select Like") may improve the auto-generated FHPs, but you may still want to make manual adjustments in some cases.

EOF's RS1 export isn't changed very often and should be mostly functional, but it doesn't get tested often anymore. Please let me know if you run into problems on the editor side (ie. errors when saving the project). Taking a quick look, RS1 export may be writing some unneeded attributes for phrase tags, but I don't know if the toolkit would complain about that when creating RS1 DLC packages.

Hi, folks. The latest hotfix is in the first post. Changes are as follows: *Fixed a bug with new Feedback import automatic resnap logic that could prevent notes from importing correctly if they occur after the last tempo change or text event. *Improved Feedback import to process toggle HOPO and slider markers at the end of each track difficulty's import, reducing the likelihood that long charts with these features will exceed EOF's track note limit and have some of the chart content skipped. If there are too many notes to import from a Feedback chart, EOF will now explicitly warn about this. *Improved the performance of the secondary piano roll by removing unneeded processing that would cause noticeable lag for charts with many notes and phrases. *Fixed a bug where lyric line overdrive was saved to the project file, but wasn't applied when the project is loaded. *Fixed a bug with Feedback import where slider phrases wouldn't correctly combine consecutive slider notes into one phrase if the track has multiple difficulties of notes defined. *Fixed a bug where using the up/down arrow keys to seek while Feedback input mode is in use would cause the selected lyric's tone to play back even though no transpose occurred. *Improved the auto-adjust logic for clicking and dragging beat markers to resnap sections and fret hand positions appropriately. This should keep notes and sections/FHPs better synced when changing beat tempos. *Changed MIDI export logic so that HOPO phrases are written with a length of 1 delta tick instead of 0 ticks if the note has crazy status. This should allow overlapping notes with opposing HOPO statuses without causing issues where notes can get combined during export if the minimum distance between notes is set to 0ms. *Fixed a bug with MIDI import where the presence of GHL open notes could cause notes to be given a longer sustain than they should have. *Updated the "Beat>BPM Change" function to update highlighting immediately in case notes lose grid snap, and changed its logic to prevent notes from losing grid snap due to math rounding errors as beat marker timings are recalculated. *Changed the beat click and drag logic to process the entire chart's content instead of just the beats that are directly affected, to ensure notes won't lose grid snap unexpectedly due to math errors as beat marker timings are recalculated. *Improved the paste logic so that if copying and pasting lyrics within the same EOF session, and the copied lyrics are in a lyric line, the pasted lyrics have lines marked accordingly. *Improved the normal save function to restore the active track and seek position if all presented warning prompts to cancel the save are declined. *Fixed a bug where "Track>Clone>From clipboard" would fail if the cloned track had any lyric lines. *Added functions to search and replace lyric text (Note>Lyrics>Search and replace) and note names (Note>Name>Search and replace). If the "Match case" option is checked, instances of lyrics/notes are changed if they match the exact upper/lower case for each letter (case sensitive). If the "Retain first letter capitalization" option is checked, the first letter of the replacement text is changed to either upper or lower case to match the instance being replaced (this is so you don't have to worry about capitalization differences for the first letter of the first word in a sentence). If a specific note/lyric was selected by mouse click before search and replace is used, that note's/lyric's text is automatically entered as the text to replace.

Just to make sure we're looking at the same thing, could you send me a project file to test with? There may be special circumstances for either problem.

The tempo in Guitar Pro files is not honored when EOF imports the file. The beat positions need to be set in EOF. This does mean that sometimes two different Guitar Pro files won't import as easily into the same project, but you can either alter one Guitar Pro file to suit the other one, or fix the tablature after it's imported (ie. copy+paste, delete, etc).

That's a good point. If you want to force the player to hear it regardless of SFX volume settings, you'll have to edit the chart audio. Supposedly Audacity has a "Generate>Click track" feature, but I've never used it.

You just save the EOF project and as long as you didn't change the default settings, it will create a notes.mid file that you can import into Reaper.

As far as I know, you can still use "Beat>Rocksmith>Place RS Event" to place a high/low pitched tick on beat markers. It's worth a try.

First off, just know that no experienced charters recommend "live charting" by using a controller to place notes while the chart is playing. You *will* have to make substantial fixes to the chart after authoring this way. That said, if it's a game controller recognized by your OS, you can go into File>Controllers in EOF and attempt to map controller buttons here. Then you can use guitar tap or guitar strum input method (set in File>Preferences>Preferences). The manual (Help>Manual>Editing songs>Edit Modes) describes the use of the different input methods.

You may have changed your input method and now the way to add/edit notes isn't what you expect. You can go into File>Preferences>Preferences and check to see if it's something besides the default value of "Classic" or whichever method you normally use.

1. You can't. The first beat always begins on the first measure as per musical theory. 2. Add an unpitched slide. You have to give an ending fret just so the game knows what direction the slide goes and how far it is visually displayed.

I'd probably need the EOF project file and the MIDI file to examine. I doubt EOF is combining multiple notes into one note, but if there was something like a note stopping and starting again at the same timestamp, the MIDI editor you use may draw it like it's one single note even though it isn't.

I'll look at it some more, but it seems likely that the tempo map timing is just so particular that math rounding errors occur. Allowing one manipulation to cause the problem and then using "Track>Repair grid snap" on each track to fix the sync may permanently resolve the issue. I'll see if there's much I can do to have them resnap automatically in such a scenario. This beat timing recalculation was also what was happening when opening Song Properties and clicking OK. I can't think of any reason why this should be done merely by opening and closing the song properties by clicking OK, so I'll remove that.