Jump to content

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

  • Replies 476
  • Views 62.7k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Chlipouni
    Chlipouni

    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 modific

  • This warning will be in the next EOF hotfix.

  • Chlipouni
    Chlipouni

    DDC Tutorial update for DDC v2.4 : DDC tutorial   Do not hesitate to ask for updates in the DDC tutorial (missing information or too obscure explanations ;))

Featured Replies

Thanks for the comment, Alex. The need to use Wine suggests that the DDC module in the mac version of Toolkit is not functional. To be more specific, if you don't need Wine to run the creator and convertor modules from the Toolkit app, you shouldn't need it to run the DDC module. Launching DDC.exe with Wine means you're using the PC program. I'm new to this, so perhaps I'm missing something.

  • Author

Thanks for the comment, Alex. The need to use Wine suggests that the DDC module in the mac version of Toolkit is not functional. To be more specific, if you don't need Wine to run the creator and convertor modules from the Toolkit app, you shouldn't need it to run the DDC module. Launching DDC.exe with Wine means you're using the PC program. I'm new to this, so perhaps I'm missing something.

 

For now, DDC is only released for PC.

That's why you need Wine to use it in mac OS.

Thanks for the fast reply, Chlipouni. That's the definitive answer that I was looking for. I've been using the PC Toolkit via Parallels, which allows me to do everything that I need, including DDC. It works great and I think I'll continue do that. When I ran ddc.exe via Wine in Mac OS, I was having problems adding the different levels of difficulty options.

When I submit CDLC, I'm asked to enter levels of difficulty for DDC. I've been using the default_DDC setting when I create the files and I don't know the default levels of difficulty.

  • Author

When I submit CDLC, I'm asked to enter levels of difficulty for DDC. I've been using the default_DDC setting when I create the files and I don't know the default levels of difficulty.

 

If you use DDC on XML files, a log file is generated for each arrangement.

 

In the log file, just look at the "Global Informations" section to obtain the maximum level of DD.

 

As an example :

 

====================================================================================================
==   G L O B A L   I N F O R M A T I O N S                                                        ==
====================================================================================================
 
D.D.C.                          : v2.6
XML format                      : Rocksmith 2014
Artist name                     : The Company Band
Song title                      : Zombie Barricades
Arrangement name                : Lead
Phrase length                   : 8
Remove sustain                  : N
Configuration file              : C:\Rocksmith\Logiciels\RocksmithCustomSongToolkit-v2.6.1.0\ddc\ddc_default.cfg
Ramp-up model                   : C:\Rocksmith\Logiciels\RocksmithCustomSongToolkit-v2.6.1.0\ddc\ddc_default.xml
Max Differences Before Merging  : 10 %
Max Differences After Merging   : 30 %
Max Difficulty Level To Protect : 20 %
Max Differences To Link         : 25 %
DD protection limit             : 3
Maximum level of difficulty     : 8
Number of phrases               : 9
Number of phrase iterations     : 23
Average iterations by phrase    : 2

Hi chlipouni,

 

Hope all is well!

 

Applying DDC2.6 to my latest CDLC, MacGyver Theme Song, and I have a couple of questions mostly to satisfy my understanding of DDC and none of which cause me serious problems, yet:

 

1) This is not new but I neglected to ask you earlier on:  In the log file what does "DOM" stand for. Just curious.

12. Generate the result XML file
      => 1 ms
    - DOM phrases generation
      => 0 ms
    - DOM phrase iterations generation
      => 1 ms
    - DOM new linked difficulties generation
      => 1 ms
    - DOM chord templates generation
      => 0 ms
    - DOM sections generation
      => 1 ms
    - DOM DD levels generation
      ==> INFORMATION : LEVEL 0 : HandShape startTime adjustment (46.191 -> 46.402)
      ==> INFORMATION : LEVEL 0 : HandShape startTime adjustment (47.454 -> 47.662)
      => 62 ms

