AudiophileOptimizer BETA Thread (AO 3.00 beta is closed)

[AudioPhil]

41 minutes ago, kelvinwsy said:

Tried for 5 Days ,.. gave up trying to load WinServer2019 onto a USB Stick

Rufus and loaded WinServer 2019 onto my 64gb SSD of my 8650U i7 quad core.. First mode was Core mode No GUI Data Exchange version.. Loaded everything ..Ok ..Then problem

Ran into trouble Hqplayer had a 0xc000007b exe error.. Tried all solutions.. Couldnt get it to work.. Reloaded the GUI modecof the Data Exchange version. Reloaded drivers and Hqplayer 3.5.2..WORKED At first trial.. 73 processes and loaded free version of Fidelizer 8

67 processes now

The i7 quad core 8650u fanless server replaced my i7 6700k highly filtered server..-The NAA us the SOTM SM200 Ultra Neo:Isoregen/LPS1.0/Ultracap/LT3045 to iFi idsd micro BL .. 2 AN Quest Silver 300b mono driving Senn HD800

 

Comparision to Win2016 Core running on my i7 6700k .. the 8650u can do DSD 256 44k upsampling using Non-adaptive filters 

A slightly noisier than my 6700k .. on live albums not so black background

But using my fav test tracks.. WinServer 2019 is a Winner.. I am buying another Another SSD load it to my 6709k and do a closer comparison

It is a WINNER.. better tonality sweeter treble and better bass.. maybe the fanless 8650u is the reason but let the second SSD Trial we will see!!

 

I used my own CF Card guide to apply server 2019 core to a (bootable) USB stick, worked like a charm. You can try this too: http://jplay.eu/forum/index.php?/topic/1141-guide-how-to-properly-set-up-windows-server-2012-on-a-cf-card/

 

Best,

AudioPhil

[simonklp]

20 hours ago, AudioPhil said:

 

I used my own CF Card guide to apply server 2019 core to a (bootable) USB stick, worked like a charm. You can try this too: http://jplay.eu/forum/index.php?/topic/1141-guide-how-to-properly-set-up-windows-server-2012-on-a-cf-card/

 

Best,

AudioPhil

 

Look forward to trying WS 2019 with AO…

[FelipeRolim]

I'm currently testing some more operating system options, and I have some interesting remarks:

- The version of Windows Server 2016 I use is build 14393, which I can install on an 8GB .vhd and occupies 7.5GB of that .vhd with everything installed (JPLAY and Audiophile Optimizer).

- The latest Windows Server 2016 version I tested (build 17763) can only be installed on a 9GB .vhd, occupies 8.5GB of this .vhd with everything installed.

- I'm doing experiments with Windows Server 2019 (build 17763.253) and I'm surprised. I was able to install it in a .vhd of only 7GB and, with JPLAY FEMTO installed (without the Audiophile Optimizer), it occupied only 6.3GB of this .vhd. Still, with no optimization, I noticed that Windows needs 0.9GB of RAM to run, which indicates that with the Audiophile Optimizer approximately 0.5GB of RAM will be needed. This means that we will be able to make Windows Server 2019 work via RAM on computers with only 8GB installed, with a good leftovers. I haven't listened to it, and I may have been waiting for the Audiophile Optimizer 3.00 for this, but I think we can be optimistic...

[AudioPhil]

Indeed, you may be very optimistic :)

 

 

[FelipeRolim]

Phil, if I install Audiophile Optimizer 2.20 on Windows Server 2019, when will I install version 3.00 will I need to format the computer? I'm interested in testing Server 2019 with RAMdisk right away, but if I need to format in the future, I'll wait a little longer. Do you have a launch forecast?

[AudioPhil]

Hi

 

All AO version can only be installed and run on „supported“ versions of windows. Supported means that AO is tested with them and we know everything works as designed. This is important so you can experience the functionality you expect.

 

Each AO versions knows very precisely which version of Windows it works with, and checks for this on every start. Same applies for ServiceTool and Setup. (this also helps to prevent waisted Activation-Keys)

 

Or in other words, you cannot install AO 2.20 on Server 2019. you would just see the „no compatible os found“ message.

 

Updating AO never requires format and reinstallstion of the OS. If you are on AO 2.20 for example and want to update to the coming AO 3.00, all you need to do is to run setup.exe of the new AO version and then the new AO one time after the reboot, thats it, all set.

 

Best,

AudioPhil

[kelvinwsy]

Hi Felix

Good to see you on the Beta Forum for AO

I came across your posts on RAMDISK for WinServer2016

I have it on my SSD already So I decided try it for WInServer 2019

Really went NO Loaded the Iso, Did the Firadisk Registry File, Did Bootice, Booted UP and I get loading error of winserver file when on UEFI booting.

Dont know how to use your files on Google Drive.

Any quick solution like you post your tested solution with clearer instructions how to clone it on to a USB 3.0 stick.

THanks a million in advance.

[FelipeRolim]

Hi, Kelvin.

 

I've never worked with ISO files for this purpose (I never managed to make it work.), just as VHD virtual disk files. About the files I shared in Google Drive, their purpose is fully described in the instruction manual I shared. Did you read it?

 

I have a specific topic for RAMdisk with Windows Server 2016 and, as soon as the Audiophile Optimizer 3.00 is released, I'll also direct it to Windows Server 2019. I ask you to post there about any doubts, to avoid off topics in this one.

 

Thank you!!!

 

PS.: regarding clone the Windows to a USB 3.0 stick, once you did everything correctly, there's no secret: it's just copy and paste...

[AudioPhil]

Hello Folks

 

Since many months we are working on AO 3.00. Now is the time to start the testing with more users. This is going to be a very long post, sorry for that... If you are interested in testing AO 3.00 beta please make sure that you are OK with the following conditions:

 

- Only users of AudiophileOptimizer 2.X are able to participate in the AO 3.00 beta phase

 

- You need to format your system and start with a fresh windows installation. Systems with older AO version already applied are not suitable for beta testing

 

- The dedicated beta activation portal will let you create two Activation-Keys instead of five like the normal portal

 

- AO 3.00 uses a different algorithm to calculate the Activation-Keys. So your Hardware-ID will be the same as usual, but you will definitely need a new Activation-Key. The keys you need during the beta phase are "sponsored" through us

 

- There is a separate activation counter for AO 3.00 beta. After the beta phase this counter will be reset to zero for all participants. This beta activation counter does not interfere with your normal activation counter of AO 2.20

 

- To download and activate any AO 3.00 beta version you always have to use the dedicated beta portal. If you try to generate an Activation-Key for AO 3.00 beta on the regular portal of AO 2.20 you will loose one Activation-Key. Your regular activation counter will not be adjusted afterwards, so be sure to use the beta activation portal only!

 

- AO 3.00 Beta needs an active internet connection to work. Without a working internet connections you cannot install it and you cannot run AO or ServiceTool etc. The final version of AO 3.00 will not have this limitation

 

- When you receive a notification about a new beta version of AO, you need to download it via the dedicated beta portal, not the regular download portal

 

- You might be required to format and reinstall your OS multiple times

 

- There is only little risk of breaking something by using the AO 3.00 beta. But new features might not yet work as intended so your feedback is required

 

- It is strictly forbidden to use any other foreign optimization scripts like CAD etc during beta testing AO 3.00

 

- AO beta testing is only for you if you are computer savy and already know very well how AO works. You need to be able to handle DAC/DDC driver installations yourself, especially in core mode. If you are new to AO or computer audio and need help with computers often, this is probably not for you

 

- Server 2016 & 2019 LTSC (Long-Term Service Channel) are supported, all editions except Hyper-V Edition

 

- Server 1709 & 1803, etc. SAC (Semi-Annual Channel) are not supported at the moment. If there is any interest in the SAC versions of Windows Server we can have a lookt at it during the beta phase

 

- There is quite a big list of additional features still to come during the beta phase

 

- All feedback about possible issues, problems, wishes, ideas and quesions go in this thread. 

 

- There is no updated version of the PDF guide yet, ask your quesions in this  thread

This is no public available beta phase, but you can participate in the beta if you really like to. To do so please write an email to [email protected] and explain in a few sentences why you would like to test the AO 3.00 beta, what OS and Player you plan to use it It is important that you also include the PayPal/Email-Adress you already use to download/activate AO 2.20.

 

 

So now let's have a look at the actual change log. Please keep in mind the beta phase just startet, so that's not all that is going to be in AO 3.00!

 

