[TrojanNemo]

you absolutely need the new one, as in it are many of the changes included in v1.1. make sure you install the latest official magma first, then extract and overwrite. there are two files in the gen folder, leave the .hdr file and replace the ark with the one included.

[Scienyde]

you absolutely need the new one, as in it are many of the changes included in v1.1. make sure you install the latest official magma first, then extract and overwrite. there are two files in the gen folder, leave the .hdr file and replace the ark with the one included.

Okay, maybe my Magma V2 install wasn’t up to date. I’ll redownload and reinstall once again then.

[Scienyde]

All right, very weird. Apparently I had a newer version of Magma v2 installed on my computer than the one in pksage’s thread… the one linked there is 2.0.101.0, my install was 2.0.102.0. Uninstalling 102 completely, redownloading 101 and reinstalling, and then installing C3R 1.1 over the top has worked successfully.

 

If you want, I can provide you with the 102 installer if you’d like to test and see if you can reproduce on your end… but if I’m the only one that was using that and had that problem, I guess it’s not a big deal ” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />

[TrojanNemo]

It all comes down to the hdr file I’m certain. I’ll add the hdr file to the package and reupload so others don’t have the same issue

[TrojanNemo]

UPDATED TO v1.1.1

 

v1.1.1

- included the .hdr file that goes along with the ark file to ensure the program works regardless of which previous version of Magma you had

- removed the Release Label section since we can't do anything with that

- extra information will be saved to the songs.dta to work better with Visualizer

- since now we know by default MagmaCompiler tells oggenc to encode the audio at quality 3 (rather than the assumed 5), that is the new default

- minor aesthetic changes

 

Same link in the OP.

[TrojanNemo]

another small update pushed. same link in the OP. the text file in the OP has the few changes. mostly fixing a couple of small bugs. all of you should download v1.1.2 or you will have problems saving projects when your path has spaces.

[Psym]

first time using it and magma throws some wierd shit in my face. Passes everything but shoots this at me after everything else passes

 

MIDI Compiler: Validating…

MIDI Validation failed: (noteOnTime == NOTE_OFF)

e:prjrbnsystemsrcrbnvalidatorMidiValidator.cpp, line 238

 

MIDI: The previous failure caused the following failure:

 

MIDI Validation failed: (ValidateMidiChannelEvent(eventType))

e:prjrbnsystemsrcrbnvalidatorMidiValidator.cpp, line 408

 

dunno if its magmas fault or mine, but the chart is pretty prestine.

[TrojanNemo]

That’s an error with MagmaCompiler, not Magma, and it is coded by Harmonix. So it’s something with your chart, unless you run the same project and midi through the old Magma and somehow it compiles. But I’m pretty certain it won’t.

 

Post the whole project here if you’d like me to take a look.

[Psym]

That’s an error with MagmaCompiler, not Magma, and it is coded by Harmonix. So it’s something with your chart, unless you run the same project and midi through the old Magma and somehow it compiles. But I’m pretty certain it won’t.

 

Post the whole project here if you’d like me to take a look.

 

aight thanks ill send a pm in a bit.

 

Over 600 converts and this is the first time ived seen this so yeah thought it might was the messing around with the program that did it.

[TrojanNemo]

Here’s the problem: You did not author anything for drum animations.

 

It seems something in the hacking of MagmaCompiler messed up the auto-drum animations, so when you have NOTHING for drum animations, you get that error. as soon as you drop a single animation note, it compiles fine…but this means you have to author drum animations.

 

Sorry to say but I don’t think that’s an error we’ll be dedicating too much time to fix because 1) hacking MagmaCompiler is dirty and messy, and finding how we messed up that portion will be difficult if not impossible, and 2) all C3 authors are required to author drum animations.

 

If you’d like some help on how to do basic drum animations shoot me a message. Basic animations take 5 seconds. Decent animations take ~5 minutes.

 

As a side note, your chart was not “pristine”…none of the drum notes (didn’t check guitar) were snapped to grid and were charted as 1/128th notes unnecessarily…and while I know you only author in Expert…why were HME at different points than X? are you selecting all, then pressing Alt + C to copy down the difficulties?

[Psym]

Here’s the problem: You did not author anything for drum animations.

 

It seems something in the hacking of MagmaCompiler messed up the auto-drum animations, so when you have NOTHING for drum animations, you get that error. as soon as you drop a single animation note, it compiles fine…but this means you have to author drum animations.

 

Sorry to say but I don’t think that’s an error we’ll be dedicating too much time to fix because 1) hacking MagmaCompiler is dirty and messy, and finding how we messed up that portion will be difficult if not impossible, and 2) all C3 authors are required to author drum animations.

 

If you’d like some help on how to do basic drum animations shoot me a message. Basic animations take 5 seconds. Decent animations take ~5 minutes.

 

As a side note, your chart was not “pristine”…none of the drum notes (didn’t check guitar) were snapped to grid and were charted as 1/128th notes unnecessarily…and while I know you only author in Expert…why were HME at different points than X? are you selecting all, then pressing Alt + C to copy down the difficulties?

 

Thanks and im fine with manually fixing drum animations i still havent figuered out how to alternate between left and right hand tho(i barely do drums and i hate getting em through magma).

 

Song wasent pristine per se i meant good enough to pass through magma(or should be). The file you got was basically a cleanup(to pass magma) of a fof chart that would throw tick errors in my face if i didnt 1/128 it(3 minuttes of work to test if i even wanna use time fixing magma errors it might throw at me), Allso reworked in EOF cause leadin was none existent. I dont care for animations and i usally only do guitar so that is my main focus. I dont care about other diffs so yeah i copy paste the expert chart down to HME so i can pass OD later on.

 

I just did a diffrent song with exact same setup and no errors at all and it made auto drum animation…magma got a will of its own.

 

EDIT: Re startet the project and did the same thing and now it works…no midi compiler error… magma i hate you,

[TrojanNemo]

EDIT: Re startet the project and did the same thing and now it works…no midi compiler error… magma i hate you,

 

so you don’t hurt my feelings, let me correct you. you hate MagmaCompiler. so do I. Magma, I have full control of. MagmaCompiler, we do not…and that’s what most of the times people have problems with.

[Psym]

EDIT: Re startet the project and did the same thing and now it works…no midi compiler error… magma i hate you,

 

so you don’t hurt my feelings, let me correct you. you hate MagmaCompiler. so do I. Magma, I have full control of. MagmaCompiler, we do not…and that’s what most of the times people have problems with.

 

Lol wasent meant for you was just my frustration with magma as allways, been using it since 2011 and its still just as unpredictable as allways.

 

Anyways i finished up my pack and didnt have any problems after that song i sent you. Now to test the pack with my loyal testers lol .

[MFX]

Here’s an issue with Magma C3…

 

It doesn’t seem to know anything about a “dirty” state for the audio files anymore. Used to be that if you didn’t touch the audio, it would have the old .mogg around in a cache somewhere and not have to redo the encoding. That’s the potential of a lot of build time saved, if you could make that work again.

 

EDIT: For the record, I’m using the “Song ID” edit field for this custom I’m working on. Perhaps that could have something to do with it.

[MFX]

Separate issue…

 

We now have a way to set “vocal_tonic_note”, but there’s no setting for “sonic_tonality” (0 == major, 1 == minor, I think)

[Author]

Posts