2) You'll notice that in the above code I get a "HandShape startTime adjustment" comment. Problem is that, according to the image below  the unadjusted times 46.191 & 47.454 seem to not require any adjustment. I checked in-game and it doesn't have adverse effects on the CDLC  in that the fingerprints and the blue handshape markings along the side of the note highway are fine but I was wondering if you could clarify what is going on here.

 

http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/DDC%20Log%20Handshape%20Adjustment%20Question%20-%2011Mar15/Handshape%20Start%20Time%20Adjustment_zpsxi9yxyqd.png

 

 

3) I see in the DDC Log section called "Sections & Phrase Iterations" a column called "Overlap". I am unfamiliar with this and see a bunch of Y and N so I was wondering if this was worrisome. I'm noticing it may a benign informational item stating that the beginning of a measure has a note sustain tail crossing it. I guess this information display is related to the 2nd bullet in the DDC2.5 updated feature set:

"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)"

I'm not sure how to read this "Overlap" column and judge that I should fix something or not. Here is the DDC log I am getting and below is an EOF screenshot of measures 17 and 18 shown and reported as Overlap = Y, which wouldn't normally alarm me unless I am missing something. 

+----------------------+--------+---------+---------+----------+--------+--------+--------+---------+
| SECTION              | PHRASE | MEASURE | PROTECT |     TIME | EBEATS | LENGTH | EVENTS | OVERLAP |
+----------------------+--------+---------+---------+----------+--------+--------+--------+---------+
| intro.0              | p0     |       1 |         |    0.098 |      4 |  1.902 |      0 |       N |
|   .                  |  .     |       2 |         |    2.000 |      4 |  1.902 |      0 |       N |
| intro.0              | p1     |       3 |         |    3.902 |      4 |  1.687 |      7 |       N |
|   .                  |  .     |       4 |         |    5.589 |      4 |  1.666 |      7 |       Y |
|   .                  |  .     |       5 |         |    7.255 |      4 |  1.687 |      7 |       N |
|   .                  |  .     |       6 |         |    8.942 |      4 |  1.634 |      7 |       Y |
| intro.1              | p2     |       7 |         |   10.576 |      4 |  1.690 |      7 |       N |
|   .                  |  .     |       8 |         |   12.266 |      4 |  1.627 |      6 |       Y |
|   .                  |  .     |       9 |         |   13.893 |      4 |  1.692 |      7 |       N |
|   .                  |  .     |      10 |         |   15.585 |      4 |  1.692 |      7 |       Y |
| transition.0         | p3     |      11 |         |   17.277 |      4 |  1.651 |      2 |       N |
|   .                  |  .     |      12 |         |   18.928 |      4 |  1.675 |      3 |       N |
|   .                  |  .     |      13 |         |   20.603 |      4 |  1.622 |      2 |       N |
|   .                  |  .     |      14 |         |   22.225 |      4 |  1.681 |      2 |       N |
| hook.0               | p4     |      15 |         |   23.906 |      4 |  1.681 |      8 |       N |
|   .                  |  .     |      16 |         |   25.587 |      4 |  1.645 |      4 |       N |
|   .                  |  .     |      17 |         |   27.232 |      4 |  1.685 |      3 |       Y |
|   .                  |  .     |      18 |         |   28.917 |      4 |  1.660 |      5 |       Y |
|   .                  |  .     |      19 |         |   30.577 |      4 |  1.693 |      4 |       N |
|   .                  |  .     |      20 |         |   32.270 |      4 |  1.673 |      3 |       Y |
|   .                  |  .     |      21 |         |   33.943 |      4 |  1.633 |      3 |       Y |
|   .                  |  .     |      22 |         |   35.576 |      4 |  1.663 |      5 |       Y |
| buildup.0            | p5     |      23 |         |   37.239 |      4 |  1.663 |      2 |       N |
|   .                  |  .     |      24 |         |   38.902 |      4 |  1.679 |      7 |       N |
|   .                  |  .     |      25 |         |   40.581 |      4 |  1.660 |      6 |       Y |
|   .                  |  .     |      26 |         |   42.241 |      4 |  1.669 |      5 |       Y |
|   .                  |  .     |      27 |         |   43.910 |      4 |  1.649 |      3 |       Y |
| riff.0               | p6     |      28 |         |   45.559 |      4 |  1.687 |      8 |       N |
|   .                  |  .     |      29 |         |   47.246 |      4 |  1.663 |      8 |       N |
|   .                  |  .     |      30 |         |   48.909 |      4 |  1.669 |      6 |       N |
| hook.0               | p7     |      31 |         |   50.578 |      4 |  1.679 |      7 |       N |
|   .                  |  .     |      32 |         |   52.257 |      4 |  1.657 |      4 |       N |
|   .                  |  .     |      33 |         |   53.914 |      4 |  1.675 |      3 |       Y |
|   .                  |  .     |      34 |         |   55.589 |      4 |  1.643 |      5 |       Y |
|   .                  |  .     |      35 |         |   57.232 |      4 |  1.684 |      4 |       N |
|   .                  |  .     |      36 |         |   58.916 |      4 |  1.663 |      3 |       Y |
|   .                  |  .     |      37 |         |   60.579 |      4 |  1.645 |      3 |       Y |
|   .                  |  .     |      38 |         |   62.224 |      4 |  1.655 |      5 |       Y |
| buildup.0            | p8     |      39 |         |   63.879 |      4 |  1.696 |      2 |       N |
|   .                  |  .     |      40 |         |   65.575 |      4 |  1.654 |      2 |       N |
|   .                  |  .     |      41 |         |   67.229 |      4 |  1.693 |      2 |       N |
| buildup.1            | p9     |      42 |         |   68.922 |      4 |  1.643 |      8 |       N |
|   .                  |  .     |      43 |         |   70.565 |      4 |  1.657 |      8 |       N |
|   .                  |  .     |      44 |         |   72.222 |      4 |  1.714 |      7 |       N |
+----------------------+--------+---------+---------+----------+--------+--------+--------+---------+

http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/DDC%20Log%20Handshape%20Adjustment%20Question%20-%2011Mar15/Overlap_zpsp7f6elsc.png

 

Nothing urgent, just wondering.

 

Bonne journée!

 

 

EDIT

 

I just think I figured it out for question 3. "Overlap = Yes" is an indication that Level 0 for that measure will be quite boring to play since there is no new note to play at the beginning of the measure, i.e.

<ddc>
  <level maxCategory="1" maxSubCategory= "1" maxChordNotes="1"/>
</ddc>

"A dreamer is someone who wants beyond what is reasonable. A hero is a dreamer who cannot take no for an answer." (Martin Spina)

My Released CDLC - Blaze Bayley - Stare at the Sun & MacGyver Theme Song & Iron Maiden - No More Lies

Check out the Tech Notes Tutorial Version 1.1 // Chordify Tutorial Rough Draft.

  • Author

Hi Berneer,

 

  1) DOM = Document Object Model

       => the instanciation of the XML file in memory

 

  2) The "handshape startTime adjustment" is only to synchronize the time position of the first chord and the start time position of the associated handshape.

       In your specific case, it may have a bug in the logic. Can you share the XML file to investigate more deeper ?

 

  3) The overlap flag is about the sustain of the last note of the previous measure.

       I added it to avoid the lost of sustains (when the empty phrases are generated).

       I use it only to explain the phrases created automatically by the DDC process.

 

Thanks

Hey Chlipouni,

 

Thanks for the answers! Very kind of you to read through and answer so fast.

 

Here is a link to a folder containing  the guitar.ogg, notes.eof, psarc, Pre-DDC-XML,Post DDC XML, DDC Log just in case you need to explore more than expected.

 

https://www.mediafire.com/folder/3m51lr4nlo8b8/HandShape_startTime_adjustment

 

Basically what I am noticing is that, if you see below the slightly more expanded view than the earlier screenshot, it seems like DDC is moving the handshape start point from the first to the 2nd note in the 2nd and 4th marked handshapes, but interestingly the 1st and 3rd marked handshapes remain untouched. So it seems like DDC wants to start handshapes on a beat marker, which  handshapes 1 and 3 allow but handshapes 2 and 4 don't since they start between beats.

 

