thuandb Posted February 13, 2018 Share Posted February 13, 2018 On 2/6/2018 at 3:39 AM, Blawre said: After reading johsgjerde's comments on the JPlay forum, I tried WASAPI in 2016 core. The results are stunning. Although you can only use "Classic" mode in the JPlay settings, I think the results are superior to anything else that I have tried. I use Hysolid as the player. As you say Phil is owed a very bug thakyou. Hi, As a HySolid user I am disappointed not able to run WASAPI. Could you please share your settings required to do so? Right now I'm on KS, UltraStream, 1Hz, 10s. Only Jplay driver appears on my iPad HySolid. WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted February 13, 2018 Share Posted February 13, 2018 53 minutes ago, Blawre said: Hi, Pleased to let you have my stable settings. I, too had JPlay KS and setting 1Hz 10s. However I found that Nontallion 8.88 would not run with these settings so I had former for Hysolid and 20 Hz 1s for Nontallion. When I injected WASAPI I found that 1Hz 10sec did not run and after experimentation I have settled on 20Hz 2s, which, incidentally is OK with Nontallion too. I feel that the JPlay settings are probably determined by the DAC and computer HW so its a case of experimenting. I run WS2016 in core mode on single INTEL i5 computer with 8Gb RAM. My DAC is an M1 Mus Fid preceded with a MS 192 VLink. Usually when I run Hysolid I run from the lock screen (i.e. before sign in.) Control is from an Android tablet or phone. Regards Hi, I need to experiment more. Mine is a dualPC setup, with B.M.C DAC. Does your 20Hz 2s setting work with DSD too? Many thanks for your kind response. For a long time I haven't had Bug Head on my PC, just using HySolid exclusively. JplayMini gets use sometimes for testing mainly. Foorbar2k will be next on my list. Beside using optimization software, how do you tweak your PC hardware? Happy listening! WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted February 13, 2018 Share Posted February 13, 2018 1 hour ago, JazzDoc said: Earlier today, Marcin posted the following on the JPLAY Forum: "From a technical point of view, it's impossible for WASAPI to sound better than KS. At least not via JPLAY." I wonder if he is implying that it is theoretically not possible for WASAPI to sound better than KS or whether he is stating that WASAPI will not sound better than KS via JPLAY I think he meant what he said, WASAPI can't be sounding as good as KS [due to the latter's lowest latency] technically. As to which sounds better subjectively, it's up to personal preference. I had doubt whether one is sounding better or worse than the other. Now that I've listened a bit more, I realized that this is actually a win-win situation, that we poor audionuts now have a choice, that whether we prefer one over another depends on our HW, SW, tweaks, optimizations, moods and personal tastes. That said, there're distinctions in SQ between the two IMHO. In comparison, KS seems to be the ruthless, matter-if-fact version of truth while WASAPI seems like the romantic version of truth. Both are like freshly roasted coffee, KS is more like dark to medium roasted white WASAPI is more like medium to light roasted coffee. WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted February 13, 2018 Share Posted February 13, 2018 3 hours ago, Blawre said: Hi, My DAC doesn't support DSD. BTW having a low time on JPlay Buffers has the added benefits that Hysolid is virtually gapless. The only HW tweaks I have is a dedicated USB card which is battery powered. My OS SSD drive is also battery powered. I have tried dedicated linear power but much prefer LI batteries. Foobar doesn't seem too picky at all. Cheers There're optimized settings on network card, USB hubs, and DAC driver you might want to look at. What OS are you running? WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted February 13, 2018 Share Posted February 13, 2018 Sorry I missed the WS2016 Core part. Basically, I turn off power management of USB hubs and Ethernet card, set DAC, NIC, USB parameters to lowest latency. Hope you've done most if not more of them already. WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted February 25, 2018 Share Posted February 25, 2018 Like WS2012r2, with WS2016 one can control the music server from his smart device wirelessly even though the server connects to local wired network. The server doesn't need to be wifi enabled or capable. The home router provides wifi to smart device. That's my two cents understanding, and that's what I'm doing. Highly recommend WS2016 Core and AO. Coming from WS2012, there should be no insurmountable issues upgrading to WS2016. Reward in SQ is for real. WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted March 3, 2018 Share Posted March 3, 2018 WS2016 Core offers higher SQ than GUI but requires knowledge on using command line to install drivers. AO is a must imho to successfully install the OS, drivers and optimization tweaks. If I can do it, you can and will do better. You'll enjoy the OS and better SQ. Good luck! WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted March 4, 2018 Share Posted March 4, 2018 4 hours ago, simonklp said: Dear Phil, wish you all the best and could recover completely at the soonest. Get better soon! WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted March 4, 2018 Share Posted March 4, 2018 5 hours ago, tboooe said: I am a dummy....forgot to run AO -WASAPI. Everything working again! Looking forward to comparing Server 2016 to 2012 Congrats! Let us know your findings. WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted April 17, 2018 Share Posted April 17, 2018 Ctrl + Alt + Del ? WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted August 19, 2018 Share Posted August 19, 2018 Even in core mode with command prompt, we can navigate around until we find the executable file we want, type its name then hit Enter to run it. For essential commands in core, please read AO manual page 8, "Basic DOS commands". In addition, Q-Dir is our friend. Install it and we will have a "Windows Explorer"-like style interface. With it we can navigate around, copy, paste, delete, execute files, etc. In fact for us most, install Q-Dir is about the very first thing we do after an OS installation. Navigating around and doing things in core mode, compared to GUI mode, is like switching the driving from automatic transmission to manual (aka stick shift) transmission. It seems a bit challenging at first, but educational, powerful, and fun later on. If you Amir decide to go this route, good luck and enjoy the ride. WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted December 1, 2018 Share Posted December 1, 2018 My wishes for AO 3.0: 1/ Similar to a high-end Canon camera, there would be 2 to 3 Custom Settings named C1, C2, C3. AO will be capable of memorizing, logging, and saving user's settings into those custom holders. Next time the user configures the AO, he/she just picks C1 or C2 or C3 with a keystroke and bam, AO will swiftly fly thru those presets without errors and time consuming efforts. 2/ AO provides options for the tinkering user to further optimize his/her server at his/her own risk. For instance, killing/disabling certain services/processes the user feels unnecessary, enabling/disabling certain OS features the user needs/doesn't need. 3/ Similar to a high speed broadband service, AO would provide a tool by which the user can use to monitor, measure and tune his/her system's audio performance, before and after changing a setting. AudioPhil 1 WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
Popular Post thuandb Posted December 23, 2018 Popular Post Share Posted December 23, 2018 In point #3 I meant to ask for a way, an yardstick the AO user can use to monitor his system performance that directly is related to SQ: thermal, CPU, memory, network. Then based on that information, AO user would be capable of tuning the SQ by adjusting system parameters with help from AO tools. Understandably, it's a tall order. But expecting no less from AO, I'm sure that way AO will stay strongly competitive and extremely useful to computer audiophiles who are growing daily in number. moriez and AudioPhil 2 WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted January 23, 2019 Share Posted January 23, 2019 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. AudioPhil 1 WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted January 23, 2019 Share Posted January 23, 2019 I'm using JPLAY FEMTO (v7) as music playback software. WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted January 24, 2019 Share Posted January 24, 2019 While running AO -u, I had to make the choice of whether to disable JplayStreamer or not. It should not ask the question because I'm running JPLAY 7 which consists of JPLAY audio service and JPLAYFemto server service. JplayStreamer is long gone in the current JPLAY Femto. AudioPhil 1 WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted January 25, 2019 Share Posted January 25, 2019 BASELINE: DualPC, both running WS2019 JPLAY Femto CAD script. Warm, adequately detailed, musical SQ. Preferred over WS2016/AO 2.20 AO3 Beta phase 1: Same as baseline except: AO3 installed on AudioPC. Digital filter X, Sound signature X. SQ: more sophisticated than baseline with a touch of digital like. More clarity, cleaner background, faster sounding (pros), with a touch of upper range grain that makes longer than 10 minute listening unpleasant (cons). Without further testing various DF/SS combos, CAD 8.1 was applied as SQ mitigation and for further reduction of extraneous processes/services. Now it sounds more like it: there's a good balance of musical warmth and increased clarity, the upper range grain is gone. I'm torn between the baseline and this AO3/CAD 8.1 combo. Either setup sounds really good on certain albums/music genre but not so on others. thuandb 1 WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted January 25, 2019 Share Posted January 25, 2019 Hi AudioPhil, Can you please help me delete my posts #915 and #918? The primary reason is that I unintentionally violated the Beta Testing Rules by including a foreign script to the mix. Doing so invalidates the purity of testing environment thus producing misleading results. Thanks for pointing it out promptly. In all honesty, the misleading report is lagging in time. Last night I properly installed AO3 on controlPC which I should have done in the 1st place and stated up til 3 am, amazed at the awesome SQ. Stupidly, I posted the delayed 1st phase report in attempt to save the best for last. Now, I'm going to remove the CAD script from AudioPC, have both PCs properly optimized and post a more complete (SQ, how easy/difficult to install), still unbiased but violation free thus not misleading report. AudioPhil 1 WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
Popular Post thuandb Posted January 26, 2019 Popular Post Share Posted January 26, 2019 Where am I coming from: for the last 6 months, especially since JPLAY FEMTO release on 10/31/2018, I've been hooked running WS2019 Standard on both PCs as in dualPC. Without AO availability, and thanks to JPLAY Forum goers (Nobi, Milen, and Minorisuke), I managed to install WS2019 Standard (Core) with FOD (Features On Demand) ISO, inject KS driver capability to the system, customize the CAD 8.1 scripts, and enjoy the wondeful music flowing out from the setup. Basically, it was a warm very easy to listen to kind of SQ. For the purpose of comparison I call it base line SQ. Fast forwarding to last Tuesday 1/22/2019 when AO3 Beta test was announced, I'm one of those who applied to be a Beta tester and accepted. Not wasting any time, I started right away with the AudioPC, leaving the controlPC unchanged thinking it'd be best to change one PC at a time. That's the first mistake. Fresh installation of OS on AudioPC went well, but what pleasantly surprised me was how quickly, smoothly, and precisely the installation of AO3 went. As long as there's Internet connection, the AO3 gets installed, configured, and executed blazingly fast and with ease, just like it says, "sit back and relax". As a clumsy tinkerer like me who had struggled endlessly to achieve the KS injection, Device Manager capability (a must for successfully installing drivers), more than anyone else I understand and appreciate the value of brainwork, time consumption, and labor put into this achievement. The end result in execution of commands and operations is very well done, to say the least. It clearly outperforms the AO 2.20 in speed and sanity of execution. Eager to hear AO3 firsthand, I let the unchanged controlPC stream music onto the AO3 optimized AudioPC and had a listen. This manifested the first mistake. Upon the short listen I found the new SQ a mixed bag. While it seemed more "sophisticated" (for lack of better word) sounding, clearer, cleaner background, there's a touch of grain in the highs that made me not want to continue. "Since the CAD scripts are available and have been serving me well, why not utilize them just to see what they can do to improve the sound?", I thought and did it. That's the second mistake I made that produces misleading results as shown above. The rest is known to everyone. AO3 author promptly corrected me, and I'm here writing a report on an ongoing test, hopefully done with more ethics and competency. Another fast forwarding to Friday 1/25/2019. Most current AO3 is Beta 29 so that's the version to be installed on both PCs. Fresh OS, chipset, drivers, static IP, JPLAY, and AO3 have been installed properly. Before sounding off, there're a few notes and observations: 1/ unless Shell replacement has impact on SQ, I'll leave it to others to chime in and discuss 2/ disabling JPLAY FEMTO is already done on AudioPC, how about choice of disabling JPLAY Service on ControlPC? 3/ there're a number of extraneous processes and services that are still running while not appearing to contribute to the music playback or JPLAY. Can AO3 terminate them? Now and finally, onto the sound quality. The short version is, it is shockingly good. The level of improvement is as impressive as JPLAY Femto when the latter was released over 3 months ago. With the AO3 optimizing dualPC running WS2019 and JPLAY Femto, the resulted SQ is stunning clear, detailed, and emotion conveying, scaling musically and effortlessly with most if not all music genres no matter how fast or slow the music is played. What keeps on coming to mind is, "Wow, what a Trinity of AO3, JPLAY, and WS2019". While listening, it's easier to switch (or be switched) from analytical mode to pleasure mode than vice versa. There's a clearer sense of weight, confidence, decisiveness vs music played in baseline setup. It's much easier to "see" what happing in recordings, more sense of ambience and depth sometimes audible from the first second into recording. Music played were: Angel Romero's A Touch of Class, Telarc 1988, tracks Claire De Lune, Adagio Flamenco Passion, track Las Minas Alex Lofoco's Beyond Eleani Karandrou's Tous des oiseaux Mask and Mirror Rebecca Pidgeon's Spanish Harlem Rachel Podger plays Vivaldi in DSD Many tracks from Best Audiophile Voices AudioPhil and FelipeRolim 2 WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted January 26, 2019 Share Posted January 26, 2019 I'd like to report an issue upon attempt to install AO3 Beta 30 on controlPC. After successfully installing, configuring and executing AO3 Beta 30 on AudioPC, I went on to controlPC, making sure there's active internet connection prior to and during the AO3 installation. Again my expectation, the software kept giving me the warning, "AO 3.0 NEEDS AN ACTIVE INTERNET CONNECTION", stayed on screen for a short 2 seconds and went away. By nature the controlPC always has active internet connection, otherwise DualPC wouldn't work. Evidence of that is, I'm now using BubbleUPnP as control point communicating to controlPC via internet to play music. AO3 Beta 30 is on AudioPC, AO3 Beta 29 on controlPC, until I can convince AO3 Beta 30 to land on my controlPC. Appreciate any advice. WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted January 26, 2019 Share Posted January 26, 2019 Thank you for the message. Per your advice I went to the explorer folder to find no files in there. Then I tried to install Firefox as interim brower. The Firefox installer took too long and didn't seem to get anywhere. I guessed it could be successful after an AO3 reset, so I killed the Firefox installer and was about to reset. But looking at both PCs connecting to each other and connected to the Internet, I had an instinctive curiosity, "What if the controlPC may fool AO3 into thinking that the static IP between the two PCs are the only network connection available?" Sure enough, I shutdown the AudioPC, left only Internet connection available on controlPC, reran AO3 Beta 30, and bingo - Beta 30 successfully landed on controlPC ground. By the way, I love the way Beta 30 cleverly automates network enabling on both AudioPC and controlPC as Beta test default. This is another step in pushing the envelope. WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted January 26, 2019 Share Posted January 26, 2019 Great tip, thanks! WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted January 26, 2019 Share Posted January 26, 2019 7 minutes ago, AudioPhil said: Your network setuü is miced up thuan Not related to AO I plead not guilty 😋 AudioPhil 1 WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted January 30, 2019 Share Posted January 30, 2019 Beta 31: Set up and Shell Replacement work normally considering available software in the PC. Overall operations seem a tad slower than Beta 30, hesitating in checking for software security. Driver Helper does help. WASAPI availability is a big welcome, especially to Roon users. AO -filter is a nifty feature. As good as X/X used to be on both PCs, 1A/4D is noticeably different in a more favorable way. Switching from X/X to 1A/4D is almost like seeing someone just stepping out of the fog. WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
thuandb Posted February 14, 2019 Share Posted February 14, 2019 I'm running AO3 B32 on DualPC setup. IE shortcut found in Desktop folder on both PCs. Clicking on the IE shortcut results in the following message(s): On AudioPC: "Missing shortcut" On ControlPC: "Missing shortcut", then "Fix, Delete, or Cancel", click on Fix, then a big long blue warning on the center of screen, "This app can't run on your PC. To find a version for your PC, check with the software publisher." AudioPhil 1 WS2019 Core Datacenter, dualPC, JPLAY Femto, AO3, Fidelizer Pro 8.8, MC2XY, IOS app. Link to comment
Recommended Posts