Vocal Authoring Issues

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #390802

    Okay so my entire project works if I exclude the Part Vocals track from it before compiling it in Magma. Vocals are important to me so I was really hoping you guys could help me sort this out. Every time I include vocals Magma shoots out this Error:

     

    ERROR: MIDI Compiler: (MIDI FILE): Cannot parse MIDI file; one or more MIDI tracks may be corrupt (usually due to missing or extraneous track name events)

     

    Does anyone know why this is so? I’ve driven myself crazy trying to fix this and I’m at a loss. Please respond if you have a possible solution.

    #425619
    Kloporte
    Participant

      Hey,

      Since it’s pretty much the same issue as before, maybe it wasn’t necessary to start a new thread <img decoding=” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif” />

      Ok, here’s what I would do :

       

      Open your PART VOCALS track and

      1. check the “Text Events” section, to see if the track name matches (PART VOCALS, and it should be set to : text: PART VOCALS; Type: Track name), like above:

       

      or

      2. Set the view to Event list, like this:

      Look at the events and check if something’s wrong with the track name event (like 2 identical track names, or a text event (note, lyrics) accidentally set to Track name).

       

      I’m not really used to vocals so maybe I’m missing something here <img decoding=” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif” />

      #425640
      espher
      Participant

        Kloporte gave you a rundown of what to look for, but it’s worth noting that this is one of the Magma errors that is actually pretty straight-forward and easy to interpret.

         

        If you’re not familiar with track names as a concept, or how to set an event ‘type’, you may need to revisit the docs (for REAPER more so than for authoring), but if you’re just having trouble figuring out how to check for dupes or incorrectly typed events, that post should have you covered. <img decoding=” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif”>

        #425641
        Nyxyxylyth
        Participant

          There’s another stealth way this problem can happen: if the MIDI track itself doesn’t start at 0:00. An errant mouse drag or cursor key might move the whole track. Right-click on the MIDI track in the main window, pull up the item properties, and make sure it doesn’t start at something stupid like 0:00.001.

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