IRISMAN

PS3 IRISMAN {information] - A manager for CFW enabled PS3's (developed by Aldostools) 4.91.2

Do you think you'd be able to enable hardware acceleration for Movian when launched from IRISMAN? Unfortunately most videos are unplayable at the moment.
 
Do you think you'd be able to enable hardware acceleration for Movian when launched from IRISMAN? Unfortunately most videos are unplayable at the moment.

Does it behave the same on multiMAN or through the standalone application?

IRISMAN uses multiMAN's SHOWTIME.SELF to launch MOVIAN
 
Does it behave the same on multiMAN or through the standalone application?

IRISMAN uses multiMAN's SHOWTIME.SELF to launch MOVIAN

It works perfectly on the standalone app and through multiMAN. I even copied SHOWTIME.SELF from IRIS to mm and it was still fine.

When launched through IRISMAN, I get some info saying "Unable to open Cell codec. Error 0x80610180"
 
Last edited:
Hi, quick question - sorry to "interrupt" - is Irisman backward compatible with older CFW ?
On the page linked in first post about Irisman 4.88 I see "Extended the support to several CFW up to version 4.84." so it looks like not all previous CFW would be supported, but couldn't find a list of those ?

My PS3 has an old REBUG 4.65.2 REX CFW, and I would like to try Irisman, is it safe to just install the latest available ?
Thanks in advance.
 
It's still the same, unfortunately. I tried launching it from the Showtime option, and directly from the video file.

In that case I don't know why you're getting the error. I don't have much videos, but the ones that I have don't display any errors.

The change that I did was this:
Code:
//sysProcessExitSpawn2((const char*)MOVIAN, NULL, NULL, NULL, 0, 3071, SYS_PROCESS_SPAWN_STACK_SIZE_1M);
sysProcessExitSpawn2((const char*)MOVIAN, NULL, NULL, NULL, 0, 1001, SYS_PROCESS_SPAWN_STACK_SIZE_512K);

beselerbnot said:
Hi, quick question - sorry to "interrupt" - is Irisman backward compatible with older CFW ?
On the page linked in first post about Irisman 4.88 I see "Extended the support to several CFW up to version 4.84." so it looks like not all previous CFW would be supported, but couldn't find a list of those ?

My PS3 has an old REBUG 4.65.2 REX CFW, and I would like to try Irisman, is it safe to just install the latest available ?
Thanks in advance.
Yes. It is compatible with old CFW versions, including Rebug 4.65.2.

It is highly recommended that you upgrade to at least Rebug 4.84.2 REX.
 
In that case I don't know why you're getting the error. I don't have much videos, but the ones that I have don't display any errors.

The change that I did was this:
Code:
//sysProcessExitSpawn2((const char*)MOVIAN, NULL, NULL, NULL, 0, 3071, SYS_PROCESS_SPAWN_STACK_SIZE_1M);
sysProcessExitSpawn2((const char*)MOVIAN, NULL, NULL, NULL, 0, 1001, SYS_PROCESS_SPAWN_STACK_SIZE_512K);


Yes. It is compatible with old CFW versions, including Rebug 4.65.2.

It is highly recommended that you upgrade to at least Rebug 4.84.2 REX.

Maybe some parameters are passed to the self? multiMAN actually does have the issue if using the update option when pressing triangle. deank uploaded the self from the standalone app by mistake (I know because it quits to the xmb, and not mm).

Also, the error is only in the log, and not a pop up.
 
In that case I don't know why you're getting the error. I don't have much videos, but the ones that I have don't display any errors.

The change that I did was this:
Code:
//sysProcessExitSpawn2((const char*)MOVIAN, NULL, NULL, NULL, 0, 3071, SYS_PROCESS_SPAWN_STACK_SIZE_1M);
sysProcessExitSpawn2((const char*)MOVIAN, NULL, NULL, NULL, 0, 1001, SYS_PROCESS_SPAWN_STACK_SIZE_512K);


Yes. It is compatible with old CFW versions, including Rebug 4.65.2.

It is highly recommended that you upgrade to at least Rebug 4.84.2 REX.

I did some digging, and found this from the official (v5.0) source. Hopefully it will be of some help. It looks like it's started slightly different compared to your code.
 

Attachments

I did some digging, and found this from the official (v5.0) source. Hopefully it will be of some help. It looks like it's started slightly different compared to your code.

Try downloading again the installer from Github.

Now it uses the flags 1200 like the code that you posted.
sysProcessExitSpawn2((const char*)MOVIAN, NULL, NULL, NULL, 0, 1200, SYS_PROCESS_SPAWN_STACK_SIZE_1M);

SYS_PROCESS_SPAWN_STACK_SIZE_1M = 0x70
 
Try downloading again the installer from Github.

Now it uses the flags 1200 like the code that you posted.
sysProcessExitSpawn2((const char*)MOVIAN, NULL, NULL, NULL, 0, 1200, SYS_PROCESS_SPAWN_STACK_SIZE_1M);

SYS_PROCESS_SPAWN_STACK_SIZE_1M = 0x70

It's still not using hardware acceleration. The only other thing I can think of is something to do with showtime.txt?
 
I just discovered a freeze while testing some more things. If an mp3 file is played from the file manager, the PS3 will freeze once the last song has finished. I had a quick look at the source, but I'm not seeing anything immediately obvious that would cause it.
 
I just discovered a freeze while testing some more things. If an mp3 file is played from the file manager, the PS3 will freeze once the last song has finished. I had a quick look at the source, but I'm not seeing anything immediately obvious that would cause it.

Recently Alann-Mints is maintaining IRISMAN. I'm basically approving and compiling the changes.

Honestly I cannot dedicate much time to debug/fix this project.

In regards to the issue with Movian's hardware acceleration, I was trying a few things like permissions, settings files, flags, etc. but I couldn't find the reason why it isn't working when launched from IRISMAN.
 
just want to say thanks to the developer for irisman so much more easier to use in my opinion any way there multiman and webman tools and the fact you can use an ntfs drive with it is a lifesaver. made my journey getting my games onto the ps3 slightly easier with a boat load of googling as it seems doing anything on the ps3 superslim on hfw 4.89.1 is a dark art.
 
are there any updated sources for the payloads @aldostools ? I am too lazy to port them on my own and on github it just goes up to 4.81.

No. The LV2 kernel offsets are the same from 4.75-4.89 (except 4.80 & 4.90 that share the same LV2 offsets).

In other words, copy payload_480C.bin to payload_490C, and payload_475C.bin to 476C, 478C, 481C, 482C, 483C, 484C, 485C, 486C, 487C, 488C, 489C.

payload_481D is the same for 482D, 483D, 484D and 490P (ported 4.84DEX).

SRC: https://github.com/aldostools/IRISMAN/tree/master/payloads
 
No. The LV2 kernel offsets are the same from 4.75-4.89 (except 4.80 & 4.90 that share the same LV2 offsets).

In other words, copy payload_480C.bin to payload_490C, and payload_475C.bin to 476C, 478C, 481C, 482C, 483C, 484C, 485C, 486C, 487C, 488C, 489C.

payload_481D is the same for 482D, 483D, 484D and 490P (ported 4.84DEX).

SRC: https://github.com/aldostools/IRISMAN/tree/master/payloads
oh, didn't know that this is possible. nice, thank you :)
maybe I will make a small and useful release these days, still thinking about it
 
Back
Top