ERROR: MIDI Compiler: (MIDI FILE): MIDI track header for track 2 is corrupt
- This topic is empty.
-
Posts
-
I’m making my first custom and keep getting this error when building the song in Magma, after exporting midi from Reaper and cleaning it using C3 CON Tools.
Project Compiler: Entering Phase 1 of 5…
Metadata Compiler: Starting…
Metadata Compiler: Done.
Project Compiler: Entering Phase 2 of 5…
MIDI Compiler: Starting…
ERROR: MIDI Compiler: (MIDI FILE): MIDI track header for track 2 is corrupt
MIDI Compiler: Done.
ERROR: Project Compiler: Midi compiler failed.I’ve spent hours trying to figure this out on my own. I’ve seen others ask about this in the forum but I can’t find an actual solution anywhere. I think the Track Names for each track are put in correctly. I don’t know what else to do. What is the issue and how do I fix it?
Thanks a bunch!
I had this happen to me on a GH coverision, turned out there was a hidden note that didn’t show up in Reaper. I actually think I loaded into EOF just to see what happened and found it there
I had this happen to me on a GH coverision, turned out there was a hidden note that didn’t show up in Reaper. I actually think I loaded into EOF just to see what happened and found it there
It happened to someone else when doing a GH conversion, too. There wasn’t a stated solution for him, though.
In my case, I actually used EoF to create the Expert Guitar, Bass, and Drums parts, then I took that and brought it into Reaper and made the rest there. I noticed the problem occurs as long as I export from Reaper with any of those 3 parts unmuted – Guitar, Bass, and Drums. (It always says “track 2” no matter which of those 3 are muted and which are unmuted. No idea why that is.) If I mute Guitar, Bass, and Drums, and only export Vocals, Harm1, Harm2, Events and Beat, this error doesn’t come up in Magma. So my guess is that it has something to do with bringing it from EoF to Reaper. But I don’t know.
Any other ideas on what to do or where to find the problem(s)? I don’t know where to look for a mysterious hidden note, or why that translates in Magma as a corrupt track header. What did the note look like? Where was it in the file? Any more help would be much appreciated. Thanks!
(It’s possible that if I delete those 3 tracks and then create them in Reaper over again, the phantom problem will be gone, but that seems like a big waste of time. I have a good handful of other songs I completed the Guitar, Bass, and Drums for in EoF that I want to complete in Reaper, so my hope is that that’s not the only solution.)
If you can ever reproduce on demand a condition where opening a project in EOF and saving creates a corrupted MIDI file, please send the project my way. If the MIDI opens fine in REAPER and other programs but Magma still complains it’s corrupt, it could be a Magma bug instead.
If you can ever reproduce on demand a condition where opening a project in EOF and saving creates a corrupted MIDI file, please send the project my way. If the MIDI opens fine in REAPER and other programs but Magma still complains it’s corrupt, it could be a Magma bug instead.
The midi file did work fine when I put them into Reaper. It also worked fine when I played it in Phaseshift for just guitar, bass, and drums, before I brought it to Reaper to add vocals and whatnot. The issue only happens when I try to run it through Magma after exporting from Reaper…
This is my first custom, so I’m happy to send it along so you can see if you can figure it out?
You can send me just the MIDI file being refused by Magma if you want and I can check to see if I immediately notice anything bizarre that sticks out.
I believe I have already handled it, there were a few issues but I think I have filled him in. It compiled for me here so we will see.
You can send me just the MIDI file being refused by Magma if you want and I can check to see if I immediately notice anything bizarre that sticks out.
I really appreciate it, but yeah, rubydanger checked it out already, and now I’ve got the file working. I’m actually still not entirely clear what exactly the error was (“ERROR: MIDI Compiler: (MIDI FILE): MIDI track header for track 2 is corrupt”) but whatever he did when cleaning it up worked.
rubydanger, do you know what specifically that error was about? Sorry if you already answered in PMs, but I just want to make sure if anyone ever runs into it and finds this thread, they’ll have a direct answer. Several threads talked about this error over the years but I never saw a fix.
I don’t know how Reaper could end up writing a corrupt MIDI, I have to still assume this was a false positive or incorrect error message on Magma’s part.
- You must be logged in to reply to this topic.