Magma: C3 Roks Edition v3.3.2 [07/28/15]
- This topic has 697 replies, 6 voices, and was last updated 1 year, 9 months ago by
.
-
Posts
-
UPDATE!
Image below shows a project after importing the CON for Starlight, as released by the GHtoRB3 team. I’ve spent a lot of time testing this, but things always sneak through. Let me know of any issues you find.
v1.2
- Added option to import CON / LIVE file (single songs only, no packs) - this will create a project folder, extract and move the audio (.mogg), album art (.png_xbox) and midi to the folder, create the Magma project, convert the album art and load it in the project, load the midi in the project, process the songs.dta file and set all the project settings and metadata to match, and save the Magma project for you...all you have to do is process the audio. Magma will give you the choice to open the mogg in Audacity for you to process
- Added option to customize the Package Title Display (what you see on your Xbox dashboard) and the Package Description (only seen in Le Fluffie, read by Visualizer too) with preset formatting or your own custom text
- Added ability to customize Package Thumbnail (what you see on your Xbox dashboard)...it defaults to the same image as the album art, to change it, just click on the smaller image to select a different image to use
- Added option to send the final CON to Le Fluffie or to Visualizer from the Build form
- Added option to select the compiler executable from within Magma - ADVANCED USE ONLY = 99% of you don't need to change this, but it's there for the 1% who might
- Fixed several minor bugs...let me know of any others you findI have a problem when I try to compile a CON for a 2x pedal version of a song where it takes about half a minute longer than the single pedal version, and when I try to open it in the LeFluffie visualizer it shows no tiers or album art, just the song title which makes me think the actual CON must be corrupted for some reason. Is there any way to get past this?
That sounds like a bug… and its definitely not a “feature”. This is the first time I’ve heard this so I need a lot more information from you.
Are you using v1.2? Is the log saying anything to suggest something goes wrong during compilation? Are you marking 2x using the icon? Have you tried extracting the con in lefluffie to see what’s inside?
That sounds like a bug… and its definitely not a “feature”. This is the first time I’ve heard this so I need a lot more information from you.Are you using v1.2? Is the log saying anything to suggest something goes wrong during compilation? Are you marking 2x using the icon? Have you tried extracting the con in lefluffie to see what’s inside?
I use V1.2, no error messages in the compile, I used the 2x icon to mark it, and I looked into it on LeFluffie and it does contain the MIDI and MOGG. To me it seems like it might be a glitch related to the version number feature, as my MIDI is named “songnameV2doublepedal” (I marked it as such as V1 was my “build” project while V2 was the one ready for playtest) and whenever I load the project it resets the version number to 2 even if I change it to be 1. Going to try and rename my MIDI and avoid the number 2 in any of the info and see if that works, hold on
EDIT: Nope, still broken in vizualiser even with a renamed MIDI and info.
no clue what’s going on. only way i’ll be able to find out is if you post the project. you can send it to me privately if you’d rather keep it a secret for now. just include blank audio files so the project is as small as possible. i don’t need to hear it, just need all the files necessary for magma to compile.
I would like to report that when I compile a 2x Bass Pedal version of a song it does compile, but it shows up corrupt in-game. Album artwork also fails to load in LeFluffie. Any advice for this?
Did ya read the two posts before you posted? Same applies to ya. I’ll do tests on my own but need more details.
just had a thought…both of you guys, please upload your options.c3 file. it’s in the same directory as Magma.
i’m fairly certain it’s not a Magma project issue, but something in the compilation based on your settings, which are probably different than my own settings, and that’s why I can’t replicate the problem on my end with your projects.
Here’s an update that will hopefully fix most of the issues mentioned. Download v1.2.1 from the OP.
v1.2.1
- added option to change song tonality - this is mainly for expert users who want to beta test this function. DO NOT USE IF YOU DON'T KNOW WHAT IT DOES. DON'T ASK.
- fixed bug where Magma would add pro guitar/pro bass entries on the songs.dta even after unchecking them in the project
- fixed bug where Magma would add vocal tonic note value of 0 (C) instead of not adding it when it was unchecked
- added catch for filenames longer than 26 characters...there is a combined filename + extension limit of 40 characters inside the CON, so to fit songname_keep.png_xbox, "songname" can't be more than 26 characters...Magma will shorten to 26 characters and let you know
- added fix for filenames with characters that would / might mess up inside the CON, Magma will now remove things like #$%^*', and others from the filename
It’s pretty late so hopefully I didn’t make things worse. I would appreciate feedback on whether things are working better now for you…
very small update. this should really have been part of the last update but I guess it skipped me with how tired I was. I strongly recommend staying up to date.
v1.2.2
- further bug fixes, no new features added
Here’s one that I get
MIDI Compiler: Loaded autogen theme 'ArenaRock.rbtheme'...
MIDI Compiler: Skipping drums autogen...
MIDI Compiler: Autogenerating PART KEYS animations...
MIDI Compiler: Skipping vocals autogen...
MIDI Compiler: Skipping 'PART GUITAR' autogen...
MIDI Compiler: Skipping 'PART BASS' autogen...
MIDI Compiler: Skipping lighting autogen...
MIDI Compiler: Autogenerating camera cues...
MIDI Compiler: Validating...
MIDI Validation failed: (velocity <= 127)
e:prjrbnsystemsrcrbnvalidatorMidiValidator.cpp, line 221
MIDI: The previous failure caused the following failure:
MIDI Validation failed: (ValidateMidiChannelEvent(eventType))
e:prjrbnsystemsrcrbnvalidatorMidiValidator.cpp, line 408
ERROR: MIDI Compiler: Validation failed; corrupted file.What do you think this is?
Pretty straightforward error being thrown by MagmaCompiler…note velocity must be 127 or less. Default is 96.
Well I’m a little ocd but I always load every chart, ctrl+a to select all, right click on a note and set the velocity to 96. Repeat for all charts.
Don’t do this for probass or proguitar charts.
Well I’m a little ocd but I always load every chart, ctrl+a to select all, right click on a note and set the velocity to 96. Repeat for all charts.Don’t do this for probass or proguitar charts.
True that!
I rebuild after every track and it was in the beat track. It must have happen when I made the extra beats between 1.1 and 3.1
And thanks for the quick response!
- You must be logged in to reply to this topic.