Jump to content

Jim Hurley

Members
  • Content Count

    79
  • Joined

  • Last visited

  • Days Won

    1

Jim Hurley last won the day on March 1 2019

Jim Hurley had the most liked content!

Community Reputation

43 Excellent

About Jim Hurley

  • Birthday 03/15/1952

Recent Profile Visitors

686 profile views
  1. This project is one of several that I use to test for dropouts and performance issues. I have a 9900K running at 5.1 gHz. I set the buffer to 144 samples at 48kHz and I run the WASAPI exclusive drivers using the 64-bit double precision engine, Pow-r 3 dithering. The project uses 20 instances of MassiveX using a brutal preset and 64 notes (voices). I don't see any issues at all.
  2. But on the other hand, the original template files seem to have an embedded image saved that might be that icon. If you save your own template that part is removed and the icon path is saved.
  3. In the CWP files they are saved as a relative path and not copied anywhere. I would expect the template CWT files have the same behavior.
  4. I call that batch file my 'Affinity Gauntlet'. ✊
  5. Yes. I often run Reaktor in standalone mode using this batch file to put eight copies in their own core. (Reaktor only uses a single core for its audio). In an even more extreme case I can just select the best performing cores as most CPUs these days have varying qualities of core performances. I have 4 or 5 good ones and 3 poorer performing ones, I believe that is fairly common in the Silicon Lottery. I don't believe my CPU is above average in any regard. The '/high' means set high priority.
  6. In Task Manager (right click on process and choose Set Affinity):
  7. I have a 9900K (8 core/16 thread - 5.1Ghz) system with a custom waterblock loop (420 mm radiator/ EK Magnitude wb) and fairly good overclocking capabilities. It is about 2 years old now and it has performed quite well in things like Folding@home and neural net training, beside audio. I use Windows Pro 20H2 build 19042.662. I built a Reaktor ensemble that allows me to dial in the amount of load it uses on an audio track from about 10% load to 90% load (as reported by the Reaktor CPU load indicator. Although I normally don't worry much about audio settings, when I need some extreme performance, I find that hyperthreading might get in the way. In the case of using this Reaktor tool, it is immediately obvious - but that is probably because it is the same process running in the hyperthreads, so sharing CPU resources between the two logical cores is not optimal. Here are some images of the results. The first is showing 8 copies of the tool set at load = 60%. I hear audio glitches sporadically at this setting, but not when the load is 50%. Next, if I set the CPU affinity to Cakewalk to use only the even cores I can run the load up to 90% with no glitches at all. I use the 'Ultimate Performance Power Plan': And I use MSI Util to set all interrupts in the MSI mode (but I don't think this matters very much, I don't see much different when normal interrupts are on): Here are my driver settings: and Aud.ini: And a short Latency Mon run:
  8. Intel® Turbo Boost Max Technology 3.0 was introduced into Windows 10 recently, it is also called something like 'Favored Cores'. It can be read about here: https://www.intel.com/content/www/us/en/architecture-and-technology/turbo-boost/turbo-boost-max-technology.html I was wondering what might be the impact of that on Cakewalk and the selection of the thread scheduling models. For those who don't know, this is only available on certain models of Intel processors. It adds a driver to Windows and adds some firmware support to the chip's p-code to support thread movement to different cores without OS involvement. Supposedly it will help thermals and help prevent thermal limiting. Or that is how I read it. My naive thoughts are that moving a process from one core to another will wreak havoc to the cache memory. I ran some tests using a high load Reaktor ensemble running standalone outside a DAW and saw this: (R6-CPU-all-cores.png). Notice the spread in load across all cores. There is no evidence that any core is stressed. Probably that is due to the low sampling rate or averaging of Task Manager. Then I set affinity to use only Core 7: (Reaktor-set-affinity.png). And then I ran again and see Core 7 showing the load Reaktor reports: (Reaktor-using-only-one-core.png). I don't know if or how this could be disabled and it does make measuring and testing loads a bit tricky. Does anyone know more about this new feature and what it means for us in audio?
  9. I see a different policy page (Win 10 1903 {Version 10.0.18362.207}). It seems to say that policy is no longer supported. (yellow highlight).
  10. Here are some graphics - an icon and a track PNG Massive X.ico
  11. I have 'Hide related VST2 plugins' set, and I have MeldaProduction VST2 and VST3 plugins installed. Cakewalk 2019.03 shows both plugins in the plugin list. Is there something else needed to hide them?
×
×
  • Create New...