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 fungusDig.
-
AuthorPosts
-
June 13, 2013 at 2:52 am #401246
When I set the start preview time in C3 magma to 1m 0s, Rb3 plays from the very beginning.
Has anyone else experienced this?
June 13, 2013 at 3:04 am #401247Isn’t this supposed to allow the bypass of only charting 5lane keys and not real keys? I did a song on keys and it gave me errors about no overdrives in realkeys, I muted all the real keys tracks before compiling the MIDI, is there something else I need to do?
June 13, 2013 at 3:43 am #401249When I set the start preview time in C3 magma to 1m 0s, Rb3 plays from the very beginning.Has anyone else experienced this?
Deleting the song cache might fix it.
June 13, 2013 at 11:05 am #401260Isn’t this supposed to allow the bypass of only charting 5lane keys and not real keys? I did a song on keys and it gave me errors about no overdrives in realkeys, I muted all the real keys tracks before compiling the MIDI, is there something else I need to do?already answered ya in the other forums. it was supposed to. apparently that did not work out. i’ll look into it for the next update.
June 13, 2013 at 11:07 am #401261When I set the start preview time in C3 magma to 1m 0s, Rb3 plays from the very beginning.Has anyone else experienced this?
is this the first time you’re adding it to the game? have you tried clearing the song cache? remember that something like the preview start time goes in the songs.dta file, which will not reflect a change in game until you rebuild the cache.
I only changed the default time, not how it saves to the project or to the songs.dta file, so theoretically it should be working as the original. all of my songs have previews working fine but I haven’t set any to exactl 1:00 (maybe that’s the problem).
let me know more details please.
June 13, 2013 at 1:51 pm #401281When I set the start preview time in C3 magma to 1m 0s, Rb3 plays from the very beginning.Has anyone else experienced this?
is this the first time you’re adding it to the game? have you tried clearing the song cache? remember that something like the preview start time goes in the songs.dta file, which will not reflect a change in game until you rebuild the cache.
I only changed the default time, not how it saves to the project or to the songs.dta file, so theoretically it should be working as the original. all of my songs have previews working fine but I haven’t set any to exactl 1:00 (maybe that’s the problem).
let me know more details please.
Deleting the song cache definitely fixed my problem. It also fixed another issue i was experiencing, where I added new instruments to a song I had been testing, and they weren’t showing up in game. if you write a faq for magma, this information would be appreciated for users not familiar with RB testing.
June 13, 2013 at 1:57 pm #401282Deleting the song cache definitely fixed my problem. It also fixed another issue i was experiencing, where I added new instruments to a song I had been testing, and they weren’t showing up in game. if you write a faq for magma, this information would be appreciated for users not familiar with RB testing.
It’s one of the customs mantra: anything related to metadata/song’s information can’t be changed once the song has been loaded in the cache. Title, artist, position in the album, instruments (including harmonies added to a previously vocals-only song), anything basically except the audio and the MIDI file can’t be changed. However, you don’t need to delete your cache (which will wipe away any information about the songs you’ve played in TU4, including number of times you’ve played a song, high score, date added, etc.), you just need to change song ID (saving the RBA file with a different name, and then let Magma C3 take care of using that name as song ID).
June 13, 2013 at 3:04 pm #401290you just need to change song ID (saving the RBA file with a different name, and then let Magma C3 take care of using that name as song ID).Next version will make this even easier. Already integrated just got to wait on a few other things before v1.1 goes out.
June 13, 2013 at 3:39 pm #401294I found two problems when trying to compile songs longer than 10 minutes.
1: you can’t change the preview to anything after 9:59
2: magma won’t accept a MID bigger than 1 megabyte, which is especially a problem because I’m trying to compile a song that’s an hour long
June 13, 2013 at 3:55 pm #401296Great. There was no way to catch #2 without having the file to compile. #1 is an oversight on my part…should be easy to fix.
Can you upload the whole project so I can try to remove that 1mb limitation? Mute the audio so its small when compressed. I need everything necessary to compile including dryvox if there are vocals.
Should have these issues fixed in next release.
June 13, 2013 at 4:19 pm #401299Here’s everything I used.
I was just trying to compile someone else’s drum charts into one song to play for my own purposes (colors by between the buried and me) and the mid they had was too big for magma. after cutting out a lot of notes from the other difficulties, i was able to get it just below the 1 megabyte mark and compile it.
http://www.mediafire.com/?b86w454ftskgc5v
“Colors” is the one i used to compile with, and “Colors 1-p” is the original MID which is too big. the silent audio is really low quality because at full quality it’s about 917 MB. That’s about all. The RBPROJ and RPP are also included
June 14, 2013 at 1:16 am #401334preview time limitation fixed. expanded it to 75 minutes. which is more than enough. gotta figure out the 1MB limit….
June 16, 2013 at 5:52 am #4014572: magma won’t accept a MID bigger than 1 megabyte, which is especially a problem because I’m trying to compile a song that’s an hour longThat’s a HUGE MIDI. I took a look at it, it’s not encoded with the “running status” trick. I put it into EOF and resaved and the MIDI is only about 318KB, which is using running status encoding, compared to the original MIDI being 1.25MB. This encoding makes a very big difference when entire tracks are pretty much just a series of on and off events (especially the BEAT track). What chart/MIDI editor did you use to create the MIDI?
If necessary, I could probably whip up a command line program in C that accepts an input MIDI and just rewrites it optimized for size with running status. This could be invoked by Magma C3 or the code could be adapted to be included internally, whichever works best.
June 16, 2013 at 6:11 am #4014581: you can’t change the preview to anything after 9:59
This is just me, but if you can’t recognize a song in 10 minutes, the song is either hipster-certified or not that memorable.
June 16, 2013 at 10:24 am #401464If necessary, I could probably whip up a command line program in C that accepts an input MIDI and just rewrites it optimized for size with running status. This could be invoked by Magma C3 or the code could be adapted to be included internally, whichever works best.
sending you a PM.
-
AuthorPosts
- You must be logged in to reply to this topic.