Michael

A bit late, but here's another archive sample, created using zip-rs rust crate (https://github.com/zip-rs/zip), with compression level 20 Its not directly usable as an application, but here's a sample cli utility that uses it internally (slightly patched since the original is outdated, you'll need to compile it yourself) -> https://github.com/Zapeth/zippy

A bit late, but here's another archive sample, created using zip-rs rust crate ( (https://github.com/zip-rs/zip), with compression level 20 Its not directly usable as an application, but here's a sample cli utility that uses it internally (slightly patched since the original is outdated), though you'll need to compile it yourself -> https://github.com/Zapeth/zippy

A little late reply, but I just saw this ticket and would like to provide more information: - mp3 tag lyrics are provided via id3 tags -> https://id3.org/id3v2.3.0#Unsychronised_lyrics.2Ftext_transcription - you'll also see a tag for "Synchronized lyrics", which basically includes timestamps with the lyrics (but for me a first implementation with just unsynchronized lyrics would suffice) - other audio formats may provide lyrics via their respective metadata formats, here's a little overview (last...

mingw compilation issues

Ah, so its literally all checksums accumulated? Then maybe the description in the 7zip interface is a bit misleading, I would still expect "SHA1 checksum for data" to mean "the checksum over the entire selected/specified data". I understand that the result in that case is dependent on the order of the data, but do you think it would be possible to provide that functionality anyway? Maybe the data could be parsed in the order that gets selected in the ui or specified as arguments in cli, that way...

Ah, so its literally all checksums accumulated? Then maybe the description in 7zip is a bit misleading, I would still expect "SHA1 checksum for data" to mean "the checksum over the entire selected/specified data". I understand that the result in that case is dependent on the order of the data, but do you think it would be possible to provide that functionality anyway? Maybe the data could be parsed in the order that gets selected in the ui or specified as arguments in cli, that way the user would...

Ah, so its literally all checksums accumulated? Then maybe the description in 7zip is a bit misleading, I would still expect "SHA1 checksum for data" to mean "the checksum over the entire selected/specified data". I understand that the result in that case is dependent on the order of the data, but do you think it would be possible to provide that functionality anyway? Maybe the data could be parsed in the order that gets selected in the ui or specified as arguments in cli, that way the user would...

Not sure if this is intentional or not, but I have noticed that 7zip's crc function returns different/unexpected checksums for data of multiple files. Simple example: Two textfiles, one containing the character '1', the other containing the character '2' 7zip returned SHA1 checksum for data: 0FB6AB6233E07D3EF15EADE2793C0B8F6FE4385B When checksumming over the merged data (as in, create a third textfile containing the sequence '12') 7zip returns the (expected) SHA1 checksum: 7B52009B64FD0A2A49E6D8A939753077792B0554...