http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/DDC%20Log%20Handshape%20Adjustment%20Question%20-%2011Mar15/Handshape%20Start%20Time%20Adjustment%20expanded_zpsltzhualn.png

 

 

 

In case you were going to check the included psarc, which I suspect you won't have to, it still requires good tones, a tiny bit more polish/testing,  optimized DDC ramp-up, resolve Linknext/Marked handshape issues causing noteheads to disappear in random places of my (Part Real_Bass)  finger-style arrangement and resolve intended linked phrases not leveling together.  All good testing fun. :)

 

Merci!!

"A dreamer is someone who wants beyond what is reasonable. A hero is a dreamer who cannot take no for an answer." (Martin Spina)

My Released CDLC - Blaze Bayley - Stare at the Sun & MacGyver Theme Song & Iron Maiden - No More Lies

Check out the Tech Notes Tutorial Version 1.1 // Chordify Tutorial Rough Draft.

  • Author

Hey Chlipouni,

 

Thanks for the answers! Very kind of you to read through and answer so fast.

 

Here is a link to a folder containing  the guitar.ogg, notes.eof, psarc, Pre-DDC-XML,Post DDC XML, DDC Log just in case you need to explore more than expected.

 

https://www.mediafire.com/folder/3m51lr4nlo8b8/HandShape_startTime_adjustment

 

Basically what I am noticing is that, if you see below the slightly more expanded view than the earlier screenshot, it seems like DDC is moving the handshape start point from the first to the 2nd note in the 2nd and 4th marked handshapes, but interestingly the 1st and 3rd marked handshapes remain untouched. So it seems like DDC wants to start handshapes on a beat marker, which  handshapes 1 and 3 allow but handshapes 2 and 4 don't since they start between beats.

 

http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/DDC%20Log%20Handshape%20Adjustment%20Question%20-%2011Mar15/Handshape%20Start%20Time%20Adjustment%20expanded_zpsltzhualn.png

 

 

 

In case you were going to check the included psarc, which I suspect you won't have to, it still requires good tones, a tiny bit more polish/testing,  optimized DDC ramp-up, resolve Linknext/Marked handshape issues causing noteheads to disappear in random places of my (Part Real_Bass)  finger-style arrangement and resolve intended linked phrases not leveling together.  All good testing fun. :)

 

Merci!!

 

Hi Berneer,

 

  The two handshapes need to be adjusted because their first note is not selected at level 0. They are complete start with level 1.

  This behaviour is expected for DDC.

 

  Do you have an issue about this behaviour in RS2014 ?

 

Thanks

  • Author

hi, i posted in a new thread like a doofus, and was directed here.

 

i did a song thing. it is crashing DDC. i havent had enough sleep. sorry for being stupid.

 

zip with eof file, xml files, and guitar.ogg is here:

 

https://drive.google.com/file/d/0B2TjljRp4LJucVJYdmQxWWx3M0k/view?usp=sharing

 

if anyone could take a look and help me out, that would be awesome.

 

thanx!

Hi III_Demon,

 

  Your XML files are not valid.

  There are extra informations after the end tag "</song>".

 

  To correct them :

  - open each file with a text editor (notepad++ for example)

  - delete all informations after the "</song>" end tag

  - save the file

  - generate DD with DDC

 

  How did you obtain these files (EOF, Toolkit, other) ?

  That's the second time I see this issue.

 

Thanks

 

Hi Berneer

The two handshapes need to be adjusted because their first note is not selected at level 0. They are complete start with level 1.

This behaviour is expected for DDC.

 

Do you have an issue about this behaviour in RS2014 ?

 

 

Thanks Chlipouni! Ok I get it, handshapes are to only appear when a note or chord is to be struck, and in lower difficulty levels with notes removed that means shifting the handshape start time to the right to the next non-removed note in the handshape sequence. And DDC is clever to monitor this and move handshakes at lower difficulties as necessary. I never noticed how official DLC deals with handshapes in lower difficulties so I assume you programmed it as it is done in official songs. Either way I don't see an issue with it.

 

