Jump to content

Avatar

Magma: C3 Roks Edition v3.3.2 [07/28/15]


  • Please log in to reply
691 replies to this topic

#21 TrojanNemo

TrojanNemo

    The Programmer

  • 4,860 posts
  • Location
    Miami, Florida

Posted June 5, 2013 - 02:25 AM

not sure I follow what you're saying. why were you creating new magma projects everytime?
anyways, you can definitely change the song id within magma now so that's good. rbn songs use something like ugc_xxxxxxx where the xxxxxxx represent a unique number. we use typically the name of the song. you can use almost anything I suppose.

#22 Nyxyxylyth

Nyxyxylyth

    Magnificent Bastard

  • Administrator
  • 1,402 posts
  • Location
    Michigan

Posted June 5, 2013 - 02:31 AM

One of the most annoying (but certainly not most important) problems I've had with Magma in the past is that I've had to make a new Magma file every single time I want to update the latest RB3CON. Am I right in saying that with the option to make my own custom song ID, this will no longer be a problem?

And what do I put in the ID? Numbers? Letters? Symbols?

You could have just deleted the cache. Or edited songs.dta yourself, bumped the ID, and used RB3Maker's "Full Song" to repackage.

Anyhow, now it's all better, and you're right.

I suggest just bumping a number, like bestsongever1, bestsongever2, etc.

#23 DeathThreatUK

DeathThreatUK
  • 302 posts

Posted June 5, 2013 - 03:00 AM

One of the most annoying (but certainly not most important) problems I've had with Magma in the past is that I've had to make a new Magma file every single time I want to update the latest RB3CON. Am I right in saying that with the option to make my own custom song ID, this will no longer be a problem?

And what do I put in the ID? Numbers? Letters? Symbols?

You could have just deleted the cache. Or edited songs.dta yourself, bumped the ID, and used RB3Maker's "Full Song" to repackage.

Anyhow, now it's all better, and you're right.

I suggest just bumping a number, like bestsongever1, bestsongever2, etc.


What I mean is that if I just used the same Magma file, then no matter what I changed, the song would not be identified as different by RB3. Even if I deleted the old file and injected the new one, with all different details, I would still see the first file, despite having deleted it already.
Posted Image
Hail To His Majesty.

#24 Nyxyxylyth

Nyxyxylyth

    Magnificent Bastard

  • Administrator
  • 1,402 posts
  • Location
    Michigan

Posted June 5, 2013 - 03:12 AM

What I mean is that if I just used the same Magma file, then no matter what I changed, the song would not be identified as different by RB3. Even if I deleted the old file and injected the new one, with all different details, I would still see the first file, despite having deleted it already.

Once RB3 enters a song into the cache, that's where RB3 pulls the songs.dta information and MIDI data. You have to either delete the cache, or change the song ID.

#25 TrojanNemo

TrojanNemo

    The Programmer

  • 4,860 posts
  • Location
    Miami, Florida

Posted June 5, 2013 - 04:22 AM

What I mean is that if I just used the same Magma file, then no matter what I changed, the song would not be identified as different by RB3. Even if I deleted the old file and injected the new one, with all different details, I would still see the first file, despite having deleted it already.


sorry to hear you've been under this confusion. it all comes down to what nyx mentioned. the song cache. the only thing that you were accomplishing by doing a whole new magma project is that in the process, you'd most likely end up with a new file name = new song id, since rb3maker and now this version of magma use your project name to create the song id, although now you have the option of changing that. you could have stayed with the old magma project, just changed the name of the RBA file, and it would have been fine. or what I always do, delete your song cache.

some people freak out because you lose offline scores. i didn't care for online scores, I certainly don't for offline scores that only I see. my life is infinitely easier this way, i just delete and rebuild my cache. no problems.

EDIT: anyways, I thought of something else to add...option to choose ANSI/UTF8 encoding right in Magma, so for those songs like Queensrÿche, you don't have a problem. I have most of it done already, so :dance:

#26 Farottone

Farottone

    The Lean Mean Customs Charting Machine

  • Administrator
  • 6,393 posts

Posted June 5, 2013 - 09:10 AM

EDIT: anyways, I thought of something else to add...option to choose ANSI/UTF8 encoding right in Magma, so for those songs like Queensrÿche, you don't have a problem. I have most of it done already, so :dance:


