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

I'm only adding the bass part as that's what I play and not the guitar parts. There's 18 parts for the guitar alone for the tab I'm using. I can't find any more due to DMCA's.  As for the sections... how do I go about doing that?

I'm only adding the bass part as that's what I play and not the guitar parts. There's 18 parts for the guitar alone for the tab I'm using. I can't find any more due to DMCA's.  As for the sections... how do I go about doing that?

 

To create sections with EOF, select the first beat of a measure and use [beat][Rocksmith][Place RS Section].

 

With the vocals in the song, you can easily detect the start of each verse and each chorus. Then add an intro section at the beginning and an outro section a few measures before the end ...

Is there any notification that it's successful or added?

Yes, the name of the added section is displayed on the top of the vertical bar. It may depends on the EOF preferences you have ...

Is it possible to make an update of the DDC that incorporates the new function of the ghost handshapes of EOF? Cause the chords i've made with this function only shows its boxes (without DD there's no problems).

Also, sometimes certain chords appears as if in EOF it be marked with crazy status (the chord show its gems, not just the repeat box). I set the phrase length in DDC longer than the phrases i've made in EOF so i don't know why a chord that doesn't cross a phrase it's showing like it has crazy status.

Is it possible to make an update of the DDC that incorporates the new function of the ghost handshapes of EOF? Cause the chords i've made with this function only shows its boxes (without DD there's no problems).

 

Also, sometimes certain chords appears as if in EOF it be marked with crazy status (the chord show its gems, not just the repeat box). I set the phrase length in DDC longer than the phrases i've made in EOF so i don't know why a chord that doesn't cross a phrase it's showing like it has crazy status.

 

Hi giulianolanz,

 

  I never used this functionality in EOF.

  Can you describe how to use it ?

  I need a test case to reproduce this issue ...

 

Thank you for your help

Here's a description of its purpose:

http://customsforge.com/topic/22596-handshapearpeggio-for-multiple-notes-at-a-time/page-2?do=findComment&comment=183033

 

It basically is just a mechanism to override the handshape tag that would be exported for a chord, so the handshape and chord tag for a single chord in EOF would end up referring to different chord template IDs.

Thanks raynebc,

 

  But I don't find how to set it in EOF  :huh:

It's the "Ghost HS" checkbox in the edit pro guitar note dialog.

Raynebc,

 

  Ok.

  So this generates a new chordTemplate with no name for each chord with this special flag.

  

  Does it work in all cases ?

  Are there special cases in which an anonymous chordTemplate is not generated ?

  

  I tried to use it with the following example :

 

And EOF generated the following XML sequence :

  <chordTemplates count="3">
    <chordTemplate chordName="D" displayName="D" finger0="-1" finger1="-1" finger2="-1" finger3="1" finger4="3" finger5="2" fret0="-1" fret1="-1" fret2="-1" fret3="2" fret4="3" fret5="2"/>
    <chordTemplate chordName="D3" displayName="D3" finger0="-1" finger1="-1" finger2="-1" finger3="-1" finger4="3" finger5="2" fret0="-1" fret1="-1" fret2="-1" fret3="-1" fret4="3" fret5="2"/>
    <chordTemplate chordName="" displayName="" finger0="-1" finger1="-1" finger2="-1" finger3="1" finger4="-1" finger5="2" fret0="-1" fret1="-1" fret2="-1" fret3="2" fret4="-1" fret5="2"/>
  </chordTemplates>
...
      <chords count="3">
        <chord time="4.295" linkNext="0" accent="0" chordId="0" fretHandMute="0" highDensity="0" ignore="0" palmMute="0" hopo="0" strum="down">
          <chordNote time="4.295" 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="3" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/>
          <chordNote time="4.295" linkNext="0" accent="0" bend="0" fret="3" 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"/>
          <chordNote time="4.295" 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="5" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/>
        </chord>
        <chord time="6.295" linkNext="0" accent="0" chordId="1" fretHandMute="0" highDensity="0" ignore="0" palmMute="0" hopo="0" strum="down">
          <chordNote time="6.295" linkNext="0" accent="0" bend="0" fret="3" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" 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"/>
          <chordNote time="6.295" 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="5" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/>
        </chord>
        <chord time="8.295" linkNext="0" accent="0" chordId="2" fretHandMute="0" highDensity="0" ignore="0" palmMute="0" hopo="0" strum="down">
          <chordNote time="8.295" 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="3" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/>
          <chordNote time="8.295" 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="5" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/>
        </chord>
      </chords>
