Chlipouni

I used the repair for 400 songs , 50 of them became corrupted , anything I can do with these to be able to play them again , of just redownload them ? also in some songs , I can now see all the repeating notes instead of the first then the blanks , new glitch ?

To correct the chord density issue, you can download DDC v3.2 beta and replace the files in the ddc folder of your RSToolkit install. Then apply DD again on the psarc file.

@@iminashi,

 

  Thanks a lot for reporting this issue.

 

  I have just fixed the bug.

  Can you download the last release of DDC v3.2 (Beta) in the first post of this topic and try again ?

For me, the best way would be to add a custom attribute in the "phraseIteration" nodes.

I proposed the event solution because we already use it to define the Time Signature changes.

Hi raynebc,

 

  I would like to improve the phrase process management in DDC.

  The first time DDC is used on a CDLC, it possibly generates new phrases that override the existing phrases defined in EOF.

  Then, the following uses of DDC on this CDLC keep those new phrases and don't have the knowledge of which phrases was defined or not in EOF.

 

  I am thinking of adding new events in the "events" XML node in order to keep the phrase markers as defined in EOF.

 

  What is your opinion about that ?

  Is it possible for you to add them during the XML file generation process in EOF ?

 

Thank you in advance for considering this new proposal

Hi,

 

  I am using Windows 10 with a 1920x1080 screen resolution.

 

  I had the same issue with the RSToolkit.

 

  I solved it by changing the display scaling property.

@@Berneer,

I know that the DDC tab of the Toolkit is now using the same process as the remaster.exe. As some old CDLCs fail to convert when the tone names are not consistent, maybe cozy1 has added an automatic repair feature which is more intrusive than necessary. Can you tell him about your issue ?

Major features of DDC v3.2 are :

- the ability to fix the chord density status in old CDLCs

- no more split of handShapes and anchors when they overlap a phrase marker

DDC v3.2 Beta is available in the first post for testing purposes :

 

@@Berneer, can you test again with the new beta release of DDC v3.2 ?

@@firekorn, @@Billkwando,

FYI, DDC v3.2 will be able to correct the high density chord status automatically when generating DD.

"- If I remove the sustain of the previous note that overlaps the "verse.3" phrase, that solves the issue"

 

I believe that EOF threw an arpeggios error warning for this CDLC that was the original tip-off of the problem. arpeggios <=> sustain

The phrase that causes the issue is added by DDC due to the length parameter value. So EOF could not warn about it.

I have to adjust the DDC phrase creation process to avoid this kind of issues ...

EOF doesn't warn about that, but I can add a warning for it. The warning will probably only be given if it looks like DD is being authored elsewhere in the same arrangement (ie. another phrase has multiple difficulty levels). I think this would be a good match for recent changes where the toolkit leaves author-defined DD instead of creating it again.

After more investigations, the number of notes in a phrase or the number of difficulty levels are not the root cause of the crash issue.

It seems that it happens only when a sustain overlaps a phrase marker.

@@TomSawyer2112,

 

  If you create the phrases in EOF, it is highly recommended to use a high value in the "phrase length parameter" of DDC (16 by example) to avoid the creation of new phrases during the DDC process.

Hi,

 

  Last finding about this CDLC :

  - If I remove the sustain of the previous note that overlaps the "verse.3" phrase, that solves the issue ...

Hi,

 

 After a few more investigations about this issue :

 - Only the first phrase iteration "verse.3" causes the issue (this is the only phrase with only one note)

 - The two other phrases with only two notes each and only one level of difficulty work fine in RS2014

 - The issue is also present in RS2014 first edition

 

 I need more investigations to identify precisely the root cause of this issue

 

 I am interested in other CDLCs with a similar issue ...

 

Thank you

@@TomSawyer2112,

 

  If you define the phrases in EOF (to define the ranges of measures that contain similar patterns of notes), you can use a high number in the "phrase length" parameter of DDC (16 by example).

 

  The "phrase length" parameter is here to create the phrases automatically, when they are not defined in EOF, but the DDC process is mechanical and not very clever.

 

  So for a best result :

  - create the phrases yourself in EOF (you can use various lengths of phrases)

  - generate DD with DDC with a high value in the "phrase length" parameter to prevent DDC to divide the existing phrases in smaller ones

@@raynebc,

 

For your information, I made this topic about RS2014 crash when a non-empty phrase has only one level of difficulty.

http://customsforge.com/topic/33783-rs2014-remastered-crashes-if-a-non-empty-phrase-has-only-one-level-of-dd/

 

This issue may arrive with manual DD too ...

I don't remember if EOF displays a warning when a phrase has only one note ?

