Magma: C3 Roks Edition v3.3.2 [07/28/15]
- This topic has 697 replies, 6 voices, and was last updated 1 year, 2 months ago by
.
-
Posts
-
i think I figured it out. Magma was compiling to RBA, during which I have no control of the encoding. then reading back the raw songs.dta. then after parsing through it I was trying to save it in UTF8 or ANSI, but both were messed up because the original was messed up. now it just gets the artist, album and song name from magma itself and voila, working. at least in NotePad++, gotta check it out in game.
updated the file in the OP.
added what i hope is working UTF8/ANSI encoding. it works fine in Magma and in the resulting file. let me know if it works in game, I have no time to test right now.
it will check against the most common “funny” characters so if your song name, artist name, or album name has any and you’re not using UTF8 it’ll suggest that you do.
also did a few minor visual changes to the way the menu items are labeled, the toast notifications changed look a little bit, and other small changes like that.
the lack of negative feedback gives me the false sense that it’s working fine for everyone and nothing needs fixing? which can’t possibly be true!
I personally don’t have any songs finished to send through right now, but I’ve put all of my other projects on hold so I can finish a 16 minute beast and send it through to test that feature.
that’s possibly the least of my concerns since I compiled both Xanadu and Abbey Road Medley and tested them in game and worked. it’s all the other “features” I’ve added to try to please everyone that are difficult to test effectively. the first round of feedback was great, specially from farottone and pikminguts, but after those things were supposedly fixed, it’s all quiet. too quiet.
maybe I should just be celebrating
My question is why we have the option to check whether it’s Karaoke or multitrack when an image file isn’t created with the album art and difficulties and such? Maybe I was mistaken?
because you create that image using the Visualizer in Le Fluffie. I *could* integrate the whole thing into Magma, but I feel it’s already pretty bloated and i’d rather just keep it in Le Fluffie.
by selecting those things (by the way, only once, they’re saved for any future time you open that project) when you open the CON file in Visualizer (once I update it), it will pick up those flags and the visualizer won’t need you to click whether it’s karaoke or multitrack, etc, it’ll do it automatically.
right now there is no way to do that since the normal song.dta files don’t include anything to let us know. now they do with this new Magma
does that make sense?
because you create that image using the Visualizer in Le Fluffie.Plus, I suppose Karaoke Version gets automatically appended to the title, no?
eh no?
why would it? we have 0 songs that use that. the Karaoke flag is for songs that have karaoke stems, meaning vocals + backing. but it’s no different in any other respect from another custom.
it’s not like (Rhythm Version) or (RB3 version) if that’s what you mean. those get appended to the song title.
it’s not like (Rhythm Version) or (RB3 version) if that’s what you mean. those get appended to the song title.
You’re right. I have one song that’s actually gonna have a karaoke version but it’s probably one in a million (different masters, different tempo map). Carry on.
” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif”>updated the OP again.
Рtested the accented characters (Michael Bubl̩) which in the past had not worked for me when doing it manually. entered it as such in Magma and worked beautifully in game using UTF8.
– I had a derp moment and while doing this code I messed up the songs.dta IF YOU DOWNLOADED PRIOR TO THIS MESSAGE, RE-DOWNLOAD OR YOUR SONGS WILL SHOW A WHITE IMAGE AND WON’T LOAD!
– took the program on a diet -> removed a few unused resources, and compressed all remaining images = 600KB lighter now
– photoshopped some of the bright spots out of the background. you’re welcome.
– a few other minor design changes.
getting closer to ready for release i think.
updating my Beatles songs and man, compiling Abbey Road Medley in one click is so cool
Would it be possible to take out the error for tempo maps over 300 BPM? A lot of those Frets on Fire songs have terrible tempo maps, but they are playable. I’m able to compile a Con file with the tempo over 300 BPM through LeFluffie and it would be easier if I was able to pass them directly through Magma.
most likely yes.
send me a project file that will compile as is except for that 300 bpm restriction. just open the audio file in audacity, mute it, RAR and upload, so it’ll be very small. i don’t need to actually hear it, just have all the necessary files so the project will compile once we bypass the 300 bpm thing.
most likely yes.send me a project file that will compile as is except for that 300 bpm restriction. just open the audio file in audacity, mute it, RAR and upload, so it’ll be very small. i don’t need to actually hear it, just have all the necessary files so the project will compile once we bypass the 300 bpm thing.
Make sure though this is a selectable option not on by default, because we’re effectively removing a valid check on temp map issues (300+ BPM means the song has a fudged tempo map, 99,999% of the times).
most likely yes.send me a project file that will compile as is except for that 300 bpm restriction. just open the audio file in audacity, mute it, RAR and upload, so it’ll be very small. i don’t need to actually hear it, just have all the necessary files so the project will compile once we bypass the 300 bpm thing.
Make sure though this is a selectable option not on by default, because we’re effectively removing a valid check on temp map issues (300+ BPM means the song has a fudged tempo map, 99,999% of the times).
that’s a check done by MagmaCompiler. all we can do is disable it or changing the value, but it’s a permanent change, not selectable in Magma. so you guys battle it out then.
I don’t see why anyone would ever want something with 300BPM so I have no stake on this.
- You must be logged in to reply to this topic.