Midi Larger than 1MB
- This topic has 26 replies, 5 voices, and was last updated 8 years, 10 months ago by
.
-
Posts
-
Hey all,
Magma has thrown the error that my midi file is larger than 1mb (it’s a very long track…
” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif” /> ) and won’t compile. I didn’t realize this was a limitation, but it’s good to keep in mind for future reference.The midi itself is only 1.1MB, so I think I can cut some stuff out to bring it down under the limit. Is there another way around this issue though? Just figured I’d ask for some advice from the amazing community.
Thanks!
Simplify lower diffs, work on drums animations, etc.
” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif”>Also something really strange just happened. I re-selected the MIDI, and Magma said “hey, this was too big, but I made it smaller for you! So it should work fine!” then when I went to build, it still threw the error (even though the resulting file was only 800kb). I went back, and the file had been increased in size again, presumably by Magma…
I’ll work on simplifying the lower diffs. I’ve never touched drums animations so that sounds pretty daunting haha. Any other advice with the information above?
Magma uses raynebc’s midishrink to, among other things, shrink MIDI files when possible. What it sounds like is Magma is throwing it at midishrink, getting the smaller MIDI, then it’s auto-generating whatever you have set it to do, and then the resulting file is too big again. So either don’t have it auto-generate anything or have it auto-generate less things. Edge cases like this are hard to handle because that 1MB limitation is hard coded and not something to get around because it can cause problems in game.
I thought it might be the auto-generating that was causing the issue, and I was even typing that up in my initial response and then realized that was a complete guess and I didn’t want to sound stupid haha.
I looked through all the options for auto-generating and I didn’t see anything marked. There are no keys, so none of those are marked. I haven’t changed any of the options and the only “advanced settings” checked is override album art.
Here’s a screenshot of what I’ve got:
I tried cleaning the compressed MIDI and noticed it shot straight back up to the original file size. Maybe that’s what’s happening when I attempt to build? Sorry if I sound like a complete idiot I’m totally shooting in the dark here haha.
Also, I totally understand the 1MB limitation. I don’t understand the specifics of why, but it makes sense that the bigger something is the more likely it might cause problems in the game. So I get why it is there and why it’s hard coded.
” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” /> just trying to figure out how I can work with the limitation, as opposed to trying to “get around it”. Should the usage of midishrink be put off until all MIDI cleanup and auto-generation features have been performed?
Should the usage of midishrink be put off until all MIDI cleanup and auto-generation features have been performed?
It seems like that would solve this particular issue. Like I said, the resulting file is < 1MB, but then it shoots right back up to it's original file size during the Test/Clean/Build process. I have no idea how to go about doing that, of course haha.
Worst case scenario, delete some lower diffs, compile and check that everything works. Then re-export with all diffs, shrink and don’t compile but replace the MIDI in the CON file with C3 CON Tools.
Hmm… That’s an interesting idea! I actually haven’t done any of that injection work with C3 CON Tools yet, but I knew it was possible. I already took Easy out of Guitar and Bass… it’s harder to do on Drums because of the Gems after Fills requirement, so I’m avoiding that for now. File is about 30kb too big still with no easy, so I’ve moved onto optimizing Medium. Maybe I’ll just try taking it out completely and using your suggestion instead though.
You don’t have to rely on C3 CON Tools for that. Magma has the option to override the MIDI that goes in the CON File. Just rename the file override.mid and enable the option under advanced options. It’ll compile with the regular MIDI and then use override.mid to go into the CON file. Obviously, use that with caution.
You don’t have to rely on C3 CON Tools for that. Magma has the option to override the MIDI that goes in the CON File. Just rename the file override.mid and enable the option under advanced options. It’ll compile with the regular MIDI and then use override.mid to go into the CON file. Obviously, use that with caution.
Thanks for the heads up. I’m working on getting it to build now, I got it under 1MB but I have to put gems back in for overdrive and stuff.
Song is built and plays well! I noticed there were no drums or guitar/bass animations on this track though, which is weird because they have been in every other custom I have made. Drums for sure…I think the others as well but I’ll have to double check. I thought maybe it was because of the size issue…but I determined that doesn’t really make sense, because of how we know it was increasing the size of the midi before, presumably because of the auto generated animations and stuff.
Anyway I’m going to look into it, but looks like it’s about ready to go live.
If anybody has any more suggestions about how to get the full midi in there let me know. Thanks so much for all the help and input!
Sent from my iPhone using Tapatalk
- You must be logged in to reply to this topic.