Skip to content

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

Open
@fighter-01

Description

@fighter-01
No description provided.

Activity

sz3

sz3 commented on Mar 6, 2025

@sz3
Owner

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

fighter-01 commented on Mar 6, 2025

@fighter-01
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

sz3 commented on Mar 6, 2025

@sz3
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      What do the generated default file names, such as 111.52532, represent respectively? What is the naming rule? · Issue #42 · sz3/cfc