Hello!
While I think the PA is a great format I have the problem that most of my contacts use WinZIP and thus can only process ZIPX when exchanging JPEG and MP3.
Unfortunately PowerArchiver supports extraction of all ZIPX-archives, but when compressing to ZIPX the really useful JPEG- and MP3- and … algorithms are not supported.
Please consider adding these ZIPX-compression-capabilities for better interoperability.
Thanks!
One feature most archive formats are lacking is archive integrity/recovery. RAR has had this capability from the start and thus remains the format of choice for those concerned with data loss from events such as storage media bit rot: https://en.wikipedia.org/wiki/Data_degradation
It would be a shame to not use this opportunity to also incorporate data integrity.
PAR1 and PAR2 specifications are available on the net; however, I’m not sure where to find the actual PAR3 specification, but maybe you could start here: https://www.livebusinesschat.com/smf/index.php?topic=2118.0 and here: https://multipar.eu/
PA needs a huge push on the deduplication department.
Further improvements to rep-fma will help but given that rar for example can completely destroy PA for some sets of data it would be a good idea to consider other options.
Hash based deduplication like rar5 can do could be a very good way to ensure no complete duplicate files are stored twice with almost complete disregard for dictionary sizes or how far apart they are.
Sorting the data before storing it could also be a good idea, compress all the files with the same extension secuentially, given that they are more likely to contain similar data.
these kinds of optimizations are all in all relatively cheap to do in terms of run time but can help for deduplication dramatically in cases plzma4 and rep-fma are failing
Thread for Jpeg codec for advanced codec pack / .pa format.
We already did our jpeg codec 6-7 years ago, maybe @eugene remembers what time exactly :). I believe our initial numbers were that it got compression gain of around 18% (vs 22%-24% of competition) but was 2x-3x faster than WinZip jpeg even in single thread state.
So @eugene gene started rewriting it earlier this year. It will be fun to see what specs we end up with.
Solved show estimated memory usage in add window (.pa)
-
… moving
-
@spwolf speaking of running out of memory, a little feature request…
7-zip for example shows the memory usage for compressing and decompressing, which is incredibly handy for knowing what settings I can actually set and what PCs will be able to decompress the created file:
it would be really cool to have this on PA, at the very least on the custom options tab
-
@tokiwarthoot it has been planned, thanks for reminder. I have moved it to the wishlist so we can track it better. Due to many different settings and codecs used in Optimized methods, it gets relatively complicated, so we have left it for closer to finalized release. Thanks!
-
Additionaly a warning when memory usage would exceed available free memory will be pretty nice.
-
@nikkho did you encounter a problem when it used too much memory? x64 is kind of good with this. x86 is horrible so we have to do it due to x86 for sure.
-
@spwolf during my tests, I managed to make PA x64 allocate about 12 GB of RAM. My system has 16GB, and at that point about 9GB free.
Compression was really slow, the system started to paginate contents to disk, and even if it is a SSD drive, it became unresponsive, until PA finished, and the memory was deallocated.
-
@nikkho how many threads did you set? That seems like more of max threads issue. We try to manage amount of threads in optimized modes simply because these codec chains internally use many threads already. So quite often mt4 is too much for 4 thread cpu and you would see your system freezing a bit.
Try lowering process priority to low and see how it behaves then.
Better test would be a system with 4GB of RAM and 4 cores, that would always do more in extreme mode.
Thanks!
-
@nikkho check out new low priority checkbox in add window… it should make it more smooth even if you max out the threads.
You can also now influence properly optimized modes with increasing many of the parameters… let us know if you notice it not working properly or anything interesting really.
-
Looking very nice the low priority checkbox. Love it.
Thanks. -
@nikkho said in show estimated memory usage in add window (.pa):
Looking very nice the low priority checkbox. Love it.
Thanks.I want to add it checked as default, it would be good for more people to test it out to make sure there are no adverse conditions… in my testing there is no loss of performance as long as user is not doing anything else, which is how it should be… if you have 30 chrome tabs open and are browsing, then you likely want to browse without hickups too.
thanks for the feedback!
-
I guess you can mark it as solved, since estimated memory is shown since 17 RC2.
-
This feature in PowerArchivier 2022 seems to not reset the calculations and at each click even without changing compression settings it adds the estimated memory values to those already written.
-