Jump to content
Sign in to follow this  
AudioPhil

AudiophileOptimizer BETA Thread (AO 3.00 beta is closed)

Rate this topic

Recommended Posts

Beta 38 installed without issues and run in Windows Server 2019 spanish version with FoD.

Players: Foobar2k, HQPlayer, BugHeadEmperor

 


Intel DH67BL motherboard. Intel i7-3770 CPU. 16 GB RAM DDR3 1333. HDPlex H5 2nd Gen. HDPlex Linear PSU 200W. HDPlex 300W DC-ATX psu. ifi-iUSB3.0 / ifi-iGalvanic3.0, Paul Pang V2 USB card. Asus Xonar Essence STX. Nixon Saru DAC TDA1543 nos, DIYINHK USB interface, diy PCM1704 NOS DAC, ifi nano DAC. ODAC. diy Pass F4 & BA3 frontend, diy EML-320BXLS SE amp., diy D.Self Compact Blameless, diy Aksa 55.  PGA2310 Volume Control.

Dual boot Windows Server 2019 GUI - Windows Server 2019 (Core)

Bug Head 7.27 (avx), Foobar2k, Hysolid

WTFplay

 

 

Share this post


Link to post
Share on other sites
3 hours ago, AudioPhil said:

FYI:

 

js.cmd can only launch JPLAYSettings when it actually does work. When it does not work, js.cmd can‘t launch it :(

 

JPLAYSettings does not launch when it has a (physical) connection issue with the DAC/DDC. This is default behavior of JPLAYSettings.

Phil this does not make sense to me.

 

the only difference between working and not working is setting the default shell on the Control PC to Roon Server  from the Windows default.

 

Nothing changes on the Audio PC or the Control PC.  How do I trouble shoot this?  

 

 

magicknow

Share this post


Link to post
Share on other sites

I think control PC interacts with audio PC. When there is a certain interaction (jplay driver, streaming protocol, etc), you have that lock up. So they are not independent of each other. There was some start up sequence change (manual to automatic, that is) in the control pc, right? Somehow the automatically started control PC kicked the audio PC, in turn, putting it into a numb state hence no response to the js command (or something like that).


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

Share this post


Link to post
Share on other sites

It‘s the default behavior of JPLAYSettings. When there is something wrong with the DAC or its connection, you will just get a black screen. js.cmd cannot change this.

 

when you set roon as shell it occupies the device, therefore jplaysettings can no longer connect to it = black screen.


ıllıllı [  ...AO 3.00 IS HERE... ] ıllıllı
____________________________________________________________________________________

 

Shop | Core Audio Music Server | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide

 

Share this post


Link to post
Share on other sites
2 minutes ago, AudioPhil said:

It‘s the default behavior of JPLAYSettings. When there is something wrong with the DAC or its connection, you will just get a black screen. js.cmd cannot change this.

 

Fair enough but how does something suddenly go wrong with the DAC connection just by changing the default shell on the Control PC?

Share this post


Link to post
Share on other sites

Booting sequence is a very complex one. If roon core and jplayasio code load and run during the boot sequence (i.e. automatically loaded), there can be some unexpected because certain programs are required to be loaded prior to certain others. That is why things are fine when you load manually after boot sequence settles.


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

Share this post


Link to post
Share on other sites

thanks for this, Is there any way to get this working correctly?

 

I think by design JPLAY has to load automatically and obviously if I set Roon Server as the default Shell it also has to load automatically, correct?

 

Given this what is the way to get this working correctly?

 

Cheers

 

 

Share this post


Link to post
Share on other sites
4 hours ago, shinyc said:

Maybe you can place a delay command like "timeout /t 20"  just before the roon core invoking line in the AO startup shell script. 

Perhaps you can edit the AO roon startup script per above quote and try see if it works.


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

Share this post


Link to post
Share on other sites

Ok but I am not sure how to do that  exactly, is this the correct place to find the startup script?  If so which file it does not have any named just room Server Shell?

image.png.024ca9ab91124590dbc9931d56df67fb.png

Share this post


Link to post
Share on other sites

Yes, I would try that cmd script. Of course you would delete (or REM) the hqplayer line. It seems it has a timer built in. If you are not sure, you can still add the following line to delay the "start" command:

 

timeout /t 20


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

Share this post


Link to post
Share on other sites
40 minutes ago, shinyc said:

Perhaps you can edit the AO roon startup script per above quote and try see if it works.

Please NEVER try to edit anything that comes with AO, expect it‘s meant to be edited!

 

AO 3.00 offers a custom shell (custom_shell.cmd) which can be set as shell replacement using ServiceTool. This is the one and only part of AO that is meant to be edited.

 

Edit the custom_shell.cmd to suit your needs. Test it very well so it does exactly what you need it to do. After verifying it works as you need it, set it as shell replacement. Voilà :)


