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

Hi iminashi,

 

  Don"t forget that DDC is an automatic process. I'm positive that Ubisoft creates its DD levels by hand ...

 

  The whole DDC process is defined by measure, so the position of notes inside a measure is important.

  If I allow a phrase or a section to start in the middle of a measure, I have to separate the notes of this measure in two distinct sets.

 

  This feature has already been requested by Firekorn and if I want to implement it I will have to change a lot of things in the existing code.

  Nevertheless, I keep it in my todo list ...

 

  About the first time position of a beat, I setted it like that because EOF generates the "0.000" beat by default. 

 

  About the first time position of a beat, I setted it like that because EOF generates the "0.000" beat by default. 

 

Not sure what you mean by that. EOF sets the startBeat and the first beat at the time where the beat map begins, not at 0.000.

 

It only matters if people want to use ODLC-like leading silence (10+ seconds of silence). I've tried it, but haven't noticed any merits in doing so myself. Anyway, Firekorn advises that people do that in his tutorial. And if you move the first beat from 10s to 0s, it will mean that about half of that silence will not be skipped like it is in ODLC.

 

 

  About the first time position of a beat, I setted it like that because EOF generates the "0.000" beat by default. 

 

Not sure what you mean by that. EOF sets the startBeat and the first beat at the time where the beat map begins, not at 0.000.

 

It only matters if people want to use ODLC-like leading silence (10+ seconds of silence). I've tried it, but haven't noticed any merits in doing so myself. Anyway, Firekorn advises that people do that in his tutorial. And if you move the first beat from 10s to 0s, it will mean that about half of that silence will not be skipped like it is in ODLC.

 

 

It depends on how you use EOF.

 

In my case :

- I update myself the audio file to add the leading silence

- I update the GP Tab to add a leading measure (for that silence)

- I start my EOF project with these files and I move the measure number 2 to the beginning of the audio track

 

So, I set the first beat at "0.000" to manage these different ways to make CDLCs.

 

Did you notice an issue or a special behaviour in RS2014 due to this first beat position ?

 

Did you notice an issue or a special behaviour in RS2014 due to this first beat position ?

 

 

Only the leading silence thing I mentioned. I don't think there are any other issues.

@@Chlipouni Your method means that you have to actually sit through the silence though because the game will start at 0s and not around 6/7s if the first beat is at 10s.

 

@@iminashi as for the first beat of the measure obligation, that's why i now make my own difficulty by hand, and even then i get limited by EOF regarding the fact that a section have to be on a beat while oDLC clearly don't have that obligation at all...

 

On another subject, the more i look at oDLC and make my own DD the more i notice that DDC don't create enough level to fit correctly into the difficulty sorting that RS does. I know that a lot of stuff can be hard to program but the idea is that they rarely ever delete more than 1 or 2 note especially in most situation and they also don't hesitate to have empty levels when they want a phrase to actually be higher in the skyline either.

 

When DDC barely reach 8 level of difficulty even with the keep all levels configuration while oDLC can have up to 30 levels and usually sit around 10/15 levels for most riff.

@@firekorn, my leading silence is only about 3 or 5 seconds, so I don't have to wait 10 sec before playing.

 

About the maximum number of levels of difficulty, I agree with you but I had to find a compromise when I started to design DDC.

Some users desliked to have too many levels (too fastidious to reach the highest level)

@@Chlipouni Nobody ever has to wait 10s if it's done right but if you do it the same way oDLC work but anyway to each their own and as long as there's no issue, it's not a deal breaker regarding CDLC quality if you ask me :)

 

As for the number of level, i can understand the issue when we didn't had any control over DD speed (or to simply deactivate it) but it makes less sense now and the sight reading level at max means that you reach level 16 directly which DDC never reaches even in incredibly complicated solo.

 

I'll admit that some choice made in oDLC could be impossible to reproduce with an automated system (they sometimes do very bold choices that i would have hesitated to make) but i think that by going for a first level that is 1 note every 2 measure like oDLC could already allow DDC to reach 10 level of difficulty a bit more easily.

 

