Compiling errors
- This topic is empty.
-
Posts
-
Magma: C3 Roks Edition v3.2.7
=============================
Build started at 19:16
Starting Nemo’s MIDI Validator…
Everything looks good, continuing…
Loading MagmaCompilerC3.exe…
Nemo’s MIDI AutoGen process started
Added drum mix events successfully.
Nemo’s MIDI AutoGen process completed
Reading the archive
Project Compiler: Reading project ‘C:UsersAlternityGoogle DriveCustomsRock Band-Phase ShiftBlotted ScienceSynaptic PlasticitySynapticPlasticity.rbproj’…
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: songs/short_name/short_name.mid (PART DRUMS): Error ending drum lane 4 at [30]
ERROR: MIDI Compiler: c:/users/alternity/google drive/customs/rock band-phase shift/blotted science/synaptic plasticity/synaptic plasticity.mid (PART DRUMS): Double note-off 112, [30]
ERROR: MIDI Compiler: (PART DRUMS): Error adding drum lane 4 at [45]
ERROR: MIDI Compiler: c:/users/alternity/google drive/customs/rock band-phase shift/blotted science/synaptic plasticity/synaptic plasticity.mid (PART DRUMS): Double note-on 112, [45]
ERROR: MIDI Compiler: songs/short_name/short_name.mid (PART DRUMS): Error ending drum lane 3 at [47]
ERROR: MIDI Compiler: c:/users/alternity/google drive/customs/rock band-phase shift/blotted science/synaptic plasticity/synaptic plasticity.mid (PART DRUMS): Double note-off 111, [47]
ERROR: MIDI Compiler: songs/short_name/short_name.mid (PART DRUMS): Error ending drum lane 4 at [47]
ERROR: MIDI Compiler: c:/users/alternity/google drive/customs/rock band-phase shift/blotted science/synaptic plasticity/synaptic plasticity.mid (PART DRUMS): Double note-off 112, [47]
ERROR: MIDI Compiler: (PART DRUMS): Error adding drum lane 4 at [50]
ERROR: MIDI Compiler: c:/users/alternity/google drive/customs/rock band-phase shift/blotted science/synaptic plasticity/synaptic plasticity.mid (PART DRUMS): Double note-on 112, [50]
ERROR: MIDI Compiler: songs/short_name/short_name.mid (PART DRUMS): Error ending drum lane 4 at [56]
ERROR: MIDI Compiler: c:/users/alternity/google drive/customs/rock band-phase shift/blotted science/synaptic plasticity/synaptic plasticity.mid (PART DRUMS): Double note-off 112, [56]
ERROR: MIDI Compiler: (PART DRUMS): Error adding drum lane 4 at [59]
ERROR: MIDI Compiler: c:/users/alternity/google drive/customs/rock band-phase shift/blotted science/synaptic plasticity/synaptic plasticity.mid (PART DRUMS): Double note-on 112, [59]
ERROR: MIDI Compiler: songs/short_name/short_name.mid (PART DRUMS): Error ending drum lane 4 at [63]
ERROR: MIDI Compiler: c:/users/alternity/google drive/customs/rock band-phase shift/blotted science/synaptic plasticity/synaptic plasticity.mid (PART DRUMS): Double note-off 112, [63]
ERROR: MIDI Compiler: songs/short_name/short_name.mid (PART DRUMS): Error ending drum lane 2 at [63]
ERROR: MIDI Compiler: c:/users/alternity/google drive/customs/rock band-phase shift/blotted science/synaptic plasticity/synaptic plasticity.mid (PART DRUMS): Double note-off 110, [63]
ERROR: MIDI Compiler: (PART DRUMS): Error adding drum lane 2 at [65]
ERROR: MIDI Compiler: c:/users/alternity/google drive/customs/rock band-phase shift/blotted science/synaptic plasticity/synaptic plasticity.mid (PART DRUMS): Double note-on 110, [65]
ERROR: MIDI Compiler: (PART DRUMS): Error adding drum lane 3 at [65]
ERROR: MIDI Compiler: c:/users/alternity/google drive/customs/rock band-phase shift/blotted science/synaptic plasticity/synaptic plasticity.mid (PART DRUMS): Double note-on 111, [65]
ERROR: MIDI Compiler: (PART DRUMS): Error adding drum lane 4 at [65]
ERROR: MIDI Compiler: c:/users/alternity/google drive/customs/rock band-phase shift/blotted science/synaptic plasticity/synaptic plasticity.mid (PART DRUMS): Double note-on 112, [65]
ERROR: MIDI Compiler: songs/short_name/short_name.mid (PART DRUMS): Error ending drum lane 3 at [77]
ERROR: MIDI Compiler: c:/users/alternity/google drive/customs/rock band-phase shift/blotted science/synaptic plasticity/synaptic plasticity.mid (PART DRUMS): Double note-off 111, [77]
ERROR: MIDI Compiler: songs/short_name/short_name.mid (PART DRUMS): Error ending drum lane 4 at [77]
ERROR: MIDI Compiler: c:/users/alternity/google drive/customs/rock band-phase shift/blotted science/synaptic plasticity/synaptic plasticity.mid (PART DRUMS): Double note-off 112, [77]
ERROR: MIDI Compiler: songs/short_name/short_name.mid (PART DRUMS): Error ending drum lane 2 at [94]
ERROR: MIDI Compiler: c:/users/alternity/google drive/customs/rock band-phase shift/blotted science/synaptic plasticity/synaptic plasticity.mid (PART DRUMS): Double note-off 110, [94]
ERROR: MIDI Compiler: (PART DRUMS): Error adding drum lane 3 at [122]
ERROR: MIDI Compiler: c:/users/alternity/google drive/customs/rock band-phase shift/blotted science/synaptic plasticity/synaptic plasticity.mid (PART DRUMS): Double note-on 111, [122]
ERROR: MIDI Compiler: songs/short_name/short_name.mid (PART DRUMS): Error ending drum lane 3 at [124]
ERROR: MIDI Compiler: c:/users/alternity/google drive/customs/rock band-phase shift/blotted science/synaptic plasticity/synaptic plasticity.mid (PART DRUMS): Double note-off 111, [124]
ERROR: MIDI Compiler: (PART DRUMS): MIDI events at [93] after the end event at [93]
ERROR: MIDI Compiler: (BEAT): MIDI events at [93] after the end event at [93]
ERROR: MIDI Compiler: (VENUE): music_start event at [3] is not allowed
ERROR: MIDI Compiler: (VENUE): music_end event at [151] is not allowed
ERROR: MIDI Compiler: (VENUE): end event at [151] is not allowed
ERROR: MIDI Compiler: (PART DRUMS): Gem at [3] in easy difficulty has a duration of 1921 ticks; max is 120
ERROR: MIDI Compiler: (PART DRUMS): Gem at [3] in medium difficulty has a duration of 1921 ticks; max is 120
ERROR: MIDI Compiler: (PART DRUMS): Gem at [3] in hard difficulty has a duration of 1921 ticks; max is 120
ERROR: MIDI Compiler: (PART DRUMS): Gem at [3] in expert difficulty has a duration of 1921 ticks; max is 120
MIDI Compiler: Done.
ERROR: Project Compiler: Midi compiler failed.
I’m having this when tyring to compile, I’ve been trying to find what are the cause but no luck… I was wondering if anyone could help.
Here is the RPP: http://www.mediafire.com/download/73a9j … ticity.rar
Your first time signature is botched, which chews up a measure, that’s why you get the long note error. The charts comes from FoF or EOF and thus all notes are too short, hence the double note off issue: make them all 1/16th or 1/32nd, depending on the shortest note in the chart.
Thanks for the advices. I see the time signature problem, but I can’t seem to be able to fix it, If I delete the time signature marker to make it right it screws up the chart. I also made all the notes to 48th (because fastest notes are 48th), if I make them 32th they will overlap, and it doesn’t fix it, same errors. I was wondering what the first error (and related errors) are about, since this chart doesn’t have any drum lanes charted.
This chart wasn’t done on EoF. I always put them back to 1ms (or so) lenght, and it nevertempered with Magma C3 until now. (Making this chart on EoF would be a pain… non x/4 time signature on EoF is not supported, thus you would need to double cpm for x/8, quadruple for x/16.. would be a real pain to make it work with Magma
Post a link to the .rpp (or PM it to me), and I should be able to fix the time signature / measure problem for you. I’ll provide you with the feedback on my steps so you should be able to fix this in the future =]
Edit: Thanks for pointing out I’m an idiot
” src=”/wp-content/uploads/invision_emoticons/default_SA_biggrin.gif” /> haha my bad.The RPP is posted on the OP.
” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif” /> Thanks for the help.Thanks for the advices. I see the time signature problem, but I can’t seem to be able to fix it, If I delete the time signature marker to make it right it screws up the chart.Yeah, I know. Only thing I can suggest is:
– Select from current M4.1 up to the end of the project
– Export MIDI using current selection only
– Torch your tempo map
– Import the MIDI at M3.1, tempo map included.
It should work.
This chart wasn’t done on EoF. I always put them back to 1ms (or so) lenght, and it nevertempered with Magma C3 until nowWhy?
http://www.mediafire.com/download/ror4w … ticity.RPP
There, I fixed the skewed measure issue and it compiles now with no errors.
I basically just re-tempo mapped measures 1-5 so they matched back up. There was a tempo marker fractionally after 3.1 (which I believe was meant for 3.1) that was causing the problem. It was a “set time signature” marker due to the time signature change, and because it was not directly on 3.1, REAPER technically starts 3.1, and then it gets eaten up by the marker because it has to start 4.1 at the actual marker location (confusing, sorry).
Deleted the problem marker, and readjusted the tempo so it realigned at 4-5.
To solve the issue of the note being messed up:
1) Open up a new project tab
2) Copy over the tracks into the temp project (I did Drums and Beat because they had notes) as backup
3) Delete the notes from the main project (right click -> select all notes -> delete)
4) Fix the tempo issue
5) Copy the notes from the temp project (right click -> select all notes -> copy)
6) Paste the notes at the correct starting location in the fixed project
Steps 5 and 6 will be done individually for each track you backed up.
In a more usual file, this step would not really be necessary. You could have just fixed the tempo issue, and then moved all the notes forward the missing beats. However, do the time signature change pretty much every measure (wtf by the way ha), REAPER had a terrible time trying to maintain everything; thus why I had to remove the note and bring them back in.
Sorry about the lack of explanation for the tempo fix. I use a modified version of the “Q” shortcut that C3 uses, with mine having a LOT more versatility. I tried to recreate it using Q, but I was not able due to some limitations (or possibly MY lack of understanding with how the C3 Q works). I’m planning on releasing a tempo map advanced tutorial in the future using my method showing off all the help on issues such as this… just need a mic and a computer than can handle video capture without lagging ha.
… annnnnnd Far fixes the problem in a few sentences
haYeahhh, that way works too lol. Much easier to understand in words as well. I mean, I was able to do mine quickly too, but trying to explain it out made it seem terrible compared to his
” src=”/wp-content/uploads/invision_emoticons/default_SA_cheeky.001.gif” /> Side note: I’m not sure where you were seeing “42nd” notes?!?! (More so, how* and where). The strictest I saw was 32nds, so I expanded the notes to 1/32 and everything seemed fine with no overlaps.
… annnnnnd Far fixes the problem in a few sentences ha.What actually happens when ONE marker is corrupt/illegal in Reaper is that only that marker has issues, but if you change that one, you chain-mess up everything after that. Since all the other markers are fine though, I find that sometimes you can just export the MIDI (you only need the tempo map in reality) and use the tempo map from after the mess up to replace your current one from that point on. It’s a neat trick that doesn’t require you to redo the tempo map.
Side note: I’m not sure where you were seeing “42nd” notes?!?! (More so, how* and where). The strictest I saw was 32nds, so I expanded the notes to 1/32 and everything seemed fine with no overlaps.
Also, under 1/32T everyone should check that the song is really that dense, because it’s unusual and it may indicate something wrong is going on.
Yeah, I know what happens when the measures skip like that. Usually (when I use to have this problem), I would select the tempo map nodes and just copy/remove them, and then paste them back in after fixing. I feel that is harder to explain though as not many people likely know you can copy/paste/ect the nodes themselves in the master track (I certainly didn’t at first).
I never actually thought to export an embedded midi and import back. Makes sense though. I feel the nodes are quicker for me, but the midi is pretty damn easy to explain ha. Thanks for that.
As per the notes. Firstly, I feel like an idiot. I do realize now that 1/32T is 42nds (well, 41.666)… not happy that I didn’t see/realize that at first. Secondly, I was saying that I put on the 1/32T grid and while there are some notes on that grid, they aren’t “rolls” at the speed, just spaced notes. The tighest grouping of notes I saw were all streams/rolls of 32nds. Thus, expanding all note lengths to 32nds worked fine with no overlaps. Unless I was missing a part somewhere (which I’m hoping the original poster will comment on when he’s back).
It’s a lot of double bass and fills charted at that speed, so the tempo seems fine. The general bpm throughout is about 103, so it seems about right.
Yeah, I know what happens when the measures skip like that. Usually (when I use to have this problem), I would select the tempo map nodes and just copy/remove them, and then paste them back in after fixing.That’s a good process actually.
This chart wasn’t done on EoF. I always put them back to 1ms (or so) lenght, and it nevertempered with Magma C3 until nowWhy?
For drums only, to eliminate all possible sustains I might have made without knowing, it’s an easy way to do it.
There, I fixed the skewed measure issue and it compiles now with no errors.Thanks for that, and the infos!
” src=”/wp-content/uploads/invision_emoticons/default_SA_biggrin.gif” />However, do the time signature change pretty much every measure (wtf by the way ha), REAPER had a terrible time trying to maintain everything; thus why I had to remove the note and bring them back in.Yeah I love this band. Making the tempo map and the chart gave me a headache though, even with music sheets it’s mindfuck
As per the notes. Firstly, I feel like an idiot. I do realize now that 1/32T is 42nds (well, 41.666)… not happy that I didn’t see/realize that at first. Secondly, I was saying that I put on the 1/32T grid and while there are some notes on that grid, they aren’t “rolls” at the speed, just spaced notes. The tighest grouping of notes I saw were all streams/rolls of 32nds. Thus, expanding all note lengths to 32nds worked fine with no overlaps. Unless I was missing a part somewhere (which I’m hoping the original poster will comment on when he’s back).You’re right, sorry, I took the 24th for 48th.. I guess I was still sleeping when I looked.
- You must be logged in to reply to this topic.