Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Correct power output detail for the every channel used case #749

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

rtertiaer
Copy link
Contributor

What does this change intend to accomplish?

This PR attempts to add clarity around our all-channel peak output power (am I even saying that right?)

I'd like feedback on how this is represented; I will go through the process of stamping out a new rendered manual and hosting it upstream once the verbiage here is correct.

Checklist

  • If applicable, have you updated the documentation/manual?

@rtertiaer rtertiaer requested a review from Lohrer June 14, 2024 15:17
@rtertiaer rtertiaer marked this pull request as ready for review June 14, 2024 15:17
@rtertiaer rtertiaer force-pushed the add_power_output_detail branch from 79d6ca4 to 902ec5d Compare June 14, 2024 15:21
@rtertiaer rtertiaer force-pushed the add_power_output_detail branch from 902ec5d to 8d70b74 Compare June 14, 2024 15:22
Comment on lines 24 to 26
|Speaker Power | 55 WPC @ 4 Ω |
| | 32 WPC @ 8 Ω |
| | 23 WPC all-channel driven power |
Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm not sure how you want to format this in here, but these measurements are for <0.1% THD+N and taken at 1kHz. Both of those are important because they strongly influence the result. For example the much higher 10%THD (note the lack of +N which also makes this weaker) of the amp chip spec results in a much higher output wattage, but when tested I had to clip the signal to get 10% THD.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm putting this in front of you largely cuz I have no idea how to properly represent that data; this is not my area of expertise.

Could you provide a recommendation on how you would represent it?

@rtertiaer rtertiaer marked this pull request as draft June 19, 2024 14:42
@linknum23
Copy link
Contributor

@Lohrer where is this at? Should we just try to merge this as-is?

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.

3 participants