MIDI Compiler Error On Drum Track

  • This topic is empty.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • February 8, 2015 at 5:47 am #391719
    Freewaymad
    Participant

      Hi,

       

      I am getting the following error from the MIDI Compiler on the drum track:


      
Welcome to MIDI Tester 1.1
      
This program is intended to quickly let you test MIDI after MIDI for compliance with RBN2.0 standards.
      

      
All you have to do is drag the MIDI file(s) here. This program will read through it, and create an adequate test project. MagmaCompiler is then called to process the MIDI for RBN2.0 compliance without actually compiling the song (so no time wasted compiling the audio).
      

      
You can do back-to-back MIDIs without having to close this form.
      

      
Ready to begin....
      

      
MIDI Tester initialized via command-line
      
Arguments: -miditester
      

      

      
Loaded MIDI file JP_Green Manalishi.mid successfully.
      
Found PART VOCALS...
      
Found PART DRUMS...
      
Found TextEvent PART BASS...
      
Found TextEvent PART GUITAR...
      
Nemo's MIDI AutoGen process started
      
Added drum mix events successfully.
      
Nemo's MIDI AutoGen process completed
      
Starting Basic EMH Check
      
MIDI passed Basic EMH Check without reporting any problems
      
This means the charts most likely have reductions charted
      
Ready to send files to MagmaCompiler ... hold on.
      
Output from MagmaCompiler follows:
      
Reading the archive
      
MIDI Compiler: Starting...
      
ERROR: MIDI Compiler: (PART DRUMS): Gem at [56] in hard difficulty has a duration of 1500 ticks; max is 120
      
ERROR: MIDI Compiler: (PART DRUMS): Gem at [56] in expert difficulty has a duration of 1500 ticks; max is 120
      
MIDI Compiler: Done.
      
MagmaCompiler reported some errors. Please see the log for details on what must be fixed.
      
Process completed in 0 minutes and 0 seconds.
      
You may drag another MIDI or just click Close to exit.

      I know I can send it to the MIDI Cleaner to fix it, but how do I fix it in Reaper? Please help.

       

      Thanks,

      February 8, 2015 at 11:34 am #437964
      Farottone
      Keymaster

        You need to fix your time signature markers, right now the first one comes at a random spot instead of being at the 1 of a measure.

        February 8, 2015 at 5:14 pm #437973
        Freewaymad
        Participant

          I am assuming to “re-tempo map” since my tempo map seems to have been changed when I put the imported the MIDI. Yes?

          February 8, 2015 at 5:18 pm #437974
          Farottone
          Keymaster

            Not quite sure what you mean. The Reaper project shows you have a TS change mid-measure, you can’t do that.

            February 8, 2015 at 5:39 pm #437976
            Freewaymad
            Participant

              That happened when I imported the MIDI and merged the tempo map. How do I fix it?

              February 8, 2015 at 5:58 pm #437979
              Farottone
              Keymaster
                That happened when I imported the MIDI and merged the tempo map. How do I fix it?

                 

                You need to delete them and create them anew on the 1 of the measure (right click on top of the tempo map, Insert time signature marker).

                February 8, 2015 at 6:06 pm #437980
                Freewaymad
                Participant

                  Okay. Thanks,

                • Author
                  Posts
                Viewing 7 posts - 1 through 7 (of 7 total)
                • You must be logged in to reply to this topic.
                Back to top button