Found some more NIN customs online, but unsure of the format
- This topic is empty.
-
AuthorPosts
-
September 14, 2013 at 4:37 pm #389201
This thread at ScoreHero has a bunch of EMHX multitrack customs for Nine Inch Nails that I haven’t seen anywhere before, but I have no idea what the format is: http://rockband.scorehero.com/forum/vie … hp?t=28931
The contents look like this:
Anyone know how to use a file like this, and whether or not it could be converted to a con for RB3?
September 14, 2013 at 8:13 pm #406206A FLAC is just a music file. I don’t know what that chart file is but I’m pretty sure none of this is set up for Rock Band.
September 14, 2013 at 9:08 pm #406213You could convert it if you wanted to, just load the audio in audacity & export it as a multitrack ogg file.
The “chart” file is actually a midi file, just rename it/add the extension. create a simple DTA…
example
(nin_survivalism_rb
(name "Survivalism")
(song_id nin_survivalism_rb)
(master TRUE)
(song
(name songs/survivalism_rb/survivalism_rb)
(tracks
((drum (0 1 ))
(bass (2))
(guitar (3 4))
(vocals (5))
)
)
;
(pans ( -1.0 1.0 0.0 -1.0 1.0 0.0 -1.0 1.0 ))
(vols ( -2.5 -2.5 -2.2 -4.5 -4.5 -1.5 -5.0 -5.0 ))
(cores ( -1 -1 -1 1 1 -1 -1 -1 ))
(drum_solo
(seqs (kick.cue snare.cue tom1.cue tom2.cue crash.cue))
)
(drum_freestyle
(seqs (kick.cue snare.cue hat.cue ride.cue crash.cue))
)
(midi_file songs/survivalism_rb/survivalism_rb.mid)
)
(bank sfx/tambourine_bank.milo)
(anim_tempo kTempoSlow)
(song_scroll_speed 2300)
(preview 45000 75000)
(rank (vocals 1))
(format 10)
(version 30)
)Package it up in CON format & test.
::EDiT:: btw, those packages he supplied are made for RAWKSD, so they contain additional RB info in the midi.
September 14, 2013 at 9:13 pm #406214damn. bluzer beat me to it. you can import the flac to audacity and export each stem. he included what audio channel is for what instrument, so you can have multi track audio in the file. the chart, rename to .mid and it’s good to go. it’s from RBN1.0, so it needs some adjusting to compile in Magma, but I would strongly suggest going the Magma way. Then you end up with proper animations, lipsync, etc. it should be minimal work.
September 15, 2013 at 2:46 am #406226If you do this, would you mind sharing links for them too?! Heck, I would even take the Dire Straits – Money for Nothing. I see a link for that song on the RockBandCustoms spreadsheet that is FullBand but I can’t tell if it’s all difficulties or not. I wonder if these NIN songs from that thread are FB and all difficulties too.
EDIT: Nevermind, I see TrojanNemo already has a conversion of that Dire Straits song out in his older customs thread that I would assume has all difficulties. Carry on with your NIN discussions!
September 16, 2013 at 5:23 pm #406304You could convert it if you wanted to, just load the audio in audacity & export it as a multitrack ogg file.The “chart” file is actually a midi file, just rename it/add the extension. create a simple DTA…
…
Package it up in CON format & test.
damn. bluzer beat me to it. you can import the flac to audacity and export each stem. he included what audio channel is for what instrument, so you can have multi track audio in the file. the chart, rename to .mid and it’s good to go. it’s from RBN1.0, so it needs some adjusting to compile in Magma, but I would strongly suggest going the Magma way. Then you end up with proper animations, lipsync, etc. it should be minimal work.Thank you for these tips! I just installed Magma and the C3 Roks add-ons. I’m looking at one of the audio files, “Discipline” in Audacity now.
There appear to be 2 tracks for drums, 1 for bass, 2 for guitar, 1 for vocals, and 2 for “everything else” (scattered keys in this song, a little bit of droning and backing vocals at the end). If an instrument has two tracks, would I downmix and save both as a single mono file? Then add that to Magma? And should the format be .WAV at 44100Hz?
I’m new at this so feel free to dumb it down. But I think I’m off to a good start! ” src=”/wp-content/uploads/invision_emoticons/default_SA_biggrin.gif” />
If you do this, would you mind sharing links for them too?!Definitely, whatever I get done I’ll be posting for the benefit of those who want it (or would like to improve upon it ” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif” />).
September 16, 2013 at 7:32 pm #406313There appear to be 2 tracks for drums, 1 for bass, 2 for guitar, 1 for vocals, and 2 for “everything else” (scattered keys in this song, a little bit of droning and backing vocals at the end). If an instrument has two tracks, would I downmix and save both as a single mono file? Then add that to Magma? And should the format be .WAV at 44100Hz?
If it’s two channels, then it’s a stereo file, so leave those two in audacity, click on the arrow next to the name for the top one, make left channel, bottom one make right channel, click on the arrow again, make stereo file, then export. leave the sample rate at whatever it came in and yes WAV. If it’s a mono stem, same thing, but leave it as mono. Point being try to mess as little as possible with the audio, just get it out as WAV files that Magma can take.
September 16, 2013 at 9:09 pm #406320There appear to be 2 tracks for drums, 1 for bass, 2 for guitar, 1 for vocals, and 2 for “everything else” (scattered keys in this song, a little bit of droning and backing vocals at the end). If an instrument has two tracks, would I downmix and save both as a single mono file? Then add that to Magma? And should the format be .WAV at 44100Hz?
If it’s two channels, then it’s a stereo file, so leave those two in audacity, click on the arrow next to the name for the top one, make left channel, bottom one make right channel, click on the arrow again, make stereo file, then export. leave the sample rate at whatever it came in and yes WAV. If it’s a mono stem, same thing, but leave it as mono. Point being try to mess as little as possible with the audio, just get it out as WAV files that Magma can take.
Got it! Can any part be added in stereo if the audio is available? Because I’ll go ahead and do the same process for Guitar and Backing if Magma can take that fine.
September 16, 2013 at 9:17 pm #406321Magma will take stereo files for all instruments, and will take mono files for all instruments except drum kit, that must be stereo. Files can be 44,100 Hz or 48,000 Hz, 16-bit or 24-bit (but they all must match).
Lipsync files must be 16,000 Hz 16-bit mono.
September 16, 2013 at 9:45 pm #406324Magma will take stereo files for all instruments, and will take mono files for all instruments except drum kit, that must be stereo. Files can be 44,100 Hz or 48,000 Hz, 16-bit or 24-bit (but they all must match).Lipsync files must be 16,000 Hz 16-bit mono.
These audio tracks appear to be 32-bit by default. Should I change the sample format on all of them to 24?
I did set the dry vocal track to 16-bit 16000 Hz, so I think I’m good to go on that front.
EDIT: whoops, actually that dry vocal isn’t cooperating. I resampled it to 16000 in Audacity, set sample format to 16-bit PCM, and exported that to a WAV… but when I open that new file in Audacity it shows up as 32-bit 44100 anyway >” src=”/wp-content/uploads/invision_emoticons/default_SA_frown.gif” />
September 17, 2013 at 3:43 am #406342hmmm… got all the pieces together and this is what I ended up with:
Project Compiler: Entering Phase 1 of 5...
Metadata Compiler: Starting...
Metadata Compiler: Done.
Project Compiler: Entering Phase 2 of 5...
MIDI Compiler: Starting...
ERROR: MIDI Compiler: (): Cannot parse meta event 0x7f at [1]
MIDI Compiler: Done.
ERROR: Project Compiler: Midi compiler failed.
RBA Build ended at 11:40 PM.
It looks like there was an error creating the RBA file.
Stopping here...Okay so now what??
September 17, 2013 at 4:46 am #406343That means there is some stuff in the MIDI that MagmaCompiler doesn’t like. That happens with midis from other games that may use that. Open each track, view – events list, and delete anything that isn’t “lyric” “note” “text event” or “track name”.
or post the midi here so i can take a look.
September 17, 2013 at 11:08 am #406348That means there is some stuff in the MIDI that MagmaCompiler doesn’t like. That happens with midis from other games that may use that. Open each track, view – events list, and delete anything that isn’t “lyric” “note” “text event” or “track name”.or post the midi here so i can take a look.
I have Reaper, but navigating it is still a big scary mystery to me. So I’ll take you up on that; and maybe it’ll be educational. ” src=”/wp-content/uploads/invision_emoticons/default_SA_cheeky.001.gif” />
Here’s the chart: http://www.mediafire.com/download/ec3cv … Dchart.mid
September 17, 2013 at 1:13 pm #406351It seems to be mostly old chart problems, but there may be a few issues. Here’s the reaper project after I went through it. Obviously I’m not saying the charts are good, I have no way to know since I don’t have the audio or time to verify them, but this midi should compile.
PART DRUMS
- drum mixes are old, RBN2.0 does not use [mix 0 drums3easy] = now it's just [mix 0 drums3]
- drum mixes are incorrect - you said there were two channels for drums, that's [mix # drums0] not drums3]
- in View Events List, you right away see an Event Type of "PC" - Magma won't allow that, delete it
- [play] event does not go at 1.1.00, you gotta place it where the chart starts
- missing an [idle] event at the end of the chart
PART BASS
- in View Events List, you right away see an Event Type of "PC" - Magma won't allow that, delete it
- why so many [play][idle] events? You even had some on top of each other...
- missing an [idle] event at the end of the chart
PART GUITAR
- in View Events List, you right away see an Event Type of "PC" - Magma won't allow that, delete it
- why so many [play][idle] events? You even had some on top of each other...
- missing an [idle] event at the end of the chart
- midi notes at 105 and 106 are from old charting, not used with RBN2.0 - remove those
PART VOCALS
- in View Events List, you right away see an Event Type of "PC" - Magma won't allow that, delete it
- You don't need so many [play][idle] events...specially not when there's one measure or less of "idle" time
EVENTS
- [music_start] can't be at 1.1.00, that tells the game the music starts right away. Move it to where in the midi the music starts.
- section names use the old format...got to change them from [section Outro] to [prc_outro] for example...Replace the "section " with "prc_", and any capitalized letters put them back down to lower case. Replace empty spaces with underscore. So [section Verse 1] becomes [prc_verse_1] and so on. Everything else should be fine.
- You may also want to add more sections to make it easier to practice a song in game....i.e. outro section seems way too long?
BEAT
- in View Events List, you right away see an Event Type of "PC" - Magma won't allow that, delete it
VENUE
- that's an old style venue, trash it, start from scratch. Magma will autogenerate one for you, so for now concentrate on getting everything else fixed
TEMPO MAP
- is this song supposed to be a fixed 122bpm tempo? or did you not import it when importing the midi?
September 17, 2013 at 4:43 pm #406365It seems to be mostly old chart problems, but there may be a few issues. Here’s the reaper project after I went through it. Obviously I’m not saying the charts are good, I have no way to know since I don’t have the audio or time to verify them, but this midi should compile.
PART DRUMS
- drum mixes are old, RBN2.0 does not use [mix 0 drums3easy] = now it's just [mix 0 drums3]
- drum mixes are incorrect - you said there were two channels for drums, that's [mix # drums0] not drums3]
- in View Events List, you right away see an Event Type of "PC" - Magma won't allow that, delete it
- [play] event does not go at 1.1.00, you gotta place it where the chart starts
- missing an [idle] event at the end of the chart
PART BASS
- in View Events List, you right away see an Event Type of "PC" - Magma won't allow that, delete it
- why so many [play][idle] events? You even had some on top of each other...
- missing an [idle] event at the end of the chart
PART GUITAR
- in View Events List, you right away see an Event Type of "PC" - Magma won't allow that, delete it
- why so many [play][idle] events? You even had some on top of each other...
- missing an [idle] event at the end of the chart
- midi notes at 105 and 106 are from old charting, not used with RBN2.0 - remove those
PART VOCALS
- in View Events List, you right away see an Event Type of "PC" - Magma won't allow that, delete it
- You don't need so many [play][idle] events...specially not when there's one measure or less of "idle" time
EVENTS
- [music_start] can't be at 1.1.00, that tells the game the music starts right away. Move it to where in the midi the music starts.
- section names use the old format...got to change them from [section Outro] to [prc_outro] for example...Replace the "section " with "prc_", and any capitalized letters put them back down to lower case. Replace empty spaces with underscore. So [section Verse 1] becomes [prc_verse_1] and so on. Everything else should be fine.
- You may also want to add more sections to make it easier to practice a song in game....i.e. outro section seems way too long?
BEAT
- in View Events List, you right away see an Event Type of "PC" - Magma won't allow that, delete it
VENUE
- that's an old style venue, trash it, start from scratch. Magma will autogenerate one for you, so for now concentrate on getting everything else fixed
TEMPO MAP
- is this song supposed to be a fixed 122bpm tempo? or did you not import it when importing the midi?
Wow thanks a lot! I’m just having an issue now where Reaper crashes every time I try to export. I recently uninstalled the 64-bit version because I heard there were some limitations when working with RB stuff, so now I’m using the 32-bit version. Could that be part of the problem?
What I’m doing now is selecting File > Export project MIDI… I get as far as the “Consolidate MIDI” options, and when I select OK from there the program instantly crashes. It doesn’t hang or anything, just a crash as soon as I click OK, every time. ” src=”/wp-content/uploads/invision_emoticons/default_SA_frown.gif” />
-
AuthorPosts
- You must be logged in to reply to this topic.