Version 3.00 Beta 28
==========================================================================
AudiophileOptimizer 3.00
- Enables Kernel-Streaming in Windows Server 2016/2019 Core Mode
- Enables Device Manager in Windows Server 2012 R2/2016/2019 Core Mode (en-US only)
- Enables RoonServer & RoonBridge in Windows Server 2016/2019 Core Mode
- AO disables automatic maintenance (Win10/Server 2016/Server 2019)
- Update of "Prepare Essentials Edition" feature for Windows Server 2019
- Ability to remove Windows Defender (Windows Server 2016/Windows Server 2019)
- Updated MediaPlayer support for Windows Server 2016/2019 Core Mode
- Support for Windows Server 2019 RTM (Standard, Datacenter & Essentials)
- Support for Windows Server 2019 Evaluation (Standard, Datacenter & Essentials)
- Removed Support for Windows Server 2012 (Standard, Datacenter & Essentials)
- LockScreen disabled for Windows Server 2016/2019
- ActionCenter disabled for Windows Server 2016/2019
- Enables TIDAL Windows Player in Core Mode
- Minor changes and updates

 

ServiceTool 3.00
- Custom shell as shell replacement
- Support for Windows Server 2019 RTM & Evaluation (Standard, Datacenter & Essentials)
- Removed Support for Windows Server 2012 (Standard, Datacenter & Essentials)
- Shell replacement for coming JRiver Media Center 25 & 26 (x86 & x64) (Since JRiver brings updates very often shell replacements for future versions of JRiver are already included)
- Minor changes and updates

 

AudiophileShell 3.00
- Initial version of AudiophileShell

 

Setup 3.00
- High-DPI Mode for high-resolution displays (4K etc.)
- Enables Device Manager in Windows Server 2012 R2/2016/2019 Core Mode (en-US only)
- Support for Windows Server 2019 RTM & Evaluation (Standard, Datacenter & Essentials)
- Removed Support for Windows Server 2012 (Standard, Datacenter & Essentials - no worries, 2012 R2 is still supported!)
- Adds link to Control Panel on desktop
- Minor changes and updates
 

 

Best,

AudioPhil

[rickca]

9 minutes ago, AudioPhil said:

AudiophileShell 3.00

What is this?

[AudioPhil]

3 minutes ago, rickca said:

What is this?

 

It basically is a "launcher tool". You can either set it as shell replacement, or you can just run it by typing "as" and press enter. It is very early stage yet, but i see a lot of potential for it. The beta phase will give all of you the chance to help to shape and form it to your needs

 

[Anto]

Request sent, pending ...

[FelipeRolim]

Hi, Phil. I already sent you the e-mail and I'm waiting for an answer. I was left with some doubts:

 

- Which Windows do you recommend, Standard or Essentials?

 

- In my case, I've already used three of the five licenses of the Audiophile Optimizer v. 2.20. You said that the two v. 3.00 BETA licences will be unlinked from v. 2.20, right? I ask why I want to test it in the Audio-PC (where I've been using the Audiophile Optimizer v. 2.20 for a long time) and also in a Windows Server-based notebook. It turns out that in the notebook I never installed the Audiophile Optimizer. Does that mean I'll need to use a license, or will the two remain there? I wouldn't want to use a "real" license with this notebook.

 

Thank you!

[Anto]

I'm sorry not to be able to test the beta, which requires internet connection, my dedicated audio PC, has no network card, why this choice?
Thank you
Anto

 

[AudioPhil]

3 minutes ago, FelipeRolim said:

Hi, Phil. I already sent you the e-mail and I'm waiting for an answer. I was left with some doubts:

 

- Which Windows do you recommend, Standard or Essentials?

 

- In my case, I've already used three of the five licenses of the Audiophile Optimizer v. 2.20. You said that the two v. 3.00 BETA licences will be unlinked from v. 2.20, right? I ask why I want to test it in the Audio-PC (where I've been using the Audiophile Optimizer v. 2.20 for a long time) and also in a Windows Server-based notebook. It turns out that in the notebook I never installed the Audiophile Optimizer. Does that mean I'll need to use a license, or will the two remain there? I wouldn't want to use a "real" license with this notebook.

 

