Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

What do the generated default file names, such as 111.52532, represent respectively? What is the naming rule? #42

Open
fighter-01 opened this issue Mar 6, 2025 · 3 comments

Comments

@fighter-01
Copy link

No description provided.

@sz3
Copy link
Owner

sz3 commented Mar 6, 2025

The first number is "encode id". It increases sequentially every time a new file is encoded, and loops at 127 since only 7 bits are used. Its main purpose is to allow multiple files of the same size to be decoded within the same session. (it starts at 109 for arbitrary-yet-slightly-interesting bit pattern reasons to give the color correction more to work with...)

The second number is the compressed file size. Combined, the encode_id+size pair is treated as a unique id for the data -- decoded frames that match are collected under whatever their id is. The current naming scheme (until filename support is added) just reflects that back to the user. 🙂

@fighter-01
Copy link
Author

If two files are of the same size, does it mean that their names are the same, for example, both are 111.52532?

@sz3
Copy link
Owner

sz3 commented Mar 6, 2025

If two files are of the same size, does it mean that their names are the same, for example, both are 111.52532?

The second number will be the same. The full name will be the same only if the autoincrementing encode_id (the first number) happens to be the same.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants