Magma Roks Edition
- This topic is empty.
-
Posts
-
I have unpacked and run Magma to test my setup and when running TEST Midi on the Game data tab, I get :
“Ready to begin….The following files are required for this process and was not found:
RockBandMAGMAUnpackaudioblank_backing44.wavPlease redownload this program and do not delete any files.”
I have not deleted any files, so why is this file missing …?
Thanks in advance
Oops. I didn’t include that file in the last release. Get it from the v2.2 pack and copy it into the audio tab for now. I’ll include it in the next release.
Also, these kinds of questions are much better suited to be asked in the release thread, no need for individual threads cluttering the forums.
OK – Thanks. In the interests of not creating another thread…
Magma now reports when I run TEST a single error …
” Multiple tracks share the name PART REAL_GUITAR”
I check and only one track has the name PART REAL_GUITAR…?
The REAL BASS track is using the PART REAL_GUITAR track name. The RB3 Template from here has that issue. Just change it to PART REAL_BASS, mute the real tracks so they do not export, or just delete them if you have no intention of charting out real parts (which I’m assuming most people do not).
The REAL BASS track is using the PART REAL_GUITAR track name. The RB3 Template from here has that issue.Not anymore. Fixed.
Also of note: They’ve always been muted in the template. Beware of unmuting all tracks before doing an export.
1) So do I take it that when I create the Audio file for the MAGMA project, I MUTE all but the tracks that I want to export ..? So, if I want to test solely the DRUMS on my console which is all that I have authored at this stage – I simply mute all EXCEPTING the AUDIO track and DRUMS?
2)What are the REAL_BASS / REAL_GUITAR distinction in the template from GUITAR and BASS in any case..?
Thanks
1) So do I take it that when I create the Audio file for the MAGMA project, I MUTE all but the tracks that I want to export ..? So, if I want to test solely the DRUMS on my console which is all that I have authored at this stage – I simply mute all EXCEPTING the AUDIO track and DRUMS?Audio and MIDI are different things. You render the audio with its count in and then export the MIDI with all the unneeded tracks muted.
1) So do I take it that when I create the Audio file for the MAGMA project, I MUTE all but the tracks that I want to export ..? So, if I want to test solely the DRUMS on my console which is all that I have authored at this stage – I simply mute all EXCEPTING the AUDIO track and DRUMS?2)What are the REAL_BASS / REAL_GUITAR distinction in the template from GUITAR and BASS in any case..?
You also have to have an EVENTS track and a BEAT track.
PART REAL_BASS and PART REAL_GUITAR are used for pro bass and guitar.
Audio:
– First things you need are your tempo map finished, your audio file(s) placed/lined up correctly, and your count-in created (easiest to use the count-in track)
– “Solo” your audio track and the count-in track
– hit ctrl+alt+r (which will bring up the render box).
– Make sure the Sample Rate is 44100, and the WAV bit depth is either 16 bit or 24 bit PCM
– Render (which will create your new audio file)
– This is the file you use in Magma for the backing track (you can also import this to REAPER and use it in place of your SONG TRACK / COUNT-IN tracks.
MIDI: [when you are ready to test your file in-game]
Every files needs at least an instrument to test, EVENTS, VENUE (can be unfinished), and BEAT. There are two main ways to do this:
1)
– Mute each track that you do NOT wish to export into the game (ie, all unfinished or unused charts)
– File -> Export Project MIDI…
– Make sure Consolidate MIDI items = All, Multitrack MIDI File is selected, and Embed Tempo Map is checked
2)
– Hold down ctrl and manually select the tracks that you wish to export
– File -> Export Project MIDI…
– Make sure Consolidate MIDI items = Selected Tracks Only, Multitrack MIDI File is selected, and Embed Tempo Map is checked
These options will create the .mid that will be used in the Magma tester.
Seems I lave cocked up bigtime… the song is 67 BPM – although when I started the project tapping the BPM button as instructed it came back with 34 BPM (evidently I was not in time). Despite this I tempo mapped and although the initial marker at the start of the song is 34 all subsequent markers denote nominally a beat of 67 BPM.
I have done the DRUM track in accordance with this…
Now when I compile – MAGMA tells me the speed of 34 is too slow and must be a minimum of 40 BPM. So if I change the initial marker from 34 to 67 – this of course changes the tempo map and all note underlying this are moved out-of-sync.
Is this recoverable or do I have to start all over again.?..gulp…
Change it to double and pull back all notes, if it’s the first marker only. However, never trust a doubling of the BPM unless the song really sounds like going that faster.
Have redone all the drum sequence… well one things for sure I am picking up the speed… Herewith Compiler log…
Loaded MIDI file mvon3.mid successfully.
Found PART DRUMS…
Nemo’s MIDI AutoGen process started at 08/10/2014 22:38:28
Added drum mix events successfully.
Nemo’s MIDI AutoGen process completed at 08/10/2014 22:38:28
Starting Basic EMH Check
WARNING: PART DRUMS Hard only has 5 notes but Expert has 854 notes
WARNING: PART DRUMS Medium has the same amount or more notes than Hard
WARNING: PART DRUMS Easy has the same amount or more notes than Medium
There were only 3 problems reported
This means the charts most likely have reductions charted except where reported in the log
Ready to send files to MagmaCompiler … hold on.
Output from MagmaCompiler follows:
Reading the archive
SystemInit Params:
RockBandMAGMAUnpackMagmaCompilerC3.exe -have_lock -export_midi RockBandMAGMAUnpacktesttest.rbproj RockBandMAGMAUnpacktesttest_compiled.midMIDI Compiler: Starting…
ERROR: MIDI Compiler: (PART DRUMS): Cannot parse event 0x00 at [13]
MIDI Compiler: Done.
Any ideas what the problem is here… I cant see anything untoward at 13.3.000
Farottone – thanks.
I did run CAT and it didnt remove invalid markers?… I went through the DRUM track and sure enough I had overlooked some markers I had placed (for my own quick reference so I could see quickly whereabouts in the sequence I was …!)
Took them out manually… and:
“Seems this MIDI is in excellent condition. No errors reported by MagmaCompiler.”
Still not there… I build and get…
ERROR: Metadata Compiler: [D] sub_genre: ‘subgenre_alternative’ is not a valid value.
- You must be logged in to reply to this topic.