MIDI track header is corrupt error
- This topic is empty.
-
AuthorPosts
-
May 24, 2014 at 12:00 pm #390462
Hello,
I’m trying to convert some songs from GH, and the two I’ve tried so far both run into this error:
ERROR: MIDI Compiler: (MIDI FILE): MIDI track header for track 2 is corrupt
Which is the drum track. Only the drum track runs into this error. I initially copied it over incorrectly by pasting the GH note tube into an empty customs template track, but I’ve since started over and done it the right way and I still get the error.
Here is the project file:
https://drive.google.com/file/d/0BzrByyrp1nIJNEdZQ05lVmd2MzQ/edit?usp=sharing
Hopefully its something simple I’m doing wrong ” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />
May 24, 2014 at 12:06 pm #420957Bass has a ton of Sysex events that are not allowed, use the MIDI Cleaner or remove them in Reaper.
May 24, 2014 at 12:16 pm #420958Yeah I use the cleaner immediately before I compile. Can I reimport that clean midi into Reaper and then post that project? I guess that would make it easier to determine the problem.
May 24, 2014 at 12:37 pm #420959Package up everything: Reaper, audio, Magma files (audio and MIDI). I’ll give it a look later.
May 24, 2014 at 1:18 pm #420963Here is the package:
http://www.mediafire.com/download/1k10g … tblues.rar
Let me know if I missed anything.
Thanks!
May 24, 2014 at 3:26 pm #420973Magma project file is missing.
May 24, 2014 at 4:12 pm #420974That sounds like an error caused by an old version of MIDI Cleaner. Update to the latest C3 CON Tools and get rid of this damaged MIDI. Export a new one from REAPER and if you want, then use the latest MIDI Cleaner on that new MIDI.
May 26, 2014 at 6:23 pm #421111Thank you guys for your help.
Farottone I think I sent you the wrong files ” src=”/wp-content/uploads/invision_emoticons/default_SA_frown.gif” /> That version that I sent you doesn’t have the drum track in the midi. Here is an uncleaned version of the midi with drums, a version I sent through the cleaner, and the Magma Project file: http://www.mediafire.com/download/o3dtl … es14-2.rar
TojanNemo, I have been using the ‘test’ and ‘clean’ buttons in Magma version 2.2.0. I also ran it through the cleaner directly from the C3 con tools, which tells me it is version 3.3.0, and I get the same error.
May 26, 2014 at 6:46 pm #421116If you’re running it through the tools after having run it through an old version, the problem won’t get fixed. Start with the MIDI out of REAPER. Does Magma say that? If so, the problem is in the exporting from REAPER. If not, then run it through MIDI Cleaner. Does Magma say it now? Then the problem is with MIDI Cleaner. Etc.
By the way, the Clean button in Magma just launches MIDI Cleaner, so there’s no point in doing that twice.
May 26, 2014 at 6:52 pm #421118I take it those are the most up to date versions of the tools then?
If so, I have run a midi straight from Reaper export through the tool, and received the header error.
Sounds like it’s some sort of export error. If it helps, spindoctor made his own drum track from the original GH midi and sent it to me. I copied his drum track into my project and it worked just fine. It’s probably user error at some point, but it beats me what it is.
May 26, 2014 at 7:48 pm #421122I run the mid through con tools midi cleaner BEFORE putting into Reaper. Always do this and you will have fewer errors to deal with in the end. It takes less than 10 seconds to clear up thousands of errors before you start working on it.
May 26, 2014 at 9:40 pm #421135Ah, maybe that’s what it is. I will give it a shot later.
-
AuthorPosts
- You must be logged in to reply to this topic.