Thank you!

 

Hi Felipe

 

If license/costs is no conscern for you then i would go Standard. Otherwise Essentials is fine too, The ServiceTool will strip out the additional components the essentials edition normally would have in comparision to the standard edition.

 

Yes of course the activation counter for AO 3.00 beta is seperated. Your current 2.20 activation counter (your "real" license) will be untouched, no worries at all.

 

All activations needed to test AO 3.00 beta are of course offered by us. Just be sure to use the beta activation portal from my email and not the regular one from the publicly visible homepage

[AudioPhil]

4 minutes ago, Anto said:

I'm sorry not to be able to test the beta, which requires internet connection, my dedicated audio PC, has no network card, why this choice?
Thank you
Anto

 

 

Hi

 

Sorry to hear there is no internet connection available. This is needed to get update notifications and to prevent further usage of AO beta versions once the beta period is over, this is important for various reasons. The final release of AO 3.00 will of course not have this limitation.

 

Best,

AudioPhil

[moriez]

14 hours ago, AudioPhil said:

 

It basically is a "launcher tool". You can either set it as shell replacement, or you can just run it by typing "as" and press enter. It is very early stage yet, but i see a lot of potential for it. The beta phase will give all of you the chance to help to shape and form it to your needs

 

 

Ooooh nice! Nice to see OSK in there.

 

Phil, until when can we apply for the beta?

[AudioPhil]

The beta phase will certainly be for more than a few weeks, so please feel free and go ahead if you like

 

Sadly the OSK does not work in Core. The needed graphical components are missing. but it was a nice idea..

[kelvinwsy]

Hey everyone

I tried the Data Exchange Version (without the Experience _GUI )

AudioPhil is absolutely correct. All the video display/Graphical elements are missing. You have to (Absolutely Have) load the GUI version whether it is Data Exchange or Standard -- HQplayer will not run. I tried all the tricks, running MSFT Viscalc C++, Loading Intel GPU drivers etc etc.

Gave up and loaded up the GUI version of Data Exchange Server Version (GUI) of WinServer 2019.

HQplayer loaded IMMEDIATELY and played. All my DAC drivers loaded not problem, iFi idsd, XMOS, LH Labs Geek Pulse, PS Audio PWD Dac II, and best of all (as it should be for Windows devices... WASAPI endpoint (Creative Tech SXFi) was plug and play.

Kelvin

[thuandb]

AO Beta testing has begun...

 

AO 3.0 has been successfully installed and running on a fresh installation of WS2019 Standard (i.e. Core).  Beside a few items not yet available in AudiophileShell 3.0, there're no problems getting music playback from the Beta setup.

 

One observation:  after getting out to Command Line from the AudiophileShell, attempt to run Q-Dir failed eventhough Q-Dir had been copied to the C:\Windows\System32 folder and later on Q-Dir can be run from Task Manager or from a more "normal" command line mode.

[kelvinwsy]

Hi Thuandb - Your WinServer 2019 Core mode? No GUI

What Music playback software have you loaded.

I tried my JRiver MC 24 64bit - also did not load.

THX

[thuandb]

I'm using JPLAY FEMTO (v7) as music playback software.

[AudioPhil]

12 minutes ago, kelvinwsy said:

Hi Thuandb - Your WinServer 2019 Core mode? No GUI

What Music playback software have you loaded.

I tried my JRiver MC 24 64bit - also did not load.

THX

 

Did you say yes to "Install Kernel-Streaming and MediaPlayer support" during AO run? JRiver (and most other players) will not work in Core without that.

[kelvinwsy]

No I have been trying to load HQPlayer and JRiver MC just with plain Taskmgr.exe in core

That was on the weekend when I dont have the AO 3 Beta (which u released just )

Ha Ha I have forgotten that for my WinServer 2016 the HQPlayer loading was AFTER AO2.20

okay SO i can go back to Data Exchange / Core Mode and load AO3 before I do the HQPlayer and JRiver loading.

BTW is the COre Mode of Data Exchange Much more Stripped down than the Standard or the Essentials

AudioPhil - Your opinion.. is there a SQ difference between the 3 versions of 2019Server?

Thx

 

THx

[AudioPhil]

Yes you need AO for that to work

 

no difference between standard core and datacenter core edition, both identical.