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

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

Thanks chlipouni. I confirm that DDCv3.2 Beta fixes the issue I raised in Post 336 regarding floor (carpet) FHP temporarily not aligned when intended.

 

Awesome.
 

For the Handshape issue I reported in Post 349, you explained to me in PM that  a handshape will disappear when only the fundamental note of a chord is left.  So now I know when the HS marking should disappear. Since my Handshape does start off at highest difficulty with a single note, I guess you just mean that Handshapes disappear when the ramp model becomes MaxChrStr=1. I guess I am then just curious why, from the video I posted in Post 349, that the handshape (which I call concatenated partial handshape to simulate partial handshapes) with the B1 hammer-on, does maintain it's handshape blue lane markings since it also it is in a MaxChrStr=1 state.

 

Thanks for the Beta and solution. I appreciate it.

I came across a case of notes going missing when using DDC in a custom of mine. I have isolated the part where it happens into a test custom:

 

https://drive.google.com/open?id=0B_0HDnEbZi4PNzVDX0NDTXdvdUk

 

After using DDC, the two slides (at 7.624 and 8.153) that come after the chords are missing. Also, the slide at the beginning of the next section (at 13.271) is not found at max difficulty, but it does appear at a lower level.

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

Tried it. Seems to be fixed. Thanks.

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

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

 

@Chilipouni

thanks for you hard work! Regarding those two quotes for version 3.2, is there anything we have to change in the configuration file to make the density fix work?

• I downloaded 3.2 beta
• replaced all the 3.1 files in the Rocksmitih Custom Song Toolkit ddc subfolder (and Toolkit now shows DDC's version as 3.2)
• Imported an old custom into toolkit
• changed version number
• hit generate in the toolkit

Result:

• the 100% bug is fixed
• repeated chords are shown full and not "ghosted" (= not fixed)

Is the ddc beta supposed to fix that last issue, or does the "chord density status" mean something else?

 

Cheers!

@@Azrael,

 

  If you import the psarc file in the first tab of the RSToolkit, you have to generate DD on each XML file before packing again the CDLC.

 

  Another way (and easier if you just want to correct the chord density status), is to use the DDC tab :

  - drag and drop the psarc files

  - set a high value for the "phrase length" parameter (8 or 16)

  - set the check boxes the way you want

  - click on "Generate DD" button

 

  If you choose to generate the DDC log files you can check if this process has been used or not :

  "==> WARNING : High density status is not correctly used (current : 0 / estimated : 504). The density correction process is activated for this arrangement (misused percentage 100 >= 25)."

 

  The last thing to know is that you can adjust the misused percentage (25% by default) that DDC uses to activate or not this new functionality :

  - open the file "ddc_default.cfg" with a text editor

  - change the value of the "minHighDensityMisused" parameter (value in range : [0-100])

  - save the file

  - generate DD again

 

Enjoy ...

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

C could someone explain the different options there are in the DDC section of the custom song creator tool kit. What they actually do?



Phrase Length

The different options in Ramp up model,
ddc_chord_protector
ddc_chord_remover
ddc_dd_remover
ddc_default

Same goes for options under Config file

What I don't like about DCC is it removes so much, It removes all the easy notes along with the hard notes as you lessen the difficulty. At least at the lowest setting it would be nice if it showed at least all the chords of the song.

Kind of like chordify.net shows the chords of the song at he simplest form.

I  mean at least you can just play the root notes of the chords on bass and it sounds good, but DCC takes all that out on the lowest setting, You many have a song with just one chord in it at the lowest dd level.

But it also could be I'm just not using it properly

@@mikejl46

 

This thread's 1st post has a tutorial website that explains everything one needs to fully understand DDC. Check it out.

 

http://www.guitarcade.fr/en/dynamic-difficulty-creator/

 

The DDC software is highly customizable and can accomodate user-created ramp-up schemes to match the one you described in your post, simply by going into the Toolkit's directory, opening the "ddc" sub directory, opening the ddc_default.xml file, customizing it, saving it, and then in the toolkit, clicking "Add" to add your new model.

 

If I understood you correctly, you would get your desired ramp-up model by setting all the "maxChordNotes" attributes to 6, which means that chords would never get dumbed down - either the chord appears or it doesn't for a given level, with lower level showing less chords to allow the user to make chord switches more easily.

 

Phrase Length: If phrases authored in EoF last longer than this number of measures,  DDC will split up those phrases to be the number of measures long dictated by the "phrase length" setting. (Setting of 4 means that 1 phrase of 8 measures will be split in 2; or that 1 phrase of 10 measures will split into 2 phrases of 4 measures plus a "remainder" phrase with the last 2 measures). If you neglect to place phrases in EoF, then DDC will automatically add them, defining them with a duration equal the number of measures in the phrase length setting.

 

For most charters, defining proper phrases in EoF with meaningful durations and names organizes the song in segments that will best link similar passages, making them level up and down together more optimally, let alone be more fun for users to Riff Repeat. Without proper phrase defintions DDC will make very good guesses as to which phrases throughout the song are similar. In the ideal case of good charter phrase defintions, simply set the phrase length to a large number like 20 or higher to prevent DDC from automatically splitting up phrases you've carefully defined.  

The different options in Ramp up model:
ddc_chord_protector:  In fact checking the file for this model, it is exactly the model I proposed to you earlier.  As stated it protects the chords. @@Chlipouni already thought about you :)
ddc_chord_remover: If you just want to play the base notes of chords, then select this model.
ddc_dd_remover: Before October 2016 when Rocksmith Remastered made playcount dependent upon having Dynamic Difficulty (DD) and gave us the ability to prevent songs from frustratingly ramping down mid-song, many people not fans of DD, chose to use DDC to actually remove DD. This is not longer a necessary model.
ddc_default: Default model ramps down the difficulty by a community-established natural combination of removing off-beat notes/chords as well as reducing the number of strings to be played in a chord.

 

