AudioPhil Posted April 9, 2019 Share Posted April 9, 2019 Hm, not good no more ideas at the moment, sorry ıllıllı [ ...AO 4.00 BETA... ] ıllıllı ____________________________________________________________________________________ Shop | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide Link to comment
shinyc Posted April 9, 2019 Share Posted April 9, 2019 Let me delve into this matter some time in the future. Thank you, Phil. AudioPhil 1 Music Source: NAS[Synology], Qobuz, Tidal Music Player: Roonserver[Mac mini] Control PC: squeeze2upnp, fb2k, dirac, Jplay Femto, Fidelizer, AO(4D), WS2019 GUI, Mac mini w/HDPlex 200W Audio PC: Jplay Femto(KS/1000hz), Fidelizer, AO(4D), WS2019 core, i7 w/HDPlex 200W DDC: Iso Regen w/LPS1.2, Acousence afi+USB (USB to S/PDIF) w/Li-ion battery PS DAC: Yggdrasil Analog 2 Link to comment
AudioPhil Posted April 9, 2019 Share Posted April 9, 2019 I‘m sure there will be a solution for this as well. Should you find it, please let me know. Should I find it, i‘ll put it into AO for sure! ıllıllı [ ...AO 4.00 BETA... ] ıllıllı ____________________________________________________________________________________ Shop | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide Link to comment
shinyc Posted April 9, 2019 Share Posted April 9, 2019 Sure thing. I just connected another recording devices of mine (an ADC) and it does bring up usbaudio2 without problem so it must be something to do with microphone device, possibly class type not defined or recognized by the new OS. I will talk to the manufacturer. I hope they are knowledgeable enough in the driver domain. Thank you. AudioPhil 1 Music Source: NAS[Synology], Qobuz, Tidal Music Player: Roonserver[Mac mini] Control PC: squeeze2upnp, fb2k, dirac, Jplay Femto, Fidelizer, AO(4D), WS2019 GUI, Mac mini w/HDPlex 200W Audio PC: Jplay Femto(KS/1000hz), Fidelizer, AO(4D), WS2019 core, i7 w/HDPlex 200W DDC: Iso Regen w/LPS1.2, Acousence afi+USB (USB to S/PDIF) w/Li-ion battery PS DAC: Yggdrasil Analog 2 Link to comment
thuandb Posted April 9, 2019 Share Posted April 9, 2019 I’d try this: Install the driver run ao -e run st -r Then check the status of the driver in Device Manager. WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
shinyc Posted April 9, 2019 Share Posted April 9, 2019 I gave this a try. Thanks. Unfortunately, no change came after this. If I have time, I will try the GUI 2019 version. In the meantime, I will produce the room calibration data using my Windows 10 machine. Until I solve this problem, I won't know the difference anyway. Most frequent cure for IT was, is and will be time. That has been my belief. I give 6 to 12mo give or take 12mo. Music Source: NAS[Synology], Qobuz, Tidal Music Player: Roonserver[Mac mini] Control PC: squeeze2upnp, fb2k, dirac, Jplay Femto, Fidelizer, AO(4D), WS2019 GUI, Mac mini w/HDPlex 200W Audio PC: Jplay Femto(KS/1000hz), Fidelizer, AO(4D), WS2019 core, i7 w/HDPlex 200W DDC: Iso Regen w/LPS1.2, Acousence afi+USB (USB to S/PDIF) w/Li-ion battery PS DAC: Yggdrasil Analog 2 Link to comment
Blueline Posted April 14, 2019 Share Posted April 14, 2019 Hi AudioPhil You can sort the operating systems in the order they perform audio. I'm still on server 2012r2 Core, will find out if server 2016/2019 GUI is an upgrade, or do I need to use Core to achieve better sound Server 2019 Core Server 2016 Core Server 2012r2 Core Server 2019 GUI Server 2016 GUI Server 201r2 GUI Windows 10 Link to comment
Popular Post AudioPhil Posted April 15, 2019 Popular Post Share Posted April 15, 2019 Of Course Worst to best: - Windows 10 - Server 2012 R2 GUI - Server 2012 R2 Core/Windows Server 2016 GUI - Server 2016 Core/Windows Server 2019 GUI - Windows Server 2019 Core So my recommendation for almost all scenarios is Windows Server 2019 in GUI with the soon coming AO 3.00. For those seeking absolute maximum 2019 Core with AO 3.00. rickca and motberg 2 ıllıllı [ ...AO 4.00 BETA... ] ıllıllı ____________________________________________________________________________________ Shop | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide Link to comment
Blueline Posted April 15, 2019 Share Posted April 15, 2019 Then server 2019 gui, is a good alternative. as it is on par with the 2016 Core! Link to comment
AudioPhil Posted April 15, 2019 Share Posted April 15, 2019 Exactly thats the reason why in the future I will recommend Server 2019 in GUI to everyone who asks me. absolutely hassle free GUI experience paired with jaw dropping sound quality on the level of 2016 Core. What a no brainer! ıllıllı [ ...AO 4.00 BETA... ] ıllıllı ____________________________________________________________________________________ Shop | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide Link to comment
shinyc Posted April 18, 2019 Share Posted April 18, 2019 On 4/10/2019 at 12:05 AM, shinyc said: I gave this a try. Thanks. Unfortunately, no change came after this. If I have time, I will try the GUI 2019 version. In the meantime, I will produce the room calibration data using my Windows 10 machine. Until I solve this problem, I won't know the difference anyway. Most frequent cure for IT was, is and will be time. That has been my belief. I give 6 to 12mo give or take 12mo. One more reason to recommend WS2019 "GUI version". My microphone is properly working now after changing from core to GUI version on my control PC. At the same time, my system is much more stable after the change. No more "all of a sudden music stops playing" events. SQ is slightly different but I cannot say it is for the worse. Or should I say more stable sound! I recommend GUI version at least for the control PC for now. I am still using core version for the audio PC, thou. Please do your own experiment for there are so many variables. Music Source: NAS[Synology], Qobuz, Tidal Music Player: Roonserver[Mac mini] Control PC: squeeze2upnp, fb2k, dirac, Jplay Femto, Fidelizer, AO(4D), WS2019 GUI, Mac mini w/HDPlex 200W Audio PC: Jplay Femto(KS/1000hz), Fidelizer, AO(4D), WS2019 core, i7 w/HDPlex 200W DDC: Iso Regen w/LPS1.2, Acousence afi+USB (USB to S/PDIF) w/Li-ion battery PS DAC: Yggdrasil Analog 2 Link to comment
bummer Posted May 8, 2019 Share Posted May 8, 2019 @ Phil, when trial-period of WS2019 is over (including extension) can I take the same (already used) ISO and make a new clean install or do I have to download a new ISO (with different footprint) to make a new install? Martin Link to comment
AudioPhil Posted May 8, 2019 Share Posted May 8, 2019 Hi Martin If you format the drive you can use the same ISO as many times as you wish. even easier is to just extend the trial period by another 180 days. This can be repeated five times, then you really have to format and start with a fresh installation. see this how-to article: https://sid-500.com/2017/08/08/windows-server-2016-evaluation-how-to-extend-the-trial-period/ Best, AudioPhil ıllıllı [ ...AO 4.00 BETA... ] ıllıllı ____________________________________________________________________________________ Shop | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide Link to comment
shahed99 Posted May 8, 2019 Share Posted May 8, 2019 Anyone installed Windows Server 2019 on a NUC? I'm planning to use an optane drive in my NUC. Wondering if 32GB is enough or should I go for 64GB? Also, how easy/hard it is to install WS2019 in core mode in NUC used exclusively as audiopc and HQP NAA? If it seems flaky, I would stick to WS2019 GUI. Link to comment
thuandb Posted May 8, 2019 Share Posted May 8, 2019 I know a good guy in JPLAY forums who has successfully installed and been using WS2019 core on two NUCs. His screen name is taxman2. shahed99 1 WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
AudioPhil Posted May 8, 2019 Share Posted May 8, 2019 32GB will be more than enough for Server 2019 👍🏼 shahed99 1 ıllıllı [ ...AO 4.00 BETA... ] ıllıllı ____________________________________________________________________________________ Shop | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide Link to comment
shahed99 Posted May 8, 2019 Share Posted May 8, 2019 Just saw the following on the Windows Server installation requirement on microsoft site. I want to install WS 2019 GUI. From their official statement, it seems 32GB would be pushing it? " Be aware that 32 GB should be considered an absolute minimum value for successful installation. This minimum should allow you to install Windows Server 2019 in Server Core mode, with the Web Services (IIS) server role. A server in Server Core mode is about 4 GB smaller than the same server in Server with a GUI mode. The system partition will need extra space for any of the following circumstances: If you install the system over a network. Computers with more than 16 GB of RAM will require more disk space for paging, hibernation, and dump files. " Link to comment
AudioPhil Posted May 8, 2019 Share Posted May 8, 2019 No need to worry too much This is a fresh 2019 Standard GUI installation from today: shahed99 1 ıllıllı [ ...AO 4.00 BETA... ] ıllıllı ____________________________________________________________________________________ Shop | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide Link to comment
Jiffi32 Posted May 8, 2019 Share Posted May 8, 2019 Hi @AudioPhil Any release date yet for AO 3? I've just had to install a new OS drive and took the opportunity to update to server 2019. Hoping that it's not too far away now🤞 customer server+AudiophileOptimizer >>UltraRendu (SR4) >> Lush(JSSG360) >>> IsoRegen(SR4) >>> Lush^2 >>> blu2 >>Blaxius^2D >> Dave > HD800(SDRmod) Link to comment
Popular Post AudioPhil Posted May 8, 2019 Popular Post Share Posted May 8, 2019 Not too far away from now! 😎 We are currently doing the final tests as well as are updating and creating new PDF guides. AO 3.00 will be released by the end of the month at the latest. Jiffi32 and motberg 2 ıllıllı [ ...AO 4.00 BETA... ] ıllıllı ____________________________________________________________________________________ Shop | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide Link to comment
moriez Posted May 9, 2019 Share Posted May 9, 2019 Copied from the BETA thread. Would still like to hear about this: Because of the dual boot I went into SSD properties and noticed that indexing was ticked. Am I correct in assuming this is functionless because the index service is removed or disabled by AO? Task manager does not show WSearch running. Thanks in advance :] Link to comment
AudioPhil Posted May 9, 2019 Share Posted May 9, 2019 Hi @moriez I do not know of a way disabling (or removing) the tick at the index checkbox of a drive. but that setting is irrelevant as long as the search service isn‘t running. Hope this helps to clarify Best, AudioPhil moriez 1 ıllıllı [ ...AO 4.00 BETA... ] ıllıllı ____________________________________________________________________________________ Shop | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide Link to comment
moriez Posted May 9, 2019 Share Posted May 9, 2019 Thanks Phil. To be sure, AO completely terminates the search service? Link to comment
AudioPhil Posted May 9, 2019 Share Posted May 9, 2019 Indeed ıllıllı [ ...AO 4.00 BETA... ] ıllıllı ____________________________________________________________________________________ Shop | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now