http://guitargames.files.wordpress.com/2013/11/ddc-512.png
                            {Original icon from Svengraph}
 
  Dynamic Difficulty Creator
  I am pleased to share with you the "Dynamic Difficulty Creator" which :
  - uses the XML files of each arrangement to produce a new version of these files (files like "PART REAL_GUITAR.xml")
  - generates all phrases automatically (if not already created in EOF)
  - generates all levels of dynamic difficulties from 0 to 19 if needed for each phrase
 

DDC v3.7 supports various time signatures :  
- if a time signature is missing, you can now configure its categorization maps  
- the synchronization process in EOF must respect the rhythm (the measures, beats and time signatures have to be correctly defined in EOF)    
For best results :  
- during the synchronization process in EOF, do not move the notes, just move the main measures (vertical bars)  
- create sections and phrases in EOF carefully because they strongly influence DDC process  
- All sections and phrases must start on the main beat of a measure   
If these rules are bypassed, DDC can work, but the results are not garenteed ...

 
  I'm writting a dedicated tutorial about DDC : DDC Tutorial
 
------------------------------------------------------------------------------------------------------------------------
-- D O W N L O A D   L I N K
------------------------------------------------------------------------------------------------------------------------
  Production (stable) : ddc_v3.7.zip (Requires RSToolkit v2.8.1.0-980b5022 beta or greater)

 
------------------------------------------------------------------------------------------------------------------------
-- U P D A T E S
------------------------------------------------------------------------------------------------------------------------

 

  Update v3.7 : (14/07/2020)

   - New specific part in the log file to display the handShapes properties
   - Fixed bug : HandShapes are not always generated when they contain both single notes and chords

 

  Update v3.6 : (02/12/2018)

   - The "offset" property is now setted if the first beat starts after 0.000

   - New "maxMeasuresPerPhrase" parameter to disable the automatic phrase creation process based on the average number of measures per input phrase

   - Fixed bug : A new beat was always added at time 0.000

   - Fixed bug : A COUNT phrase iteration was always added at time 0.000

   - Fixed bug : The time position of the last noguitar section was always adjusted

   - Fixed bug : The maximum number of generated DD levels wasn't limited to 30

 

  Update v3.5 : (27/07/2018)

   - Fixed bug : When generating the transcriptionTrack tag, a chord must be ignored if it is replaced by single notes at upper levels

   - Fixed bug : Notes are not always generated for odd measures when "ddc_dd_remover.xml" template is used

   - Fixed bug : The computation of number of differences is wrong for the first level of difficulty

 

  Update v3.4 : (20/09/2017)

   - More levels added in the default configuration file

   - In order to add more levels of difficulty, each level is splitted in two sublevels, the first one keep only new notes added in odd measures.

   - Fixed bug : The last notes may be omitted when the last "noguitar" section has an adjusted time position.

   - Fixed bug : Error in calculating the total number of events in each phrase that affected the process of merging adjacent difficulty levels.

   - Fixed bug : Transcription track could produce several single notes at the same time position and on the same fret

   - Fixed bug : Embedded handShapes may produce issue when generating the transcriptionTrack tag

   - Fixed bug : Spaces in chord name and display name were not managed correctly

   - Fixed bug : Count attributes may have wrong values in transcriptionTrack children tags

 

  Update v3.3 : (07/04/2017)

   - Set the default value when an attribute is missing in the input XML file

   - Generation of transcriptionTrack tag without attributes that have the default value

   - Don't generate XML attributes with default value in the DDC output file (RSToolkit v2.8.1.0)

   - Fixed bug : High density status may be forced even if the chord contains any technics

   - Fixed bug : A value of 100 for the "minHighDensityMisused" configuration parameter doesn't deactivate the density correction process

 

  Update v3.2 (28/11/2016)

   - New process to force the density status of chords depending on their position in a sequence

   - New parameter in the configuration file to adjust or not the density status of chords

   - New process to add open notes in chord tags in order to remove display glitches

   - New message in the log if the time position of an anchor is adjusted

   - No more protection of adjacent measures that share the same handShape during the phrase creation process

   - No more generation of linkedDiffs node (only newLinkedDiffs is usefull)

   - Fixed bug : Wrong time position used when generating a new anchor at the beginning of a phrase

   - Fixed bug : HandShapes and anchors may be splitted at the beginning of a new phrase

   - Fixed bug : Linked notes may never appear in any difficulty level

 

  Update v3.1 (02/10/2016)

   - 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

 

  Update v3.0 (01/02/2016)

   - The chords without chord notes are now supported

   - New process to add measure 0 at time 0.000 when startBeat is greater than 0.000

   - New process to keep the highDensity value as defined in EOF

   - Fixed bug : HighDensity status can be overrided with a wrong value

 

  Update v2.9 (23/01/2016)

   - New logic to avoid the split of existing handShapes when the new phrases are generated

   - New process to allow excotic handShape phrases

   - New check to remove handShapes which are empty

   - New logic to allow handShapes without a valid chordTemplate reference

   - Fixed bug : Start time of the first handShape in a phrase may be greater than the phrase start time

   - Fixed bug : HandShape with no visible note inside maybe generated

   - Fixed bug : DDC may crash if duplicate nodes are found in the XML file

   - Fixed bug : The highDensity attribute was not recomputed for lower levels of difficulty

 

  Update v2.8 (06/12/2015)

  - Single distinct notes which are located on the same time position are now managed like a chord if they are associated with a handShape and a chordTemplate.

  - The transcriptionTrack generation process has been modified to manage multiple notes on the same time position.

  - New check about the maximum number of phrases and automatic increase of the phrase length parameter if possible. 

  - New process for increasing the phrase length parameter if the maximum number of phrases will be reached (new parameter in the config file to define this limit).

  - New process for detecting similar phrases (similarities are now computed by measure).

  - New process for detecting duplicate events on a same time position and to avoid a crash of DDC (only the first occurrence is kept by time position).

  - Fixed bug : TranscriptionTrack generation may produce events in the wrong order based on their time position (when the highest level has less events than the lower levels).

  - Fixed bug : Always add the first event of each phrase in the first level of difficulty to avoid a crash in RR.

 

  Update v2.7 (06/04/2015)
  - Fixed bug : XML prolog was missing in the result XML files.

 

  Update v2.6 (31/01/2015)
  - New default value for the phrase length parameter (4).

  - Fixed bug : DDC may generate a wrong value in the "count" attributes when it merges all existing difficulties to create the "transcriptionTrack" tag.

  - Fixed bug : The highest level of difficulty is not use when DDC merges all existing difficulties to create the "transcriptionTrack" tag.

  - Fixed bug : A measure may be not protected by a preceding one if it contains a new sequence of linked notes.

 

  Update v2.5 (05/07/2014)
  - New process to merge all levels of existing Dynamic Difficulty if the "transcriptionTrack" tag is empty.
  - Notes and chords sustain are now considered if they overlap two or more measures (prevent the creation of empty phrases which break the handshapes length).
  - Fixed bug : DDC error when the number of chordNodes is lower than the number of frets defined in the chordTemplate

   Update v2.4 (13/06/2014)
  - New categorization process to allow multiple time signatures.
  - New notation to define the ramp up models.
  - New configuration file (ddc_default.cfg) to allow the modification of internal parameters (category and subcategory maps, merging levels, linked diff.).
  - New parameter to specify the configuration file to use.
  - New checks and associated warnings about the categorization process.
  - New merging process to reduce the number of difficulty levels (separate from the DD generation step).
  - New view of difficulty levels in the log file for a better differentiation of the levels before and after the merging process.
  - Fixed bug : Adjacent levels of difficulty may be wrongly merged together.

   Update v2.3 (13/06/2014)
  - Fixed bug : Some adjacent measures are wrongly protected in the same phrase.
 
  Update v2.2 (15/03/2014)
  - Synchronize events on the timeline before generating the new phrases.
  - Protect adjacent measures in the same phrase if they contain a sequence of linked notes.
  - Generate a warning if a sequence of linked notes overlaps two sections or two subsections.
  - Fixed bug : Last chord may be missing.
  - Fixed bug : New phrase can be created with only one empty measure.
 
  Update v2.1 (15/02/2014)
  - Auto-adjustment to the previous main beat for each section and phrase iteration which is not placed on the main beat of a measure.
  - DDC now allows handShape's end time equals to the start time of the following one.
  - Fixed bug : Technics on chords can be lost if the chord is the first one in the current phrase iteration.
  - Fixed bug : Chord notes may be missing if the chord is the first one in the handShape in the current level of difficulty.
  - Fixed bug : First chord reference in a sequence may be the wrong and chord note technics may appear or disappear.
  - Fixed bug : Phrase length parameter can be ignored when only the last measure of the current phrase is empty.
  - Fixed bug : Linked notes can be ignored when two notes have the same time position.
  - Fixed bug : First section may be missing.
 
  Update v2.0 (24/01/2014)
   - New display of DD levels in the log file to facilitate the DDC process check.
   - DDC now supports anchors on the secondary beats of a measure.
   - New logic added for merging two adjacent levels of difficulty if there is no more than 10% of differences between them.
   - New comparison system to detect similarities between two distinct phrases (less than 25% of differences).
   - New warning added in the log file if a chordNote tag is not found for the fundamental note.
   - New optional parameter "-p" to overwrite the XML file content without changing its name (value "Y").
   - New optional parameter "-t" to generate or not the log file (value "Y").
   - Fixed bug : notes and chords may be missing on the highest level of difficulty.
   - Fixed bug : arpeggios are not generated by DDC if they are at the last position in the chord templates list.
 
  Update v1.9 (10/01/2014)
   - New warning added in the log file if sections or phrases don't start at the first beat of a measure.
   - Fixed bug : Wrong value in "count" attribute of the "phraseIterations" tag in specific cases.
   - Fixed bug : "ChordNote" tag may be missing in lower levels of difficulty for fret hand muted chords.
   - Fixed bug : Process may stop when loading XML file informations if a phrase is defined before the first section.
 
  Update v1.8 (04/01/2014)
   - Arpeggios are now supported.
   - File path removed in the ramp-up model name for the generated comment.
   - Chord Templates are now fully described in the log file.
   - Fixed bug : The phrase "p0" was always generated even if no iteration of the phrase was referencing.
   - Fixed bug : Wrong categorization, if the last measure is not complete (based on the current time signature) and contains notes or chords.
   - Fixed bug : A few notes or chords are missing due to a bug in the sub-categorization process.
 
  Update v1.7 (25/12/2013)
   - New "transcriptionTrack" tag management.
   - Now supports the DD remover functionality.
   - First phrases and sections are not generated if they are empty for the current arrangement.
   - First "COUNT" empty phrase iteration is added between the first beat and the first non-empty phrase.
 
  Update v1.6 (15/12/2013)
   - Synchronize the first measure with the first section before generating new phrases.
   - Fixed bug : The last phrase iteration was missing in the generated XML file.
   - Fixed bug : Minor correction in the "linkNext" sequence management.
 
  Update v1.5 (11/12/2013)
   - New "INFORMATION" status for log messages.
   - New validity check of the XML format.
   - New security checks about the time position of the first anchor and the first handShape.
   - ChordNote tag children are cloned for the fundamental notes in lower levels of difficulty.
   - HandShape endTime is adjusted when it is splitted due to a new phrase iteration.
   - Remove sustains parameter is set to "N" by default.
   - Fixed bug : Sections are lost if there are less phrase iterations than sections.
 
  Update v1.4 (05/12/2013)
  - First empty phrase iterations are not generated.
  - Protect the loading of XML chords and notes when the last measure is not complete.
  - Anchor "time" value is adjusted for the first event of each new phrase iteration.
  - Chord sustains are now collected from the "chordNote" tag.
 
  Update v1.3 (03/12/2013)
  - HandShape "startTime" value is now adjusted to the "time" value of its first associated chord in the current level
  - HandShape "endTime" correction
  - HandShape added for the first chord of each new phrase iteration if necessary
  - Chord notes added on the first chord of each new phrase iteration if necessary
  - Only the needed anchors are now inserted on each level of difficulty
  - Fixed bug : Wrong "chordId" was used in "handShapes" for lower levels of difficulty
 
  Update v1.2 (24/11/2013)
  - Supports the Rocksmith 2014 Score Attack mode
  - Automatic difficulty selection for the three Score Attack levels
  - New "heroLevels" tag added for each non-empty "phraseIteration"
 
  Update v1.1 (19/11/2013)
  - Auto detection of the Rocksmith XML format (2012 or 2014)
  - The following Rocksmith 2014 technics are now supported :
    - All new attributes on notes and chords
    - New "chordNote" elements under "chord"
    - New "bendValues" elements under "note" and "chordNote"
    - "linkNext" logic for combining several chords and/or notes in a complex note in RS2014
  - DDC now works with no "section" and/or no "phraseIterations"
  - Existing phrases in the input XML file are now used as subsections
  - Fixed bug : Wrong "chordId" was used for the lower levels of difficulty
 
  Update v1.0 (03/11/2013)
  - New lightweight executable for Windows 32bit (command line tool)
  - DDC program totally rewritten in Tcl
 
  Update v0.9 (21/09/2013)
  - DDC now supports all technics on the fundamental notes of the chords (palm mutes, bends, slides, ...). 
    You must first activate [song][Rocksmith][Export chord techniques] in EOF for export these informations in the XML files.
  - Two new sub-categories (1 & 2) for category 8 in the default ramp-up model (to soften the rise of the first levels)
 
  Update v0.8 (12/09/2013)
  - Sustain of the fundamental note of a chord was not generated if this chord was the last one of the tab (now it works)
  - Sustain correction wasn't apply on all notes (now it works)
 
  Update v0.7 (03/09/2013)
  - New more powerfull web hosting (but not free ...)
  - New parameter to choose the length of the phrases (2, 3 or 4 measures)
  - New parameter to remove or not the note's sustain
  - New parameter to configure the ramp-up model (* & **)
  - The transformation process starts instantly when the queue is empty
 
  Update v0.6 (30/08/2013)
  - New leveling model with a maximum of 4 new notes or chords at each level transition
  - Up to 21 levels of difficulty for a phrase
  - In the previous release, palm muted effect was omitted during the generation of the XML result file (now it works correctly)
  - Phrases length can be set to 2, 3 or 4 measures (the difficulty highway bar doesn't display when there are too many phrases; increasing the phrase length resolves this problem)
  - Automatic sustain correction for each note with length less than 1/4 of its measure (we can keep those sustains in EOF for future compatibility or different behavior in Rocksmith 2014)
 
  Update v0.5 (26/08/2013)
  - Faster than v0.4 (less than 20 seconds for an arrangement)
  - Source XML files with only two phrases ("COUNT" and "END") are now supported
  - When a phrase reaches its maximum level of difficulty, it is not written in the higher levels
  - Similar Chords templates was merged in the previous version and can loose some specific finger positions
  - "controls" and "phraseProperties" XML elements was omitted in the previous versions
  - DDC now supports chords HandShapes for single notes
 
  Update v0.4 (20/08/2013)
  - Faster than v0.3 (less than one minute for an arrangement)
  - Now supports original XML files with multiple levels inside
  - "events" and "linkedDiffs" XML elements was omitted in the previous version

@@Alex360,

 

The link is in the post from Billkwando ...

@@Chlipouni not sure if Cary on my wayward son has ignores, i need official example tho...

you think it's because of those mutes have douplicate ignore statuses?

it may be the mastery too I think

@@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 ...

@@Chlipouni not sure if Cary on my wayward son has ignores, i need official example tho.

You weren't confusing my signature with the link were you?

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

I think maybe Remastered has broken DD. Or, something.

 

I turned the difficulty override on, played my CDLC Kijun, by KREVA, and saw myself miss at least 4 or 5 notes (not that I should've but....it always fails me a couple times) and my 98% score jumped up to 100%.

708

 

I think maybe Remastered has broken DD. Or, something.

 

I turned the difficulty override on, played my CDLC Kijun, by KREVA, and saw myself miss at least 4 or 5 notes (not that I should've but....it always fails me a couple times) and my 98% score jumped up to 100%.

708

 

 

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 ?

Possibly overmastery bug with mastery values, now RS take those values in account i guess.

It usually off like this, Officials mastery about 0.6
customs like 1.3-1.6 values... 100% granted if this is multiplier for scoring mastery per note I guess?

Note : IT IS NOT LINK TO DDC, my custom made with DD inside EOF have the exact same issue and some custom with DDC don't have the issue at the same degree (not go to 100% directly but still mastery superior to accuracy even at 100% difficulty)

Bonjour @@Chlipouni,

 

I am trying to weed out my final imperfection in final testing of my latest custom, Blaze Bayley - Stare at the Sun. It's not a big deal, but since I've spent so much time on it  I'd like to try to remove this blemish.

 

See this passage where an 1/8 of a measure with no notes shows a floor-FHP of 5. I pause it in the animated gif.

 

http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/Temporary%20half%20beat%20%20floor%20FHP5%20when%20should%20be%204/Temporary%20half%20beat%20wrong%20floor%20FHP5_zpsfceodniu.gif

 

In EoF, it is authored like this. Sorry Customsforge is bugging and won't allow me to post an image other than via a URL.

 

 

You could see I force the FHP to 4 a quarter beat before the b5 note, and FYI I place a new section and phrase at the beginning of measure 247, which contains no note until a quarter beat later.  I am suspecting DDC doesn't is not comfortable with this but I don't see any indication in the DDC log. All I could find in line 10960 and 10961 in one of the difficulties, a peculiar absence of anchors between the B5 note and the previous anchor being a huge 15 seconds earlier with an FHP of 5....

 

Here are the lines of code in question:

        <anchor time="398.692" fret="5" width="4" />
        <anchor time="413.475" fret="4" width="4" />

But as you could see when I pack the CDLC without DDC, it works fine as shown below:

http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/Temporary%20half%20beat%20%20floor%20FHP5%20when%20should%20be%204/PreDDC%20works%20as%20desired_zpsuars7sft.gif

 

I am using DDC 3.1 from RSToolkit 2933f3b1 (dated 24Oct2016).

 

Would you know how I can avoid this issue?

 

I have made a Google Drive folder with all pertinent files, in case you needed to inspect more closely.

 

Thanks.

Berneer:

 

I didn't look at your files (sorry if I'm wrong) but I bet there is a start of a section/phrase where that little glitch is.

 

Try placing a fret hand position of 4 at the start of the section/phrase, even if there isn't a note there.

Thanks rockfirstlast.

 

Just tried it. It doesn't fix the issue unfortunately. It looks like this instead. Early in the song, in the first of 3 iterations of this same phrase, it looks slightly different but still with the issue. Again slightly different but still with issue in 2nd iteration of this phrase. Interesting the first two iterations highlight the floor as if FHP was 2. THe 2nd iteration shows a floor FHP of 2 but with width 5? The inconsistent look suggests it is a game glitch?

 

Aside: Is anyone else having the same issue of not being able to post images on Customsforge for at least a week now?

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. 

@@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

@@Chlipouni The problem is that the FHP (or anchor) move in a way that isn't actually define anywhere in EOF by the user. The anchor move to the 5th position (with ddc) while it should move to the 4th (as define in EOF).

 

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.

Yes, exactly as Firekorn wrote.

 

I did set FHP of 4, for the single notes. I tried shifting it a bit to the left and to the right but the same problem occurred with DDC and did not occur without DDC.

 

Thanks a lot for your attention. I really appreciate it!

@@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

Thanks for looking into this @@Chlipouni!!

 

I will try to check out your new psarc tonight but it's tight for me this weekend and I might only be able to check Sunday evening.

 

I did not invert the animated gifs in my earlier post.

 

Top animated gif --> After DDC

Bottom animated gif --> Before DDC

 

When I say "floor FHP" that was in contrast to yellow highlighted fret numbers below the strings which are goverrned by the anchor XML code. Well both should be governed by the anchor XML code. 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). 

 

When you click the link to the 3 screenshots from post 338 where I did as per Rockfirstlast's suggestions of moving the FHP=4 to the beginning of the section instead of being at the first single note, B5,  after section start, each screenshot behaves a bit differently. The 1st link (3rd occurence in the song) shows a momentary floor FHP=5, width 4, the animated gifs and EoF screenshot  are based on this occurence. The 2nd link shows the 1st occurence of this same phenomena in the song, in this case with a "floor FHP = 3,width 4". The 3rd link shows the 2nd occurence in the song and it also has a "floor FHP = 3, width 4. Sorry if I wasn't clear on that earlier. In each occurence, the preceding event is the same power chord with same FHP. But really we only look at the 3rd occurence screenshot for which I provided animated gifs and EoF screenshot and solving that will solve the issue. Perhaps you've already solved it. :)

 

Regarding: " 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." 

 

There is an FHP definition, and by extension an XML anchor initially at the B5 note,but now at section start since Rockfirstlast's suggestion and shown with in-game footage  in post 338.

 

Regarding: "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."

 

That is what I did in EoF upon Rockfirstlast's suggestion and the problem persists. So I'm unsure this will solve the issue. I will try my best to confirm late tonight. Soccer party till 3am & waking up at 5am to drive out of town 3 hours away..... but I am burning to solve this so sleep be damned. :) 

 

