@sandungas
You mean that ps3 while in game mode couldn't decypt iso, right?
I explained to Zar what i'm starting to do with my games, it's simple! But as I said I don't know if is a nonsense making a redump collection of my games on my pc hard drive if then I could not use it for gaming at a later time transferring them to my console. what do you suggest to do?
Yes, lets say... while playing the game is going to request files that are located far away from each others, and the decryption function needs to process them on real time
We are not decrypting the whole ISO, but only small parts of it when needed, if the game asks for the same file multiple times then is needed to decrypt the same file several times
One of the reasons why nobody implemented this feature before is because the success of something like this are doubtful... i mean... independently of the coding skills of the person who try it... we dont really know how many CPU workload is going to cause this additional job... and it could happen that the games have low fps, lag, or broken functions caused by low file access (soundtrack not playing, textures missing, etc...)
In the practise this potential problems could made this PS3 backup format using encrypted ISO's could decrease a lot the compatibility with the whole PS3 game library
With the decrypted ISO format generated by makeps3iso we are like 100% compatibility, if this method reduces the compatibility to lets say... 95% i guess not much people is going to use it
But who knows ?, thats the fun of doing experiments, maybe it works great
Im not being pesimistic, just explaining this for the people that would like to see this feature working... the problem is we dont know the cost... and doing it "at any cost" could not be good enought
In the PS3 the crypto tasks are made by a controller (an small part of the circuitry) named ENC/DEC located inside the SouthBridge chip
The SouthBridge is like a "hub" and the devices connected to it can be considered peripherals (HDD, USB, BD, and some more) so all the data that is moved back and forth in between them needs to pass throught it. If we find how to tell the ENC/DEC controller to encrypt or decrypt the data for us then it could be considered that is made "by hardware" (without causing any additional workload to the CPU)
...btw for curiosity sake... the same principle can be applyed to the "kraken" de/compressor of the PS5, is a controller inside the APU dedicated to it... so the PS5 can do de/compression "by hardware" while having 100% of the CPU cores availables for other tasks
The new XBOX doesnt have that (neither the PC's) so the de/compression causes a penalty to the CPU cores
---------
Personally i always thought the IRD format is something very useful, at the first days not much people was caring about it, except the ODE owners of course, but i always been interested in it because i relized the list of files with his MD5's inside IRD files (and the way how that IRD files was generated) was very accurate
Lets say... i realized since day one that the IRD format was good enought.. and that same principle of "is good enought" was applyed also to some tools, e.g: the ISO's generated by makeps3iso.exe differs a bit from the ISO's generated by 3k3y tools but it was made for simplification purposes (and also because the 3k3y tools was not so perfect in some taks, i remember to find a couple of bugs, also was abandoned anyway when the 3k3y company dissapeared)
My suggestion is to get used to the IRD files, and how to check your games with them (managunz can do it). If you are making backups from the real disc run a IRD check while doing the backup in decrypted format and you are going to see that all your games are going to pass the IRD verification (with a very few exceptions)
Thats good enought, it means all the paths inside the ISO and all the game files are identical to the originals... is just are not covered by an "encryption layer"
