efhiii/midi-ch

.midi to clone hero converter

midi-ch's Issues

Setting the number of frets to a number higher than five crashes the webpage

I figured setting the number of frets to 6 would be useful for charting to GH Live controllers, but it just freezes to note display, and you got to reload the page to get it working again.

Worked with offline?

I've been downloaded the source and pasted it to my XAMPP, its not working when its offline, but its arrived the download when it goes internet and pops-up the download prompt?

But the code runs smoothly, no download prompt on offline, it has prompt when goes internet.

Code license

Heya, I'm writing to ask if your code here is available under a free/open-source software license -- I was interested in building off of it but could not find a license designation.

For context, I develop an app that supports converting charts between various game formats such as CH/RB/GH. I would like to add a few different pieces of functionality that depend on a decent way to "shrink" note charts into a smaller number of lanes like your tool does, such as making a 5-fret guitar chart from formats like:

• RB Pro Guitar
• RB Pro Keys
• Vocals
• 6-fret guitar
• Rocksmith
• BeatMania

I made a quick demo to try out a few of these with your logic and the results are very promising!

If allowed to integrate your work, I would of course:

• credit you in release notes + app readme + copyright file
• credit you in comments/metadata on any output files that use the logic (such as loading_phrase in song.ini like your app does)

Add Lyrics auto-charting

Would probably have to parse Music XML files, which are encoded as .zip which contains an XML file (and some other stuff), in the XML file, lyrics are stored inside notes (which are stored in measures), so parsing the tempo, tempo changes, time signature, and time signature changes would be necessary in order to determine the correct time-stamp for the lyrics.

Example of what the important part of the XML looks like

<score-partwise>
  <part>
    <measure number="1">
      <attributes>
        <divisions>12</divisions>
        <time>
          <beats>4</beats>
          <beat-type>4</beat-type>
        </time>
      </attributes>
      <note>
        <duration>3</duration>
        <type>16th</type>
        <lyric number="1">
          <syllabic>single</syllabic>
          <text>LYRICS</text>
        </lyric>
        <direction>
          <metronome>
            <beat-unit>quarter</beat-unit>
            <per-minute>144</per-minute>
          </metronome>
        </direction>
      </note>
...

On top of all that, to match it to the .chart format, the correct resolution would need to be known, probably user-provided.

A botched way to do less work might involve having the user provide both the Music XML and the Midi file, then using the measure to help match them to the Midi. That'd eliminate the problem of needing the user to provide the resolution manually.