[DoNotPassGo]

Yeah, those docs are extremely helpful, and I absolutely agree that if you one is serious in their intentions to start authoring, they should give them a read. Bottom line.

 

However, I also know that they can be a lot of information at once, and a big part of learning things is by doing. I read the docs over a lot, and I still had trouble with my first compiles. I was asking a lot of questions on here then, and the community really did help pinpoint errors I did not understand yet. After I was helped in doing, the docs started making a lot more sense, and I could follow them much better.

 

I enjoy giving help, and I was honestly planning soon on possibly making a Magma help video showing the steps of a “finished” REAPER chart through Magma. I’m holding off as I feel either PK or another Admin might have that idea already (as we got a C3Tools one recently).

 

 

Also, yeah, I do agree that trying to give out complete and perfect steps is almost impossible with some of the topics covered here… I just know that when I was starting out, having a laid out starting point like that could have been a large help in the initial “I can’t get this stupid thing to work… iSad” moments ha

[TrojanNemo]

I’m not going to answer everything mentioned in this thread, because it reads like this: “I haven’t tried anything and I’m all out of ideas. Please help.” As you’ve been told, you need to understand what you’re doing before you try to do it. Read the docs, watch the existing tutorial videos, read the threads. Then you can ask questions and expect helpful answers.

 

“Cannot find file: C:Program Files (x86)Customs Creators CollectiveMagma C3 Roks Editiontesttest.rbproj

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

 

Either copy/paste the entire Magma folder to your desktop or somewhere that doesn’t require special permissions, or run Magma as an Administrator. That’s probably what’s causing that issue. Next update (if there is one) is going to do away with that installer crap. I was trying to be helpful and instead got into all these permission issues.

 

I was honestly planning soon on possibly making a Magma help video showing the steps of a “finished” REAPER chart through Magma. I’m holding off as I feel either PK or another Admin might have that idea already (as we got a C3Tools one recently).

 

Correct. Just wait a little bit longer ” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif” />

 

After you test and make sure your midi runs up to compile standards, it’s best to export it. When Magma is running the midi test, it will make some changes to the midi. It auto generates missing venue options, missing animations, and other things. This is also where the game will take care of x1 and x2 Bass pedals if you use the documentation to allow that to happen. You are going to want to export the midi, so you have a copy of the new, updated, and more polished/finished midi. When you go to export:

 

1) If this is a new Magma project, you’ll be asked to save the .rbproj file. This is so you can open up Magma again with the information saved. This is a Magma type file.

 

You have the right idea but not quite the right understanding of how it works. The MIDI Tester in Magma is designed to assist you in determining whether any MIDI file you’re thinking of compiling, will indeed compile or require a lot of work, without you needing to set up an entire project file to find out.

If you are already working on creating the song, and you’ve already created a project file for it (always save it before trying to build), you can skip the Test portion and go straight into Build. Everything that you mentioned happens when you click Test, also happens when you click Export and when you click Build. Which is, Magma will separate the tracks into 1x and 2x if you followed instructions, as well as generate whatever needs to be generated. The same error message you’d get when hitting Test, is what you’ll get when hitting Build.

If you’re counting on Magma to auto-generate a venue that you want to modify, you can set up the project, click Export, open that MIDI in REAPER, copy/paste the VENUE track into your REAPER project and customize. If you’re not going to modify anything that is created by Magma, again, just skip to Build.

 

But none of that makes any sense unless you’ve read the authoring docs and have a basic understanding of what we’re talking about.

[Author]

Posts