Latest EOF releases (9-26-2020)

Alex360 · September 16, 2017

wtf is that create new openfile selector? can you bring back windows one not the win95 ish looking one? or am I getting some odds here?

firekorn · September 16, 2017

@@PC Plum You only need the first one for EOF to work, the second is an hotfix which is necessary to be up to date but isn't needed for EOF to work.

raynebc · September 16, 2017

@@Alex360 I'm not sure what you mean. I haven't changed any of the dialogs' appearance.

Alex360 · September 18, 2017

@@raynebc, somwhow it fliped a bit of this disable_windows_fs = 0 to disable_windows_fs = 1 and all came like really old :D

figured out creating new cfg file, thanks for the help! I should believe in myself from the beginning ;)

raynebc · September 18, 2017

That's the "Disable Windows UI" EOF setting.

Alex360 · September 23, 2017

@@raynebc um somehow I'm unable to copy\paste notes without broking it's adjustments it seems like paste old used for both paste operations, Is it ok? EOF's adjust notes set to both bpm and in F11 setting menu, any tips? also working with handshapes it seems like if i hit ctrl+shift+R to fix it's position it adds new notes to handshape which is clearly moveton to me >__>
Eof's 'helping' me to place them all night long here :)

also is there a way to place a ghost note with right-click, like holding g key and right-click?

raynebc · September 23, 2017

