Skip to content

Conversation

@mertalev
Copy link
Member

Description

The max bitrate can be set with different units at the end. However, if no unit is provided, the default is to interpret it as bytes. This is almost definitely not what they meant; it's better to assume kbps instead.

@bo0tzz
Copy link
Member

bo0tzz commented Jan 11, 2025

Is this something we need to call out in the changelog in case it's messing up someone's expected setting?

@mertalev mertalev changed the title chore(server): default max bitrate unit to kbps chore(server)!: default max bitrate unit to kbps Jan 11, 2025
@mertalev
Copy link
Member Author

Is this something we need to call out in the changelog in case it's messing up someone's expected setting?

Good point, it counts as a breaking change since it's possible someone actually uses bytes.

@alextran1502 alextran1502 merged commit fef36e6 into main Jan 12, 2025
41 of 42 checks passed
@alextran1502 alextran1502 deleted the chore/server-default-bitrate-unit branch January 12, 2025 04:09
yosit pushed a commit to yosit/immich that referenced this pull request Jan 13, 2025
arctic-foxtato pushed a commit to arctic-foxtato/immich that referenced this pull request Jan 14, 2025
agross added a commit to agross/ansible-home-network that referenced this pull request Jan 24, 2025
vladd11 pushed a commit to vladd11/immich that referenced this pull request Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants