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
-
I don’t think it matters — use the lowest possible with a short 1-2s track to keep file sizes down and you should be golden.
” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif”>haven’t forgotten you guys…instead of just pushing out that little fix I’ve been working on adding some new features…one of which i’m rather proud of and will be very helpful to those of you who take existing customs and improve them….where was this tool when I was doing that a year ago?!?!
one [new feature] … i’m rather proud of and will be very helpful to those of you who take existing customs and improve them I want to guess and say MIDI extraction or Venue patching, but most likely I’m wrong.
C’mon, man, what is it?
or Venue patchingI’ve said it before, so let me clear that out right now. I have no interested in doing the charting for people. So nope, sorry, not that. And never will be. Neither Magma nor Le Fluffie will ever chart for you…but I keep trying to make everything else easier
” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif” />Since I am about 95% of the way there, I figure I’d show you what I’ve been working on. For me, at least, this feature would have been a godsend a year ago. I’m not longer doing this, but I know some of you are, so I hope those of you I’m thinking of will find it as useful as I hope you will. After all, I’m doing this for you!
I can see my self using that alot. I downloaded alot of songs/upgrades, some the only way to get to work is to rebuild the whole thing. Can you imagine if you could export to a *.RPP file?
Many, many thanks to you!
Hey Trojan what would that best be used for? Something like when I updated some songs with 2X Bass Pedal? It seems like it does everything LeFluffie can do but just does it way quicker. Is that correct?
There are two ways to update an existing custom. You can extract the midi in LeFluffie, make changes to it and replace the midi back in LeFluffie. This method keeps everything as originally done, including the bad parts if there are any and you dont have Magma to verify the quality of the work.
The other way, which is how I’ve always done it and recommend others do, is to extract the whole thing, set up the magma project all over again and recompile once you make adjustments to the midi. This forces the new and “improved” midi to pass quality control in Magma. This was also a tedious multi step process until now.
The import function will extract the files, convert the album art, set all the Magma settings to match the songs.dta file of the existing song, save the Magma project for you. If you have Audacity installed then it allows you to click to open Audacity and send the mogg to it. So your job now consists only of setting up the audio files and not all other steps you had to do before.
I think the answer to that should be obvious: nope.
But you can extract the files yourself and then import the songs.dta in Magma and still save a lot of time.
this is indeed a godsend. You and the rest of the team that made this possible have my upmost gratitude.
as far as I can see, it works with Cons. what about official content?
when extracting MIDI, when opened in Reaper, do the notes snap to their starting points? or are they slightly off? or is that just me? nothing that can’t be fixed with quantizing, but I’d like to know.
what about the dry vox files?
probably not your field, but is there a loss of quality by reformatting audio from “Original” to WAV to mogg, back to WAV and back to mogg?
There are a few issues with what you’re asking.
The image shows the import option will work with both CON and LIVE files so yes it imports official content.
However, nothing this or LeFluffie do when extracting the midi affects the midi behavior in REAPER. Notes being slightly off when importing is a bug in REAPER. I reverted to an older version because of that.
Dry vox files are stored in the milo file and that can’t be modified unfortunately.
If you’re importing official songs the mogg will be encrypted and Audacity won’t be able to open it.
But yes everytime you go from wav (uncompressed) to mogg (compressed) there is quality loss, so you always want to render from the original wavs. If you’re just enhancing the midi but not adding new tracks, you can compile in Magma and then replace the new mogg with the old one. If you’re adding new charts you can’t use the old mogg anymore so you have no choice but to recompile the audio.
This is by no means a solve-all solution but should simplify things considerably.
oh yes yes, I understand that. and it’s beautiful.
a bit off topic:
what Reaper version do you use/recommend? the bug in the latest version is tedious to the work with when transferring RPPs to other users.
so suppose, with the Magma update, I tweak the original instrument chart for say… Mighty Morphin Power Rangers. To prevent quality loss, could I make a “dummy” CON, and replace the “original” MIDI with the improved MIDI from the dummy (using leFluffie to dissect and yadayadayada.) if not, what would be the “correct” way to do so?
Well there’s a few things to consider.
First, if you’re making minor adjustments to the MIDI in an otherwise top notch custom, then yes I would replace the old midi and be done with it.
More often than not you’re working with customs from the rbn1.0 era or poorly created customs from when we didn’t know better or had the tools we have now. In that case I would redo the whole thing in Magma and just replace the mogg in the new con with the old con. This way you have all the new and great features without audio quality loss. This also works with official content that has encrypted moggs. This works as long as your new con has the same number of channels and you don’t move the audio in REAPER. I tested this way back in the day the manual and tedious way when I rebuilt and recompiled Caprici di Diablo and then put back the encrypted official mogg. Bam it works in game and no crashing anymore.
One thing to consider though is most older “subpar” customs that need fixing most likely will have a single mp3 backing track, often times way too loud that the audio clips and/or with the same backing track assigned to all instruments instead of using mute tracks. In that case there is no benefit to keeping the old mogg and instead you’re probably better off getting a clean flac or wav and use that with your project.
As far as my version of REAPER it’s something from January of 2012 so it’s ridiculously old. They may have fixed it for all I know but I see no need to update my copy.
- You must be logged in to reply to this topic.