That would be gorgeus. Why an option though? Can't you just make it so by default?

#27 Farottone

Farottone

    The Lean Mean Customs Charting Machine

  • Administrator
  • 6,393 posts

Posted June 5, 2013 - 09:11 AM

What I mean is that if I just used the same Magma file, then no matter what I changed, the song would not be identified as different by RB3. Even if I deleted the old file and injected the new one, with all different details, I would still see the first file, despite having deleted it already.


That only gos for song's information data: tiers, instruments, title, etc. If you update your MIDI (which is 99% of the times) there's no need to change song ID.

#28 TrojanNemo

TrojanNemo

    The Programmer

  • 4,860 posts
  • Location
    Miami, Florida

Posted June 5, 2013 - 11:15 AM

EDIT: anyways, I thought of something else to add...option to choose ANSI/UTF8 encoding right in Magma, so for those songs like Queensrÿche, you don't have a problem. I have most of it done already, so :dance:


That would be gorgeus. Why an option though? Can't you just make it so by default?


I could, but the vast majority of songs are encoded in ANSI and use 'latin1'. Only the few with special characters use UTF8. I don't know if it's a good idea to just switch completely to UTF8?

anyways, it's a pain in the behind it seems. i'm testing with Michael Bublé and even though the file is correctly being created in ANSI or UTF8, the accented é is messed up in both. So still got to keep digging on how to do this correctly.

#29 espher

espher

    Harmonies Hacker

  • Administrator
  • 1,900 posts
  • Location
    Canada

Posted June 5, 2013 - 11:25 AM

anyways, it's a pain in the behind it seems. i'm testing with Michael Bublé and even though the file is correctly being created in ANSI or UTF8, the accented é is messed up in both. So still got to keep digging on how to do this correctly.


I'll check what I did with RB:HP when I get home since I got that sorted out (finally), though I had to change to English (United States) for my regional/non-unicode settings.

C3 Author/Admin, Project Lead for the Rock Band: Harmonies Project


#30 TrojanNemo

TrojanNemo

    The Programmer

  • 4,860 posts
  • Location
    Miami, Florida

Posted June 5, 2013 - 12:19 PM

please do. i'd love to figure this out.
more importantly, how are you doing this on your pro upgrades? because if you're combining all songs and just doing utf8 for them all, even the ones that don't need it, I can do that here AND in LeFluffie's packager then.

#31 TrojanNemo

TrojanNemo

    The Programmer

  • 4,860 posts
  • Location
    Miami, Florida

Posted June 5, 2013 - 12:41 PM

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.

#32 TrojanNemo

TrojanNemo

    The Programmer

  • 4,860 posts
  • Location
    Miami, Florida

Posted June 5, 2013 - 10:58 PM

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! :what:

#33 Polish Weener

Polish Weener
  • 89 posts

Posted June 5, 2013 - 11:33 PM

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.

#34 TrojanNemo

TrojanNemo

    The Programmer

  • 4,860 posts
  • Location
    Miami, Florida

Posted June 5, 2013 - 11:41 PM

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 :excited:

#35 Jdcow45

Jdcow45
  • 72 posts

Posted June 5, 2013 - 11:46 PM

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?

#36 TrojanNemo

TrojanNemo

    The Programmer

  • 4,860 posts
  • Location
    Miami, Florida

Posted June 5, 2013 - 11:51 PM

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 :dance:

does that make sense?

#37 Farottone

Farottone

    The Lean Mean Customs Charting Machine

  • Administrator
  • 6,393 posts

Posted June 5, 2013 - 11:59 PM

because you create that image using the Visualizer in Le Fluffie.


Plus, I suppose Karaoke Version gets automatically appended to the title, no?

#38 TrojanNemo

TrojanNemo

    The Programmer

  • 4,860 posts
  • Location
    Miami, Florida

Posted June 6, 2013 - 12:04 AM

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.

#39 Farottone

Farottone

    The Lean Mean Customs Charting Machine

  • Administrator
  • 6,393 posts

Posted June 6, 2013 - 12:08 AM

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. :)

#40 TrojanNemo

TrojanNemo

    The Programmer

  • 4,860 posts
  • Location
    Miami, Florida

Posted June 6, 2013 - 05:09 AM

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 :excited:




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users