...
      <handShapes count="3">
        <handShape chordId="0" endTime="4.351" startTime="4.295"/>
        <handShape chordId="1" endTime="6.351" startTime="6.295"/>
        <handShape chordId="2" endTime="8.351" startTime="8.295"/>
      </handShapes>

Only one anonymous chordTemplate was generated, and the second chord (with "Ghost HS" checked) has a name.

Is it normal ?

 

Another issue, is when I update an existing chord with the "Ghost HS" by changing the chord notes inside. In this case, the anonymous chordTemplate disappears in the XML file ...

 

Thanks

You did chords that doesn't contain ghost notes so the ghost handshape doesn't has sense at all (the idea of the Ghost HS is to represent the full fingering despite that the strumming doesn't contain all the notes). You have to modify your example like this in EOF:

e|-----2-------2---------2-------|
B|-----3-------3--------(3)------|
G|-----2------(2)-------2--------|
D|---------------------------------|
A|---------------------------------|
E|---------------------------------|

                    (G)        (G)

Now, the chords with ghost HS can have the same fingering than the D chord.

@,

 

  Thank you for this information   :)

It's a pretty new feature so I haven't stress-tested it, but I'll definitely want to fix any bugs people find.

It's a pretty new feature so I haven't stress-tested it, but I'll definitely want to fix any bugs people find.

 