All that being said, i do think an adjustement with a new config and ramp up model could probably already go a long way to make DDC a bit closer to oDLC standard so that would avoid any kind of algorithm modification but i'll admit i haven't looked too much into it right now.

I actually like the way DDC categorizes notes and I tend to remove levels from the dedault ramp-up since I find much music has a pattern such that if you remove/add next level notes (eighths to sixteenths, for example) in one go the song becomes easy to play and what the user plays sounds natural. I actually find it hard on the user to tell him/her to play a16th note here but not there in the same measure. For the ear to hear and play a note in a measure and then purposely hear and ignore another note in the same measure, to me, feels unnatural and ironically feels harder to play.

 

I never thought of starting a section other than on a beat. I'd be curious to see which ODLC does this, to see why it is necessary. Maybe sporadic tone changes in a measure in crazy groups like SoaD... :)... I recall Firekorn writing something earlier about this, I think, I read back to earlier posts to possibly answer my question.

 

I did notice too some interesting ODLC ramping behaviour of a single note becoming a power chord (G5) becoming a full chord (ex G Major chord).

@@Berneer Well take The trooper by Iron Maiden, the riff starts on the 16th note before the measure and so does the section that is impossible to even do in EOF.

 

Right now i'm working on Ropes by In Flames and it's the same issue, i have the 16th note that starts the riff that is right before the measure start :

http://imgur.com/CWJ3yfV

And in that song, the solo section has to start on the 4th beat of the measure instead of the first one and that's far from an uncommon sight (and there's note in the measure too though they aren't visible in this case because i already made the different difficulty) :

http://imgur.com/NO7Pirm

 

It's true that probably 90% of the song don't have many situation like that if any but there's still quite a good number of case where a riff starts off-beat or slightly before the 1st beat of the measure.

 

As for the fact that you prefer to get rid of all 16th (or whatever) at the same time is highly debatable. Right now i'm following what i've saw in most oDLC where they simply start by cutting the last note so that the transition is easier to make, that's pretty natural especially when the picking pattern end on a down strum, i think it's easy to agree that i make sense. Then it starts to be harder, they usually cut the riff in chunk of a subdivision (group of 3 for 16th note for example) so it actually allow you to slowly build up speed and have better control over your picking pattern than going straight from 8th to 16th and they will slowly cut the 16th to avoid overwhelming the user. I find it actually quite tolerable in many occasion but some riff will require a very different treatment.

 

As for some chord evolution, i'm not a fan when they start to build one kind of chord and shift to a slight variation of it but sometimes it can make sense, that's really the kind of thing that requires to think about the riff and how could it be played more easily and not just cut note because. There's the same thing when it comes to some bend where they actually introduce the bend note and then will move you to the actual note that will be bend but that is always done without altering the FHP and it's really something that requires to evaluate if it actually make sense to do so. There's also the fact that they cut many slide in and out early and will move the note so that the user will always pick at the same time, some for some fast HO/PO where they will keep the last note and adjust the timing. It makes sense but it really depend on each case, the bpm, how easy will it really be, etc...

 

So i don't expect DDC to go as deep as they do on many occasion but i do consider that the actual level discrepancies which have an impact on the difficulty sorting could use a little more harmonization which is why i suggest to simply change the config files first so that the "issue" can be somewhat simply solved.

@@firekorn,

 

  In order to generate more level of difficulties, modifying the config files is not sufficient.

  It is needed to add logic in DDC process, to split two adjacent levels if too many notes appear.

  For example, in a 4/4 time signature, 4 notes can appear at the same time if they belong to the same category and subcategory.

So i guess DDC doesn't support a maxsubcategory=0 ?

 

Also since Chord are removed after the rhythm is removed, if the maxchordnote is only change when maxtegory is 1 wouldn't that create a few more level than what the default config would.

