All Things PRO AUDIO

[toleda]

According to the thread you linked it appears that PM on 9900K isn't an option yet

9900K supported in a special build that shipped with the late 2018 iMacs
Simply have not verified 9900K support made it to 10.14.4 or 10.14.5

Also I learned from @pastrychef that other than PluginType=check nothing else is necessary in terms of PM.

Not true, PluginType=1 is mandatory; depending on cpu, other parameters may require setting
In my opinion, native CPU PM is clearly not working on your machine

 

[toleda]

Apparently, 4 out of 8 real/virtual cores do all the work in this Logic Project.

My mistake, confused users and systems
Your 7700K has 4 physical cores and 4 hyperthreads, supports 8 threads as you know
Intel hyperthreading is invisible to applications

So what goes 'wrong' with the Logic project?

No idea
Contact developer

 

[luckyal]

Not true, PluginType=1 is mandatory; depending on cpu, other parameters may require setting. In my opinion, native CPU PM is clearly not working on your machine

@CaseySJ I recall you saying that PM is enabled by using PluginType=true and nothing else. This seems to be in conflict with the statement above, no?

 

[toleda]

Post #61:

Also I learned from @pastrychef that other than PluginType=check nothing else is necessary in terms of PM

Post #68:

I recall you saying that PM is enabled by using PluginType=true and nothing else

For config.plist/ACPI/SSDT/Generate/PluginType/:
"true" is correct (TextEdit) as is YES (Xcode) as is 1 (binary)
"check" is not correct as noted in Post #61

Regarding "nothing else," many users posting to macOS Native CPU/IGPU Power Management did not get native CPU PM with only PluginType=true. A few users were unable to get native CPU PM with PluginType=true and all known PM fixes.

 

[luckyal]

Post #61:

Post #68:

For config.plist/ACPI/SSDT/Generate/PluginType/:
"true" is correct (TextEdit) as is YES (Xcode) as is 1 (binary)
"check" is not correct

As in like so?

 

[toleda]

As in like so?

macOS Native CPU/IGPU Power Management/Post #1/Requirements/3. System Definition/SMBIOS

• Native CPU PM (PluginType=YES (Xcode) or true (text editor))
  • Do not use CloverConfigurator, disables property

I do not use CloverConfigurator, do not know if bug has been fixed.

 

[luckyal]

macOS Native CPU/IGPU Power Management/Post #1/Requirements/3. System Definition/SMBIOS

• Native CPU PM (PluginType=YES (Xcode) or true (text editor))
  • Do not use CloverConfigurator, disables property

I do not use CloverConfigurator, do not know if bug has been fixed.

It appears that way. As a side note however, the instructions above as well as the original post are fairly confusing. It appears that you're pointing folks to a category/sub-category in the config.plist, however, there is no sub-section in the the SMBIOS section of the config.plist that allows a user to address the CPU PM entries, whether you're using Xcode or Clover Configurator. That leads me to believe that you're referring to ACPI/SSDT entries.

 

[toleda]

As a side note however, the instructions above as well as the original post are fairly confusing

Apologies, perhaps you missed these instructions:
macOS Native CPU/IGPU Power Management/Post #1/Installation/5. Clover Settings

1. Mount EFI Partiton
2. Remove EFI/CLOVER/ACPI/Patched/SSDT.aml (ssdtPRgen ssdt, if installed)
3. Xcode/edit config.plist
4. CPU: All Systems/CLOVER/config.plist/ACPI/SSDT/
   • DropOEM/NO
   • Generate/CStates/NO
   • Generate/PStates/NO
   • Generate/PluginType/
     • No entry or NO (with XCPM ssdt or ssdtPRGen ssdt)
     • YES (no PM ssdt)

SMBIOS/Post #1/Settings/CLOVER/config.plist/SMBIOS

"The instructions above" are not a substitute for the original post; each reply has included a link to the same thread for complete and correct CPU PM information.

It appears that you're pointing folks to a category/sub-category in the config.plist, however, there is no sub-section in the the SMBIOS section of the config.plist that allows a user to address the CPU PM entries, whether you're using Xcode or Clover Configurator

config.plist is a Clover document, not macOS. Xcode/CloverConfigurator/text editor are used to edit Clover settings in config.plist. Clover uses config.plist to edit macOS system files prior to macOS starting.

config.plist screenshot shows PluginType is set properly. Without an IOReg, it is not possible to know if PluginType is actually 1 in macOS. As stated previously, IPG screenshot shows CPU PM is not working.

 

[xanderevo]

Sorry I had literally no time to get on the forum,
I have something similar to you as a result of the multithread load spreading with one difference, that last core spike.

Into Logic options the only difference is "Playback & Live Tracks" is set just to Playback, and in my BIOS settings I have the Multi-Threading-Management-Something, I need to post you a screenshot later when I get home.

No way I can play this one on my macbook pro 2015 or my old cheese grater to compare, difference would be abysmal.

Difference is it, I'm on iMacPro 1,1 and bounce it's faster than macmini or imac.

 

[xanderevo]

Those are the results, no difference between 96Khz and 44.100 on the playback just on the cores,
this is on 10.14.3 LPX 10.4.4 I can play 15 tracks smoothly

iStat shows about 83% cpu use, got no overclock just a standard install.

Increasing buffer size from medium and 256 samples however lowers the cpu load.

44.100

96.000

and those were the 8 cores in istat