One custom model I'd like to try soon which I've notice in REM - Losing My Religion would make a full EMaj chord level down to an E5 power chord, for example. I guess this could be accomplished with a level defined by  maxChordNotes="6" followed by the next level down defined by maxChordNotes="2".

 

Once you sink your teeth into that you can then begin to explore the ddc_default.cfg config file that allows you to further customize DDC:

 

For example:

1) it allows you to set criteria for "how similar" phrases must be for DDC to link them (ramp them up and down simultaneously).

  <linkedDiffParameters>
    <maxDifferencesToLink pct="25"/>
  </linkedDiffParameters>

2) it allows you to define in what order to remove notes at lower levels, for different time signatures

...
<timeSignature beatsPerMeasure="4"  categoryMap="1 3 2 4" subCategoryMap="1 9 5 13 3 11 7 15 2 10 6 14 4 12 8 16"/>
...
<timeSignature beatsPerMeasure="8"  categoryMap="1 3 2 4 1 3 2 4" subCategoryMap="1 9 5 13 3 11 7 15 2 10 6 14 4 12 8 16"/>
...

3) it allows you to define how many ramp-up model levels to merge together into one level change if each level is too similar, in order to avoid having 20 barely different levels for a phrase.It also allows to define which % of the easier levels not to merge together for fear of a steep ramp-up. 

  <mergingLevelsParameters>
    <maxDifferencesBeforeMerging pct="10"/>
    <maxDifferencesAfterMerging pct="30"/>
    <maxDifficultyLevelToProtect pct="20"/>
  </mergingLevelsParameters>

I haven't learned what the following are since they are probably new - they are probably desribed on the web site linked above:

1) <minHighDensityMisused pct="25"/> --> DDC 3.2 says: New parameter in the configuration file to adjust or not the density status of chords. @@Chlipouni, can you elaborate on this one please?

 2) <maxPhraseIterationsLimit val="100"/> --> Rocksmith phrase bars disappear when over 100 phrases are defined in a song. I'm guessing this allows the user to limit the number of phrases in a long song with low phrase length setting.

@@mikejl46 that's the idea behind the Chord protector setting which should force DDC to keep chord for as long as possible.

 

