My question is not about dual boot. My question is if I can clone the disk to do the test without the license decaying or requiring a new registration.
I see. Cloning disk should be fine as long as hardware configuration remains the same. 
Okay. Very pleased
With pleasure.
Fidelizer 8.10 released â Improved core isolation optimization and compatibility with ExerciseStabilizer/ExtremeStabilizer
After releasing Fidelizer 8.9 with some changes to support more cases, I realized two things from customerâs feedback. First is no feedback from customers configuring processor to have specific cores turned off. Next is some people prefer 8.8 sound.
After realizing how this new change doesnât actually improve customerâs satisfaction, I changed my approach to fully focus on most common implementation with 2 cores per floating point unit and optimize core isolation to handle physical/logical cores better.
Now non-audio processes wonât touch cores in first FPU and focus more on logical cores if thereâs no enforcement to last core only. Media Player Application will focus on physical cores. ExerciseStabilizer/ExtremeStabilizer is now compatible with Fidelizer too.
As a result, Fidelizer 8.10 has reached a new high improving synergy between Windows audio thread, media player applications, and non-audio processes. This update is very important and I highly recommend everyone to install this update.
Changelog for version 8.10
Free
-Changed processorâs core detection back based on common implementation of 2 cores per FPU unit
-Disabled Apply Core Isolation Policy option in free version as it does nothing without components from Plus/Pro version
-Increased progress dialog size and adjusted all progress dialogsâ size uniformly
-Improved process affinity optimization on non-audio processes to use logical cores and leave first cores in FPU alone
-Improved software compatibility with ExerciseStabilizer and ExtremeStabilizer
Plus
-Changed default option to not enforce non-audio core to last physical/logical core only
-Changed failing license verification allow main dialog access for uninstallation and contact support
-Changed processorâs core detection back based on common implementation of 2 cores per FPU unit
-Improved Core Isolation Policy to handle core affinity of Windows audio thread and media player applications better
-Improved process affinity optimization on non-audio processes to use logical cores and leave first cores in FPU alone
-Improved software compatibility with ExerciseStabilizer and ExtremeStabilizer
-Increased progress dialog size and adjusted all progress dialogsâ size uniformly
-Replaced âAudio Player (without network connection)â audio profile with âDisable/Stop network servicesâ option in Advanced configuration
Pro
-Changed default option to not enforce non-audio core to last physical/logical core only
-Changed failing license verification allow main dialog access for uninstallation and contact support
-Changed processorâs core detection back based on common implementation of 2 cores per FPU unit
-Improved Core Isolation Policy to handle core affinity of Windows audio thread and media player applications better
-Improved process affinity optimization on non-audio processes to use logical cores and leave first cores in FPU alone
-Improved software compatibility with ExerciseStabilizer and ExtremeStabilizer
-Increased progress dialog size and adjusted all progress dialogsâ size uniformly
-Replaced âAudio Player (without network connection)â audio profile with âDisable/Stop network servicesâ option in Advanced configuration
Download: Fidelizer 8.10
Upgrade: Fidelizer Upgrade Program
You can download latest version of purchased Fidelizer software from the same download link that we sent in email before. If you are not sure where to download purchased Fidelizer software, feel free to contact us and request software download link.
Hi. If you tick âApply Core Isolation Policyâ option on HQPlayer application, it will restrict some cores and can affect HQPlayerâs application performance with CUDA offload.
If you use HQPlayer with CUDA offload or intensive DSP, I recommend to leave HQPlayer to run with all cores for optimal performance.
Regards,
Keetakawee
2 Likes
Fidelizer 8.11 released â Improved compatibility with Windows 11, processor with efficient cores, and MajiorityCamisole
Due to new changes in hardware and software, Windows 11 with new updates caused Teamviewer failing to work in Purist user level, Intelâs new generation processor with efficient cores messed up hyper-threading detection and have stability issues with some options.
To resolve this problem, I bought Intelâs latest generation NUC with efficient cores to test on Windows 11 environment and resolved reported issues now. Since efficient cores are counted as physical cores, hyper-threading detection algorithm was revised to handle these cases better.
Rather than assigning non-audio processes to logical cores, Fidelizer will assign cores to latter part of processors with efficient cores leaving more room to physical cores unless user chooses to force only one last core for non-audio process.
This version is tested in NUC PC with Windows 11 and clientâs machines to make sure everything is working fine and MajiorityCamisole is also recognized by Fidelizer now. If you use Windows 11 or have processor with efficient cores, version 8.11 is highly recommended.
Changelog for version 8.11
Free
-Fixed Teamviewer not working after stopping/disabling non-audio services in Windows 11
-Improved hyper-threading detection reliability with processors having efficient cores
-Improved software compatibility with MajiorityCamisole
Plus
-Fixed Teamviewer not working after stopping/disabling non-audio services in Windows 11
-Improved hyper-threading detection reliability with processors having efficient cores
-Improved software compatibility with MajiorityCamisole
Pro
-Fixed Teamviewer not working after stopping/disabling non-audio services in Windows 11
-Improved hyper-threading detection reliability with processors having efficient cores
-Improved software compatibility with MajiorityCamisole
Download: Fidelizer 8.11
Upgrade: Fidelizer Upgrade Program
You can download latest version of purchased Fidelizer software from the same download link that we sent in email before. If you are not sure where to download purchased Fidelizer software, feel free to contact us and request software download link.
Getting the most of Fidelizer Plus / Pro configuration with Roon
In year 2016, I wrote about Fidelizer configuration with Roon to recommend audio profiles to use with different Roon software. As some clients asked me lately about options for Roon as media player applications, I decided to write Part 2 to get the most of Roon as below.
First of all, I recommend âPuristâ user level and âNetwork Playerâ audio profile as general recommendation to use in Fidelizer Plus / Pro version. These options are available on both Plus and Pro version and should work optimally as a default option.
If you setup dual PC with Roon core and Roon Ready, using âStreamerâ audio profile on Roon core device and âNetwork Rendererâ on Roon Ready device is recommended. This way you can maximize RAATâs streaming performance through networked audio protocol.
Next part is optimizing Advanced configuration options for Roon. Although default configuration is recommended and already optimal, it wouldnât hurt to go into details why I recommended default configuration as shown in this article.
First of all, Roon has clock priority option for each audio output so maximizing OS Timer Resolution at 0.5ms for low latency audio will help improving clock priority performance. This will allow Roon core to communicate with audio output devices with higher clock priority better.
I recommend âHigh transparencyâ option in Core Isolation Policy. This will setup core audioâs thread priority in Windows platform on first core in processor. Combined with âApply Core Isolation Policyâ option in media player application, those processes will be isolated from core audio thread.
You can try lowering non-audio process priority more aggressively but I donât recommend enforcing non-audio process to use only one core because Roon relies on .NET framework and other non-audio processes so it may affect Roon performance and sonic performance too.
The last part is Media Player Appplication section where you can choose Roon processes to be optimized with Fidelizer Plus/Pro version where you can locate Roon application files in %LOCALAPPDATA%\RoonServer directory after Fidelizer prompts for each media player application file.
The first media player application is RoonServer.exe Using âHighâ priority with âApply core isolation policyâ option. This will allow Roon to be run after Fidelizer optimizations or apply tweaks on running process with high priority and isolated from core audio thread and non-audio processes.
The second media player application is RAATServer.exe Using âRealtimeâ priority with âApply core isolation policyâ option. This will allow Roon to handle low latency audio performance better and improve audio performance on both audio devices in Roon core and Roon ready devices.
The last media player application is RoonAppliance.exe Using âBelowNormalâ priority without âApply core isolation policyâ option. This will reduce interference from Roonâs non-audio tasks to some extent without crippling Roonâs performance too much. If you use Roonâs DSP features, skip this part.
If you use HQPlayer with Roon, you can select HQPlayer5Desktop.exe instead of RoonAppliance.exe and make sure âApply core isolation policyâ is not checked. HQPlayer needs access to all cores to maintain stable operations with its DSP capabilities like RoonAppliance.
And donât forget to change Wait Time to 15 seconds so RoonServer.exe can launch and load RAATServer.exe and RoonAppliance.exe processes first before applying tweaks. Tweaks in Media Player Application are optional and should not be applied if it affects application performance negatively.
After a lot of ups and downs with Roon 2.0 updates that keep affecting sonic performance from time to time, I hope this Fidelizer configuration for Roon can lessen the changes of sound signature in Roon. Using Roon 1.8 legacy is recommended for stable sound quality for audiophiles.