Hi raynebc,

 

  In DDC, the handshape management is complex because :

  - DDC creates new chordTemplates for chords with less notes than the original one (a chord with 6 notes generates 4 new templates for 5, 4, 3 and 2 notes)

  - The chordId of a chord can be different at each level of difficulty (it has to reference the right chordTemplate)

  - DDC has to manage the phrase switching and may update handshapes (in the game, a phrase can have a level which is not the same than the previous or following phrases)

  - DDC may split or merge handshapes when a chord is not selected at a specific level of difficulty

 

  This new functionnality should work without modification in DDC if you keep the following rules :

  - Use as many chordTemplates as you want (for each ghost chord, you can create a new template with no name if this template doesn't exist yet)

  - Split the handShapes if necessary, but their chordId must be the same as those of the chords located in the same period of time

  - Always keep the "chordId" coherence between chordTemplates, chords and handShapes

 

  What I understand about this new feature is that when a chordTemplate has no chordName, the name of the chord and the finger positions are not displayed in the game.

 

  For now, DDC doesn't keep an handShape when it has a chordId which is not the same as the one used by the chords located between the startTime and the endTime positions of the handShape.

 

  I am curious how official songs work with this feature.

  Do you have an XML file from an official CDLC with various levels of difficulty ?

 

Thank you

@@Rockfirstlast posted a video link to "Heart Shaped Box" (https://youtu.be/UA5AQ-9y61s?t=25s) that seems to have chords inside of a handshape tag. I don't have an official XML for it though.

 

EOF won't specifically add/remove the name from whatever chord template ID it uses for a ghost handshape chord's handshape tag, it probably just depends on the chord and whether the user manually named it.

Raynebc,

 

  I tried a simple test with standard chords (no ghost note and no ghost handshape).

  If I simply unset the chordName and displayName of the chordTemplates in the XML file, the chords are displayed with no name in the game (and it works fine with DDC).

 

  What are the reasons of using a so complex logic for this functionality ?

 

Thank you

Raynebc,

 

  For your information, I made a test case directly with EOF without using ghost notes nor ghost handshape feature :

  - Design all chords as usual with the displayed notes only

  - For each chord for which the name has not to appear in the game, set its name field with a space character (empty field is automatically replaced by the known chord name)

  - Save

  - Generate DD

  - It works ...

 

  We maybe need a new checkbox to explicitly set this feature !

 

Hope that this tip simplifies your work ...

The thread I linked to had some very specific ways some people wanted to author things (ie. a handshape tag where several different partial versions of a single chord are played back to back) and at the time this was the solution I decided on. Since then, EOF's improvements to handshape phrases and honoring chord names (even identical chords with different names are exported as different chord templates) may have made the ghost handshape feature less necessary, but it offers another way to do things.

 

I'm a bit confused about what functionality you're suggesting could use a checkbox?

Actually in EOF, I have to set a space character inside the name field to obtain a chord without name.

If I let this field empty, EOF generates automatically the known name of this chord.

 

I talked about a checkbox (or something else) to have something more explicit and simpler to generate a chord without its name in the game.

 

About the "Ghost HS" functionality, it could be another way to implement this feature, but I think you would have more work to do to obtain consistency in the "chordId" references between the chordTemplates, chords and handShapes. It would also ask more work for the users to use this feature in EOF.

 

Thank you

If EOF shows a chord with a name in brackets, it will indeed export with that name. I'm not sure if it's much simpler for the user to have to check a box for each chord that should export with no name than to use the "Edit name" function which could even be used for multiple dislike chords at the same time.

 

The more specific a author's wants are for charting something, such as whether two adjacent chords both display a chord name, the more complicated things get. If you provide a specific example (ie. screen shot and/or project file) of EOF handling a chunk of tablature in a way that is problematic for DDC I can put some thought into it, but what EOF wants and what DDC wants are likely going to ultimately conflict in some ways. Honestly, I'm not sure if there's a real need for ghost handshapes at this point, but it's possible that it could still be used unique ways.

I missed a few new features in EOF ...

 

I am analyzing the relationships between chordTemplates, notes, chords, and handShapes. I have to find a way to implement them in DDC.

 

It might take a while and a few more questions from me on these forums ...

 

Thank you for your patience  :huh:

@@SmellsLikeMonkey,

 

  I have generated DD in your CDLC with DDC v2.8 beta.

 

  You can download it here

 

  Can you try it and tell me if it is ok for you about the new handShapes features ?

 

Thank you

Looks perfect when i set the maximum difficulty in the riff repeater (all the gems, chords, handshapes), but it crashes when i try to resume the song. There's a little error, but you got it! it's only a little mistake, i hope you can fix it!

Looks perfect when i set the maximum difficulty in the riff repeater (all the gems, chords, handshapes), but it crashes when i try to resume the song. There's a little error, but you got it! it's only a little mistake, i hope you can fix it!

 

  The issue may be caused by the missing following informations in the XML file :

  - the first ebeat which usually starts at time = "0.000"

  - the first phrase with name = "COUNT"

  - the first phraseIteration for the COUNT phrase

 

  I don't know if the "COUNT" phrase is mandatory in RS2014, but DDC had always considered the first phrase in the list as this special one.

 

  Can you generate again your CDLC with the last hotfix of EOF and check if the COUNT phrase is here or not ?

 

Thank you 

 

Looks perfect when i set the maximum difficulty in the riff repeater (all the gems, chords, handshapes), but it crashes when i try to resume the song. There's a little error, but you got it! it's only a little mistake, i hope you can fix it!

 

  The issue may be caused by the missing following informations in the XML file :

  - the first ebeat which usually starts at time = "0.000"

  - the first phrase with name = "COUNT"

  - the first phraseIteration for the COUNT phrase

 

  I don't know if the "COUNT" phrase is mandatory in RS2014, but DDC had always considered the first phrase in the list as this special one.

 

  Can you generate again your CDLC with the last hotfix of EOF and check if the COUNT phrase is here or not ?

 

Thank you 

 

I always get the advise "There is no COUNT phrase..." in EOF and never had problems with crashes including DD . What is the COUNT phrase? i really don't know