[DoNotPassGo]

I’m trying to build out a song project so I can play-test myself (and to just know it works), and the .midi tester freezes and becomes unresponsive.

 

I passed in individual tracks until I narrowed it down to the PART DRUMS. Next I was going to go through each section and figure out, but removing the Drum Fill notes enables the midi to pass instantly.

 

So does anyone know off hand what could cause drum fill notes to freeze the compiler?

 

– I re-quantized the notes just in case.

– I gave space between them

– Checked that there were no “double notes” under any of them

 

I got nothing. I’m sure it’s something simple, but it’s something I don’t know or understand about the compiler and tester.

[TrojanNemo]

I’m sure it’s something simple, but it’s something I don’t know or understand about the compiler and tester.

 

I don’t have an answer to your question, but wanted to point out that the “test” and the “compiler” are not two separate things. The tester prepares a dummy project based on the contents of the MIDI, then sends it to the compiler, just as if you manually created a project using Magma and then clicked Build.

 

I have no idea why it gets stuck on a loop. It literally is called the same way when building a song or when testing a song. But since I know it does go in a loop, I have that code to catch it and tell you after 30 seconds. If you can figure out why it happens at all (the loop) then I would love to know.

[DoNotPassGo]

Sorry being being vague, I meant the tester (drag the .midi over and then test before exporting the new midi).

 

I just mentioned that it passes steps up until it “passes the midi off to the MagmaCompiler” or something, and then it hangs. Yeah I know it’s set to ask after 30 seconds, but I’m just curious what could do that. Literally removing the notes has it pass instantly, but with the fill notes in just hangs there.

 

I don’t know if there are actual compiler “rules” that could fail it, but I’ve been make sure everything follows “make sense” rules.

 

– Quantized

– All the same length (I know not required)

– All have about a 2-4 measure gap

– No “tail notes” on either end

– No double notes underneath

– No fills before overdrive

– No fills in the last 4 measures

 

I know a lot of those aren’t “rules” per-say, so it should be that.

[djmike534]

I was thinking that they needed to be one full measure long, is that not right? If so, what are the accepted min/max lengths? Only error I ever had besides having no fills was spacing needed to be one measure min.

You can ignore many of the magma testing errors as the compiler itself isn’t so strict. A good trick I learned is when you get an unusual error try restarting Magma and sometimes the error doesn’t repeat.

[Farottone]

I was thinking that they needed to be one full measure long, is that not right?

 

They don’t.

[DoNotPassGo]

This was an existing Magma project I was updating a revised midi on. I tried with a fresh Magma as well. No luck.

 

Honestly, I’m over it for now. I’m trying to keep this file off the radar for a while, so I really don’t want to bother giving out the .rpp. I just removed the fills for now and I’ll just redo them later on from scratch and see if that works. Just weird because I know this compiled before as I’ve play tested it before lol. When I’ve been updating the chart I would not have touched any of the fills.

 

Oh well. Worse case, I need to start a new project itself and transfer everything over. Just very strange ha.

[AddyMills]

I was thinking that they needed to be one full measure long, is that not right?

 

They don’t.

They do need to be a certain amount of time apart though (can’t remember if it uses seconds or ticks). But magma will start bitching at you if they’re too close.

 

Since you said you have some 2 measures apart, try make it so that they’re all at least 4 apart.

 

Have you tried to compile it? I don’t mean the test button, but actually compiling it. It sometimes gives errors that the test function doesn’t.

[Farottone]

They do need to be a certain amount of time apart though (can’t remember if it uses seconds or ticks). But magma will start bitching at you if they’re too close.

 

Yeah but that’s a simple error message, so I would rule it out in this case.

[AddyMills]

Not if you’re using the test button. I just did a test midi purposely having two fills close together. The test button caused the program to hang, the compile button gave me the error.

 

I have to leave now, but if nemo doesn’t see this by the time I get back I’ll mention it in the Magma thread.

[DoNotPassGo]

I’ve moved on and already deleted the previous fills so couldn’t tell you off hand. Maybe that was it. I believe* the were only 2 measures apart in some areas, but my usual is 2-4. I’ve never really had this happen before on any other songs (which I honestly do the same) so couldn’t tell you.

 

If that’s producing an error in the compiler then maybe that could be it.

[AddyMills]

Could it be that the BPM is higher on this song than your other songs? I just double checked and Magma requires that fills have 2.5 seconds between them, so the spacing is not determined by the amount of measures between them, but the amount of seconds.

 

So a 2 measure distance on a song with 120BPM would be 4 seconds and Magma is fine with that. The threshold is 192 BPM at which point 2 measures becomes exactly 2.5 seconds. Any BPM higher than this, and the 2 measures between fills will give an error.

 

Also, I have to recant my previous “finding” of the hanging ups. Magma only does it some of the times with this error. Sometimes it hangs, sometimes it tests correctly. I just happened to get 3 hang ups in a row earlier tonight. So, if the error you are experiencing is fill space related, either you’re getting really unlucky with the hanging of the program, or there is a different problem (like others have mentioned and if this is the case then I apologize to Farrotone for being a snarky ass!).

 

Next time you experience a hang up in Magma, I recommend trying to compile instead of test. This might give a more concrete error message than a hang up.

[TrojanNemo]

I have to leave now, but if nemo doesn’t see this by the time I get back I’ll mention it in the Magma thread.

 

Nemo sees everything

 

But unfortunately I have not found the cause of the different behavior in testing vs compiling since from my point of view, it’s the same process once it gets to the compiler. That’s why I added the check for whether it had entered a loop rather than fix the cause of the loop.

[DoNotPassGo]

BPM is ~65 so it’s a slower song.

 

One measure in itself is a little over 3 seconds (my count in works in just one measure). Most of the fills in this songs were half measure long, so even at “every 2 measures”, you were looking at a trigger spacing of 1.5 measures, which would be ~5 seconds.

 

 

Alright, so I remembered that (since I keep my files on a flash drive) that I back them up every week or two on my actual computer. I found I still had that old chart in there, so I could test with that. Throwing the midi without testing into the compiler DOES give me more errors:

 

 

Project Compiler: Entering Phase 2 of 5…

MIDI Compiler: Starting…

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [28] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [30] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [32] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [34] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [37] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [39] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [41] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [43] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [45] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [51] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [53] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [55] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [59] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [61] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [63] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [65] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [67] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [69] for easy difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [28] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [30] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [32] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [34] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [37] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [39] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [41] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [43] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [45] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [51] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [53] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [55] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [59] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [61] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [63] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [65] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [67] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [69] for medium difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [28] for hard difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [30] for hard difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [32] for hard difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [34] for hard difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [37] for hard difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [39] for hard difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [41] for hard difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [43] for hard difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [45] for hard difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [51] for hard difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [53] for hard difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [55] for hard difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [59] for hard difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [61] for hard difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [63] for hard difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [65] for hard difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [67] for hard difficulty

ERROR: MIDI Compiler: (PART DRUMS): No gems after drum fill at [69] for hard difficulty

MIDI Compiler: Done.

ERROR: Project Compiler: Midi compiler failed.

 

 

 

Story about this project now. It use to have Fills, Overdrive, and Reductions. I started making changes and updating from early charting days, and decided to scratch the reductions and redo them later. I also removed the overdrive as I have been actually finishing up keys and wanted to redo the activations again.

 

This has no overdrive charted, and no reductions. Now, I assumed before that overdrive could have been the culprit, but adding it in did not do fix anything.

 

Sooo… I’m guessing that drum fills need to have reductions charted to work? Somewhat similar to how solos need notes under them?

 

This came about because I was just looking to test my files last weekend with the expert charts. Does this all sound about right now?

[DoNotPassGo]

Yep. I just threw in yellow quarters throughout the entire song, and it compiled “without problems”.

 

Good to know lol. I have always done personal reductions and never used CAT, so I never really thought that fills needed notes on all difficulties. I usually make sure to perfect my expert charts before doing ANY overdrive/reductions, so testing is never been an issues before. Because I was updating an old file and left in the fills I used, this is the first time I saw this.

[Author]

Posts