@@firekorn,

 

  You are right, we can add 5 more levels in the config file by defining only one change between two adjacent levels.

 

  However, the new levels will be used only if notes exist for these levels and if the merging process is not too high configurated.

 

  If I understand the main purpose of this request is to have more differences between songs in order to select them in Ignition ?

  Do we need to apply these new parameters in the default config of DDC ?

 

Thanks

@@Chlipouni It has nothing to do with ignition but with the sorting option of Rocksmith remastered. The difficulty sorting take the max level to organize them by order of difficulty, a song that has only 8 level will be put around others song that have only that amount of level so when oDLC use up to 30 levels for difficult songs while DDC barely use 10 you end up with hard cdlc being placed among easy oDLC.

 

If DDC can at least go up to 16 (which is the max sight read level in RS), that means that there will be less difference in sorting inside RS which will offer a better experience when using the game options and it might also allow for greater skyline since there will be more visible difference when a riff is indeed complex.

@@iminashi as for the first beat of the measure obligation, that's why i now make my own difficulty by hand, and even then i get limited by EOF regarding the fact that a section have to be on a beat while oDLC clearly don't have that obligation at all...

I'm hoping the need for this is relatively rare. It would be very complicated for me to change EOF to allow events to be defined outside of a beat marker's position.

@@raynebc i guessed so that i wouldn't be easy to allow event to not be tied to a beat which is why i never asked.

 

As for the need for it, well it's a matter of how precise you wanna be, in most case you can get around that "issue" and if you really want, you can always play with the BPM and such to make something that would work anyway even if it wouldn't exactly be as oDLC.

 

So i wouldn't want you to bother with that at all.

Hi,

 

I have noticed a few times now that when I use DD it can chop off the last note of the chart

 

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

 

becomes

 

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

 

i.e. it chops off the linknext unpited slide to finish the song.

 

 

I am using rstoolkit-2.8.2.0-273b0ba2-win (DDC 3.3).

 

Any ideas or fixes would be nice, I always like to finish a song with some style :D

@PC Plum it's your phrase length value that create a new phrase/section right on that measure so the linknext just disappear because of it apparently.

Thanks I'll try a different phrase length and see what happens :D

 

 

Edit - I did not try a different phrase length as it was already at 8 and should have been plenty.  What I did was change the position of the outro Section/Phrase in EoF, so measure 368 (where it cuts in the screenie) is the 3rd bar of the Outro Section/Phrase and the DDC phrase length was set to 8 anyway.

 

The last linknext unpitched slide still gets chopped off.

Double post ftw :D

 

I wouldn't say solved but I found a workaround.  Placing a dummy ghost note at the end of the chart helped

 

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

 

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

@PC Plum, hope that not a toolkit linknext mask bug

Well you are the expert on that not me :D

 

There are many linknexts that work fine (in this chart and many others I have made) and it's only when I put one on the last note of the chart (lead/bass) that it disappears.

I would guess that it happens because DDC moves the END phrase to the first beat of a bar.

@@iminashi That would still be weird on DDC part to move the END phrase on a position where a note exist....

 

@@PC Plum you can try to create a phrase name END on the first bar of the measure 369 to see if that will solve the issue more properly.

Hi,

 

I have noticed a few times now that when I use DD it can chop off the last note of the chart

 

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

 

becomes

 

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

 

i.e. it chops off the linknext unpited slide to finish the song.

 

 

I am using rstoolkit-2.8.2.0-273b0ba2-win (DDC 3.3).

 

Any ideas or fixes would be nice, I always like to finish a song with some style :D

 

@@raynebc,

 

  It seems that it is an EOF issue.

  I can reproduce it and EOF omits to generate the last note if the previous one has the linknext status

Can you provide a simple example EOF project file? I authored that example (an arrangement ending in an A6 single note linked to an A6 single note that unpitched slides to fret 2) and EOF exported both single notes:

        <note time="3.750" string="1" fret="6" sustain="0.250" linkNext="1" />
        <note time="4.000" string="1" fret="6" sustain="0.750" slideUnpitchTo="2" />