Jump to content

gonefishing

  • Content Count

    22
  • Joined

  • Last visited

About gonefishing

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @ Phil, Happy to hear your feeling better, seeing your back 🙂 Interesting bit about the JPLAYfemto activation. Can you reproduce this behaviour, or did this happen only once? "Confirmed seems this only happened once and has been ok on subsequent rebuilds - No action required". Phil, In all the years with AO and each upgrade I have never had this situation. I have always installed JPLAY and my DAC driver on a clean OS and tested audio is operational in a dual JPLAY PC setup. Then I install AO for optimisation. Though with AO 3.0 the DAC driver is knocked out when running AO optimisation for the first time and I have to reinstall the DAC driver. Easily fixed with a reinstall but different behaviour compared to all versions of AO before 3.0 I adopted the process outlined in the online manual https://www.highend-audiopc.com/PDF/audiophile-optimizer-setup-guide.pdf “Best Practice After installing Windows, a Media Player, Drivers for your DAC or DDC as well as the AudiophileOptimizer be sure that everything works before you actually use the AudiophileOptimizer” OK if AO 3.0 is changed and does not follow the previous manual processes explicitly and a new manual will guide the right process to use 😊 Cheers John
  2. Hi Through all the bata’s tested 31 to 36 I have never had to disable the driver signing at startup. Its never been a problem. Regarding my DAC driver getting knocked out after running AO - Audio Optimisations. From Audio Phil’s manual page 5 - Recommended Scenarios "Best Practice After installing Windows, a Media Player, Drivers for your DAC or DDC as well as the AudiophileOptimizer be sure that everything works before you actually use the AudiophileOptimizer." It made sense to me when I read the manual and having verified - everything works before you actually use the AudiophileOptimizer. AO - Optimisation - is knocking the DAC driver out. AO is an optimiser, shouldn’t it need to know about JPLAY and DAC drivers before running AO -Audio Optimisations. Or has the best practise process manual page 5 - Recommended Scenarios changed? I would like to hear from Audio Phil on that thanks 😊
  3. Hello Phil, There is only two minor issue that I encounter during installation but easily worked around to get going. Is this something which can be remedied. Starting with a clean OS windows server 2019 core build Install JPLAYfemto and activate = restart and confirm activated. Install PS Audio DAC driver = confirmed DAC connected. Install AO beta 36 Run AO beta 36 in ultra-mode and results in JPLAYfemto now unlicensed, I need to run turbo activation restart and confirm activated again. PS Audio DAC driver is now in error in device manager, I need to uninstall device and reinstall device all is ok after that. JPLAY and DAC driver installed before I run AO optimisations, that’s the right process order or am I wrong? Thanks John
  4. Report single PC in Ramdisk. second PC under-construction OS: build 17763 windows server standard 2019 core DAC/DDC: PS Audio Directstream = USB connected Driver/Version: USB ver 1.61.0.0 Need to press F8: No, however if I have the USB driver installed before installing and running AO optimisations, I need to go into Devmgmt.msc delete the PS Audio driver and reinstall it. All is good after that. Player: JPLAYfemto KS working: YES WASAPI working: NOT used Needed HD Audio Driver: NA
  5. Hello Phil, I’ve tried each Beta since 31, 32 and now on 33 I’m using Single PC in windows core 2019 with JPLAYfemto in Ramdisk, no trouble experienced with any version sounding great. I'm using the compacting feature now to, and my single pc works well going into hibernate and coming back out with no trouble using Firadisk as the controller. Phil does AO support the other Ramdisk controller I know of which is "SVbus" https://sourceforge.net/projects/svbus/ I tried SVbus before beta was available it worked as well as firadisk as Ramdisk it could be another option for those wanting Ramdisk. SVbus is a later driver. Although the software designer stated SVbus does not support hibernate mode if those wanting to use SVbus for Ramdisk, then hibernate may not work as expected. Great work Phil and thanks, AO is making the software installation process way simpler and providing some flexibility to tune sound Thanks John
  6. In GUI, if settings is minimised thereafter play is possible
  7. Hello Phil On a PC running Audiophile Optimiser. In GUI desktop there is the Performance Options window in the advanced tab there is processor scheduling – adjust for best performance programs or back ground services. If this is changed does this affect Filter settings of AO? Thanks John
  8. Hi Phil, sorry my poor grammar. I’m not 100% certain what the shell does in AO. The new JPLAYFemto (server) software does run as service in task manager, the services are JPLAYFemto and JPLAYService, would there be a benefit for a shell in AO for JPLAY. Thanks John
  9. Hello Phil Regarding shell replacement - bypass Explorer/Desktop in GUI mode for better Sound Quality With the new JPLAY Femto could you create shell? for AO Thanks John
  10. Hello Phil Bug report for Version 2.20 Beta 4 on windows server 2016 in core on Control PC Problem report if I have disable network related services I lose the JPLAY link to the Audio PC. no ping possible. error unable to contact IP driver. General failure. Phil wrote "This no ping possible. error unable to contact IP driver. General failure." it has been like that since the introduction of this feature three years ago. it is by design and completely normal." I'm talking about the USB nic dongle, the PCIE nic and on board mobo nic of the Control PC work as expected it is only when the USB nic on the Control PC I get this problem "error unable to contact IP driver. General failure" it worked in Win Serv 2012R2 AO Version 2.20 Beta 4. problem arose when I switched to Win Serv 2016 AO Version 2.20 Beta 4 Regards, John
  11. Hello Phil, Re Bug report for Version 2.20 Beta 4 on windows server 2016 in core on Control PC Problem report if I have disable network related services I lose the JPLAY link to the Audio PC. no ping possible. error unable to contact IP driver. General failure. The network adapter displays using: ipconfig /all. If I was to set - rewrite make static again I get the RPC server is unavailable. Repeating this with "network related services" = disabled the cmd works as expected overnighting the static address. Does this help narrow things down
  12. Hi Phil Yes set static via cmd line. DHCP =NO
  13. Hi Phil, Any chance this problem could be resolved? Bug report for Version 2.20 Beta 4 on windows server 2016 in core on Control PC Problem report if I have disable network related services I lose the JPLAY link to the Audio PC. no ping possible. error unable to contact IP driver. General failure. if I roll back and enable network related services the Audio PC can be ping and plays as normal. Windows server 2012R2 with AO 2.20 Beta 4 worked OK and other previous version until I changed to win serv 2016 Really looking forward to the access to device manager under 2016 core great stuff Cheers John
  14. Hello Phil What exact setup did you have when it was working? OS and exact AO version is of interest Previous install = server 2012R2 core mode with AO Version 2.20 beta 4 in ultimate mode with all setting that can be shutdown, I've previously had network services off, as using static. Using serv2016 on the Audio PC I get the same trouble as with the control pc with USB dongles. Would you like me to record the settings in detail, I can reset drivers (st) and run (ao) again writing them down as I go?
  15. Bug report for Version 2.20 Beta 4 on windows server 2016 in core on Control PC Problem report if I have disable network related services I lose the JPLAY link to the Audio PC. no ping possible. error unable to contact IP driver. General failure. if I roll back and enable network related services the Audio PC can be ping and plays as normal. this is when I'm using a USB dongle on the Control PC. A PCIE network adapter in the same PC does not exhibit the problem, but does not sound as good as the USB dongle.. most services are disabled where I can in AO using ultimate mode. This is a repeatable problem. previous AO builds I could disable network related services. Static is set. anything else I can do to help trouble shoot Phil? Thanks John
×
×
  • Create New...