Bon weekend!!

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

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.

 

Can you share the psarc file without DD inside ?

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

 

Thanks

 

 

I would, but I already went ahead and made the DD manually.  :)

 

It is the same issue that Berneer is describing, so it should be solved.

Great stuff and fast work @@Chlipouni. Your fix resolved the issue completely and I am thrilled!

 

Here is the 3rd occurence of my original issue:

New animated gif

http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/Temporary%20half%20beat%20%20floor%20FHP5%20when%20should%20be%204/DDC%203.2%20fixes%20my%20issue%20-%20thankyou_zpscy342cwt.gif

(trying posting image from Google drive, doesn't work, any special procedure to post an image from Google Drive? )

 

I also prefer how the yellow number FHP below the strings behave. So it seems you have somehow improved that too.

 

When I come back in town I'll have to ask you some questions about handshapes working differently from top level to lower level, such as starting later a lower level than a higher level or even splitting up and making a handshape hole in the middle of an intended handshape. I was just going to accept it and post my custom, but I thought maybe this was an issue you'd like to know about and why not make it perfect? :)  I'll post more details later, but they are the same details as I had noticed while testing chordify in my latest long chordify post I made a month ago. In fact if you check my custom I posted a few posts above in that Google Drive it's already present in that custom in the intro when you level down 1 or 2 levels. But I'll show specifics ASAP.

 

Hmm, 4:13am. Supposed to be waking up in 47 minutes.... screw it, staying awake and will watch newest MacGyver episode! At 41 years old, it should take me 12 days to recover from this.... :) It's ok, we are the soccer champions and it feels great!

So using your DDC 3.2 psarc you linked above for my Blaze custom, I wanted to show you the following.

 

1. I did notice DDC 3.2 seems to fix the "Handshape starting later than in a higher difficulty" problem I reported in the chordify testing thread and which I thought I noticed in my DDC 3.1 packaging of the custom linked in Post 340 but can't seem to find anymore. I guess I'll confirm it when I resume chordify testing.

 

2. In the intro of my custom I noticed when leveling down 1 step the disappearing of every 1st of 2 concatenated handshapes (by concatenated I mean separated by 2ms, to give semblance of a partial handshape spanning the multiple concatenated handshapes). See below:

 

Here it is in EoF:

 

Can you please refresh my memory by confirming the following:

DDC intends to keep handshape marking (lane highlights and all fingerprints, even those of notes not appearing in lower levels) all the way down to the bottom level? If yes are there circumstances when it is expected that DDC will not do this. I have found some instances in my custom at lower levels where some or all handshape markings are dropped.  Just curious the criteria to know if the behaviour I see in-game is expected.

 

Thanks!

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

   - New process to force the density status of chords depending on their position in a sequence

   - New parameter in the configuration file to adjust or not the density status of chords

   - New message in the log if the time position of an anchor is adjusted 

   - Fixed bug : Wrong time position used when generating a new anchor at the beginning of a phrase

   - Fixed bug : HandShapes and anchors may be splitted at the beginning of a new phrase

 

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

Thanks chlipouni. Will do.

 

I think it is just a bad coincidence that I tried your DDC 3.2 beta you sent me 2 days ago by PM and repackaged my custom and though the original anchor-FHP issue i reported above is resolved, some strange behaviour is happening and my custom's solo tone is now dead and I have no idea yet how to fix it. I have no reason to believe it is DDC-related. Interesting though PC Plum has experienced a similar issue last Saturday when trying to add DD with DDC. Tonight PLum found a solution and I will attempt to understand and implement it tomorrow. Once my custom is working again I believe I will be able to give you confirmation that DDC 3.2 Beta from the above link is performing as intended.

 

Not sure I understand exactly all your bullet points above as I've fallen a bit out of the loop, so I will at least confirm my issues have been fixed. If you have other specific tests you'd like me to do, I would be happy to help.