SOS: Tick duration is killing me…
- This topic is empty.
-
Posts
-
Good morning, everyone. I’m currently working on a Stones song with Kemiroch that is kicking my ass. The vast majority of the song is in 4/4, but there are four measures (3, 26, 46, and 72) that are in 2/4. I’ve done the tempo map, created a drum chart, and finished the vocals. However, when I process it through Magma I get the following error messages:
ERROR: MIDI Compiler: (PART DRUMS): Gem at [46:2:479] in easy difficulty has a duration of 121 ticks; max is 120
ERROR: MIDI Compiler: (PART DRUMS): Gem at [72:2:479] in easy difficulty has a duration of 121 ticks; max is 120
ERROR: MIDI Compiler: (PART DRUMS): Gem at [46:2:479] in medium difficulty has a duration of 121 ticks; max is 120
ERROR: MIDI Compiler: (PART DRUMS): Gem at [72:2:479] in medium difficulty has a duration of 121 ticks; max is 120
ERROR: MIDI Compiler: (PART DRUMS): Gem at [46:2:479] in hard difficulty has a duration of 121 ticks; max is 120
ERROR: MIDI Compiler: (PART DRUMS): Gem at [72:2:479] in hard difficulty has a duration of 121 ticks; max is 120
ERROR: MIDI Compiler: (PART DRUMS): Gem at [46:2:479] in expert difficulty has a duration of 121 ticks; max is 120
ERROR: MIDI Compiler: (PART DRUMS): Gem at [72:2:479] in expert difficulty has a duration of 121 ticks; max is 120
So basically my first two time changes (at measure 3 and 26) are fine. However, there are no drums in measure 3, so it could be screwed up too. Measure 26 does have drums though, which means that Magma is fine with it for some reason. I used the exact same methods whenever a time change appeared, but for some reason only measures 46 and 72 are giving me problems.
Now let me just say that I’ve scoured the database looking for a solution to this problem. One thread talked about how this error can crop up if your time change doesn’t fall exactly on the first beat of the measure. However, all my time changes fall on the first beat. I also read that you can try to trick Reaper by changing the length of the note (from, say, a 16th note to a 128th note), but that didn’t work either. I also read that this problem can arise if you have two upbeats in a row in the Beat section—but that wasn’t the issue either.
Long story short: I need someone to help me out here. I just want to process this custom through Magma and test my work, but this one little tick is preventing me from doing that. Any help would be appreciated.
I didn’t look at your project but this is almost certainly a problem with the tempo map either before or after the measures in question. Make sure your time signature markers are perfectly on the measures X.1.00. Then quantize the notes in the affected measures.
Everything seems to be just fine. I’ve only managed to ever fix such weird problems by removing the notes and then putting them back. No cut-paste, simply double click to put each note back where it should be.
The error suggests those notes start one tick into the end of the last beat, but REAPER doesn’t show it, not even in the Event list view.
The problem is what I said it was. With Snap on, grab the “T” and drag it carefully to the right. You will see the time change from 4:17.207 to 4.17.209. Go back through your song and do this to all of them since I noticed at least a few of them did this (likely starting from M46 at your first time change.) Start at M46 and continue to the end of the song.. Changing one will have an effect on others that come after it
The problem is what I said it was. With Snap on, grab the “T” and drag it carefully to the right. You will see the time change from 4:17.207 to 4.17.209. Go back through your song and do this to all of them since I noticed at least a few of them did this (likely starting from M46 at your first time change.) Start at M46 and continue to the end of the song.. Changing one will have an effect on others that come after it
Thanks for helping me out—I followed your advice and got it to work! I have to admit, I was definitely thrown off by your point about starting the measure exactly on the first beat. I just assumed that if Reaper said it was on 73.1.00, then it was fine. I didn’t know it could technically be on the first beat and still be a couple ticks off. I’ve worked on 20-30 customs (several of which feature time changes) and I’ve never stumbled across this problem before. Regardless, this is definitely a good thing to know, as I’m sure this error will pop up again.
Wow I read this section and it is waaay over my head. Thanks to all off you for your hard work, I get many many hours of enjoyment from everybody’s work. And lastly thanks for helping each other out. If I could buy you all a beer I would. CHEERS!
- You must be logged in to reply to this topic.