billg Posted March 26, 2018 Share Posted March 26, 2018 Hi. I just made a 2016 core machine with AO 2.0b5 and no problems :-) But when I tried to update to b6 - by copying only setup.exe to the AO directory and then running it. Setup runs to the point where I accept the Terms and Conditions and when I do it crashes. Should I run ST again? Any advice appreciated. Link to comment
billg Posted March 26, 2018 Share Posted March 26, 2018 Thanks Phil. I tried running setup from AO2.0b6 in the root directory (after replacing the setup.exe for AO 2.0b5 in the AO directory) but got the same results. Link to comment
billg Posted March 26, 2018 Share Posted March 26, 2018 No. And it did not create a new AO directory or any new files in root. Link to comment
billg Posted March 26, 2018 Share Posted March 26, 2018 It worked on the second system which is 2016 gui mode. It created new files on AO directory and the change log states 2.20 beta 6 (sorry I've been stating 2.0b6 by mistake). Link to comment
billg Posted March 27, 2018 Share Posted March 27, 2018 I copied the AO directory (2.20b6) across to the problem computer and ran audiophile_core.exe -u successfully. Not sure if there's any more I need to do. Link to comment
billg Posted October 8, 2018 Share Posted October 8, 2018 I use clonezilla with good results. Link to comment
billg Posted October 10, 2018 Share Posted October 10, 2018 Remember to use the same version of clonezilla for the restore if you need to do it. Link to comment
billg Posted November 8, 2018 Share Posted November 8, 2018 There's no shell replacement for a simple command prompt in GUI mode. Would it make more sense to add a shell for JplaySettings as it is an app with very low resources. This might be useful for both Jplay Femto and JplayMini users. Link to comment
billg Posted November 8, 2018 Share Posted November 8, 2018 It does on my system if it's open when you start playback, but you can't use it or open it while playing. Link to comment
billg Posted February 21, 2019 Share Posted February 21, 2019 There seems to be a problem with the initial audiophile_optimizer setup enabling kernel streaming. On a clean core 2019 OS on SSD I installed -Ps Audio DAC driver (ok, no KS) -Jplay Fento (audiopc) (ok, no KS) -Ao 3b34 (no KS available although I selected to enable it, Dac driver now has "!" in devmgmt) -ao -wasapi (now the driver has "!" in devmgmt) -reinstall the PS Audio dac driver (not fixed) -F8 reboot and service_tool, driver help, HD Audio driver This worked (yay) giving an installed driver with kernel streaming working. But on the next boot the high definition audio controller and the PS Audio Perfectwave DSD driver have "!" in device manager and kernel streaming doesn't work in Jplay Femto. If I boot again with f8 the dac driver shows installed without "!" and kernel streaming is available. This means I must use f8. I can't create a working vhd (I cant boot from a vhd using f8) and therefore cant use ramdisk. Link to comment
billg Posted February 22, 2019 Share Posted February 22, 2019 !!!SUCCESS!!! Windows server2019 AO3b35, Femto 2pc (Controlpc gui & Audiopc core), KS and ramdisk. I went through all the steps suggested in this thread doing several backups of the vhd along the way. Hopefully I can streamline things in future. Do I really need the FOD, wasapi injection, HD audio Controller, all those reboots, etc? Surprisingly, I did not need service tool driver help with the PS Audio DSD dac driver this time. Thanks to Phil for making KS possible and Peter A for clarifying the process. Now listening to Coleman Hawkins - Good On Broadway, and having a celebratory beer - Tuatara Kapai Pale Ale (this is in NZ). 😚 AudioPhil 1 Link to comment
billg Posted February 26, 2019 Share Posted February 26, 2019 OS: windows server standard 2019 gui (controlpc) and core (audiopc) both ramdisk DAC/DDC: PS Audio Directstream = USB connected Driver/Version: USB ver 1.61.0.0 Need to press F8: No, but needs to be reinstalled after running AO Player: 2PC JPLAYfemto KS working: YES WASAPI working: YS Needed HD Audio Driver: working probably not needed. AudioPhil 1 Link to comment
billg Posted March 3, 2019 Share Posted March 3, 2019 I have AOb36 on a new build of my Jplay Femto Audiopc, win 2019 standard core, ramdisk. I had some problems getting the KS and the driver set up but don't know what caused it. Nothing worked until I started again on a fresh OS install. Not a big deal as I had a backup copy of the clean os on vhd. OS: Windows 2019 Standard Core DAC: PS Audio Directstream dac Driver: PS Audio ASIO F8: Not needed Player: Jplay Femto 2PC KS: Yes AO -Wasapi: did not try to install HD Audio Controller: not used I haven't had time for a proper listen and it was sounding great with b35 anyway. @Herman17 I have DSD128 playing on my PS Audio Directstream dac with KS and hibernate. I cant find a DSD256 track to test although I have a couple somewhere. AudioPhil 1 Link to comment
billg Posted March 14, 2019 Share Posted March 14, 2019 Hi Phil, I wonder whether it would be nice to have a different AO interface, like a traditional GUI application. Maybe add a menu (Setup, Service Tool, Set Filters, Help). We could select all the set up options on one page and walk away while AO installs and reboots. This would be simpler to use with a config file too. Just import the file and it would pre-set the options for review. This could present your fine work elegantly in the manner it deserves. I realise such an app would entail some work and I have no wish to delay the final release of 3.0. Perhaps 3.1? Just a thought. The application designer in me couldn't resist 🙂 AudioPhil 1 Link to comment
Recommended Posts