[How-To] Playing Customs on PS3
- This topic has 1,261 replies, 127 voices, and was last updated 7 months, 2 weeks ago by
.
-
Posts
-
I think I have had enough patience and spent more than enough time assisting PS3 users when I don’t even own the console, much less play RB3 on it. So forgive me if I expect more than jumps to conclusions.
You didn’t find a solution at all – you just stated the obvious. You’re saying “hey, with your modified Mini Cooper I have a problem, but if I use a stock Mini Cooper from the dealership, I don’t have a problem – I found the solution, it’s your modified Mini Cooper!” You need to find WHAT in the modified version of Magma is causing the problem – I can’t do that, since it works as intended for my console.
Magma: C3 is composed of over 21,000 lines of code and relies on 5 external executables and 16 external libraries. I have worked on it for nearly 2 years and beyond 1,000 hours between decompiling, rebuilding, and then improving it.
Asking ME to figure out what, in all of that, causes YOUR problem, is bad form, and I simply will not do it. Specially not now that I am done working on Magma.
Whatever solution may come from this, it will still be a PS3 specific issue – Xbox users are not going to give up any of the improvements to Magma:C3 to help PS3 users, and as I said, I’m done working on Magma, so that won’t be implemented.
I have some ideas as to possible solutions that will not involve any code changes to Magma: C3, but all the solutions will limit you to songs that are not encrypted.
okey sorry if you find yourself hurt I think you did a lot of work for ps3 users and I appreciate it a lot, and I’m also trying to help and spend a lot of my free time to find the problem. I’ve isolated the problem a lot and seems like no one appreciate my work.
Well here are ps3 users so I’ll let them test both the files I’ve made and are identical just passed trough 2 different magma.
One was with c3 rock edition and one with original. The one created with original plays without any problems all the way trough the end, while the c3 rocks edition gets stuck at beginning….
Sorry but I’ve done various of testing… and I’m 100% sure the problem is in magma.
I’m not the programmer to tell you what is wrong inside the program you made, as I don’t know that kind of staff…. I just know the fact that it’s the problem how magma rock edition is creating 16 track mogg… something must be different between original and your version.
test song made with c3 rock edition:
https://drive.google.com/file/d/0B7IltJ … sp=sharing
Same test song made with original magma v2:
Sorry but I’ve done various of testing… and I’m 100% sure the problem is in magma.You need to find WHAT in the modified version of Magma is causing the problem – I can’t do that, since it works as intended for my console.something must be different between original and your version.Magma: C3 is composed of over 21,000 lines of code and relies on 5 external executables and 16 external libraries. I have worked on it for nearly 2 years and beyond 1,000 hours between decompiling, rebuilding, and then improving it.
Well maybe if some of ps3 users is a programer and can look inside magma and see what process is wrong can maybe help out.
I’ve posted the link of both identical .moggs one is working, and other isn’t both are 16 channels..
Well maybe if some of ps3 users is a programer and can look inside magmaSource code is not available for anyone to look at and it’s obfuscated in the release version so decompiling it is a waste of time.
You’re still missing the point here.
Well the only thing different that I’ve noticed when I’ve run both files into song analyzer and comparing the .mogg files from both versions is the size difference.
Magma c3 rock edition audio file size is 41.53 mb
Magma original version 34.94 mb
Well, you’re getting closer to the cause of the problem. I’m fairly sure I know, and it’s not Magma itself…but the feeling of accomplishment from solving a problem is not something I’m going to rob you of. I’m sure you can figure it out.
” src=”/wp-content/uploads/invision_emoticons/default_SA_biggrin.gif” />haha feel free to rob me off, I think I’ve done a lot of work…. had some free time as I was sick and got a week of free days.
As my brain is on a power backup I’m out of ideas… maybe the cause of problem is in ogg encoder?
Bingo.
At least, I think that’s the cause. Our modified oggenc.exe allows us to add crowd audio and raise the audio encoding quality. That’s one good starting point. You can replace oggenc.exe in Magma: C3’s folder with the oggenc.exe from Magma’s folder, and compile with that. Obviously it’ll ignore those two things if you’ve raised the encoding quality or were hoping to add a crowd track, but otherwise the audio it produces should match the one produced by the original Magma.
okey I’ll give it a shot and let you know what result is.
” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />can you try to compile one of the broken songs with the original ogg encoder so other ps3 users can test it out as well, so we can confirm that is the problem? Or you can make a tool that would re-encode broken moggs?
There’s not going to be a tool to do that, as I already said. Songs will have to be recompiled with Magma. I don’t have the time to mess with songs now, I’m sure you can get a PS3 user to help.
If you want another ps3 user’s confirmation, post the original ogg encoder or whatnot and some instructions on what you did.
- You must be logged in to reply to this topic.