There is no issue with empty phrases.

If the first arrangement of a CDLC contains at least one phrase with only one level of difficulty (level 0), RS2014 Remastered crashes when you try to play the song.

 

When you use DDC, this case may happen when the phrase has only one note or if all notes belong to the same category and subcategory.

 

As an example, the following CDLC has a lead arrangement in which 3 phrase iterations have only one level of diffculty (the first one is selected "verse.3" and has only one note) :

 

To correct the CDLC with the BPR tool :

- unpack the CDLC ([File][unpack ...])

- Select the first arrangement

- For each phrase with only one level of difficulty and that contains at least one note, delete the phrase to merge it with the previous or the next one.

- Generate DD ([File][save and Generate DD])

- Pack the CDLC ([File][Pack ...])

The 'floor' refers to the actual note highway that changes from black to dark blue in the fret lanes with upcoming notes. It is the "floor FHP" and not the yellow numbers that are momentarily wrong in the space with no notes between section start and first single note in the section (B5). 

 

Ok, I never thought to look at these level of details  :D

So, now, if we consider the changes of patterns of the carpet, I can affirm that DDC v3.2 fixes the issue.

It fixes too the yellow number issue (in your second animated gif, you can see that the minimum fret is 4 but changes to 5 in the middle of the single notes sequence).

 

Finally, we can add an other rule for RS2014 :

- the first anchor of a non-empty phrase should always start at the time position of the phrase.

I was just about to make a post about this myself.  :)

 

Here's a screenshot from my custom. A section starts where the FHP 6 is defined.

 

http://i.imgur.com/uGbjH9B.png

 

Importing the XML made by DDC back into EOF shows that DDC moves the FHP definition to the first note in the section, removing it from where the section begins. In this case it makes the anchor zone disappear in game. 

 

Can you share the psarc file without DD inside ?

I would like to check if the new release of DDC solves your issue ...

 

Thanks

@@firekorn, thanks for your explanations.

 

DDC doesn't care about FHP that are define inside EOF if there's no note on that position which can lead to difference in anchor placement after DDC.

 

When DDC loads each note and each chord, it has to synchronize it with the current "handShape" and the current "anchor".

As the anchors don't have an end time position, DDC uses the start time of the following one to define its range time.

 

So, DDC is able to manage anchors that have a different time position than the associated notes or chords.

With this logic, only one anchor can be associated to each note or chord.

 

@@Berneer, the animated gifs were inverted in your post, weren't they ?

 

In your specific case, DDC adds a new anchor for the first single note in the new section (with a correct fret position of 4), but between the start of the section and the first note, there is no anchor and RS2014 uses the previous one of the previous section.

I will try to force the time position of this new anchor to the start time position of the phrase if the note is the first one in the current phrase.

 

Edit : New psarc file with DD generated by DDC v3.2

@@Berneer,

 

  I am not sure to understand your exact problem.

 

  First two things, it is necessary to define :

   - The finger positions displayed on the strings are managed by "handShape" tags in the XML file.

   - The frets range displayed with yellow numbers under the fretboard are managed by "anchor" tags in the XML file.

 

  My understanding, about your issue :

  - the displayed finger position "2" is normally associated with the previous A5 chord, and its durability is defined by its "handShape" ("endTime" - "startTime"). So we still see the "2" finger, but it is not related to the next single notes, but simply to the previous played chord.

  - the next sequence of single notes starts with a new section and a new phrase, but without any "handShape" (no chord or no FHP defined for this sequence of single notes). So this situation may explain why the previous FHP is remanent (there is no new FHP to be displayed instead of it).

 

  So, to resolve this you should either :

  - Reduce the durability of the previous FHP (a shorter "endTime" for the associated handShape)

  - Define a new FHP for the next sequence of single notes

Please, describe your problem.

@@slgorin,

Songs without DD have this issue. Add DD to correct it ...

@@Rodman,

 

Once you have the 100% mastery bug on a CDLC, you have no other choice but to reset its stats to remove the bug.

Keep in mind that RS2014 keeps the maximum percentage score in its cache.

only small problem i notice so far is a few of the songs I've played seems to show all the notes instead of ghosting the multiples so that you can see the chord change coming. I'll see if it is still that way the more songs I play over again. But I'll take that over the 100% bug any day. 

 

For this issue, you have to ask the CDLC creator to generate again the XML files with EOF (in order to manage correctly the density of repeated chords)

It seems that RS2014 was able to correct it automatically, but no longer in the Remastered edition

Another way is to use the RSToolkit by referencing directly the ".wav" file in the creator tab. This way the Wwise conversion will be automatically made by the tool.