AudiophileOptimizer BETA Thread (AO 3.00 beta is closed)

Solid-State · February 22, 2019

8 hours ago, Anto said:

Hi all, I just tested the preview of the Beta 35, the audio drivers are no longer a problem!
Now you no longer need to disable the driver signing at startup!
Phil did a great job, he turned Server 2019 Core, from very grumpy is difficult, to a system affordable for everyone, and especially amazing from the standpoint of sound Quality!
I think short version 35 will be available for Download.

This is the procedure to follow:

1-Install FOD

2-install Ao

3-reboot by disabling the driver signature, then Service_tool and install Hd Audio driver, allow 6 red windows, exit.
4-Install the drivers of your DAC
5-Start Audiophile_core, proceed with optimization by allowing "Install Kernel Streaming ", go all the way, and then reboot.

6-on reboot, type DEVMGMT. MSC and verify that the audio drivers are installed correctly!

Greetings Anto😁

THIS IS THE ONLY AND RIGHT WAY TO DO IT!!

Install OS

install FDO

RUN WINDOWS UPPDATE !!! to get latest FDO Uppdate

Install AO reboot

Install any other driver BUT NOT AUDIO !!

Run AO -WASAPI before you install any AUDIO driver !! IMPORTANT

OPTION, NOT NESSERY

reboot and press F8. / disabling driver signature,

then Service_tool and install Hd Audio driver, allow 6 red windows, exit. )

reboot, type DEVMGMT. MSC and Install the drivers of your DAC

verify that the audio drivers are installed correctly

install JPLAY, Jriver, or what you use and test play so every thing works

Start Audiophile_core, proceed with optimization Yes NO to install kernel support, allredy installd by WASAPI

go all the way, and then reboot

THIS IS THE ONLY AND RIGHT WAY TO DO IT!!

.THIS IS THE ONLY AND RIGHT WAY TO DO IT!!

AudioKarl · February 22, 2019

Hi,

B35 works with 2019 core great for me! Dac driver installation, KS, Wasapi, all go smooth!

Great job Phil !!!!!!!

My dac: Chord Qutest

My problems:

with B33: to make the driver work, i must every time i reboot press f8

with B34: i could not install the dac driver at all

What i have done:
fresh install of 2019 core
install FOD

install AO B35

install within AO kernelstreaming and Roon & HQPlayer support

install my dac driver >>> KS works

do the wasapi injection >>> Wasapi works

ingemar · February 22, 2019

Made it simple for me,just installed core and all needed drivers thats it!The sound quality is fantastic with roon and hqplayer.My dac is Lampizator GG with amanero drivers.

Solid-State · February 22, 2019

1 hour ago, TubeMan said:

THIS IS THE ONLY AND RIGHT WAY TO DO IT!!

THIS IS THE ONLY AND RIGHT WAY TO DO IT!!

Install OS

install FDO

RUN WINDOWS UPPDATE !!! to get latest FDO Uppdate

Install AO reboot

Install any other driver BUT NOT AUDIO !!

Run AO -WASAPI before you install any AUDIO driver !! IMPORTANT

OPTION, NOT NESSERY

reboot and press F8. / disabling driver signature,

then Service_tool and install Hd Audio driver, allow 6 red windows, exit. )

reboot, type DEVMGMT. MSC and Install the drivers of your DAC

verify that the audio drivers are installed correctly

install JPLAY, Jriver, or what you use and test play so every thing works

Start Audiophile_core, proceed with optimization Yes NO to install kernel support, allredy installd by WASAPI

go all the way, and then reboot

THIS IS THE ONLY AND RIGHT WAY TO DO IT!!

.THIS IS THE ONLY AND RIGHT WAY TO DO IT!!

And one more thing, !!!!!!!!!
It VERY important that you have the latest install media for SRV2019.
to get successful installation.
download trial version from evaluation center and convert to retail if you have a valid licen,

https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2019

Gato · February 22, 2019

Success with AOb35: SOUND IS WONDERFUL!

The following procedure works for my system: WindowsCore 2019 / T+A DAC 8 DSD / HQPlayer / Fidelizer:

Install OS
Install FDO
sconfig option 6) Download ans install Updates: All
Install AO
Reboot
Install other drivers but not the Audio ones
Run ao/tools/ao -wasapi
Reboot with pressing F8 -> disabling driver signature
Service_tool and install Hd Audio driver, allow 6 red windows, exit
Reboot normal (without F8)
Install T+A DAC 8 DSD Driver
Verify via devmgmt.msc that the audio drivers are installed correctly: It's the case
Install HQPlayer 3.25.3
Start Audiophile_core
- • U ultimate mode
  • X signature
  • X digital filter
  • N Kernel-Streaming and MediaPlayer support
  • E HPET
  • Y disable/remove Windows Defender
  • D SEHOP
  • Y WASAPI / MMCSS
  • Y Disable SCSI
  • A Do not turn off display
  • E USB optimisation
  • Y Disable drivers and services
  • Y Disable Plug and play
  • Y Disable AMD CPU/SATA Drivers
  • Y Disable Remote Desktop services
  • Y Disable Remote Management services
  • N use of USBPAL
  • Y Defrag/Trim SSD
Reboot
Fidelizer 8.3
Reboot
Here we are again into Musicland

Thank you all of you for this!

alicenir · February 22, 2019

Hi,

Just installed a fresh core 2019 AO3/35 and FOD like the steps written above.

everything worked flawlessly. thank you Phil !!

to everyone that uses Roon Server and have a huge amount of music stored, keep your Roon backup scheduled in order not to waist time scanning again.

FYI - on beta 34 i used Core 2019 DataCenter and non beta 35 i installed Core 2019 STD. not sure yet but i think that the DataCenter sounds even better....

ingemar · February 22, 2019

Sorry about my ignorance but why are you guyz using this FoD??

mozes · February 22, 2019

Hi Phil

How close are we to the public Beta?

AudioPhil · February 22, 2019

48 minutes ago, ingemar said:

Sorry about my ignorance but why are you guyz using this FoD??

You need the FoD & the WASAPI injector if you want WASAPI in Core. On top of that FoD adds Explorer and few other handy things to Core mode.

AudioPhil · February 22, 2019

18 minutes ago, mozes said:

Hi Phil

How close are we to the public Beta?

Hi

there won‘t be a public beta but you can always apply to join the beta testers group and participate in the beta phase.

ingemar · February 22, 2019

2 minutes ago, AudioPhil said:

You need the FoD & the WASAPI injector if you want WASAPI in Core. On top of that FoD adds Explorer and few other handy things to Core mode.

Okidoki,thanks for your fast reply!

mozes · February 22, 2019

17 minutes ago, AudioPhil said:

Hi

there won‘t be a public beta but you can always apply to join the beta testers group and participate in the beta phase.

Ok thanks

alicenir · February 22, 2019

Hi Again,

GATO i will use your structure for the flow - hope its OK

Success with AO3 / b35: the Sound is amazing! i had many issues before with my PS Audio driver and it is now solved!!

The following procedure works for my system: WindowsCore 2019 / PS Audio DAC / Roon Server/ Fidelizer 8.3 / Jplay Classic 7 / Process Lasso:

Install Windows Server Core 2019
Install FOD
Sconfig option 6 Download ans install Updates: All
Install AO and reboot
Install other drivers but not the Audio ones, on my case the MB Ethernet Card
Run ao/tools/ao -wasapi
Reboot with pressing F8 -> disabling driver signature
Service_tool and install Hd Audio driver, allow all red windows, exit
Reboot normal (without F8)
Install PS Audio DAC Driver
Install Jplay / Roon Server
Install Process Lasso
Verify via devmgmt.msc that the audio drivers are installed correctly
Start Audiophile_core
- • U ultimate mode
  • 4 signature
  • D digital filter
  •    N Kernel-Streaming and MediaPlayer support - already instlled WASAPI after FOD
  • E HPET
  • Y disable/remove Windows Defender
  • D SEHOP
  • Y WASAPI / MMCSS
  • Y Disable SCSI
  • A Do not turn off display
  • E USB optimization
  • Y Disable drivers and services
  • Y Disable Plug and play
  • Y Disable AMD CPU/SATA Drivers
  • Y Disable Remote Desktop services
  • Y Disable Remote Management services
  • N use of USBPAL
  • Y Defrag/Trim SSD
Reboot
Fidelizer 8.3 and let it load RoonServer
Reboot
Start Process Lasso and set it up
Restore Roon backup

All the restart that you see here are very fast since we are using SSD drive so it is not an issue.

some commands to install FOD that i used:

Mounting the FOD iso(Change the drive letter accordingly):

Mount-DiskImage -ImagePath "D:\Audio\SW_DVD9_NTRL_Win_Svr_FOD_App_Compat_2019_64Bit_MultiLang_X21-91284.ISO"

Installing the FOD:

DISM /Online /Add-Capability /CapabilityName:"ServerCore.AppCompatibility~~~~0.0.1.0" /Source:D: /LimitAccess

Phil, thank you for your time solving users issues with dedication and with real solutions, i know its not always easy so thank you!

Nir

magicknow · February 22, 2019

Regarding the step to install any other driver other than Audio

I don't have any drivers i need to install is there a generic driver I can download to install just to complete this?

thanks

James 108

AudioPhil · February 22, 2019

6 minutes ago, magicknow said:

Regarding the step to install any other driver other than Audio

I don't have any drivers i need to install is there a generic driver I can download to install just to complete this?

thanks

James 108

„Install HD audio drivers“ will also install the generic USB Audio Class 2.00 driver.

i‘d give it a try

magicknow · February 22, 2019

will this still work if I rename the .so to FOC.iso or does it need to stay the original name

james 108

Solid-State · February 22, 2019

23 minutes ago, magicknow said:

will this still work if I rename the .so to FOC.iso or does it need to stay the original name

james 108

no problem,

moriez · February 22, 2019

YAY. Success here too! With help of all the posted flows I found my way and the troublesome driver surrendered in the very first round. Installing was like cutting through butter compared to all the previous effort. Thanks all and Phil for a great beta.

A small observation is that when disabling remote management via sconfig (because I ran Windows Update there), AO still asked whether I want to disable it. Unless these are unrelated it would make sense AO had picked up and skips the question. More or less the same with the firewall. AO shows ''firewall disabled'' message even if you already passed ''netsh advfirewall set allprofiles state off''

Peter Avgeris · February 22, 2019

Someone here reported to use the latest WS2019 distribution from Microsoft. I visited Microsoft and indeed, they had a new release up for downloading. Of course, after a hard hit and the lesson I had received some time ago, I never delete old distributions unless the new ones are downloaded, installed and found perfect under normal working environment.

The transformation from Evaluation license to Standard license involves the well known dism command:

> dism /online /set-edition:ServerStandardCor /productkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /accepteula

For a reason that I do not know, this command has generated errors in both 3 PCs while the older standard version downloaded a month ago had produced zero errors!

Just FYI!

Solid-State · February 22, 2019

it may depend on which version you have installed,
eg if you have set up Datacenter, you cannot convert to Standard,
but you can convert the Standard to the Datacenter

Solid-State · February 22, 2019

run this command to check

Dism /online /Get-CurrentEdition

to get wath you have

Dism /online /Get-TargetEditions

to see what you can "uppgrade" to

Solid-State · February 22, 2019

tray

DISM /online /Set-Edition:ServerStandard /ProductKey:XXXX.XXXXX.XXXXX.XXXXX /AcceptEula

Solid-State · February 22, 2019

1 hour ago, Peter Avgeris said:

Someone here reported to use the latest WS2019 distribution from Microsoft. I visited Microsoft and indeed, they had a new release up for downloading. Of course, after a hard hit and the lesson I had received some time ago, I never delete old distributions unless the new ones are downloaded, installed and found perfect under normal working environment.

The transformation from Evaluation license to Standard license involves the well known dism command:

> dism /online /set-edition:ServerStandardCor /productkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /accepteula

For a reason that I do not know, this command has generated errors in both 3 PCs while the older standard version downloaded a month ago had produced zero errors!

Just FYI!

and please delete the key !!!!!!!!

Peter Avgeris · February 22, 2019

22 minutes ago, TubeMan said:

and please delete the key !!!!!!!!

Ask your comments do not relate to my problem. The key is public. Server core is the version. I am doing everything as it should be. Problem is not caused on my side. There is an error. Older version is fully functional. Bye bye the newer one!

magicknow · February 22, 2019

Is this the correct iso file When I try the DISM command it says source files not found

It says AMD 64 but I have a i7 920 not sure if this matters

AudiophileOptimizer BETA Thread (AO 3.00 beta is closed)

Recommended Posts

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment