[MrTimotei]

(Reposted because I’m a dummy who asked this in the wrong place.)

 

Hello! I’m usually pretty good at figuring out what the problem with my song is when MAGMA spits errors out at me. However, this one song I’m compiling gives me a “Data chorus is not Array” error, and doesn’t really explain what it is at all.

Then it says to check the log file for what needs to be fixed, but there doesn’t seem to be a log created in either MAGMA’s folder, or the folder with all the project data (midi, .c3 file, etc.). Perhaps I’m not looking in the right spot? In which case, where is the log file created?

 

Below is the exact text from MagmaCompiler:

 

 

Welcome to MIDI Tester 1.1

This program is intended to quickly let you test MIDI after MIDI for compliance with RBN2.0 standards.

All you have to do is drag the MIDI file(s) here. This program will read through it, and create an adequate test project. MagmaCompiler is then called to process the MIDI for RBN2.0 compliance without actually compiling the song (so no time wasted compiling the audio).

You can do back-to-back MIDIs without having to close this form.

Ready to begin….

Found PART DRUMS…

Found PART BASS…

Found PART GUITAR…

Found PART VOCALS…

Found vocal percussion: hand clap.

Nemo’s MIDI AutoGen process started.

Added drum mix events successfully.

Nemo’s MIDI AutoGen process completed.

Starting Basic EMH Check..

MIDI passed Basic EMH Check without reporting any problems

This means the charts most likely have reductions charted.

Ready to send files to MagmaCompiler … hold on.

Output from MagmaCompiler follows:

Reading the archive

MIDI Compiler: Starting…

FAIL-MSG: Data chorus is not Array (file config/midi_verify.dta, line 372)

ERROR: MIDI Compiler: Data chorus is not Array (file config/midi_verify.dta, line 372)

ERROR: MIDI Compiler: Data chorus is not Array (file config/midi_verify.dta, line 372)

Data Stack Trace

config/midi_verify.dta(372):foreach

config/midi_verify.dta(369):do

config/midi_verify.dta(366):if_else

config/midi_verify.dta(365):if

config/midi_verify.dta(364):check

Stack Trace (map file unavailable)

756b5608

MagmaCompiler reported some errors. Please see the log for details on what must be fixed.

Process completed in 0 minutes and 1 seconds.

You may drag another MIDI or just click Close to exit.

[Farottone]

Improbable errors usually hide an improper use of the template. Are you sure you haven’t touched anything or added anything that shouldn’t be there?

[MrTimotei]

Improbable errors usually hide an improper use of the template. Are you sure you haven’t touched anything or added anything that shouldn’t be there?

 

I was pretty sure I didn’t do anything different to the template, but I seem to have found the issue.

 

I exported a separate MIDI for each individual instrument and tested to see if it would come out okay, but they all still gave the same error. This told me it had to be something with either the BEAT, VENUE, or EVENTS tracks. Figuring the venue was the most finicky of the three, I removed all the text events and notes (ctrl+a to select everything, even if it was something I couldn’t see) and sure enough, it compiled okay.

 

Don’t know what exactly I put down that caused that error but all is well now~

[Author]

Posts