yes i've tried all the proposed tweaks already, short of formatting.
"unchecked the "Allow computer to turn off this device" option"
"The factory setting for the Interface Mode, Auto, makes sure that any connected computer connection is recognized automatically. Thunderbolt, USB 3, USB 2 and Class Compliant will usually work without any further user interaction. In case of problems the current interface mode can be set manually to a fixed one. This is done under SETUP/REV, Options, Hardware/Diagnosis, Interface Mode."
I know ccleaner, I used it in the past. And those softwares including ccleaner are a bit controversial..
might do a single quick cleaning though, lets see.
downloading now foobar2000.
But this is a comparison test. It means that if I am well under the limit of what the ' Dell/ufx+ OR maudio system '
can do, then both the ufx+ and Maudio will play it easily.
mmmmh... Not sure if you absorb all of the information I post. sigh
Yes i will use more than 6 synths lol !
But current projects has well above 50 synths ! (mentioned that a few times)
More importantly, the point is NOT to freeze tracks to reduce cpu load, its a well-known method indeed, i agree.
The point is to test the limit of the ufc+/dell (mentioned already) vs maudio/dell.
The point is to optimize the setup I have, Maudio does not need to freeze tracks at all.
If the ufx+ needs tracks frozen then 2 only 2 possible reasons:
A: the Dell system is already quite optimized and
unfortunately, bizarrely, disappointingly, the ufx+ handles less than the Maudio (FOR THAT SOFT SYNTHS TEST), for some reason. On the other, the sound quality should be better, and other obvious advantages for the rme. But it would still be strange, because i would believe that, everything the maudio can do the rme can do easily AND MORE.
B : the Dell system is not optimized well enough, so
for the ufx+ to shine and be able to handle for example maybe 6 diva synths at very short rtl, the Dell has to be super fined tuned to the extreme.
The diva project file is my way of doing my personal little "benchmark" on my Dell.
The diva project test is really heavy - ON PURPOSE - (mentioned already) for the sake of testing and debugging only.
Also mentioned a few times is the fact that i've already configured core affinities with process lasso.
To no effect.
Including i/o, memory.
On that note, here is the reply from the bitsum guys:
"You should not set it to Below Normal or Idle. That snippet was trying to convey that, in your example, *other* apps which could interfere with Ableton should be lowered in priority class, rather than Ableton raised in priority class. ProBalance does this automatically.
While you could raise the priority class of Abelton to High or Real-Time, I would not expect it to improve performance or responsiveness.
In addition to process priority classes, each thread in a process has a priority. Ableton almost certainly sets its important threads to real-time (time-critical) priorities. Further raising the priority class of the entire process just won't achieve any additional effect.
I/O priorities and memory priorities aren't likely to matter either.
All this said, Windows PCs have a complex software and hardware environment, with a lot of variables to account for, so it isn't impossible some tweak that shouldn't matter, actually does.
In the end, I'd just leave Ableton alone, let ProBalance do its job, and limit the number of custom tweaks you make."
Drivers are up to date, everything has been flashed with the latest firmwares (mentioned a few times i believe).
About the windows installation: see previous post.