ıllıllı [  ...AO 3.00 IS HERE... ] ıllıllı
____________________________________________________________________________________

 

Shop | Core Audio Music Server | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide

 

Share this post


Link to post
Share on other sites

Yes, Sir.


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

Share this post


Link to post
Share on other sites

would this be a resonable one to try?

 

@echo off
REM Created by: Highend-AudioPC
REM https://www.highend-audiopc.com
Title "Launching custom shell..."
@echo off
echo Launching custom shell...
ping -n 3 127.0.0.1 -w 1000 >nul
REM start /HIGH "HQPlayer" "%Systemdrive%\Program Files\Signalyst\HQPlayer Desktop 3\HQPlayer-desktop.exe"
timeout /t 20
start /HIGH "RoonServer" %userprofile%\AppData\Local\Roon\Application\Roon.exe
exit

Share this post


Link to post
Share on other sites

That looks about right. 

 

"ping -n 3 127.0.0.1 -w 1000 >nul" is equivalent to 3 second timer (you can change 3 to 10 or 20). You can delete the timeout thing.

 

Of course, you would name this file "custom_shell.cmd".

 

 

 

 


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

Share this post


Link to post
Share on other sites
49 minutes ago, shinyc said:

Of course, you would name this file "custom_shell.cmd".

 

Exactly! Otherwise ServiceTool would not find the custom shell :)


ıllıllı [  ...AO 3.00 IS HERE... ] ıllıllı
____________________________________________________________________________________

 

Shop | Core Audio Music Server | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide

 

Share this post


Link to post
Share on other sites

thanks Shinyc  this worked great

 

Phil the path for RoonServer in the sample file is incorrect ,  it should be 

 

start /HIGH "RoonServer" %userprofile%\AppData\Local\RoonServer\Application\RoonServer.exe

Share this post


Link to post
Share on other sites

Thanks, It‘s just a sample file to show the idea about what to do. :) Will adjust it to avoid confusion.

 

For working path‘s you can use all other cmd files in the tools directory.


ıllıllı [  ...AO 3.00 IS HERE... ] ıllıllı
____________________________________________________________________________________

 

Shop | Core Audio Music Server | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide

 

Share this post


Link to post
Share on other sites

Oh cool. It did work for you. Nice going. I am glad.


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

Share this post


Link to post
Share on other sites

AO3BETA 38 installed and worked well.  Player JPLAY FEMTO.  Both KS and WASAPI worked.  WASAPI: Hibernate off, DAC Link up to 200Hz.  KS: Hibernate on, DAC Link up to 1000Hz (max).


WS2019 Datacenter Core, dualPC, JPLAY Femto, AO3, Fidelizer 8.5, BubbleUPn.

 

Share this post


Link to post
Share on other sites

Hi Phil

 

Something has changed with Audirvana,  it runs great  in Windows Server 2019 Gui,  it seems to work well with JPlay Femto  and a two PC setup.   Can you look at adding back the able to run Audirvava as a  replacement shell please?

 

thanks

 

 

Share this post


Link to post
Share on other sites
1 hour ago, StreamFidelity said:

Hi,

 

has anyone actually tested Windows 10 Pro?

 

thanks

Not really but I have been thinking about it for the Control PC.  i am wondering how important the choice of OS is on the Control PC.

 

 

Share this post


Link to post
Share on other sites
4 hours ago, magicknow said:

Not really but I have been thinking about it for the Control PC.  i am wondering how important the choice of OS is on the Control PC.

 

 

I am using 10 Pro on control PC with AO 2.2 and the attached the Audio PC uses WinServer 2019 GUI and AO latest 3.0 beta.

Sounds very good, but I did not compare to Server also on control PC.

 

AO can strip Win Pro of excess stuff and also replace the GUI... I found these AO functions changes the sound from stock WIN Pro..

 

One thing for sure, is the AO sound signature and digital filter settings on the control PC are obvious..

I was shocked by this as I found they are just as obvious on control PC in 2 PC setup as for when I used a single PC setup😲.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

×
×
  • Create New...