Skip to content

Conversation

borisowww
Copy link

@borisowww borisowww commented Aug 27, 2025

This PR adds the option to set a custom output resolution based on width input, for edge cases where a lower/higher resolution is needed.

Summary by CodeRabbit

  • New Features

    • Support for a custom capture resolution by specifying a desired width; height is auto-calculated from the current aspect ratio while existing presets remain unchanged.
  • Notes

    • Enables finer control over capture output size without requiring manual height input.

Copy link

coderabbitai bot commented Aug 27, 2025

Walkthrough

Adds a new public enum variant Resolution::Custom { width: u32 } and extends value() to compute dimensions for Custom using width and aspect_ratio (height = floor(width / aspect_ratio)). Other variants unchanged; Resolution::Captured still panics on value().

Changes

Cohort / File(s) Summary of Changes
Resolution enum enhancement
src/capturer/mod.rs
Added public variant Custom { width: u32 }. Updated value() with a new match arm returning [width, floor(width / aspect_ratio) as u32]. Existing variants untouched; Captured still panics on value().

Sequence Diagram(s)

sequenceDiagram
  actor Caller
  participant Resolution
  Note over Resolution: New variant: Custom { width }
  Caller->>Resolution: value(aspect_ratio)
  alt Custom
    Resolution->>Resolution: height = floor(width / aspect_ratio)
    Resolution-->>Caller: [width, height]
  else Fixed variants
    Resolution-->>Caller: [predefined_width, predefined_height]
  else Captured
    Resolution-->>Caller: panic
  end
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I hop through enums with a twitch and spin,
A Custom width slips softly in.
I floor the ratio, stack the frame,
Pixels tidy, none to blame.
Nose up, I stamp — the change begins! 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.


📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between f3add49 and 80d7832.

📒 Files selected for processing (1)
  • src/capturer/mod.rs (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/capturer/mod.rs
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
src/capturer/mod.rs (1)

23-27: Plan a major semver release and document the new Custom variant

I’ve confirmed that all internal match expressions over Resolution either explicitly handle Custom (in capturer/mod.rs) or use a catch-all arm (in the engine backends), so there are no missing pattern arms in this repo. However, since Resolution is a public enum without a non_exhaustive attribute, adding Custom is a breaking API change for downstream users who match exhaustively.

• Mark this release as breaking (major semver bump) and call out the new Resolution::Custom variant in your changelog or upgrade guide.
• Optionally, annotate the enum with #[non_exhaustive] if you want to avoid future breaking changes when adding variants.
• Validate that callers never construct a zero-width Custom { width: 0 }. You can either:
– Add a runtime check at each construction site (e.g. assert!(width > 0)), or
– Switch to using NonZeroU32 for type-level safety:
```rust
use std::num::NonZeroU32;

pub enum Resolution {
    // …
    Custom { width: NonZeroU32 },
    #[default]
    Captured,
}
```
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between c03f15a and f3add49.

📒 Files selected for processing (1)
  • src/capturer/mod.rs (2 hunks)

Comment on lines 38 to 40
Resolution::Custom { width } => {
[width, width / aspect_ratio.floor() as u32]
}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix incorrect height calculation (integer division, zero-division risk).

This uses integer division by aspect_ratio.floor() as u32, which:

  • Produces wrong heights (e.g., 16:9 → floor=1 → height==width).
  • Can panic for 0 < aspect_ratio < 1 (floor→0, divide-by-zero).

Align with other variants: compute using float division and floor the result.

-            Resolution::Custom { width } => {
-                [width, width / aspect_ratio.floor() as u32]
-            }
+            Resolution::Custom { width } => {
+                let height = (width as f32 / aspect_ratio).floor() as u32;
+                [width, height]
+            }

Optional (keep encoder-friendly even dimensions):

-            Resolution::Custom { width } => {
-                let height = (width as f32 / aspect_ratio).floor() as u32;
-                [width, height]
-            }
+            Resolution::Custom { width } => {
+                let mut height = (width as f32 / aspect_ratio).floor() as u32;
+                // make even
+                height &= !1;
+                let width = width & !1;
+                [width, height]
+            }

Add unit tests (example):

  • width=1280, ar=16/9 → [1280, 720]
  • width=1000, ar=21/9 → [1000, 428]
  • width=800, ar=9/16 (portrait) → [800, 1422]
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Resolution::Custom { width } => {
[width, width / aspect_ratio.floor() as u32]
}
Resolution::Custom { width } => {
let height = (width as f32 / aspect_ratio).floor() as u32;
[width, height]
}
🤖 Prompt for AI Agents
In src/capturer/mod.rs around lines 38-40, the Custom branch computes height
using integer division by aspect_ratio.floor() as u32 which yields wrong results
and can divide-by-zero; replace that with a float-based computation: cast width
to f64, divide by aspect_ratio (as f64), floor the result and cast back to u32
to get the height; add a guard for aspect_ratio == 0.0 (return a sensible
default or error) and optionally make the height even by incrementing if odd;
add unit tests for the provided cases (1280 @ 16/9 -> 720, 1000 @ 21/9 -> 428,
800 @ 9/16 -> 1422).

@borisowww borisowww force-pushed the add-custom-resolution-option branch from f3add49 to 80d7832 Compare August 27, 2025 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant