Ghost Notes & Events Giving Errors
- This topic is empty.
-
Posts
-
Hey everyone, I’ve been doing my best to troubleshoot this one on my own, but I keep getting the same list of errors and it’s really confusing me. When trying to compile my latest custom in Magma, I am getting note overlap errors at locations that don’t even have gems and an event parse error where no event is located. Here’s the actual test (from the MIDI compiler so the printout is cleaner):
ERROR: MIDI Compiler: (PART DRUMS): Overlapping or too-close gems at [3] for difficulty hard
ERROR: MIDI Compiler: (PART DRUMS): Overlapping or too-close gems at [3] for difficulty expert
ERROR: MIDI Compiler: (PART DRUMS): Overlapping or too-close gems at [5] for difficulty hard
ERROR: MIDI Compiler: (PART DRUMS): Overlapping or too-close gems at [5] for difficulty expert
ERROR: MIDI Compiler: (PART DRUMS): Overlapping or too-close gems at [7] for difficulty hard
ERROR: MIDI Compiler: (PART DRUMS): Overlapping or too-close gems at [7] for difficulty expert
ERROR: MIDI Compiler: (PART DRUMS): Overlapping or too-close gems at [77] for difficulty hard
ERROR: MIDI Compiler: (PART DRUMS): Overlapping or too-close gems at [78] for difficulty hard
ERROR: MIDI Compiler: (PART GUITAR): Cannot parse event 0xf0 at [48]
…and here’s what those locations look like
DRUMS:
GUITAR:
I should mention that this song is a GH conversion (using one of Bluzer’s stem files) so the GH note chart was loaded into my Reaper project then I copied the MIDI notes over to the proper tracks. The old tracks are deleted now. It seems like all the drum events are happening at xx:xx:240 or 241, but I don’t know what the significance of that might be.
I can provide the reaper file upon request.
For drums, re-quantize those notes.
For guitar, check for Sysex events or similar in your MIDI window. For guitar you should only be left with Text events and Velocity MIDI events.
ERROR: MIDI Compiler: (PART GUITAR): Cannot parse event 0xf0 at [48]That’s a SysEx event, which is a thing MIDI files can use, and PhaseShift uses, but not Rock Band. it’s not something you’re going to see unless you’re on View Event List mode or whatever that’s called that lists them all. It’s also something that MIDI Cleaner would have fixed for you. So you should get in the habit of running GH/FoFix/PhaseShift midis through MIDI Cleaner before starting to work on them for RB purposes.
As far as the overlapping notes. Don’t go by what MagmaCompiler tells you. I’ve said this time and time again but people don’t seem to search before they get stumped. Telling you “there is a problem at X” is very difficult when you’re talking about MIDI timing and changing tempos and changing time signatures. MagmaCompiler is giving you an approximate time, but it definitely loses accuracy the more time signatures in a song and the less “Standard” a song is. So look a little before and a little after the message to where there are notes, and you’ll find your problem there. The error is telling you the notes don’t start and end at the same time. You might have to zoom in really really close to notice it, or it might be an obvious thing. You can also just make sure you’re on a proper grid (i.e. 1/32 and proper timing) and just select the notes and quantize to note position and note length.
EDIT: ninja’d >
” src=”/wp-content/uploads/invision_emoticons/default_SA_frown.gif” />Hmm, I could have sworn I passed it all through a MIDI cleaner. Maybe I used the wrong one when I imported
. In any case, it’s fixed now, along with the drum issues. I wasn’t aware that Magma doesn’t always list the exactly correct time location. Quantizing all drum notes did the trick! Thanks for both replies 
” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />
- You must be logged in to reply to this topic.