Jump to content

Latest EOF releases (9-26-2020)


raynebc

Recommended Posts

Hi, folks. The latest hotfix (9-14-2015) is in the first post. Changes are as follows:

*Fixed a bug with the automatic resnap logic that could corrupt note positions and lengths in some conditions.

*Fixed bugs where "erase track" and "erase track difficulty" would not work if tech notes were present but no normal notes were, and tech view wasn't in effect.

*Improved "Save as" function to not warn about overwriting an existing project file if the destination file name is unique.

*Improved the handling of alternate endings during the import of Guitar Pro 4 files.

*Fixed a bug where several Note>Rocksmith menu functions were grayed out incorrectly.

 

Since Google Code is shutting down, I had to move over to Git, which has no incremental commit numbering system so for now I'll just use the build date.

Link to comment
Share on other sites

I was wondering if you could take a look at something?

 

I made this

 

https://drive.google.com/file/d/0B2oZs0ta32KyVGZtS2dfQWE1bnc/view?usp=sharing

 

and it comes in game like this

 

https://drive.google.com/file/d/0B2oZs0ta32KycW1QQk5xTDFVRkk/view?usp=sharing

 

and I was wondering why there is a chord tail?

It's probably because of the logic added a while back where a fully string muted chord is allowed to be included in the previous chord's handshape by default, and subsequently extending the handshape to fit. Ideally, I want to improve the 3D preview to reflect this (display the string muted chord as a repeat line), but otherwise the workaround is to mark the string mute with "crazy" status to force it into its own handshape, then there is plenty of space between the two in the exported XML.

 

Edit: 3D preview is displaying fully string muted chords as repeats where appropriate, I was just using the wrong preferences. Silly me.

Link to comment
Share on other sites

Going for the treble... I managed to reproduce the unpitched slide to 255 error

 

Here is the eof file

 

https://drive.google.com/file/d/0B2oZs0ta32KyUl96STFGa2dZaDA/view?usp=sharing

 

When you try to pull the resulting XML into the toolkit it tells you of an error at (3581, 291) and low and behold EoF is trying to author an unpitched slide to fret 255. You can see in the EoF project that it looks like I authroed it correctly there.

The issue is that EOF wants you to define the end position of slides as the lowest used fret instead of the lowest fretted string (ie. the unpitched slide in question should end at fret 6 instead of fret 8). Additionally, in this particular example the bug seemed to only happen because the sliding chord was linked to the previous chord and was recreated as single notes. I've added error checking to Rocksmith export so that if a project with this peculiarity is saved again, the note exports as a non slide. I've also updated the tab notation to display question marks in this scenario and the dialog functions and manual also now reflect the meaning of the slide's end position.

 

And on that note, the latest hotfix (9-15-2015) is in the first post. Changes are as follows:

*Fixed a bug with the sorting logic that would prevent temporary notes from being properly removed after Rocksmith 2 export.

*Fixed a bug with the "Edit frets/fingering" dialog where setting a string to be muted would cause EOF to incorrectly ask to set a high fret limit for the track.

*Added error checking to RS export's handling of pitched and unpitched slides.

  • Like 2
Link to comment
Share on other sites

 

The issue is that EOF wants you to define the end position of slides as the lowest used fret instead of the lowest fretted string (ie. the unpitched slide in question should end at fret 6 instead of fret 8).

 

Is this a recent change in EoF?

 

Like I said I loaded up that exact EoF file using 1409 and it exported the XML exactly as I had intended it to look in game.  I have always used the lowest (thickest) string as the slide fret variable and it's always worked fine.

 

Furthermore, in that example EoF simply won't let you author the slide to fret 6, as it sees it as a slide from fret 6 to fret 6 and gives you a warning - and subsequent 255 error.

 

I'm not at a pc with EoF just now, I can maybe have a play around tonight - like always it's probably me being a dill :D

 

 

I just think it's strange that I can author this

 

https://drive.google.com/file/d/0B2oZs0ta32KySmRpYWd3b2ExUEE/view?pli=1

 

in 1409 with my eyes closed, but in recent EoFs I am scratching my head, trouble shooting, getting errors and struggling really.

 

How would you author that in EoF?

Link to comment
Share on other sites

It's been the intended logic, but now it's more obvious and enforced. I think it makes the most sense and that more people would interpret a "slide to fret #" instruction that way. Either way I had to pick one or the other because down slides have to be bounds checked for 0 and so on.

 

