Jump to content

Chlipouni

Member
  • Posts

    909
  • Joined

  • Last visited

  • Days Won

    1
  • Country

    France
  • Donations

    0.00 USD 

Posts posted by Chlipouni

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

    • Like 2
  2. @Pc Plum,

     

      In the DDC Log file, you have the following warning :

    04. Load useful informations from the XML input file
          => 266 ms
        - Song informations
          => 0 ms
        - Measures and ebeats
          => 30 ms
        - Sections
          ==> WARNING : Section noguitar (700.271) doesn't start on the main beat of a measure (new time : 699.455)
          => 3 ms
    

      So DDC modifies the last section position on the measure at time position "699.455".

      This measure contains the last note. This is why this note is not generated by DDC process.

     

      I have to change this logic in order to protect the last note (maybe by including the sustain in the computation).

     

    Thank you for sharing the files ...

    • Like 1
  3. 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" />

     

    You can use the following EOF project : Project

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

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

  6.  

     

      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 ?

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

    • Like 2
  8. @@raynebc,

     

    There is no limit about the number of phrases that can be linked together.

     

    In my opinion the easiest way to add this feature in EOF, could be to let the author adding a tag in the phrase name. Something like intro[g1] for phrase "intro" in group "g1". So all phrases in the same group could be linked together in the newLinkedDiff XML tag ...

     

    Envoyé de mon SM-G920F en utilisant Tapatalk

  9. @@firekorn,

     

      "LinkedDiffs" tag is not used anymore in RS2014.

     

      However, you can use the "newLinkedDiffs" tag to link two or more different phrases.

      When two phrases are linked, their level of difficulty will evolve similarly in the game.

     

      As an example :

      <newLinkedDiffs count="1">
        <newLinkedDiff levelBreak="-1" ratio="1.000" phraseCount="2">
          <nld_phrase id="7" />
          <nld_phrase id="14" />
        </newLinkedDiff>
      </newLinkedDiffs>
    

    In this specific case, all iterations of the phrases id "7" and "14" will be synchronized in the game.

     

    In DDC, I already use this when two phrases contain similar sequences of notes but not exactly the same (a diff percentage is computed to decide to link them or not).

     

    I can't explain precisely the "levelBreak" and "ratio" attributes, as I always use the default values (these attributes need more investigations). In my mind, these attributes are useful only when the linked phrases don't have the same number of difficulty levels.

    • Like 1
  10. @@raynebc,

     

    During a GP tab import in EOF, a single note with a slide is terminated with a new gem related to the end fret position. I was expected to have only the first note with the slide and its end fret position, but not the last gem at the end of the sustain.

    Is it the normal behaviour ?

     

    Thanks

     

    Envoyé de mon SM-G920F en utilisant Tapatalk

  11. Those two elements doesn't have any kind of mandatory relation to each other and should work independently.

     

    I know that the handShape is here only to indicate which fingers to use and can be fully considered as independent from the notes and chords.

    But when DDC has to create the other levels of difficulty, it takes care about how many strings are used in the chords inside an handShape, in order to display only the necessary fingers.

     

    That's why DDC analyzes the handShape to see if it contains chords or only single notes. Its behaviour is not the same in these two different cases.

  12. Came across another problem. Generating DD on this arrangement causes some of the handshapes to point to the wrong chordId, with the first one pointing to chordId -1.

     

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

     

    The reason is because the handShape starts with a single note at time "15.791" and the first chord of this handShape starts at time "16.226".

    This specific case is not actually managed by DDC, and I need more explanations of what you exactly want to do in order to improve the code.

     

     Currently, DDC manages the following cases with handShapes :

     - handShape that starts with a chord

     - handShape that starts with a double single notes (two notes at the same time position but without chord)

     - handShape that starts with a single note and identified as an "arpeggios" sequence

     

    Meanwhile and for your issue, the workaround is simply to synchronize the beginning of the handShape with the time position of its first chord.

  13. I am interested to know how you built the .psarc with these characters in?

     

    It seems to me that the toolkit is filtering out some characters during the build process.  Was the toolkit behaviour amemded after your testing, using the results?

     

    Thanks :D

     

    @Pc Plum,

     

      Some characters are not displayed in the game (those with [ND] or [NV] tags in my testing XML file)

      Can you give me an example of a specific character you can't use in RS ?

     

    Thanks

  14. Hi raynebc,

     

      What is the exact purpose of the "PART VOCALS_RS2_EXT.xml" file ?

     

      For me, only the "PART VOCALS_RS2.xml" works fine with accented characters (RS2014, RST and text editors).

      When I try to use the "_EXT" file, accented characters are not displayed in the game.

     

    Thanks

×
×
  • Create New...

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