-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs on how to upgrade from v1 to v2 api? #62
Comments
I tried this in my code:
but then I get different output for my test files, so this is wrong. What did I do wrong? |
@0-wiz-0 It's unfortunate that these CRC polynomials have multiple names (https://reveng.sourceforge.io/crc-catalogue/all.htm is a pretty good reference). |
Thanks, @akhilles , that worked! |
I also have a question about this. We were using:
It seems like this should be replace by:
But this is calculating a different checksum value. Is there something equivalent to the old |
0.14.0 included an upgrade to the `crc` crate, with associated updates to use the new API, however it appears to calculate different checksums. I put a comment here asking about how to calculate an equivalent checksum using the new API: mrhooray/crc-rs#62 (comment) This also adds an alias to ensure that checkpoints written by 0.14.0 will be able to be read by 0.15.0 when it is released. Fixes: #8182 Signed-off-by: Jesse Szwedko <[email protected]>
Could you try |
Aha, yep, that appears to be it. Thanks @akhilles ! |
This was broken when porting to crc 2, based on: mrhooray/crc-rs#62 (comment) > CRC_32_BZIP2 is a different algorithm from CRC_32_IEEE, try CRC_32_ISO_HDLC instead. The correct algorithm for replacing checksum_ieee is not CRC_32_BZIP2. Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/merge_requests/555>
I upgraded from v1.8 to v2 and it was pretty straightforward and painless. I used the reference that was in the documentation (this link: https://reveng.sourceforge.io/crc-catalogue/all.htm) to figure out what constant I needed (for me this was from |
No description provided.
The text was updated successfully, but these errors were encountered: