Jump to content

Avatar

[Drums] Double-Note Off Error?


  • Please log in to reply
8 replies to this topic

#1 R_Ingtail

R_Ingtail
  • 17 posts

Posted April 11, 2014 - 05:24 AM

I keep getting the same error over and over while trying to compile this song into Magma.

It reads a Double-Note Off error for the Drums track, starting from the beginning, and running until the compiler just runs out of lines to pitch error codes into. The song itself (attempts to) trigger the Disco-Flip event which reads fine in the preview window.

Notes:
-- I have deleted, then reapplied the entire Drums chart, but the same error code still fires.
-- Animations are charted.
-- Muting the Drums allows Magma to render it no problem.

Reaper File: https://www.mediafir...9ngko4g2cct4i4d

- R_Ingtail
"I'm crazy, not stupid." - Personal Quote

Cons by Ingtail as of 3/9/2015: viewtopic.php?f=20&t=2049
The WIP (It Good) Thread as of 2/6/15: viewtopic.php?f=23&t=1747

#2 Farottone

Farottone

    The Lean Mean Customs Charting Machine

  • Administrator
  • 6,484 posts

Posted April 11, 2014 - 09:58 AM

The Drums MIDI track is at 0% velocity. Look for the red line at the bottom of the MIDI track and drag it back up to the top.

#3 Nightmare Lyra

Nightmare Lyra

    Ukulele Hero

  • 1,957 posts
  • Location
    Skyrim

Posted April 11, 2014 - 12:10 PM

Also, have you quantized the notes after placing them? Due to most MIDI programs being silly, notes sometimes go a 128th off sync, which looks poor and causes Magma errors sometimes, but can be fixed with quantizing the notes (mark the notes and press Q on your keyboard) with the "Position and note end" option selected (be sure you have the correct grid selected when doing this, if you are quantizing straight notes it will be messed up if you have a triplet grid selected for example).

horror_movie_special fan club member


#4 ws54

ws54
  • 847 posts

Posted April 11, 2014 - 11:46 PM

And if those things didn't help, look closely at the tempo map and markers near the measure the error reports to make sure they are snapped to the start of the measure.

#5 R_Ingtail

R_Ingtail
  • 17 posts

Posted April 22, 2014 - 04:57 AM

I was able to figure a solution to the fault I had. I wish to extend a thank you to those who gave me ideas on what needed to be fixed.

#6 cleverest

cleverest
  • 271 posts

Posted August 17, 2020 - 07:59 AM

I was able to figure a solution to the fault I had. I wish to extend a thank you to those who gave me ideas on what needed to be fixed.

I realize this post is very old, just hoping you see this and can share what you did to fix it. I'm having the same issue...none of the above steps worked, but I'm not sure where or how to do this: "The Drums MIDI track is at 0% velocity. Look for the red line at the bottom of the MIDI track and drag it back up to the top." (I don't see that anywhere in Reaper 4.22), but selecting all my notes and checking it in properties says all my notes are at 96 velocity.



#7 Alternity

Alternity
  • 1,225 posts

Posted August 17, 2020 - 12:53 PM

This guy was last active in 2014, I doubt you'll get any kind of answer from him.

Necro'ing posts is not a good habbit usually.



#8 cleverest

cleverest
  • 271 posts

Posted August 17, 2020 - 02:22 PM

I was referred here for help, hence the post here. I also posted elsewhere about it.



#9 cleverest

cleverest
  • 271 posts

Posted August 17, 2020 - 06:27 PM

OMG I fixed it...well I need to test the song first, but at least it compiled!

I hope this helps someone,

To fix this: You need to put your mouse on the very bottom edge of your midi track having the issue w/ displaying Vel x0.00 on the top of the track itself...after doing so it will change from a pointer to a drag icon...then hold and left click to drag upwards...almost as if you were trying to resize the actual midi track and squish it upwards..but instead a line will appear as it gets dragged up, showing THE "velocity" going up...sorta "filling the track background, as if with a liquid effect"...you want to drag it all the way up to the top edge, where it will read as VELOCITY 1.00

I don't know how in the world that got lowered all the way down (or at all) in the first place, but I'm so glad it complies without errors now!






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users