How To: Convert Phase Shift to Console

A collection of helpful posts
This topic is 3 months and 4 weeks old. Instead of replying, please begin a new topic, or search for another related topic that may be more suitable.
User avatar
InevitablEnd
Member
Posts: 112
Joined: December 9th, 2016
Reputation: 55

How To: Convert Phase Shift to Console

Postby InevitablEnd » Sun Aug 05, 2018 10:49 pm


Required:
Semi-required:
Optional but recommended:
Converting from Phase Shift to Rock Band 3 for Xbox360, PS3, and Wii
  1. Get Phase Shift audio and chart
  2. Using C3CONTools, use MIDI Cleaner on .mid file
  3. Open Magma and place .mid file into it
  4. Using song.ini, fill in song data and difficulties
  5. Place audio file(s) into designated places
    • If there is only 1 audio track, place in Backing
    • To generate lip-syncing, place audio into Vocals:
      • Right-click Dry Vocals and "Convert vocals stem to dryvox"
      • If there are Harmonies, right-click and select "Copy lead dry vocals here"
      • Change Vocals track back to silence if there is no separate Vocals stem
  6. Adjust preview timer so recognizable part of song is played when hovering
  7. Press Build Song to convert to rb3con (X360)
  8. (optional) Use C3CONTools to convert to other consoles (Wii/PS3).

Most Magma errors are pretty straightforward or Google-able
COMMON ERRORS:
  1. Silent audio gives file not found error.
    • Sometimes occurs when you don't have a full multitrack and use silent audio
        Right click audio track and select appropriate silent audio
  2. Invalid Events Track
      Commonly [preview] or [section_intro] tags used by Phase Shift, but not Rock Band
      • Open .mid in Reaper and remove them from the EVENTS track
      • Export MIDI and try again.
  3. Drum tracks cause errors
    • Sometimes occurs with multiple drum tracks.
      • If 3 Drums track, select Kit, Kick, and Snare on drop down. Most drum tracks are drums3=Kit, drums2=Snare, drums1=Kick
      • If 2 Drums tracks, usually drums2=Kit and drums1=Kick
    • Create new project and re-enter all information
    • OR Merge drum tracks into 1 audio file using Audacity/Reaper
  4. Audio not synced with chart-
    • Phase Shift has a delay tag in the song.ini that some people use.
      • Recommended: Import into Reaper to adjust timing and Render
      • OR Add the appropriate amount of delay to the beginning of the audio track(s)
    • Rock Band prefers audio and charts to start at 3.1.00 in Reaper
      • Songs that start sooner may cause errors.
      • Import into Reaper to adjust audio and/or chart and re-export/render.
Last edited by InevitablEnd on Fri Aug 17, 2018 6:25 pm, edited 3 times in total.
User avatar
InevitablEnd
Member
Posts: 112
Joined: December 9th, 2016
Reputation: 55

Re: How To: Convert Phase Shift to Console

Postby InevitablEnd » Sun Aug 05, 2018 10:50 pm

Changelog:
  • 2018-08-06: Added links and formatting.
  • 2018-08-05: Initial Post with text and video.
Last edited by InevitablEnd on Mon Aug 06, 2018 10:04 pm, edited 1 time in total.
pprincessjasmin
Member
Posts: 19
Joined: January 13th, 2018
Reputation: 3

Re: How To: Convert Phase Shift to Console

Postby pprincessjasmin » Fri Aug 17, 2018 1:09 pm

Thanks for the tutorial! I am trying to convert Joe Bonamassa - Lonesome Road Blues from Bluzer's GH release and having the following errors when compiling, how can I solve these guitar chord errors? Thanks again!

MIDI Compiler: Starting...
ERROR: MIDI Compiler: (PART GUITAR): Chord gems do not start simultaneously at [18:4:240]
Rock Band 3 does not support broken chords like Guitar Hero. You either have chords with notes starting at different times, or one note that runs too long and over the next note. Zoom in real close in REAPER and you'll see it.
ERROR: MIDI Compiler: (PART GUITAR): Chord gems do not start simultaneously at [19:1:000]
Rock Band 3 does not support broken chords like Guitar Hero. You either have chords with notes starting at different times, or one note that runs too long and over the next note. Zoom in real close in REAPER and you'll see it.
ERROR: MIDI Compiler: (PART GUITAR): Chord gems do not start simultaneously at [23:4:359]
Rock Band 3 does not support broken chords like Guitar Hero. You either have chords with notes starting at different times, or one note that runs too long and over the next note. Zoom in real close in REAPER and you'll see it.
ERROR: MIDI Compiler: (PART GUITAR): Chord gems do not start simultaneously at [23:4:240]
Rock Band 3 does not support broken chords like Guitar Hero. You either have chords with notes starting at different times, or one note that runs too long and over the next note. Zoom in real close in REAPER and you'll see it.
ERROR: MIDI Compiler: (PART GUITAR): Chord gems do not start simultaneously at [34:4:360]
Rock Band 3 does not support broken chords like Guitar Hero. You either have chords with notes starting at different times, or one note that runs too long and over the next note. Zoom in real close in REAPER and you'll see it.
ERROR: MIDI Compiler: (PART GUITAR): Chord gems do not start simultaneously at [35:1:000]
Rock Band 3 does not support broken chords like Guitar Hero. You either have chords with notes starting at different times, or one note that runs too long and over the next note. Zoom in real close in REAPER and you'll see it.
ERROR: MIDI Compiler: (PART GUITAR): Chord gems do not start simultaneously at [39:4:241]
Rock Band 3 does not support broken chords like Guitar Hero. You either have chords with notes starting at different times, or one note that runs too long and over the next note. Zoom in real close in REAPER and you'll see it.
ERROR: MIDI Compiler: (PART GUITAR): Chord gems do not start simultaneously at [40:1:000]
Rock Band 3 does not support broken chords like Guitar Hero. You either have chords with notes starting at different times, or one note that runs too long and over the next note. Zoom in real close in REAPER and you'll see it.
ERROR: MIDI Compiler: (PART GUITAR): Chord gems do not start simultaneously at [64:4:241]
Rock Band 3 does not support broken chords like Guitar Hero. You either have chords with notes starting at different times, or one note that runs too long and over the next note. Zoom in real close in REAPER and you'll see it.
ERROR: MIDI Compiler: (PART GUITAR): Chord gems do not start simultaneously at [64:4:300]
Rock Band 3 does not support broken chords like Guitar Hero. You either have chords with notes starting at different times, or one note that runs too long and over the next note. Zoom in real close in REAPER and you'll see it.
ERROR: MIDI Compiler: (PART GUITAR): Chord gems do not start simultaneously at [67:1:240]
Rock Band 3 does not support broken chords like Guitar Hero. You either have chords with notes starting at different times, or one note that runs too long and over the next note. Zoom in real close in REAPER and you'll see it.
ERROR: MIDI Compiler: (PART GUITAR): Chord gems do not start simultaneously at [68:1:000]
Rock Band 3 does not support broken chords like Guitar Hero. You either have chords with notes starting at different times, or one note that runs too long and over the next note. Zoom in real close in REAPER and you'll see it.
ERROR: MIDI Compiler: (PART GUITAR): Chord gems do not start simultaneously at [67:1:000]
Rock Band 3 does not support broken chords like Guitar Hero. You either have chords with notes starting at different times, or one note that runs too long and over the next note. Zoom in real close in REAPER and you'll see it.
ERROR: MIDI Compiler: (PART GUITAR): Chord gems do not start simultaneously at [71:4:240]
Rock Band 3 does not support broken chords like Guitar Hero. You either have chords with notes starting at different times, or one note that runs too long and over the next note. Zoom in real close in REAPER and you'll see it.
ERROR: MIDI Compiler: (PART GUITAR): Chord gems do not start simultaneously at [71:4:360]
Rock Band 3 does not support broken chords like Guitar Hero. You either have chords with notes starting at different times, or one note that runs too long and over the next note. Zoom in real close in REAPER and you'll see it.
ERROR: MIDI Compiler: (MIDI FILE): Unison phrases don't quite coincide at [75:1:000] in tracks PART DRUMS and PART BASS
ERROR: MIDI Compiler: (EVENTS): prc_blues_riff_1 event at [43:1:000] is not allowed
ERROR: MIDI Compiler: (EVENTS): prc_solo_1 event at [51:1:000] is not allowed
ERROR: MIDI Compiler: (EVENTS): prc_coda event at [76:1:000] is not allowed
ERROR: MIDI Compiler: (EVENTS): prc_blues_riff_2 event at [80:1:000] is not allowed
ERROR: MIDI Compiler: (EVENTS): prc_solo_2 event at [87:4:479] is not allowed
ERROR: MIDI Compiler: (EVENTS): No music_start event
ERROR: MIDI Compiler: (EVENTS): No music_end event
ERROR: MIDI Compiler: (EVENTS): No end event
MIDI Compiler: Done.
User avatar
InevitablEnd
Member
Posts: 112
Joined: December 9th, 2016
Reputation: 55

Re: How To: Convert Phase Shift to Console

Postby InevitablEnd » Fri Aug 17, 2018 6:23 pm

As it says, Rock Band does not support playing more notes in the middle of playing other notes like Guitar Hero does, so in your case, the midi note chords in the Guitar track are not beginning/ending at the same location. The easiest way to fix them is to open it in Reaper/EoF, remove the offending notes and redraw them so you know for sure they are starting/ending at the right places. Even if the notes look like they are separate, there can be extremely tiny note overlap that you can't always see in Reaper/EoF, but Magma can detect. Other than that, the Unison phrase error means the Drums and Bass have semi-overlapping Overdrive sections, which you can't have. Either they need to be separate (one after another) or be exactly together. The 'not allowed' events also need to be removed and the [music_start], [music_end], and [end] text events need to be added to the appropriate places too.

Return to “Tutorials and Tools”

Who is online

Users browsing this forum: No registered users and 0 guests