[ptoyonj]

Oops. You told me. Pardon my idiocy. I didn't read correctly. 

Trying!

[ptoyonj]

https://kodi.wiki/view/Supported_hardware#Linux

Set the mentioned environment variable to EGL and use vaapi. Vdpau has no support for 10 bit interop and will end up green.

Ok, so I admit I'm fairly new to LINUX and so I'm not sure whether I did this correctly. 

- I pulled up an xterm window from within my batocera user session ( which showed I was in as root, apparently )
- I entered the string [export KODI_GL_INTERFACE=EGL]
- I ran printenv to confirm it was there after adding it
- I then quit the xterm window and relaunched KODI

However, KODI's player settings still show VPDAU and H/W accel disabled as I previously left it. 
Not sure if I just re-enable H/W accel at this point but seeing it still displayed as VPDAU has me wondering.

[izprtxqkft]

- I pulled up an xterm window from within my batocera user session ( which showed I was in as root, apparently )
- I entered the string [export KODI_GL_INTERFACE=EGL]
- I ran printenv to confirm it was there after adding it
- I then quit the xterm window

export is per session, the second you closed xterm that variable was deleted

[ptoyonj]

I've been trying to figure out where to properly set this KODI environment variable and I am pretty lost. 

Can you or someone please point me in the right direction?

[ptoyonj]

- I pulled up an xterm window from within my batocera user session ( which showed I was in as root, apparently )
- I entered the string [export KODI_GL_INTERFACE=EGL]
- I ran printenv to confirm it was there after adding it
- I then quit the xterm window

export is per session, the second you closed xterm that variable was deleted

.Ok, so is there typically a kodi.conf file of some sort, or is it more appropriate to set the environment variable globally? 

I guess this build is based on RecalBox, but I don't know if that's helpful.  I have read that they treat the build kind of like a firmware, and it seems as though all important system level settings get " set back to batocera's release settings " on boot or are write-locked in the first place. I might be wrong, though. I'm fairly new to *nix

I read the links below and copied the kodi.desktop config file to my home path, but I don't understand what I'm doing after that. 
https://www.reddit.com/r/linuxquestions/...?rdt=42216

Does the install command in this example write the edited copy back so that it overwrites the kodi.desktop file i initially copied?

[black_eagle]

Open a terminal an type in "which kodi".  The response will be something like /usr/bin/kodi.  This is the script that starts the executable (or it should be).

Change into the directory with "cd /usr/bin" or whatever path you were given, and then do sudo nano kodi  This will open the script for editing.  Cursor down until you are under one of the two export lines in that script and then add your export underneath. Save and quit the editor by pressing <ctrl> + <o> followed by <enter> and then <ctrl> + <x>.

You have now added your export to Kodi's start-up script, so it will be in effect the next time you start kodi.

[ptoyonj]

Thanks!
I did find the startup script file as you described and i edited it, and saved
( though the shell wouldn't let me sudo, so I just vim edited the file and :x to save ).
I then opened the file back up to confirm my edit was still there, and it is / was. 

Unfortunately, it doesn't appear that the setting affected KODI.  I quit / relaunched KODI a couple of times, but
the player settings in the GUI still only shows VPDAU for the HW Accel version, and enabling it makes the black video stream output issue come back. 


Here's a clip from the edited file:
===========================
CRASHLOG_DIR=${CRASHLOG_DIR:-$HOME}
KODI_DATA=${KODI_DATA:-"${HOME}/.${bin_name}"} # mapped to special://home/

# Workaround for high CPU load with nvidia GFX
export __GL_YIELD=USLEEP

# Fix wasting RAM due to fragmentation
export MALLOC_MMAP_THRESHOLD_=131072
# Test for forcing VAAPI HW Accel
export KODI_GL_INTERFACE=EGL
# Check for some options used by this script
while [ "$#" -gt "0" ]



Not sure what to make of that outcome, but hopefully one of you will :-)

[ptoyonj]

Open a terminal an type in "which kodi".  The response will be something like /usr/bin/kodi.  This is the script that starts the executable (or it should be).

Change into the directory with "cd /usr/bin" or whatever path you were given, and then do sudo nano kodi  This will open the script for editing.  Cursor down until you are under one of the two export lines in that script and then add your export underneath. Save and quit the editor by pressing <ctrl> + <o> followed by <enter> and then <ctrl> + <x>.

You have now added your export to Kodi's start-up script, so it will be in effect the next time you start kodi.

I found the file and gave it a try, but it appears that upon next launch Kodi was unaffected by the change and VPDAU was still the only option available in the GUI settings. 

Is there a simple can't miss " test variable " I might try to set to make sure the startup-script file is being heeded by KODI upon launch? 

Sorry if I don't know what I'm talking about. Grasping at straws a bit

[ptoyonj]