During a GP tab import in EOF, a single note with a slide is terminated with a new gem related to the end fret position. I was expected to have only the first note with the slide and its end fret position, but not the last gem at the end of the sustain.

Is it the normal behaviour ?

This is expected behavior for a shift slide (by definition the string is picked at the beginning and again at the end of the slide). If you're certain your tab file authored this as a legato slide (the string is only picked at the beginning of the slide), I can look into it if you send me the file.

 

Edit: Well, this just disappeared as randomly as it appeared. Was working on a song for a while, quit EoF and then came back a bit later and suddenly the program was back to normal.

This kind of computer craziness sometimes clears up with a reboot. EOF rarely changes in a way that would cause such behavioral changes, but it's a good idea to keep the last couple hotfixes around so you can verify the behavior isn't happening with releases that worked normally for you before.

Well now I have another very weird problem that is somewhat similar to the image a few posts up. Game is applying pretty much all techniques to every single note or something (even though it shouldn't, going by the tab in EoF) and it looks like a damn mess. Using both latest toolkit and EoF, but also happened with the previous version of the toolkit I had.

As I say frequently, please specify the EXACT version number of the toolkit you are using. "Latest" is a relative term and isn't very accurate.

2.8.2.0-273b0ba2

If you import the XML file back into EOF, does the arrangement look correct? If you disable EOF's abridged XML output preference, save the project again and recreate the song package in the toolkit, does the arrangement look correct in-game?

The tab has definitely changed when I imported it. Here's a section where it's supposed to just be octaves, but it added an open note for each string on almost all the notes.

 

 

But, I can't see a reason to why all the notes in the intro of the song have unpitched slides and other techniques applied to them, they all look like they should.

 

After typing the above I remade the song with the abridged setting disabled and that did seem to fix the problem. Played through the first part and everything looked like it should.

Sounds like an issue worth bringing up with the toolkit developers, if there's a problem with abridged XML.

 

If you provide an EOF project file whose XML doesn't import relatively closely to the way it originally was in the editor, I'll check it out.

Hi, All

 

   CusomForge's new EOF and Toolkit combo is really pissing me off. Still makes a mess on chords after deleting and reinstalling EOF and Toolkit many times. And my AVG antivirus started blocking EOF for some crazy reason. I am starting to wonder what the Hell is going on now!

 

EOF 1.8RC12 5-23-2017

Toolkit Latest test build - 2.8.2.0 (rev 273b0ba2)

 

Later, avdocatwork

 

New Customs still look like this junk - Un-Playable!

 

AVG's issue with false positives is common for overprotective antivirus programs. It doesn't consider EOF well known so it gets flagged regardless of content. If you're in doubt, upload the EOF executable here and see what dozens of other AV programs have to say:

https://www.virustotal.com/

 

As for the issues in-game, try the following:

 

1. The screen capture shows the chart has dynamic difficulties. If you're using DDC, try creating a version of the song package without dynamic difficulty. If the problem then goes away, it would likely be a problem with DDC.

 

2. If that doesn't help, go into EOF's import/export preferences and try disabling the "Abridged Rocksmith 2 export" feature, re-save the EOF project and then use the new XML files to create your song package again in the toolkit. If the problem then goes away, it would indicate a problem with either the toolkit or EOF. Without having the project file to look at, I'd suggest that if you import the XML file back into EOF, if it looks pretty close to what you're expecting it would lead me to believe it isn't an EOF issue.

 

 

 

 

Please provide links to your original EOF project files BEFORE the arrangements have been run through the toolkit.  I wil take a look and see if it is issue with toolkit.

@raynebc @cozy1  Thanks, Guys

 

  The problem was solved by going to the EOF's Ver. 1.8RC12 5-23-2017 - import/export preferences and disabling the "Abridged Rocksmith 2 export", re-saving the EOF projects (Customs) and then using the new XML files when repacking with the toolkit. Like raynebc suggested. I new it had to be a real simple thing causing the problem, but frustrating when a simple mis-setting drives you crazy for a few days. Luckily if someone else see's this problem show up here's the cure. I also installed the Toolkit 2.8.0.0 (rev 3d133c61), which is fantastic. Thanks for all the extra new features in it. All is good again.

 

@@avdocatwork This issue was adressed in a few others topic aroun the forum : http://customsforge.com/topic/36485-chord-glitch-mode-selection/ and EOF have a clear warning regarding the use of abridged xml when this was deployed clearly mentioning the version of the toolkit needed for this to work properly.

Some of the people reporting these problems claim to be using the correct version number of the toolkit. If anybody can determine if there's a problem with EOF's abridged XML, I'd like to know. If people don't submit project files that produce this issue, it will be difficult to track down.

@@raynebc as i've said before i never found any issue by using abridged xml with the latest toolkit beta (v2.8.0.2 and higher) ever since the abridged xml function was added and i still use it without any issue at all on all the CDLC i've created.

 

I would be curious if anyone is actually capable of reproducing this cause that would mean that i'm quite the exception which seems a bit weird.

For your information, DDC v3.3 generates abridged XML only. So if there was a problem with it, we should have more people with this kind of issue.

 

Envoyé de mon SM-G920F en utilisant Tapatalk

@raynebc @cozy1  Thanks, Guys

 

  The problem was solved by going to the EOF's Ver. 1.8RC12 5-23-2017 - import/export preferences and disabling the "Abridged Rocksmith 2 export", re-saving the EOF projects (Customs) and then using the new XML files when repacking with the toolkit. Like raynebc suggested. I new it had to be a real simple thing causing the problem, but frustrating when a simple mis-setting drives you crazy for a few days. Luckily if someone else see's this problem show up here's the cure. I also installed the Toolkit 2.8.0.0 (rev 3d133c61), which is fantastic. Thanks for all the extra new features in it. All is good again.

Downgrading solves absolutely nothing.  Provide your project files that caused the chord issue using the newest beta toolkit and newest version of EOF, or have your comments accepted for what they seem to be ... 'rage and banter' that require no further response from the developers.

@@raynebc Don't know if this has been requested before but would it be possible for EOF to have an autoupdate feature?

There's no immediate, simple way for me to add something like that. Luckily though, updating manually is pretty easy.

 

 

 

 

 

Please provide links to your original EOF project files BEFORE the arrangements have been run through the toolkit.  I wil take a look and see if it is issue with toolkit.

 

 

I enabled the abridged setting and re-saved the project so it would be just like before when it wasn't working. I have not re-packed the song with this file to see if it's also busted, but that's the only thing that I changed to get it working before.

https://www.dropbox.com/s/3g6y3r2vfb1g88h/New%20folder.rar?dl=0

There's no immediate, simple way for me to add something like that. Luckily though, updating manually is pretty easy.

 

The Ability to Paste Lyrics Into the Vocals Popup/ Dialog box thingy...

Would be Great for all the times I feel like one sentence at a time is good enough and don't want to use ultrastar etc bs to do it per syllable...

 

sorry if u had responded to this old request already from years ago... i don't recall reading a response on why we shouldn't be allowed to paste text... also showing the character limit would be great... trying to eye-ball it and occasionally getting 1-2 letters cut off from the end gets annoying... 

The issue was that there's no simple, cross-platform way for me to access to the OS clipboard, as far as I can tell.

 

I enabled the abridged setting and re-saved the project so it would be just like before when it wasn't working. I have not re-packed the song with this file to see if it's also busted, but that's the only thing that I changed to get it working before.

https://www.dropbox.com/s/3g6y3r2vfb1g88h/New%20folder.rar?dl=0

 

Thanks.  I will take a look.

@@Xyber
Using the latest beta toolkit I am not able to reproduce the chord issues with the EOF project files that you posted.  The CDLC compiles and plays through completely in game with no observed chord issues.  I compiled both DropD and E Standard versions of the CDLC and both are synced and play extremely well ... good job.  (The Low E string is almost never used in the song so there is no reason it can't be played in E Standard tuning which may save time loading in the game.)

 

Here's what I observed in reviewing your EOF project files:

1)  The EOF project is missing Album Artwork so the toolkit will use default artwork.
2)  PART REAL_GUITAR_22_RS2.xml uses non-compliant phrase names, e.g. "Outro-Guitar Solo", "Pre-Chorus".  These should be "outro" and "prechorus".  Appling DD to the arrangement with the toolkit will convert and replace these non-compliant phrase names.  If you are not applying DD then this naming may be a possible source of problems.  I always apply DD with the toolkit because Remastered now requires it to maintain song stats.

 

Let me know if the linked CDLC play through in-game for you.

Are hyphens not supposed to be allowed in phrase names?

Are hyphens not supposed to be allowed in phrase names?

 I think @iminoshi help to answer what is found in ODLC here.  I don't see any hyphens in the ODLC section/phrase names.  So I am going with, not allowed.

 

Footnote:  If DD is applied with toolkit and/or DDC then DDC seems to rename all phrase names so that there aren't in-game section/phrase naming compatibility issues.