The slide to fret 6 is regarding the slide at 10:17.785 in the "Stairway Revisited" project file you posted (8_10 to 6_8).

 

About your screen capture, it's probably doable with a double stop that pitched slides and links to another double stop, the latter one with an unpitched slide down. If you author the fingering to use the index finger on both double stops, the FHP generation will place a position change at the end of the pitched slide (or you can manually set the FHP there).

Link to comment
Share on other sites

Just tried 9-15-2015 and it seems to be working e.g. making

 

3\5    (e)

5\7    (B )

5\7    (G)

 

in 1436 was pretty impossible as you had the lowest fret logic on export but with the old style warning "must slide to higher fret", you could not author that as a slide to 5.

 

But in 9/15/2015 it is possible.

 

 

I can bash on with 9-15-2015 for new projects from scratch, but I think loading up an old project in 9-15-2015 and saving (where there are chord slides authored in old money) could have horrible consequences.  I'm sure I'll have a "doh" sooner or later :D

Link to comment
Share on other sites

Wait... what?  When did this become possible?  I just updated to  9-15-2015 from 1436.

 

Wait%20what.JPG

 

Was this on purpose?  I'm just asking in case it was an accident.  But if not, what is the intended use? an un-strummed pre-slide? or???  Does RS support this? :unsure:

 

I was used to pulling back on my wheel to ensure I didn't have any unwanted note trails, and woah!

  • Like 1

Keep smiling. It makes people wonder what you've been up to.

See my Workshop here.

Link to comment
Share on other sites

I'm going through some of my hold songs and trying to fix the hand positions during some of the tapping sections. As some of the tapping sections are quite prolong and deleting the generated FHP there manually is time consuming (and generating FHP manually across the entire track looks even less appetizing), I'm looking for a way to delete across a large swath of notes all at once. Is there a way to do this? I tried shift-clicking in the FHP list and the didn't seem to work.

 

Alternatively, would there be a way to set up a region that gets "protected" during FHP generation, so I could set the FHP in there, the rest of the track would be considered to have no FHP, and when generating FHP that region doesn't get overwritten?

My CDLC releases and my workshop 
My CDLC previews (Lots of bass only stuff)
Join us at the Rocksmith Championship!

Link to comment
Share on other sites

I'm going through some of my hold songs and trying to fix the hand positions during some of the tapping sections. As some of the tapping sections are quite prolong and deleting the generated FHP there manually is time consuming (and generating FHP manually across the entire track looks even less appetizing), I'm looking for a way to delete across a large swath of notes all at once. Is there a way to do this? I tried shift-clicking in the FHP list and the didn't seem to work.

 

Alternatively, would there be a way to set up a region that gets "protected" during FHP generation, so I could set the FHP in there, the rest of the track would be considered to have no FHP, and when generating FHP that region doesn't get overwritten?

Upon Glen's request about 1.5 years ago raynebc added a special command in EoF that pretty much does what you describe. It is in the menus somewhere and being at work I cannot say exactly where but I think the command was SHIFT+DEL. I haven't used it in a while but check the Hotfixes around March,April 2014 and you'll find the proper descriptions of the feature.

"A dreamer is someone who wants beyond what is reasonable. A hero is a dreamer who cannot take no for an answer." (Martin Spina)

My Released CDLC - Blaze Bayley - Stare at the Sun & MacGyver Theme Song & Iron Maiden - No More Lies

Check out the Tech Notes Tutorial Version 1.1 // Chordify Tutorial Rough Draft.

Link to comment
Share on other sites

Wait... what? When did this become possible? I just updated to 9-15-2015 from 1436.

 

Wait%20what.JPG

Weird, I've never seen that happen. I'll try to add additional checks to prevent this, but if you find out how to reproduce it, let me know.

 

I'm looking for a way to delete across a large swath of notes all at once. Is there a way to do this?

There's not currently a way to do this, but I think I can add a menu function for it. Currently, "Note>Rocksmith>Generate FHPs" operates only on the portion of the chart covered by the selected time range of notes, so one to remove FHPs for selected time range of notes would compliment it pretty well.

 

Alternatively, would there be a way to set up a region that gets "protected" during FHP generation, so I could set the FHP in there, the rest of the track would be considered to have no FHP, and when generating FHP that region doesn't get overwritten?

This would take much more effort to add. A "protect" status for individual FHPs might not be too complicated, but I don't know if I have time to dedicate to that right now.

 

Upon Glen's request about 1.5 years ago raynebc added a special command in EoF that pretty much does what you describe. It is in the menus somewhere and being at work I cannot say exactly where but I think the command was SHIFT+DEL. I haven't used it in a while but check the Hotfixes around March,April 2014 and you'll find the proper descriptions of the feature.

I think you're referring to "Track>Rocksmith>Fret hand positions>Delete effective", which only deletes the FHP at the current seek position. I believe what albatross213 is looking for is a way to delete several FHPs all at once.
  • Like 1
Link to comment
Share on other sites

 

There's not currently a way to do this, but I think I can add a menu function for it. Currently, "Note>Rocksmith>Generate FHPs" operates only on the portion of the chart covered by the selected time range of notes, so one to remove FHPs for selected time range of notes would compliment it pretty well.

Ah, I didn't know there was something under the Note menu for FHPs (I think I was looking near the stuff for fingering and didn't fully check all the way down).

 

So if I understand correctly, if I have a long tapping section in the middle of the song, I could select all the notes before it, Generate FHPs, then select all the notes after it, generate FHPS, and then manually input FHPs for the tapping section, right? If so, that would do the job quite well. It would be slightly more convenient to be able to remove FHPs over a selection, but only slightly.

 

Edit: Yeah, that makes it much easier. Thanks!

Edited by albatross213

My CDLC releases and my workshop 
My CDLC previews (Lots of bass only stuff)
Join us at the Rocksmith Championship!

Link to comment
Share on other sites

Wait... what?  When did this become possible?  I just updated to  9-15-2015 from 1436.

 

Wait%20what.JPG

 

Was this on purpose?  I'm just asking in case it was an accident.  But if not, what is the intended use? an un-strummed pre-slide? or???  Does RS support this? :unsure:

 

I was used to pulling back on my wheel to ensure I didn't have any unwanted note trails, and woah!

 

Found a way to reproduce it.

 

Create a note

Press h

Mouse scroll down

  • Like 1
Link to comment
Share on other sites

I can't reproduce that in any input method. Would you please confirm what version of EOF you are using (as reported in Help>About)? Can you send me your eof.cfg file so I can test with your settings?

 

If you close EOF, rename eof.cfg and open EOF again, it will set all settings to default. If you do this to get all default settings, can you still recreate the issue? After you've done this test, you can close EOF, delete the new eof.cfg it created during close, and rename the original config file back to eof.cfg to restore your settings.

Link to comment
Share on other sites

I'm finding some stuff with 9-15-2015.  I read before someone saying that new notes are not highlighted, well I can concur that this does happen.  Also, when it happens you can set new notes on existing notes tails, without the tails being chopped like previously

 

https://drive.google.com/file/d/0B2oZs0ta32KycXAyVHp0NjZpUEk/view?usp=sharing

 

See at the 2.49 marker where I have created a new note on the tail of the existing note, with no linknexts or crazy status in sight.  I believe that this is the result if the fact it is not highlighted, as when highlights are "working" it chops the tail as per normal.

 

I cannot induce the fault when I please, just now its still a bit random.  But no doubt as I work on I will see a pattern.

 

 

Edit - when I erased the extra note and set a linknext, EoF did not attach the tail to the next note

 

https://drive.google.com/file/d/0B2oZs0ta32KySHBJLXo2U0pGYXc/view?usp=sharing

 

probably related and hopefully helpful.

 

 

Good luck :D

Link to comment
Share on other sites

I tried for a while, but I couldn't reproduce the issue where a newly placed note wouldn't be highlighted, regardless of whether it was placed at the edge of, on top of or away from existing notes. If anybody finds more specific ways to trigger this, please let me know. Perhaps only specific user preferences will trigger this, so if anybody can reproduce it with all default settings (ie. rename eof.cfg before opening EOF), it may help narrow down the scope of the problem.

Link to comment
Share on other sites

If Rocksmith export is not enabled, toggling on an up/down slide will not bring up the popup to set the end fret. If this is the case, you also won't get XML files when you save your project. If you go into File>Preferences and verify Rocksmith 1 and/or 2 export is enabled and it still doesn't prompt for the end fret, let me know and I'll investigate it some more. At that point I may need a copy of your current eof.cfg file so I can make sure EOF is reading it correctly.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. - Privacy Policy