when the new wineasio arrived in the repository, I registered it with
'wine64 regsvr32 wineasio' ...sans the .dll, and it worked.
I have no idea whether any system code cares if the .dll part
is there or not, but accurate status clarifications would be cool.
Speaking of clarifications, running the above ps command, I saw the priority
setting I use in qjackctl (76) was listed as the priority for 'jackdbus auto'.
I then bumped up the priority in /etc/security/limits.conf from 95 to 99,
and upped the priority setting in qjackctl from 76 to 92, higher than
the sound hardwares themselves:
92 FF 1853 132 - /usr/bin/jackdbus auto
90 FF 651 130 - [irq/41-snd_hda_]
90 FF 645 130 - [irq/16-snd_ice1]
87 FF 4600 127 - .59/reaper
87 FF 3243 127 - a2jmidid -j default
Then I did some recordings, and performance was much better,
if in unscientific mode. The old saw was that 89 was the highest setting
to be used in qjackctl, if 99 was set in limits.conf.
Some systems have a folder with second limits.conf file,
/etc/security/limits.d/limits.conf ...sometimes auto-configured with useful settings
when some audio tool is installed...does system code know/care about files
of the same name, in nearby locations?
Does anyone know what is actually happening? I am now using ptiorities of 92 and 99
instead of 89 and 99, with apparently no ill effects.
Is the new jackd code just using 'the old math' but now able to ignore the higher priority setting
I've chosen? Is there code that parses both those numbers, and applies the results to
running audio tools? Is there a ticking timebomb ?
(sorry for all the non-coder jargon
)
could there be an advantage to having a higher priority for
either reaper or a2jmidid, which currently are both at 87?
87 FF 4600 127 - .59/reaper
87 FF 3243 127 - a2jmidid -j default