Audacity 2.1.2 Alpha - CPU usage

[cmac185]

Using Yosemite, I see CPU usage about normal, about 35% until I minimize the window then the cpu usage about doubles, 75%+. Hiding the window does the same thing. With 2.1.1 it runs about 37 - 38% normally, minimized is about the same, but hiding (CMD+H) drops the CPU usage to about 10% which is nice if other things have to be going on that need CPU time. I realize that normal operation is just that, normal and probably used 99.9% of the time, but I mention it because it may be important for some other reason I’m not aware of.

I haven’t tried that on El Capitan.

Cliff

[Gale_Andrews]

@cmac185

Using Yosemite, I see CPU usage about normal, about 35% until I minimize the window then the cpu usage about doubles, 75%+. Hiding the window does the same thing. With 2.1.1 it runs about 37 - 38% normally, minimized is about the same, but hiding (CMD+H) drops the CPU usage to about 10% which is nice if other things have to be going on that need CPU time. I realize that normal operation is just that, normal and probably used 99.9% of the time, but I mention it because it may be important for some other reason I’m not aware of.

Thanks, Cliff.

I don’t see what you see with “hiding” on my Mac Mini

Model Name: Mac mini
Model Identifier: Macmini5,1
Processor Name: Intel Core i5
Processor Speed: 2.3 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache (per Core): 256 KB
L3 Cache: 3 MB
Memory: 4 GB

I guess it’s specific to portable Macs that “save power”. Certainly worth mentioning. Do any Apple apps do that?

I can’t test “minimize” in 2.1.2-alpha because the window buttons are always under the menu bar for me, wx3 removes the Window menu, and COMMAND + M and COMMAND + OPTION + M don’t work (I have default Keyboard Preferences). Do you see that shortcut issue?


Gale

[cmac185]

Model Name: MacBook Pro
Model Identifier: MacBookPro5,3
Processor Name: Intel Core 2 Duo
Processor Speed: 2.66 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache: 3 MB
Memory: 8 GB

Regarding the CPU load changing, both Garageband and Quicktime cut their CPU usage to around 1/3 of what it was when displayed in the foreground when minimized. Interestingly, they both cut the usage way down the same amount when either minimized or hidden where Audacity 2.1.1 or 2.1.0 made little difference when minimized, but the major difference was when hidden. I’ve always assumed that the saving of having to display the moving track data when the app was hidden was the help, but maybe not.

Same here regarding the window menu item, but the bar with the window buttons are still all visible here on Yosemite and El Capitan. I have the same shortcut issues that you have. They work on other windows and Audacity 2.1.0 & 2.1.1, but not on Audacity 2.1.2A. I’ve seen that problem with the buttons being under the menu bar in some other programs in the past, but I haven’t seen it for some time now.

FWIW, the issues are the same on El Capitan including CPU.

Cliff

[Gale_Andrews]

@cmac185

Regarding the CPU load changing, both Garageband and Quicktime cut their CPU usage to around 1/3 of what it was when displayed in the foreground when minimized. Interestingly, they both cut the usage way down the same amount when either minimized or hidden where Audacity 2.1.1 or 2.1.0 made little difference when minimized, but the major difference was when hidden. I’ve always assumed that the saving of having to display the moving track data when the app was hidden was the help, but maybe not.

Thanks I made a note of this but I would want to see reports on other portable Macs before putting it on Bugzilla.

If it makes any difference my typical CPU use with Audacity recording is about 15%.

@cmac185

Same here regarding the window menu item, but the bar with the window buttons are still all visible here on Yosemite and El Capitan.

I was able to get the window buttons unhidden by autohiding the Dock (and Leland has a patch that makes that workaround un-necessary).

So I can confirm now that on my Mac, minimising also makes no difference to CPU usage.


Gale

[cmac185]

If it makes any difference my typical CPU use with Audacity recording is about 15%.

Maybe your Mini with the i5 has more muscle than my MBP. GarageBand draws about the same CPU as Audacity and it’s not displaying as much changing stuff so it seems to me that Audacity isn’t too far out of line when in the foreground.

I have the Dock autohiding so that explains why the buttons appeared here.

Cliff