i'm too versed in all the settings of DDC but the DDC help will likely give you some insight on what it's about.

Thanks a lot Berneer and firekorn for the info.

 

I was thinking that might be what that setting is for "Chord protector"

 

 

I will have to take a closer look at all the options and see if I can get it to do what I need it to do.

@@Berneer,

 

  The <minHighDensityMisused pct="25"/> parameter defines the percentage level that triggers the new process of chord density correction.

  This process is designed only for old CDLCs.

  For the new CDLCs that use efficiently the chord density status in EOF, you can set this parameter with a higher value.

  

@@mikejl46,

 

  If you need more explanations about DDC, feel free to ask about it in this topic.

  You can also ask for new features or more parameters. Their development will depend on the complexity of the task.

Well Heck, I need to spend more time learning this game. I just figured out something that I never knew. In Rif Repeater, I can select sections that are hard, bring the difficulty down on just those sections, without bringing down the difficulty on all the other sections that are already easy. Then bring the selections bars back out to play the entire song, with just the hard parts difficulty brought down, pretty much exactly what I was looking for. Perfect, like a whole new game now.

Hey guys, i can't put DD on my CDLC, everytime I add DD to my CDLC, they sync got ruin, after tunning the song start right it away. Why? I'm trying to update all my CDLC to fix 100% bug, HELP please

@@reval121 You go around claiming your issue is with DDC everywhere while tons of user used DDC 3.2 without any issue. It would be nice of you to actually share the CDLC you have issue with and give detailed explanation of what is the issue you are getting. It would also be nice if you didn't hijacked other thread that are barely related to your issue.

@@reval121 You go around claiming your issue is with DDC everywhere while tons of user used DDC 3.2 without any issue. It would be nice of you to actually share the CDLC you have issue with and give detailed explanation of what is the issue you are getting. It would also be nice if you didn't hijacked other thread that are barely related to your issue.

I'm so sorry for doing that. BUt I'm using DDC 3.2 without any success. Looks like I'm screwed. Just one song of my many CDLC has no problem with the DDC 3.2. Cuz DDC 3.0 works fine, but gives me 100% bug. Thanks anyway.

If you don't provide a means (ie. files) to reproduce the problem, it's less likely to ever get fixed for you.

(Apologies for not reading through 19 pages of the topic)

 

- If the first note of a section lies on beat 2 of a measure, should the section/phrase be placed on beat 1 or 2 for best DDC results?

 

- Is it still necessary to give similar phrases the same name?

 

Thanks in advance.

For now, each section and each phrase has to start on the first beat of a measure. The first note of a phrase is always used in the first level of difficulty whatever its position in the measure.

 

The name of phrases doesn't matter because DDC identifies itself the similar phrases based on the sequence of notes they contain. That's why the result phrases are named like p1, p2, ...

Thanks!

Update v3.3 : (12/02/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

 

The big new feature of this release is the simplification of XML files generated by DDC (all attributes with a default value are not included).

For this release you have to use RSToolkit v2.8.1.0-980b5022 or greater.

 

A new option is going to be added in EOF to use the same XML file format ...

Hi Dev's, all,

 

When an error occurs in DDC, where are the logs stored?  I'm getting an error, and I am either having a severe brain fart or the logs are missing. :unsure:  Below is the error I get, and here is my project folder.  I'm sure the error is caused by something I've done, but I don't know what.  My toolkit version is 2.8.2.0-a6a5fd9d.  However, I tried on previous versions and I get the same error, which is also why I think it's something I've done.  I do get a warning for notes crossing a phrase boundaries, but that has never stopped DDC from working for me in the past.  Any help is appreciated.  Thank you, Tysylio.

Hi @@Tysylio,

 

  Just tried to generate DD on your XML files and I have had no issue.

 

  With the DDC tab of the Toolkit, you have to check the "Generate Log" checkbox to obtain the logs.

  If you apply DDC on XML files, the logs are located in the same folder. If you apply DDC on the "psarc" file, the logs are located in a subfolder named "DDC_Log".

 

  If you have no log generated, check your anti-virus settings ...

 

Thanks