Chlipouni

Sorry, I forgot to check this topic. As you used Wwise yourself, it is possible that you forgot to set the "seek granularity" parameter. Another way, is to use the RSToolkit

Does EOF apply automatically this logic each time it generates the XML files ? It may be necessary to add a check if the same sequence of chords use the low density (by a user action) and none of these chords contain any technics. In my opinion, we need to validate that before changing the EOF handshape logic.

Yes, only open notes are needed in the chordNotes tag to avoid the display glitches. But you can also add the other notes of the chord (if it's easier to code)

Did you convert the wem files by yourself with Wwise or by using the RSToolkit ?

@@raynebc, About the chord density : - As you can see in my example, the first chord in the section (and phrase) has the high density status. - In the game, this chord is fully displayed, so its density status is forced to 0 (Toolkit ?, Game itself ?) About the display glitch, it appears only when : - highdensity = "0" (this status may be forced when the chord is the first in its section) - The chord contains at least one open note - The open notes of the chord are not defined in the "chordNotes" tag So, in my opinion, each chord that contains open notes should always define its open notes in the "chordNotes" section when : - it has the low density status - its is the first chord in a section or a phrase, whatever its density

Can you share a link to your "psarc" file ?

You can use the BPR tool to move the measures and beats in order to sync the rhythm with the notes, but with this tool you will not be able to move the notes. If the song has too much issues, it should be better to recreate it completely.

@@raynebc, Let's look at the following example (CDLC : 4 Non Blondes - What's Up) : <phraseIterations count="40"> ... <phraseIteration time="90.978" phraseId="12" variation=""> ... </phraseIterations> <sections count="21"> ... <section name="verse" number="5" startTime="76.754"/> ... </sections> ... <chords> ... <chord time="87.466" linkNext="0" accent="0" chordId="10" fretHandMute="0" highDensity="0" ignore="0" palmMute="0" hopo="0" strum="down"> <chordNote time="87.466" linkNext="0" accent="0" bend="0" fret="0" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="1" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <chordNote time="87.466" linkNext="0" accent="0" bend="0" fret="2" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="2" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <chordNote time="87.466" linkNext="0" accent="0" bend="0" fret="2" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="2" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="3" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <chordNote time="87.466" linkNext="0" accent="0" bend="0" fret="2" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="3" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="4" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> </chord> <chord time="90.978" linkNext="0" accent="0" chordId="10" fretHandMute="0" highDensity="1" ignore="0" palmMute="0" hopo="0" strum="down"/> <chord time="91.425" linkNext="0" accent="0" chordId="10" fretHandMute="0" highDensity="1" ignore="0" palmMute="0" hopo="0" strum="down"/> <chord time="91.649" linkNext="0" accent="0" chordId="10" fretHandMute="0" highDensity="1" ignore="0" palmMute="0" hopo="0" strum="down"/> ... </chords> In this CDLC, a display glitch appears only on the "A" chords that are the first one in their section. In the XML code, the chord tag at time "90.978" is the first one of its phrase iteration and the first one of its section. The display glitch appears for this chord because : - the chord tag doesn't contain its chordNotes - there is one open note in this chord As this CDLC is old, maybe EOF doesn't allow this now, What is strange, is that the display glitches don't appear in RS2014 edition, only in RS2014 Remastered. The big change that Ubi has made is to allow the player to select each phrase in RR as the sections in the previous edition. So for now and only for this CDLC, my conclusions are the following : - Each first chord in a section must contain its chordNote tags (at least for the open notes) - Maybe the same for each chord that is the first in its phrase (unfortunately the CDLC doesn't contain this case) About the scoring 100% issue what we know at the moment is that : - Only arrangements with chords are concerned by this issue - Phrases iterations are now selectable in RR as the sections were in the previous release of the game => So we have to find the new rules to apply on "chords", "chordNotes" and "handShapes" That's all for me at this time

@@raynebc, About the issues we have on existing CDLC with the new release of RS2014, I think that they are related to the handShape management. In the new release of RS2014, phrases are now managed as the sections were in the previous one, so we have to apply the same rules for them : - A handShape cannot overlap two adjacent phrases - The first chord of a phrase need to be complete (all chordNotes inside) and with the low density status We just need to try these rules on a CDLC and check if that solves our issues ...

