Ok sorry I did not see that. Anyway I dont really need the web server I think, but good to know.father.mande wrote:Hi,
Some points are already discuss in the forum ...
summary :
1 ... to use myHD web ... you need to validate Web server (web admin use another server NOT open for private web interface)
... so validate Apache web server in service ... restart myHD (myHD add configuration for security) (command : myHD restart)
... remember to use (you acn change it later) credential : myhd / asusfr1 to access Web UI
OK, thanks. For now I think I will stay with ALSA, since this part works well.father.mande wrote: 2) ... using pulseaudio require a complementary configuration adapted to each model ... follow the tips & tricks advice
... shortly connect to myHD as root (myHD_root) and use script to test and validate pulseaudio : /myHD_scripts/bin/test_pulse_Intel_config.sh
... at end you get information to change in user environment to be able to use pulseaudio
... THIS is due to the fact that it's the default Ubuntu delivery (so 18.3) BUT not build as Asustor or "standard" APKG specifically for Asustor NAS ... so require some more configuration (one time)
... ALSA is always better in Kodi if you need to use pass-through (AVR or ... )
Here I still have problems. Using xrandr can indeed awake Xorg, but its very unconvenient to use it manually every time. I ended up writing a script that checks xrandr periodically via a poller... it's very ugly, but it works somewhat... it also restarts Kodi everytime the TV gets turned on, because if you reawaken Xorg via xrandr, it messes the fonts on Kodi (and for instance subtitles no longer work, along with file listings etc).father.mande wrote: 3) I never test this situation ... because I keep an HDMI plug pass-through at back of each NAS to be able to use Xvnc_server to access Asportal and Applications for functionnal test (for ex. I test Kodi19 (without sound due to vnc protocol) from my PC at 600 kms of my labs using a VPN ... so for an integrator it's a good first test approach ...
When I will go back to my lab ... I will try to run a test ...
... but using xrandrd --auto HDMIx (x depend of your system) can awake Xorg
... restarting MH-kodi18 as any APKG must be also enough
... to change Xorg or restart it ... it's also an APKG so you can ever use App. Central or usual script /usr/local/AppCentral/xorg(or any APKG name)/CONTROL/start-stop.sh start|stop|restart depend of your request
... if Asportal don't restart ... do the same after restarting Xorg
... take care that the start-stop script can change your terminal environment and generate error using some tools, so do it in a separate terminal if you want to works in parallel .
myHD application MH-xxxx are in fact only "launcher in Asportal to application in myHD" ... so generally don't need to be restarted or enabled again (it's just basic shell script created by an APKG generator)
If someone is interested, I can post my script. It's really a hacky workaround that I hate, but not sure if I can do better for now.
I am very surprised by this. What do you mean exactly? I guess what is used in the end is the kernel driver, so the one supplied by Asustor, I dont understand how stuff from the embedded Ubuntu can be used at all at this level. About my hardware - it worked perfectly (even with a long cable) before the software upgrade of ADM, so I know it should work. What do you mean by "if your codec is able to accelerate 4k" ? Which codec?father.mande wrote: N.B. myHD use an embedded Ubuntu 18.04 LTS with video acceleration 2.1 (compare to 1.7 provide by Asustor) so if your codec (use vainfo in myHD to get information) is able to accelerate 4k ... you can use it (if hardware support it) be sure to use good cable and you must understand that power supply by HDMI NAS plug is low ... so short is the cable better is the result.
NB1 please consider that I own only ONE NAS with HDMI from Asustor ... so I don't know and test all models ...
Philippe.
Anyway this is what vainfo returns:
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_1
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.1 (libva 2.1.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Broxton - 2.1.0
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointEncSliceLP
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh : VAEntrypointVLD
VAProfileH264MultiviewHigh : VAEntrypointEncSlice
VAProfileH264StereoHigh : VAEntrypointVLD
VAProfileH264StereoHigh : VAEntrypointEncSlice
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileVP8Version0_3 : VAEntrypointVLD
VAProfileVP8Version0_3 : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileVP9Profile0 : VAEntrypointVLD