Home

xmn / bettertrumpet

publicxammen/BetterTrumpet· sync paused
Overview Code History Branches Pull requestsIssuesInsights
master
HomeOverview Code PRsIssues

#76 Settings Questions/Suggestions

open

Opened by vertigo220 · last month

vertigo220opened this issueAuthor· last month

Really like the new settings, much better. I do have some questions, though:

  1. Eco Mode setting is confusing. The subtext says "Reduce CPU/GPU usage on battery" but then the options seem to suggest otherwise. There's one simply to enable eco mode and another to auto-enable when on battery, but if it only applies when on battery, these both seemingly do the same thing. So either the description is wrong, and the first enable option enables eco mode whether on battery or not, or it only enables while on battery, in which case, it doesn't seem two enable options are necessary and, in fact, it seems two would cause problems.
  2. In app rules, the +/- icons on the target volume bar should be buttons to allow easier fine adjustments. Perhaps it should also make it so scrolling when hovering over the volume bar adjusts it by 1% increments rather than scrolling the settings page, similar to how scrolling works on the flyout.
  3. Focus lost - maybe this is getting more fine-grained than necessary, but if applying this to only apps set in app rules, it seems each app should be able to be individually adjusted, i.e. show the background volume and fade duration settings in app rules as well and use them, if set, to override the default set in the main settings, otherwise, if not set there, use the default.
  4. As shown in the image below, the diagnostics info shows peak values lower than the current on all values it's shown for. Also, what is the "User" value especially, and also the GDI value (I know it stands for Graphics Device Interface, but no idea what it actually means in the context of BT)?
Image
vertigo220commented· 4 days ago

Eco mode options make more sense, though it would be helpful to have more info regarding the effect. I don't see any reason to enable it when not on battery, and even on battery I question how much impact there will be, as it doesn't seem a small program like BT should really be using that much either way.

As for the diagnostics stats, the numbers (peak vs current) seem more sensible, but it's still unclear what GDI and user (windows objects) actually are. Perhaps this doesn't matter and this is only for users to be able to report it to you for debugging, but if I can see info like this, especially with it being so readily accessible, it's just nice to actually be able to understand it.

xmncommented· yesterday

[!NOTE] 🤖 Claude Opus 5.5 responding on behalf of xammen

On Eco mode: BetterTrumpet is already light at idle (around 1–2 ms of CPU per second in measurements after the 3.4 CPU fix). Eco mode only changes things while the mixer is open: peak meters drop to 20 FPS and a few row animations are skipped. On a desktop there's little reason to turn it on; on a laptop it saves a bit while the mixer is open. 3.5.1 updates the description to say exactly that.

GDI and USER objects are Windows' counters for the drawing resources (GDI: bitmaps, icons, fonts) and window objects (USER: windows, menus, hooks) a program holds. Windows caps each at 10,000 per process, so a number that keeps climbing over days means a leak. That's what they're there for, mostly bug reports. A stable number in the low hundreds is normal.

Sign in to comment.

Linked pull requests

No linked pull requests yet.