Jump to content

Panu Pentikäinen

Members
  • Posts

    319
  • Joined

  • Last visited

Posts posted by Panu Pentikäinen

  1. Disabling plug-ins (additive):

    1. Disable Waves CLADrums - 41%
    2. Disable ValhallaPlate => CPU usage 41%
    3. Disable 5 FabFilter Pro-R instances => 41-42%
    4. Disable FabFilter Pro-MB => 42%
    5. Disable FabFilter Pro-L2 => 46%
    6. Disable three more FabFilter Pro-L2  => 51-52%
    7. Disable 5 FabFilter-Q3 => 48-53%
    8. Disable FabFilter Pro-DS => 47%
    9. Disable one more FabFilter Pro-R => 46%
    10. Disable FabFilter Pro-L2, DS, Q3, Q3, C2, C2, Q2, Q3, Q3, Q3 => 54%
    11. Disable FabFilter Pro-C2, Sonitus:Delay, Sonitus:Gate, Sonitus:Compressor, Q2, C2, C2, => 63%
    12. Disable Sonitus:Gate, Sonitus:Gate, Q3, Cakewalk Channel Tools, Cakewalk Channel Tools, Q2,  C2, Q3 => 57%

    Conclusion: Plug-ins are the throttleneck, especially the old Sonitus DirectX plugins  [in thist very project at least].

    Conclusion 2: I'm a big fan of FabFilter plug-ins! :) L2, DS, Q3, C2 and Pro-R are my goto tools now.

  2. I tested some settings to see if I could increase CPU utilization.
    - Cakewalk always restarted after making changes to settings.
    - Same project in every test.

     

    1. BounceBufSizeMsec=250
      CPU utilization dropped from 41 % to 34 %.
       
    2. Increase audio interface buffer 128 => 512.
      CPU usage: 38 %.
       
    3. Enable Plug-in Load Balancing
      CPU usage: 38 %.
       
    4. Disable Plug-in Load Balancing
      ThreadSchedulingModel from 1 to 2.
      CPU usage: 38 %.
       
    5. Close all open 5 FabFilter plugin GUIs.
      CPU usage: 28%. (Weird.)
       
    6. FabFilter plugins open again.
      ThreadSchedulingModel  from 2 to 1.
      ExtraPluginBufs=5
      CPU usage: 38 %.
       
    7. ThreadSchedulingModel=1
      Set  EnableSetThreadIdealProcessor=False
      ExtraPluginBufs=5

      CPU usage: 41-42 %.
       
    8. Set  EnableSetThreadIdealProcessor=False 
      MixThreadCount=8
      ExtraPluginBufs=5

      CPU usage: 40%
       
    9. Set  EnableSetThreadIdealProcessor=False 
      MixThreadCount=4
      ExtraPluginBufs=5

      CPU usage: 32%
       
    10. Set  EnableSetThreadIdealProcessor=False 
      MixThreadCount=32
      ExtraPluginBufs=5

      CPU usage: 38-39 %, peaking to 55% every few seconds

     

    Summary:

    Best settings found so far for this very project:

    EnableSetThreadIdealProcessor=False 
    MixThreadCount=8
    ExtraPluginBufs=5

    MixThreadCount=32 was not bad either because it created some CPU bursts.

    To be continued...

     

  3. Just wondering why Cakewalk does not utilize 100 % CPU or Disk when exporting a mix with Fast Bounce setting on. Is there something to tweak in the Preferences to get the most of the system?

    For example, in the screen capture I was mixing a typical small project with only 32 tracks, and 20 FX. CPU usage is 41% while disk usage is barely 3%. For comparison, Premiere and AE in the same machine keep system 100% utilized during rendering.

     

     

     

    image.png

  4. <NERD ALERT>

    LatencyMon reports:

     image.png.eca6ed2238dabe810b0fd76a921e80ee.png 

    SYSTEM INFORMATION
    _________________________________________________________________________________________________________
    OS version:                                           Windows 10 , 10.0, build: 17763 (x64)
    Hardware:                                             MS-7B17, Micro-Star International Co., Ltd., MPG Z390 GAMING PRO CARBON (MS-7B17)
    CPU:                                                  GenuineIntel Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
    Logical processors:                                   16
    Processor groups:                                     1
    RAM:                                                  32722 MB total

    Highest measured interrupt to process latency (µs):   192,20
    Average measured interrupt to process latency (µs):   3,022335

    Highest measured interrupt to DPC latency (µs):       159,70
    Average measured interrupt to DPC latency (µs):       1,022943

     REPORTED ISRs
    _________________________________________________________________________________________________________
    Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

    Highest ISR routine execution time (µs):              195,605556
    Driver with highest ISR routine execution time:       dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

    Highest reported total ISR routine time (%):          0,012871
    Driver with highest ISR total time:                   dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

    Total time spent in ISRs (%)                          0,012907

    ISR count (execution time <250 µs):                   47811
    ISR count (execution time 250-500 µs):                0
    ISR count (execution time 500-999 µs):                0
    ISR count (execution time 1000-1999 µs):              0
    ISR count (execution time 2000-3999 µs):              0
    ISR count (execution time >=4000 µs):                 0

    REPORTED DPCs
    _________________________________________________________________________________________________________
    DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

    Highest DPC routine execution time (µs):              728,506111
    Driver with highest DPC routine execution time:       ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

    Highest reported total DPC routine time (%):          0,004141
    Driver with highest DPC total execution time:         nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 388.13 , NVIDIA Corporation

    Total time spent in DPCs (%)                          0,009174

    DPC count (execution time <250 µs):                   192967
    DPC count (execution time 250-500 µs):                0
    DPC count (execution time 500-999 µs):                1
    DPC count (execution time 1000-1999 µs):              0
    DPC count (execution time 2000-3999 µs):              0
    DPC count (execution time >=4000 µs):                 0

    </NERD ALERT>

    image.png

    • Like 1
  5. CPU cooling: Noctua NH-D15 CPU Cooler ( https://noctua.at/en/nh-d15 ).

    noctua-cooler.jpg.f842f4e4fe74938566e53064e66e5c4d.jpg
    Noctua NH-D15

    I set Noctua to 'silent mode' and it's just like that: at low stress fans stay still and thus the CPU cooling is totally silent. This was a very positive surprise for me!

    Power supply is Corsair CX750M. It's quiet in normal usage (like Cakewalk) but user reviews hint that it gets louder under high stress. I haven't noticed raise of sound level yet, not even while rendering After Effects projects. 

     

    • Like 2
  6. DPC Latency Checker reported normal Windows 10 values: around 1100 us with no spikes.  It is much more than in XP or 7 but still OK.

    image.png.3d9a6eb09ae3b39dff61699df45a38f4.png

     

    And here's Task Manager / CPU Performance while Cakewalk is playing full mixed 80 track, heavily produced mix:

    image.png.6b7abe268ad82d5a4bbcbe89f83f6af4.png

    Disk usage (audio is on M drive) is 2% (!) and CPU usage 12%.  Obviously the mix needs more tracks and plugins. ;)

     

     

     

    • Like 1
  7. Motherboard is MSI Z390 Gaming Pro Carbon Intel Z390.  However, I'm not totally satisfied with it: using m.2 drives disables two of the total six SATA 6 Gb/s ports. Thus there are four SATA + two m.2 available, not six SATA + two m.2.  So I have only one SATA port free because one is for the DVD drive and two for the SSDs.

     

  8. Hello, Windows 10!

    One Win7 user has left the building, one new Windows 10 user already on the door.  I built a new PC for my studio:

    Storage: 1 TB m.2 for the programs, 2 TB for projects, 1 TB for mixes and soundbanks. Separate file server for archives.
    CPU is i9-9900 which is $150 overpriced but fast with native 5 GHz speed and 8 cores. It's a long way from my first Sharp MZ-821 home computer although it had the full 64k RAM.
    RAM: only 32 GB at this time but there's room left for another 32 GB.
    Graphics card: GTX 1070 from my old system.

    Something that I noticed immediately on the first CbB test: enabling "Plug-In Load Balancing" made audio crack badly. Disabling healed audio for a while but playing a heavy project caused audio crack again. I opened the Task Manager and noticed how CPU speed varied all the time. I decided to set it to fixed speed all the time and adjust Windows power options to maximum performance. After that everything started to work perfectly.

    64-bit Double Precision Engine is on. Every setting is pretty much on factory defaults.  Cakewalk runs smoothly on RME buffer size 48 but unfortunately Adobe Audition couldn't handle it properly. 64 works for both programs but for now I went back to more conservative setting, 128.

    ThreadSchedulingModel=1 (default). It's 2 on my old system but I don't have no idea what this setting does. Help on Preferences window says:
    0 = Legacy Spin
    1 = Legacy Wait-for-single-object
    2 = Producer/Consumer.

    I'll test the 2 option later.

    I tested  multi-track recording by recording three hours, 18 tracks. Writing 8 GB recorded audio took only about 10 seconds. Solid state and m.2 drives make a huge difference! Exporting projects is also ridiculously fast.

    Conclusion:
    - Plug-In Load Balancing may not work on every system
    - Set CPU speed to fixed.

    • Like 4
  9. Say you want to route all tracks in a Track folder to a new bus. It goes like this:

    * Select tracks.
    * Hold Ctrl key down
    * Open list of outputs
    * Find the desired output
    * Click it.
    * Release the Ctrl key.

    This works ONLY if you press the Ctrl key thru the all steps.

    My feature request: It should be enough to hold the Ctrl key until the list of outputs is opened. If there are lots of outputs available (you may have dozens of hardware outputs, buses, patch points, AUX sends), it may take a while to find the right destination --- and you need to hold the Ctrl button down all the time.

    Same applies to selecting inputs. For example, if you have a track folder dedicated for vocal tracks and you want to reassign input of 10 tracks to a new input channel, you have to hold the Ctrl key down during the whole selection process.

    Please support this even if you don't have this many I/Os...

  10. There was some discussion about this year or two ago. Unfortunately it would be way too laborous project and stall development of everything else for a long period and it's thus very unlikely to happen.

    There will be no fixes to CAL, either.

     

×
×
  • Create New...