Skip to content

Add clarification for auto-calculate white channel option#249

Open
marcone wants to merge 2 commits intowled:mainfrom
marcone:patch-2
Open

Add clarification for auto-calculate white channel option#249
marcone wants to merge 2 commits intowled:mainfrom
marcone:patch-2

Conversation

@marcone
Copy link
Copy Markdown
Contributor

@marcone marcone commented Mar 24, 2025

No description provided.

Comment thread docs/features/cct.md
None | No auto white calculation is performed. The white channel of colors can be manually set using the `White channel` slider in the user interface, RGB-only effects and most realtime sources will leave the white channel off.
Dual | The `White channel` slider is present in the UI and works the same as in `None` mode, however if the slider value is 0 (far left), the `Brighter` mode is used for auto white calculation. This is the default auto white mode.
Max | Sets white to the value of the brightest RGB channel. This is good for white-only LEDs without any RGB.
Max | Sets white to the value of the brightest RGB channel. This is good for white-only LEDs without any RGB, however note that using any value other than "None" will cause the light to be treated as having RGB channels, so the color picker will show in the web UI.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This is true for any mode, not just Max. Perhaps move it out of the spreadsheet.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This is true for any mode, not just Max. Perhaps move it out of the spreadsheet.

I mentioned this here because "Max" is the only option where it specifically says that it is "good for white-only LEDs". Or are you saying that the part about it being good for white-only LEDs should be removed?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

You seem obsessed with "white only". 😄 Sorry, no offense intended.
Any option is good (or possible) for "white only", depending on what you need or want (or what your external devices expect, yes don't forget that).
I'm saying that choosing anything but "None" will treat your output as RGB and not RGBW or W.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

You seem obsessed with "white only". 😄 Sorry, no offense intended.

i'm just trying to understand. As a new user, it is confusing to me to see a full RGB color picker when I only have plain white LEDs connected, have set all the outputs to be white, and chosen the white handling option that is documented to be good for white-only LEDs. I can't imagine I'm the only person in the whole world who is confused by this, so I'm trying to figure it out and hopefully update the documentation so it's more clear to other new users.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

What further adds to the confusion is that if I set the first 3 outputs to "None" and the 4th output to "Max", I don't get the color wheel, but if I set any of the other outputs to "Max" then I do get the color wheel. That seems like an actual bug to me. This is with the build you asked me to try the other day though, so maybe it's related to that. I can try one of the stable builds if you want.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The UI adapts to the main segment. Any segment can be main and it is distinguished by a lighter gray in UI. Also affecting UI are selected segments (the ones with checkmark).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I only have one segment, which contains all 4 outputs.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Then you have your answer. If one of the outputs is RGB (as when Auto white is enabled) UI will respond as segment being RGBW, separate outputs into segments and you'll have control individually.
You can automatically create segments from outputs using selection box in settings.

Please continue discussion either on forum or on Discord.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Then you have your answer

No. Perhaps I didn't explain myself well. I have 4 outputs, all in the same segment, all "PWM White". If I set the "Auto-calculate W channel from RGB" option for each of them like so:

0 : None
1 : None
2 : None
3 : Max

then I don't see the color wheel in the color tab, but if I set them e.g. like so:

0 : None
1 : None
2 : Max
3 : None

then I do see the color wheel. Again, all 4 outputs are in the same segment, and I have only one segment.

@softhack007 softhack007 added the needs_rework PR needs improvements before merging label Apr 30, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 1, 2026

Warning

Rate limit exceeded

@softhack007 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 54 minutes and 57 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 92f6c6d0-7c10-4aa9-b159-b5c67b053f81

📥 Commits

Reviewing files that changed from the base of the PR and between 16b2d5e and 810a478.

📒 Files selected for processing (1)
  • docs/features/cct.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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
Review rate limit: 0/1 reviews remaining, refill in 54 minutes and 57 seconds.

Comment @coderabbitai help to get the list of available commands and usage tips.

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

Labels

needs_rework PR needs improvements before merging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants