Magma Error – Chord gems don’t end simultaneously
- This topic is empty.
-
Posts
-
Working on a song and getting an error for my drums part, for each of e/m/h/x at time signatures of x.x.000,
x.x.120, x.x.240, and x.x.360 – where xx is every single time that I have mapped a note on drums. Keep in mind that when you look at the alt 3 version of the mini map, all notes that none of my notes have a length of 0.0.120, and none of them start at anything other than x.x.000, x.x.125, x.x.250, etc…
Also, when clicking “build” in Magma c3, i get the popup warning of “No drums overdrive fills were detected!…”.
The weird part is, I have several overdrive fills charted. I do not know why it is saying it cannot detect them.
The first few lines of magma error logs are as follows” It goes on like this until it bombs:
ERROR: MIDI Compiler: (PART DRUMS): Difficulty easy: Chord gems don’t end simultaneously at [3]
ERROR: MIDI Compiler: c:/users/lynxis/desktop/rb customs/songs/united states of whatever/unitedstatesofwhatever v11_clean.mid (PART DRUMS): Double note-off 61, [3]
ERROR: MIDI Compiler: (PART DRUMS): Difficulty medium: Chord gems don’t end simultaneously at [3]
ERROR: MIDI Compiler: c:/users/lynxis/desktop/rb customs/songs/united states of whatever/unitedstatesofwhatever v11_clean.mid (PART DRUMS): Double note-off 73, [3]
ERROR: MIDI Compiler: (PART DRUMS): Difficulty hard: Chord gems don’t end simultaneously at [3]
ERROR: MIDI Compiler: c:/users/lynxis/desktop/rb customs/songs/united states of whatever/unitedstatesofwhatever v11_clean.mid (PART DRUMS): Double note-off 85, [3]
ERROR: MIDI Compiler: (PART DRUMS): Difficulty expert: Chord gems don’t end simultaneously at [3]
ERROR: MIDI Compiler: c:/users/lynxis/desktop/rb customs/songs/united states of whatever/unitedstatesofwhatever v11_clean.mid (PART DRUMS): Double note-off 97, [3]
The following is a zip of everything that i can think to include so that some nice person with more knowledge than me (this is only my second song) can take a look and see if they can figure out what is wrong, or if anyone can offer any suggestions on things to try.
Note: If i delete the notes that cover the times where it says there are errors, then magma stops reporting the error for that time. the problem is, anything i chart, with teh grid set to 1/16 (i havent tried other times) will show the error like all the rest. I am confused
” src=”/wp-content/uploads/invision_emoticons/default_SA_frown.gif” /> It is like every single time i put a note in, the note is 0.0.005 too short.
http://teamfz.org/lynxis/RB%20Files/Uni … atever.zip
Thank you for any help you can provide!
You changed the MIDI track velocity. You’re not the first to do that, do you use a Reaper version newer than 4.22? Maybe there’s some kind of control that makes it easy to fudge it up.
Anyway, reimport the DRUMS track from our template, copy over the notes from your project and ditch your DRUMS track.
This fixed the problem! I opened a new project, imported the project template, cntrl + c the drums track from the empty template, opened my original project, and cntrl v into the original project. This made 2 drums tracks. Then just select all gems and copy/paste, and then selected my text events, copied and pasted, and done!
Problem i have now and that i had with my first song I worked on, when play testing, the timing is a complete mess. The time of the gems/lyrics/etc.. are not in time with the song audio at all, except right at the beginning. My tempo map looks flawless and all the way through everything lines up just as it should, but its a mess. To fix my first song i did which had this same problem, i had to delete my entire tempo map, and rebuild it. Just seems ridiculous to have to do this every single time you map a song. I must be doing something wrong.
Did you remember to export the tempo map with your MIDI? I think it’s set to not do that by default and need to be manually changed in the window that pops up when preparing to export it.
Also, if stuff doesn’t go accurately on grid, the Quantization tool is your best friend (if used correctly).
Yes, the tempo map is being exported.
I used the quantization tool on a few sections and nothing changed. The errors kept occurring for that section.
Yes, the tempo map is being exported.I used the quantization tool on a few sections and nothing changed. The errors kept occurring for that section.
Upload your RPP file and your exported MIDI file please.
It is uploaded.
http://teamfz.org/lynxis/RB%20Files/Uni … atever.zip
I was looking a bit more before bed last night and found where i had somehow set 4/4 time on one of the time markers, but the song is in 4/4 time to begin with. Anyways, when i “uncheck” the set time signature box and apply, something happens that causes all the gems to move way right and a large amount of space to show up in all the tracks.
It is uploaded.http://teamfz.org/lynxis/RB%20Files/Uni … atever.zip
I was looking a bit more before bed last night and found where i had somehow set 4/4 time on one of the time markers, but the song is in 4/4 time to begin with. Anyways, when i “uncheck” the set time signature box and apply, something happens that causes all the gems to move way right and a large amount of space to show up in all the tracks.
Yep, chewed up measures. I’m not gonna download it then, the issue is there. You have either put or imported a MIDI with a time signature change set on the wrong location (not at the 1 of a measure). That made Reaper chew up a measure. You need to remove that marker (sometimes the Q action does that, though I can’t say how and why, it’s a pre-built function we have no control over).
Unchecking the set time signature at the start of the 6th measure fixed the problem, but then i had to drag all gems and all text events back 1 measure. All in all, it worked. Thanks for your help!
Any idea why my drummers on all of my songs just sit there with their arms up and to the side? They all look like the Karate Kid doing the flying crane.
Unchecking the set time signature at the start of the 6th measure fixed the problem, but then i had to drag all gems and all text events back 1 measure. All in all, it worked. Thanks for your help!Any idea why my drummers on all of my songs just sit there with their arms up and to the side? They all look like the Karate Kid doing the flying crane.
Did you add drums animations and play marker?
I did not add drum animations, but i did add a play marker. Someone else i know has started to author songs and he said his drummer was animated without adding animations so i thought it might be autogenerated. I saw the bit in the wiki whatever pages that said its best to copy over expert chart to specified locations for animations but wasnt going to do that if i was missing something…
Autogeneration of drums only works if you have NO animation markers. The [play] and [idle] markers are animation markers, so Magma skips autogeneration. Even when it does generate them, it’s pretty crappy. You should consider doing it manually.
Autogeneration of drums only works if you have NO animation markers. The [play] and [idle] markers are animation markers, so Magma skips autogeneration. Even when it does generate them, it’s pretty crappy. You should consider doing it manually.So glad we’re doing that thing that we’re doing. It seems to be relevant for more than half of the authoring posts we read.
” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif”>
- You must be logged in to reply to this topic.