Could you provide a sample project file with instructions for how to reproduce this (ie. open project, change to [track name], change to [difficulty #], select notes # through #, copy, seek to [position] and paste)?

There's no shortcut for placing a gem that is automatically a ghost note, and g can't immediately be used for this purpose because it toggles grid snap on/off. If you're using one of the input modes where right click places a gem, you could use the other hand to press CTRL+G to turn a newly placed gem (which is automatically the only selected note upon creation, unless you enabled the "add new notes to selection" preference) into a ghost note. It's a couple key strokes per gem, but it's quick.

Alex360 · September 23, 2017

yeah sure. open this: https://drive.google.com/open?id=0B6zOE-7JCxwjM3VjZWVGRWdaLTg
then switch to pro guitar 22
section chorus1 at 24 sec
then cope some notes like whole bar
and paste into some space after (remove some notes to your taste for that)
than eof should mark miss snapped notes (this bug works with single notes too)

so now another buggy thing when you adjust note with ghost note(using grab or ctrl+shif+R) it should add another note to the handshape and it won't go easily with rightclicking or deleting the note...

so handshape is like anchoring both notes together, right?

raynebc · October 5, 2017

I couldn't immediately reproduce a problem where notes pasted where they weren't expected. Are you sure you seeked to a grid snap position before performing paste? If not, it's likely all pasted notes would be out of grid snap and this would be expected behavior.

When moving the chord at the beginning of a handshape, it's intentional for EOF to force a new ghost chord at the beginning of the handshape. It can be understandably annoying, but there must be a chord there to ensure proper handshape behavior during export. If you select and drag all notes within the handshape, the phrase will be moved accordingly. If you need to change the start position you'll probably have to un-mark the handshape and then add it after moving relevant notes.

raynebc · October 18, 2017

Hi, folks. The latest hotfix (10-17-2017) is in the first post. Changes are as follows:

*Corrected the fingering for the "Rock C" chord definition.

*Fixed a MIDI import bug where an open note in a legacy guitar track would import as a lane 1+6 chord.

*Fixed a bug in Rex Mundi input mode where if a lane 6 gem was toggled on for an existing note in a legacy guitar track, it didn't immediately remove all other gems to reflect that it's an open note.

*Enabled HOPO on/off status for open notes to export to MIDI, for use in Clone Hero.

*Fixed a bug performing/undoing a leading silence operation would not backup/reload the correct audio file.

*Added guitar/bass tuning definitions for "Eb drop Db", "D drop C", "C# drop B" and "Drop C" and definitions for all the "standard" bass tunings. This should cover the list of tunings used for nearly all official Rocksmith songs.

*Improved the "Edit guitar tuning" dialog to allow using Tab to change to the next input field and using the up/down arrow keys to increment/decrement a tuning value.

*Fixed a bug in the "Edit guitar tuning" dialog where if a string had a tuning value of more than 9 half steps below 0 (ie. -10), the tuning value would get truncated to -1.

*Improved the "Edit guitar tuning" dialog to recognize drop tunings where no strings are in standard tuning.

*Improved the "Edit guitar tuning" dialog to allow selecting from a list of all tunings EOF recognizes.

*Fixed a bug where editing a note to toggle a gem on lane 6 in a pro guitar track could cause a crash.

raynebc · October 21, 2017

@@raynebc um somehow I'm unable to copy\paste notes without broking it's adjustments it seems like paste old used for both paste operations, Is it ok? EOF's adjust notes set to both bpm and in F11 setting menu, any tips?

@@Alex360 I was never able to reproduce this problem, are you still able to do so even after seeking to a grid snap position before performing paste (normal paste, old paste would be expected to not resnap pasted notes automatically)?

NejiHyuga900 · October 22, 2017

"*Enabled HOPO on/off status for open notes to export to MIDI, for use in Clone Hero."

Yes! I'm glad this was fixed since I was working on a GHL chart for Clone Hero. Now to wait for Clone Hero to have support for custom GHL-style Rhythm Guitar and Bass since for some reason, while I charted GHL-styled Rhythm and Bass in EOF, they don't show up in Clone Hero).

raynebc · October 22, 2017

Allowing any of the button guitar tracks to be authored as GHL tracks was the most sensible way for me to implement it. Often, what it takes is for one program to support a feature is for another to support it first so there's a demand. It took for a PC rhythm game to support HOPO open notes before there was a reason for EOF to have it.

iminashi · October 23, 2017

A while back I ran into a bug in the Toolkit's linknext handling. I've rewritten the part to fix the bug, but I think a change should be made in EOF before I commit it.

Cases like these

should be exported in the same way:

<chord time="20.998" chordId="2" linkNext="1" >
   <chordNote time="20.998" string="1" fret="5" sustain="0.500" linkNext="1" leftHand="1" />
   <chordNote time="20.998" string="2" fret="7" leftHand="3" />
   <chordNote time="20.998" string="3" fret="7" leftHand="4" />
</chord>

I.e. linknext on the chord itself and only on the note(s) that should have it.

While doing some tests, I also came across some obscure cases where things aren't working as expected.

Here the second chord, with the slide out, doesn't get split into notes automatically.

In this case the first chord is split into notes while it shouldn't be.

Not related to linknext, but if you import a RS XML that has something like this in it into EOF, the sustain of the single note will be cut short (stops at the first chord).

raynebc · October 24, 2017

I'm not sure it's necessary to apply linknext to a chord if it only affects one chordnote. Forcing it to export a way the author didn't define may limit the ability to author certain things.

Here the second chord, with the slide out, doesn't get split into notes automatically.

I'll have to do some more testing with your other examples.

Berneer · October 24, 2017

I am coming in cold here but I think I agree with @@raynebc. I am trying to recall if making both of your Example 1 export identically would break the chordify feature.... I think it is important to differentiate linknext on a chord versus just a note of a chord.

I still have writing the chordify tutorial on my ToDo list but life got terribly busy for me in the last year so i’ve Been scarce.

I will not be able to test anything now but I will retain your example for extensive testing when I resume work on this over the winter.

Cheers and sorry for not being of great help. But this looks like something I need to look at.

iminashi · October 24, 2017

In official content, if any of the notes in the chord have linkNext, the chord itself has linkNext. Cases where only some of the notes in the chord have linkNext aren't that common, but I can find no exceptions (there are no chords with linkNext=0 that have chordNotes with linkNext=1).

Here are some XML examples:

Iron Maiden - 2 Minutes to Midnight (Lead)

</chord>

Dream Theater - Metropolis Part I: "The Miracle and the Sleeper" (Bass)

</chord>

Tom Petty and the Heartbreakers - Good Enough (Combo)

</bendValues>

</chordNote>

</chord>

Wild Cherry - Play That Funky Music (Rhythm)

</chord>

As for chordify, I'm not sure I understand how you're supposed to use it. I apply it on a chord and it makes a chord that has linkNext, but doesn't have any chordNotes, which makes the game crash...

Berneer · October 24, 2017

I would need time to think this through, which I sadly don't have at the moment but in case it helps, I can share my rough draft of the Chordify tutorial. Pages 1-17 are rather complete, Page 39 to 48 has examples which I need to polish and everything between page 17 and 39 is really rough (like a list of things for me not to forget to incorporate somewhere logical, but quite unpolished). It's a long tutorial but it's the images that make it long. It's can more or less be seen as a sequel to the Tech Notes Tutorial because chordify can make heavy use of tech notes.

CHORDIFY TUTORIAL ROUGH DRAFT (Version 0.2, dated May 29, 2016)

Please note that some of the images in the tutorial with cross-shaped gems (overlapping chord notes gems and rotating single note gems) are no longer issues per the help of chlipouni whose proposal is described in the link in the next sentence. I hadn't had a chance to update my tutorial with the improved imagery.

The latter part of the preliminary testing was documented here. The earlier work is documented in post #1574 of this thread on Page 79.... though damn Photobucket removed all my images and are asking for hundreds of dollars to restore them.... :sob: .... I do have my work backed up locally. But reading this would be overkill for now.

I would simply look at the beginning of the tutorial and check if this is or is not related to your question. Most of your examples were of a chord followed by a crazy (partially overlapping) single note so that is not really pertinent to chordify. Chordify is more about a chord with some notes of that chord doing different things than when the chord was initially strummed. I brought up chordify because one of your examples, the first one, the D5 power chord ending in a slide on the A string started with a chord. I'd have to think it through but if linkNext were to be set to 1 necessarily on both the Chordnote tag and the chordtime tag it might be like ODLC but perhaps not fully necessary, let alone probably break the non-standard but welcome EoF feature of chordify. Chordify is a workaround from RS limitations that all in-game chord notes in a chord MUST sustain identically despite real guitar playing not being constrained by this limitation as per examples in Question 1 of my tutorial and Firekorn's example (which forms the baseline example throughout my tutorial) of Tenacious D - The Metal, which sounds quite cool on the chordified riff.

I cannot say for sure without more thought if your proposal would be essential and/or possibly break stuff, but I felt I at least needed to chime in to give additional food for thought. Certainly, as can be seen from the logic tree I paste below chordify logic would break with the common linkNext's proposal. Perhaps if you confirm the importance of the linkNext commonality between chordNote and Chordtime XML tags, by means of back-to-back in-game comparisons, EoF can apply your proposal only for non-chordified chords. I did do extensive testing at the time, so I am a bit skeptical that the commonality is necessary but I forget and will explore in the coming months.

Find below the latest logic tree with which EoF implements Chordfiy. Note how countless testing showed we needed to have differing values for each of the linkNexts in chordNote and chordTime in some specific cases. We don't believe we are breaking the game doing it this way - I verified we do not break the game or crash it on all the examples I tried. Perhaps you will find one...

http://customsforge.com/topic/30267-chordify-testing/page-3 --> Post 58

IF (chordify AND (OPEN NOTES CONTAIN ho OR po OR fret hand mute OR harmonic OR pinch harmonic OR tap OR slap or pluck))THEN

use chlipouni method PLUS

chordtime LinkNext = 1

chordNote LinkNext = 1

ELSEIF (chordify AND (OPEN NOTES CONTAIN accent))THEN

use chlipouni method PLUS

chordtime LinkNext = 0

chordNote LinkNext = 1

ELSEIF (chordify AND (ONLY FRETTED NOTES CONTAIN ho OR po OR fret hand mute OR harmonic OR pinch harmonic OR tap OR slap or pluck OR accent))THEN

use chlipouni method PLUS

chordtime LinkNext = 0

chordNote LinkNext = 1

ELSEIF (Chordify AND (no technique OR vibrato OR bends that aren't pre-bends OR pitched slides OR unpitched slides OR tremolo OR arpgeggio))THEN

use chlipouni method PLUS

chordtime LinkNext = 1

chordNote LinkNext = 1

ELSEIF (Chordify AND (pre-bends)THEN

chordtime LinkNext = 0

~~chordNote LinkNext = 1~~ (can't bend an open note so moot)

high density = 1

ENDIF

Sorry for my slow progress!! Having a 2nd baby is certainly not 2x the work of having one baby.... as I am learning.... it is >>> 2x.

I will monitor your responses and try to chime in when I can.

iminashi · October 24, 2017

I'll need some time to read all that. :) That reminded me of something though:

The current implementation in the Toolkit that applies the mask related to linkNext to the notes (the CHILD mask, which causes the note to not be drawn, only its sustain) doesn't check the linkNext status of the chordNotes. It only checks the chord itself. That's why this doesn't currently work:

Also, as I mentioned in the issue I posted at Github, Rocksmith will not draw the next note of a linkNext note (note with PARENT mask) even if it doesn't have the CHILD mask in the SNG file, except if the note is an open note. Which makes sense, since I don't think ODLC uses open string notes that are linked to a technique.

Berneer · October 24, 2017

I am not familiar with the coding in the toolkit and manipulation of the SNG files, but I believe if you set chordify status to the initial chord in your example of this post you just posted above then you should get what you want? No? I sort show this in my Example 6 on page 48 of 53 of my Microsoft Word file of the Chordify tutorial rough draft.

I found your post on GitHub, but I'm afraid this is beyond my understanding though from reading it I think I understand what you mean.

I will of course test all of this later on but for now I'll have to limit myself to monitoring this thread.

I wonder if what you've found in the coding (you mention masks which I don't know what this is) is something that forced us in the past to make a workaround when we tested and implemented chordify....

Good luck.

Alex360 · October 24, 2017

Sorry guys I even TL DR this since I'm not in game for a while :(

iminashi · October 26, 2017

@@Berneer

I've been reading the tutorial and here are some thoughts:

-In Figure 5a, linkNext will not actually be used since the Toolkit ignores it in this case. Also, in the last three pictures (and in many of your other example screenshots), EOF optimizes the notes into a single note when you link one note into another one that has identical techniques (none in this case).

-The Toolkit selects the longest sustain of a chord's chordNotes and uses that as the sustain of the chord. In the SNG file, chordNotes do not have the attribute "sustain", so it is impossible for them to have different sustains. If you wanted to do that, linkNext is required (which is pretty much what chordify does):

-I tried creating the example in Figure 5 and it crashes the game for me... (and the culprit is not the showlights file ;))

-You can think of masks as on/off switches. In RS, the notes have masks for PALMMUTE, HAMMERON, SLIDE, etc. In the SNG file, linkNext is actually two masks: PARENT and CHILD. PARENT doesn't affect the appearance of a note, but CHILD causes the note to not be drawn.

-Open notes glitch:

The technical reason for why this happens is that a chord has an open note, but the chordNote doesn't have the OPEN mask. A chord that has open notes, but doesn't have chordNotes will cause this.

-As for the example from Tenacious D – The Metal; I don't own it so I can't look at the XML file, but it is not related to the sustain limitation of chordNotes since it doesn't use chords. I tried creating something similar quickly, and interestingly enough, I ran into the linkNext issue in the Toolkit:

raynebc · October 26, 2017

-The Toolkit selects the longest sustain of a chord's chordNotes and uses that as the sustain of the chord. In the SNG file, chordNotes do not have the attribute "sustain", so it is impossible for them to have different sustains. If you wanted to do that, linkNext is required (which is pretty much what chordify does)

If I remember correctly, it may have been a limitation of Rocksmith that a chord's individual notes couldn't have different lengths. Chordify was meant to address this, but authors could also use the split status or linknext to break it up into single notes.

You can think of masks as on/off switches. In RS, the notes have masks for PALMMUTE, HAMMERON, SLIDE, etc. In the SNG file, linkNext is actually two masks: PARENT and CHILD. PARENT doesn't affect the appearance of a note, but CHILD causes the note to not be drawn.

EOF uses tons of bitmasks, but generally not for individual techniques, which is why I implemented the tech notes system. Unless a significant need is found for linknext I probably will leave it as-is.

-Open notes glitch:

The technical reason for why this happens is that a chord has an open note, but the chordNote doesn't have the OPEN mask. A chord that has open notes, but doesn't have chordNotes will cause this.

If EOF is found to be the cause for any instances of this, let me know.

firekorn · October 26, 2017

As much as i appreciate all those technical investigation, i still have to find a use for many of those things. I still haven't found any situation where i was actually required to use the chordify status and i never found any limitation with the linknext status as it is.

At one point it's up to the user to use the tool already available to make it look nice, adding some convoluted system won't help most of the charter out there as i doubt more than 5 charter would use it more than once in their life.

The way i see it, the only thing i could ask for are QOL like faster mass fingering editing for drop power chord shape, some added option for placing crowd event or even a showlight editor with visual indication that would really allow user to add more quality to their chart without having to know all the menu by heart.

raynebc · October 26, 2017

What did you have in mind as far as fingering editing or adding crowd events? I'm not sure how involved the showlights stuff would be if it was done in EOF.

Sign In

Latest EOF releases (9-26-2020)

Recommended Posts

Link to comment

Share on other sites

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

raynebc

raynebc

raynebc

Posted Images

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation

Recently Browsing 0 members

Important Information