Questions about OGGs, playtesting, and beatmapping
- This topic is empty.
-
Posts
-
Hey! I’m new here
” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” /> I’m not new to making customs though – I’ve been doing that since Guitar Hero 3. I’ve been doing Rock Band authoring for a couple weeks now, and holy fresh fuck this is a lot more complex than any GH stuff I’ve ever done… but it’s a lot of fun, and I think I’ve got the whole process down and I’ve cut down on a majority of the errors magma throws at me hahaha. Just a few questions though:1. In Magma, is there a way to skip re-converting your WAVs to OGGs every time you compile? Like maybe it would just take the MOGG from your con file, or it will let you import OGGs instead of WAVs? That would save us all a lot of time between editing and testing especially when making a lot of small changes.
2. I only have an Xbox 360 guitar and a microphone (and a PS2 drumset). Is there a way I can see what each part looks like ingame without actually owning the controller, or am I stuck with using the RBN preview or Phase Shift, or having other people that have the controllers playtest each part for me?
3. I’m just going to assume most of you are used to tempo mapping with Reaper. I’ve been using Editor on Fire instead to tempo map and then import the extracted MIDI into reaper. I find that method to be much simpler because you literally just drag the beats on the actual waveform, and the bpm automatically adjusts. You can also “anchor” beats so that if you need to make a change, that beat will stay in place and you won’t have to manually “fix” that beat to shift the tempo map back into place. Anyone else experienced with EOF and have an opinion on tempo mapping in EOF vs. Reaper? Or do you guys have any tips on tempo mapping in Reaper, because it doesn’t seem as intuitive to me as EOF does. I wouldn’t be surprised if there are some handy features in Reaper I’ve missed though.
This is a pretty sweet looking community, by the way. I’m not used to posting on forums much but I’m a big GH/RB enthusiast and it’s cool to see a bunch of people that share the same interest. I’ll be here often. Rock on and stuff. Oh yeaaah
1. In Magma, is there a way to skip re-converting your WAVs to OGGs every time you compile? Like maybe it would just take the MOGG from your con file, or it will let you import OGGs instead of WAVs? That would save us all a lot of time between editing and testing especially when making a lot of small changes.
I’ll let Nemo answer on the specifics but Magma doesn’t rebuild your audio unless you’ve changed it.
2. I only have an Xbox 360 guitar and a microphone (and a PS2 drumset). Is there a way I can see what each part looks like ingame without actually owning the controller, or am I stuck with using the RBN preview or Phase Shift, or having other people that have the controllers playtest each part for me?
You can check keys, guitar and bass with your guitar controller, you only miss drums, for which you need the controller, yes.
3. Or do you guys have any tips on tempo mapping in Reaper, because it doesn’t seem as intuitive to me as EOF does. I wouldn’t be surprised if there are some handy features in Reaper I’ve missed though.
Drag the cursor to the peak of the waveform on the beginning of the measure, hit Q, tempo mapping done for one measure, repeat for all measures.
” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif”> Never used EOF to tempo map so I can’t offer comparisons.This is a pretty sweet looking community, by the way. I’m not used to posting on forums much but I’m a big GH/RB enthusiast and it’s cool to see a bunch of people that share the same interest. I’ll be here often. Rock on and stuff. Oh yeaaah
Welcome!
” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif”>1. In Magma, is there a way to skip re-converting your WAVs to OGGs every time you compile? Like maybe it would just take the MOGG from your con file, or it will let you import OGGs instead of WAVs? That would save us all a lot of time between editing and testing especially when making a lot of small changes.
I’ll let Nemo answer on the specifics but Magma doesn’t rebuild your audio unless you’ve changed it.
There is a lot of factors at play here. By default, Magma: C3 leaves the .rba file behind. The next time you try to build the song, MagmaCompiler should see what changed (typically just the charts) and reuse the rest of the .rba file so it’s quicker.
However, 1) I do not control MagmaCompiler and 2) we have hacked so many aspects of MagmaCompiler that some things may be broken – that is not one I concerned myself with much and at this point there is no fixing it if indeed it was broken in the process.
If your concern is, as I know some people are concerned, that you have one good audio build and then you’re making edits to the chart and somehow the audio is corrupted in the process, you can extract the .mogg from the good CON file and leave it in the same folder that the .rbproj file is in, go to Options -> ADVANCED SETTINGS -> Override audio file (*.mogg) and make sure that is enabled. Magma will still spend the time in creating the PCM file and converting it to .mogg, but in the CON you’ll end up with the good .mogg – obviously do this with care as you might change the audio files and Magma will continue to override with the old audio as it was instructed.
If you know everything else is good and all you need to do is test a MIDI change, then you can just take your compiled CON, open it in C3 CON Tools, and replace the MIDI with your updated MIDI. No need to go through Magma unless you need to confirm you’re not breaking any rules, and you can test that by sending it to MIDI Tester or by starting to build and canceling when it gets to the Audio Compiler section.
All of the above can be used to save your time and/or get past some limitations – but it can lead to headaches if you don’t know what you’re doing or you forget you have done any of it, so do it at your own risk.
- You must be logged in to reply to this topic.