I see arguments for both sides of the coin: the handshape appearing early at lower levels gives the user advance notice to prepare and will clue him into what will appear in he next level, however a

Handshape showing up early may have the undesirable effect of confusing and distracting he user.

 

Like I said, either way I is fine in my opinion. I happy to understand now and not worry that my CDLC is broken... :)

 

Merci

À+

"A dreamer is someone who wants beyond what is reasonable. A hero is a dreamer who cannot take no for an answer." (Martin Spina)

My Released CDLC - Blaze Bayley - Stare at the Sun & MacGyver Theme Song & Iron Maiden - No More Lies

Check out the Tech Notes Tutorial Version 1.1 // Chordify Tutorial Rough Draft.

Hi III_Demon,

 

  Your XML files are not valid.

  There are extra informations after the end tag "</song>".

 

  To correct them :

  - open each file with a text editor (notepad++ for example)

  - delete all informations after the "</song>" end tag

  - save the file

  - generate DD with DDC

 

  How did you obtain these files (EOF, Toolkit, other) ?

  That's the second time I see this issue.

 

Thanks

 

wow, i never would have found that. thanx lots! it works now!

 

these came straight out of EOF. should i post in that thread?

 

the tabs came from songsterr, i tweaked them a lot in guitar pro, then imported gp5 into EOF. somewhere along that line, something got messed up i guess.

EOF doesn't have any program logic that writes to the XML file after the tag is written.  Something abnormal would have had to happen for EOF to do such a thing (ie. program corrupted in memory), but it's more likely EOF would crash instead of write such a corrupted file.  If you can find a way to ever reproduce such a behavior (ie. load a particular file and perform certain operations), let me know.

i'm using r1359.

 

that zip file i posted includes my notes.eof file that produces the bad xml every time.

 

i havent figured out wtf reproduces it... but i did stab at it for quite a while. i re-created the song from scratch.... i guess i'll post the .gp5 i've been importing, thats the next question mark...

 

https://drive.google.com/file/d/0B2TjljRp4LJuOEFCdDBIVlFYWW8/view?usp=sharing

 

there it is, if you'd like to check it out.

 

i'm pretty lost on the whole thing. i cant think of any other info to give you guys. if i ever do run into a clue, i'll be sure to let you know. the only weird thing i discovered was some blank text annotations in the guitar pro tabs, but i cleared those out with the event management stuff in EOF.

 

for now, i have a work-around... but it does spit out bad xml every time i export, so whatever this bug is, its still there.

r1359 is almost half a year old, is there a compelling reason to not use a newer version?  Looking at the XML, it seems more like something on your computer was keeping the files open so that during a subsequent save, the files were partially overwritten instead of entirely overwritten.  EOF doesn't open files in append mode, so I don't think it's on EOF's side of things.  When I open and save your project file on my computer, the XML files are written properly with no content after the tag.

Can you post this issue in the EOF topic ?

 

Thanks

i was about to, and then i ran through some more tests.... its the toolkit thats doing it. the latest beta RST. the last stable release doesnt do it. .... so i guess i'll post in there instead. =]

 

thanx everyone for all your help. this community is fantastic.

Received this error when adding DD.  Song works fine.  Any ideas what I can do to fix it?  Thanks.

 

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

Is there a maximum number of sections you can put in a chart?

 

Some requests for the new rocksmith game is that people want to be able to pause in the song wherever they want. So I was thinking you could just create sections in the chart every half or quarter second and this would produce somewhat decent results for pausing anywhere in the track.

 

You think you could implement this?

Received this error when adding DD.  Song works fine.  Any ideas what I can do to fix it?  Thanks.

 

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

 

 

Getting the same error:

 

http://puu.sh/gJWmX/b7bd27fa0e.png/ss%20%282015-03-21%20at%2010.48.35%29.png

Recently Browsing 0

  • No registered users viewing this page.


Important Information

By using this site, you agree to our Guidelines. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. - Privacy Policy

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.