Timur Born
 
Anyway, if you set the affinity of the parent process to only use physical cores then the DAW can only set affinity of its threads (aka VST addons) to use said physical cores.
 

That's why I tried Affinity Mask in the MMCSS registry. It doesn't work.
I don't want to add a new tool like Process Lasso, unless that's the only way.
I'm about to abandon hyperthreading.
 

Well, Affinity Mask is one of the registry settings which are said to not be implemented (aka present, but not working).
 
You could at least try to set process affinity manually via Task-Manager to see whether it makes a difference or not. It's done quicker and easier than messing with the registry.

arachnaut

taccess

Well I hope it works for him he sounds exhausted with this issue ...

No that doesn't work.
 
If you have any interest in this topic as it pertains to Reaktor, I welcome you to look over this thread in the Reaktor forums:
 
Managing Behemoths
https://www.native-instruments.com/forum/threads/managing-behemoths.317483/
 
 

It sounds to me like the things you have tried should have done the job if it was going to, unless of course there is that one setting you may have missed . Sometimes I go looking for a different perspective and I would suggest ( and I mean this in a friendly manner ) trying another forum, I do and I try to find specific related forums when needed, not because the advice here is incorrect but you might get that one piece of advice no ones pointed out yet.
Example :https://software.intel.co...onitoring/topic/392519

This place has some hard core hyperthreading mad men and although hyperthreading may not be what you need it may be that someone may point out something that connects those elusive dots.
Remember also even if you have tried in a few other forums that still no reason not to try again somewhere else, the biggest mistake we make is feeling exhausted and confused and settling in on the unresolved. Go harder !
I am sure I will head over there about NUMA, soon to.

All I am saying is stay here and go try there too.

parco

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PriorityControl]
"IRQ8Priority"=dword:00000001
"IRQ18Priority"=dword:00000001
"IRQ0Priority"=dword:00000001
"Win32PrioritySeparation"=dword:00000024

 
and here are my another registry configs. Note that IRQ18 is my TI 1394 card for my Audiofire 4. So just modify the IRQ number to the IRQ of your sound device, or any USB, 1394, thunderbolt or ac-bridge ethernet card which connecting your sound device, so make sure they got their own exclusive IRQ number and not sharing with other hardwares. IRQ 0 is the clock timer of your CPU and IRQ 8 is the clock timer of your BIOS CMOS.

Nice one !

I'm not trying to be difficult here. But what I'm trying to accomplish is mostly for other users, not myself.
I have no personal need for this stuff except as a curiosity.
But others need some help running the stuff.
So DAW-specific solutions or extra tools is not an option.
Setting Affinity using Task Scheduler is a good solution, but there also Mac users.
Right now, turning off hyperthreading is the easiest solution.
 
 

I cannot test this myself at the moment:
 
In Live (and maybe Reaper) have you tried to put a track in between the Reaktor instances? Like track 1 = Reaktor 1, track 2 = empty, track 3 = Reaktor 2? I mean to remember that Live just uses one core per track, aka simply counts up. It's been a long time since I last checked, though.
 
This might be the easiest solution.

Timur Born
I cannot test this myself at the moment:
 
In Live (and maybe Reaper) have you tried to put a track in between the Reaktor instances? Like track 1 = Reaktor 1, track 2 = empty, track 3 = Reaktor 2? I mean to remember that Live just uses one core per track, aka simply counts up. It's been a long time since I last checked, though.
 
This might be the easiest solution.

 
Does that apply to audio and midi tracks in ableton ?
 
So your saying if a 2 core PC fires up ableton :
then track 1 uses - core 1 , track 2 uses - core 2 , then what happens ?
track 3 uses core - 1, track 4 uses core - 2 and keeps repeating ?
That's some pretty handy info for me ! can you confirm i am understanding you correctly ?

parco

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PriorityControl]
"IRQ8Priority"=dword:00000001
"IRQ18Priority"=dword:00000001
"IRQ0Priority"=dword:00000001
"Win32PrioritySeparation"=dword:00000024

 
and here are my another registry configs. Note that IRQ18 is my TI 1394 card for my Audiofire 4. So just modify the IRQ number to the IRQ of your sound device, or any USB, 1394, thunderbolt or ac-bridge ethernet card which connecting your sound device, so make sure they got their own exclusive IRQ number and not sharing with other hardwares. IRQ 0 is the clock timer of your CPU and IRQ 8 is the clock timer of your BIOS CMOS.

Hey i noticed you clock timer is  IRQ0Priority ! Should'nt it reflect the IRQexactly and  be IRQ00Priority ?

taccess

parco

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PriorityControl]
"IRQ8Priority"=dword:00000001
"IRQ18Priority"=dword:00000001
"IRQ0Priority"=dword:00000001
"Win32PrioritySeparation"=dword:00000024

 
and here are my another registry configs. Note that IRQ18 is my TI 1394 card for my Audiofire 4. So just modify the IRQ number to the IRQ of your sound device, or any USB, 1394, thunderbolt or ac-bridge ethernet card which connecting your sound device, so make sure they got their own exclusive IRQ number and not sharing with other hardwares. IRQ 0 is the clock timer of your CPU and IRQ 8 is the clock timer of your BIOS CMOS.

Hey i noticed you clock timer is  IRQ0Priority ! Should'nt it reflect the IRQexactly and  be IRQ00Priority ?

 

So Irq issues...I thought so....Seems some one is proving me right....Yep!
 
 

taccess

Timur Born
I cannot test this myself at the moment:
 
In Live (and maybe Reaper) have you tried to put a track in between the Reaktor instances? Like track 1 = Reaktor 1, track 2 = empty, track 3 = Reaktor 2? I mean to remember that Live just uses one core per track, aka simply counts up. It's been a long time since I last checked, though.
 
This might be the easiest solution.

 
Does that apply to audio and midi tracks in ableton ?
 
So your saying if a 2 core PC fires up ableton :
then track 1 uses - core 1 , track 2 uses - core 2 , then what happens ?
track 3 uses core - 1, track 4 uses core - 2 and keeps repeating ?
That's some pretty handy info for me ! can you confirm i am understanding you correctly ?

I wrote a document about this a long time ago. Currently things are the same for Live, but Sonar has improved.
I just bought Reaper a few days ago to test with it. With its CPU restrictor, it works best for me.
 
http://www.arachnaut.net/Reaktor/This%20is%20the%20result%20of%20a%20series%20of%20tests%20I%20made%20using%20two%20DAWs.pdf
 
I'm currently experimenting with hyperthreading OFF, but I'm not so happy with the resulting performance of non-Reaktor audio projects.
 
I'm also experimenting with CPU affinity masks set with the Task manager, but so far I can't get Affinity masks to stick to an executable, so I might be doing something wrong.