more intelligently experiment with the optimal number of cores to use which is the one control variable available in MainStage. It I had this data I would understand what is happening much better and would be able to e.g.
Yes, we get max and min - but you can't see how quickly the frequency is changing on each core or whether one core is always high and the other low. The header documentation states that the 'available' bool pointer will be set based on availability and that the result (return bool value) will be True on succe. But I can't prove this very easily atm in Intel Power Gadget as I can't see per-core frequency data. CC Good afternoon, In the latest Power Gadget for OSX (3.7.0), the header PowerGadgetLib.h has function 'PGIsPlatformEnergyAvailable'. My theory is the issue relates to different per core frequency oscillation/throttling behaviour because MainStage requests a very high freq and keeps the CPU temp near 100 degrees. And it's clear from the extremely helpful MainStage CPU meter the problem is the virtual instrument processing time (affects all virtual instruments in the same way).
Macos intel power gadget for mac os#
(The audio processing time is essentially the percentage of audio buffer required and the net result revealed by MainStage metering & actual glitching is I need at least 2x buffer size (latency) on the Mac Mini.) It's pretty mystifying given all other variables (OS, drivers, etc) are identical. For those who might think its interesting to see how much power their CPU is actively using, check out Intels Power Gadget for Mac OS X. I am trying to understand why my Mac Mini audio processing times in MainStage (using a particular patch with several virtual instruments) are about 2.5x those on my MacBook Pro (both with similar 6-core Intel chips). I am wondering if there is a way to see per-Core frequency data in Intel Power Gadget (macOS)?
0 kommentar(er)
