Magma: C3 Roks Edition v3.3.2 [07/28/15]
- This topic has 697 replies, 6 voices, and was last updated 1 year, 8 months ago by
.
-
Posts
-
Do I place a [play] and [idle] text event before and after each phrase marker?
Not usually. I only do it if the gap is more than 5 seconds or so.
Ok, so then you place the “play” text event right before the first phrase and then the “idle” event at the end of the last phrase of the song(assuming their arent huge gaps between phrases). I thought I tried this but Magma still skipped the process of auto generating the vocals.
You’re confusing things here. When Magma autogenerates animation markers, in this case the play and idle events, that only tells the game when to animate the singer’s mouth. How to animate the mouth is determined by the dry vox file. And that is not, and never has been, auto generated. You need to give Magma a valid dry vox file.
Ok, I see. I didnt know what the purpose of the dry vox track was until now. I was always muting it and not exporting the midi with that track.
Ok, I see. I didnt know what the purpose of the dry vox track was until now. I was always muting it and not exporting the midi with that track.Dryvox is not MIDI, ideally for Dryvox you should record yourself singing the song and then render it as a 16khz 16 bit Mono WAV, if done right the singer should then lipsync along fairly accurately
Here we go, another update.
Going forward, Magma: C3 is provided in a stand-alone package. You don’t need to overwrite anything, or combine with anything. Just extract the WinRAR archive or install using the installer and use.
v2.2
- Added ability to change album art dimensions (under Options -> ADVANCED SETTINGS)
- Code changes to improve opening directly into MIDI Tester
- Enabled Test and Clean buttons for use when a MIDI file is selected even if the rest of the project isn't ready
- Change to allow MIDI Tester to display ALL output from MagmaCompiler
- Made Magma logo clickable link to the Magma: C3 Roks Edition thread in our forums
- Fixed bug where a preview start time longer than 10 minutes would not save after closing the project
- Changed behavior to use stereo blank files by default instead of mono to avoid some of the audio corruption bugs reported
- Considerable streamlining of several portions of the code
poorly made skins may no longer work correctly - if that happens, make sure you're following the instructions in the template
your old settings will be reset - just make sure to put your settings back after installation and they will be maintained fine after that
- Fixed album art bug that would overwrite png_xbox in project folder with new one based on project bmp file
- Considerably expanded the toast notifications to cover all the new additions and settings that did not yet have them
- Various other bug fixes and improvements throughout
As always, I strongly suggest updating to the latest version.
Hey guys, running into a problem and was hoping you could help me out.
I was making a con file out of some mids Grinnz had made, specifically the full Colors album by BtBaM. Importing the mid file into magma gives an error saying the midi file was too big (1335989 bytes), and that the size has been compressed (1009865 bytes) and that it should compile fine.
However compiling gives the error that the midi is larger than 1mb, which appears to be due to autogeneration of keys/vocal/guitar/etc animations. Anything I can do about that or should I just make it into individual songs?
I just clicked on the link and the only thing that showed up on keepitfishy is a banner and the word “DL”. No file had come.
Did the rule checker break by any chance? I managed to compile a song with a lot of lyrics that didn’t sync with the notes, which usually makes Magma freak out with errors but neither the compiling nor MIDI tester gave me anything on it
There’s been no changes to MagmaCompiler since like August or something. So whatever isn’t working now wasn’t working since then.
Hey everyone, brand new to this whole custom thing and loving it so far. I’ve got a question though. Today I spent a couple hours creating a chart (only for Expert guitar for now) to test out Reaper and Magma. I created the audio track, midi, etc., fixing a few basic errors that I had made as I tried to build the song, but I just got this one error that I can’t seem to fix. Here’s the log:
Magma: C3 Roks Edition v2.2.0=============================
Build started at 3:24 AM.
Starting Nemo’s MIDI Validator…
Everything looks good, continuing…
Loading MagmaCompilerC3 executable…
Reading the archive
SystemInit Params: C:Program Files (x86)Magma C3 Roks EditionMagmaCompilerC3.exe -have_lock C:RockbandGuitar vs PianoGuitarvs.Piano.rbproj C:RockbandGuitar vs PianoGuitarvs.Piano.rba -mutex HMX_Magma_23523418317421311216160
Project Compiler: Reading project ‘C:RockbandGuitar vs PianoGuitarvs.Piano.rbproj’…
Project Compiler: Entering Phase 1 of 5…
Metadata Compiler: Starting…
Metadata Compiler: Done.
Project Compiler: Entering Phase 2 of 5…
MIDI Compiler: Starting…
ERROR: MIDI Compiler: (MIDI FILE): Could not find MIDI track authored for guitar, possibly due to incorrect track name event
MIDI Compiler: Done.
ERROR: Project Compiler: Midi compiler failed.
RBA Build ended at 3:24 AM.
It looks like there was an error creating the RBA file.
Stopping here…
Problem is, I DO have a text event PART GUITAR at 1.1:00 in the guitar track. Originally it was at measure 2, so I fixed that, but Magma just keeps spitting that error out at me and I’m not sure what I can do at this point. Any ideas as to what I might have done wrong? Like I said, it’s my first midi so I wouldn’t be surprised if there was something else I screwed up as well.
Problem is, I DO have a text event PART GUITAR at 1.1:00 in the guitar track.
I can’t be a text event, it needs to be a trackname event.
Originally it was at measure 2
Which means you didn’t use the C3 template, which means literally anything can happen.
” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif”> Use our template to avoid this kind of issues. 
” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif”>I did use the C3 template, I think things just got moved around a bit/deleted when I was first playing with Reaper (Guitar track started at 2.1.000 when I went and checked for the error).
I changed the event type to track name but I keep getting the error for some reason.
- You must be logged in to reply to this topic.