@@raynebc, About the issues we have with RS2014 Remastered Edition : - 100% scored when chords are in the arrangement - Display glitches that appear with this new release I think that I have found the reason : => In the previous release, we had define that handShapes cannot overlap two sections. As now phrase iterations are managed as sections, I think that we have to apply the same rule with phrases ! => About the display glitches, they appear now on chords that contain an open note, but only when the chord is the first of its phrase iteration (In my CDLC these chords don't contain the chordNotes tag)

For this CDLC : 4 Non Blondes - What's Up New display glitches appear on chords with open notes since the new release of "RS2014 Remastered". This CDLC were working fine with the previous release.

I have just tried a few songs : - Official DLC : works normally - Official CDLC : works normally - Custom CDLC without DD : works normally - Custom CDLC with DD : 100% bug For your information, XML arrangement files don't contain these kind of informations, so DDC doesn't manage them. May be a solution in the other XML or JSON files managed by the RSToolkit ?

Update v3.1 : - The order of XML attributes has changed for note, chordNote and handShape tags - The feature that automatically adjusts the sustain of notes has been removed - Fixed bug : DDC may crash during the check of overlapping sustains

@@Redslam, This issue is a bug in DDC v3.0. It is now fixed in DDC v3.1 (will be released soon). Thank you for reporting this issue

@@ShrillBear52, Your CDLC is divided in sections (intro, verse, chorus, ..., outro) and each section is divided in phrases (two or more measures). When you add the sections in EOF, you need to take care about the notes just before and after the section change. For example, if you have two linked notes, one before and the other after the section change, they will be separated in the game in case of DD usage. It is the same with the "highdensity" status of the chords. A chord is always setted as low density when it is the first one of a section. About the phrases, the rules are the same. If you have not created the phrases yourself in EOF, DDC will create them automatically by using the "phrase length parameter". It is always better to create the phrases in EOF, so you can define for DDC the groups of adjacent measures that have a repeating pattern of notes. In RS2014, you can select the sections in the Riff Repeater. The phrases are displayed as boxes which leveled up or down depending on your playing skills. So, as I said in my preceding post, the two first issues are related to the sections and phrases changes. About the synchronizing process in EOF : - You move the first measure to synchronize the rhythm markers with the beginning of the soundtrack. - You also need to synchronize the following measures all along the track, if they are not correctly synchronized. You have to do this from the beginning until the end. Importing notes on the arrangement can help you to synchronize the measures, but you only have to move the measures (never move the notes, they will follow the measures moves).

Can you share the XML file for the arrangement that causes the issue ? I would like to check if the new release of DDC solves the issue ... Thank you

I agree with that, but have you ever seen an official CDLC with a section that doesn't start on the main beat of a measure ? Rocksmith 2014 allows too to play CDLC which are badly synchronized :mellow:

@@ShrillBear52, About the two first issues (chord boxes and single linked notes), it is because these chords and notes are separated by a new section. With DD, each section can evolve separately and may have different levels of DD. To correct this, you can move the section, but as Firekorn said, a section must always start on the first beat of a measure (DDC do this automatically if it is not the case in your EOF project). About the grid you can use the [song][Highlight non grid snapped notes] menu in EOF to display all notes which are not grid snapped (it depends on the grid snap settings that you have previously chosen). When you create a new song, it is better to synchronize each measure with the soundtrack instead of moving the notes. If you do that, you will be able to import the notes in each arrangement without having to resync them with the soundtrack.

@@Alex360, By testing the song, I saw that a few sections never leveled down when I let the song running without playing a note. It maybe the case when the only notes in difference between two levels have all the ignore status. Another useful information is that when you use DD, the percentage of played notes depends on the playable notes inside the current level ...

@@Alex360, The link is in the post from Billkwando ...

@@Billkwando, In my mind, the ignore status is exactly here to ignore a note in the scoring system. But I have never tried to play with it. Another thing that may have an influence, is your last section that has an empty phrase at the end. Nevertheless, it would be interesting if you could try to remove the ignore statuses ;) Thank you

I don't know which of the following cause the issue : - All the chords with the "Fret Hand Mute" status also have the "ignore" status. - All sections of the song have the same name. So can you try first to remove the "ignore" status for all muted chords ? Thanks

Thank you for the answer. So, It is not necessary to modify DDC in order to manage such cases...

Hi Berneer, My last question in the EOF topic was about the "handshape -1 dummy chords". Does this method still needed ? If yes, how can I generate it with EOF tool, and what is its exact purpose ? Thanks

Thanks Alex360 for sharing your findings. I will have to investigate such a case when single notes are used in conjunction with chord notes. But for now, the Billkwando song doesn't use such duplicate notes.