|Release Date||13 September 2019|
|Last Modified||19 June 2022|
beat is the canonical tool for working with beat-protocol files.
BPS Is meant as a successor to the IPS file format.
BPS patches support files of any size, unlike IPS which is limited to files that are 16 MB or less.
BPS patches encode checksums of the original file, the modified file, and the patch itself. This allows patchers to alert users when the wrong original file is used to apply a patch, unlike IPS that will silently produce a corrupted file with no warning.
beat v1 is licensed under GNU GPLv3. The source code can be found at https://archive.org/details/beat_v1
Note that a v2 version exists in source code form, licensed under ISC, which can be found at https://archive.org/details/near_respite_web
Useless as a delta patcherReviewed By: zikey on 16 Oct 2019
Using the latest version of ‘beat’ I tried to create a BPS patch of an ISO. ‘beat’ warned me that it would take 35 minutes and would require 16 GB of RAM to create the patch. I thought it was a miscalculation, but boy I was wrong. I had to destroy the process before my computer blew up.
On the other hand, DeltaPatcher created the xdelta patch, at maximum compression, in under a minute. With almost no RAM usage.
So beat advertises itself as a delta-based patcher, but it fails to accomplish something that an xdelta patcher has no issue with.
I fail to see what BPS tries to be then - merely a replacement for IPS when the file exceeds 16 MB? But what problem does that solve when xdelta can be used for the same thing, much more efficiently?
Version v1 Recommended - No
|Useless as a delta patcher||zikey||16 Oct 2019||v1||No|
|A great utility for patch releasing!||mrrichard999||31 Oct 2015||v01||Yes|