Only on TV: 'player error encountered'

[banchev]

Hi guys,
I've spent probably about 40 hours or more trying to set Jellyfin on Proxmox LXC with NFS from Xpenology VM. Well, I guess I've managed to do it.
Now I am facing another problem. Some of the videos I have, are not playing on my TV. I get ' player error encountered'. I am not sure also, if I have enabled hardware transcoding. I did so many things regadring the hardware acceleration but I am not sure if it works.
I suppose that the problematic videos are either not transcoded at all, or transcoded on unsupported format.
Could you please help me end this saga. Thanks!

[tmsrxzar]

are not playing on your tv

so what is your tv? what os? what client?

f.e. i am sure it would not work on an old magnavox console TV from the 70s


some logs might be nice, mediainfo perhaps

[TheDreadPirate]

Can you share your ffmpeg logs with us? And server specs?

[banchev]

Thanks for your replies guys. Let me elaborate.

My TV is TCL 43C721, it's an 4k android os TV. I run the jellyfin app from the android tv play store.

Let's take for example the two tv shows I currenly have.
1) Lost (encounters error) - BluRay.Remux.AVC.DTS-HD.MA.5.1-STM.mkv
2) War of the Worlds (runs fine) - DSNP.WEB-DL.DDP5.1.H.264 playWEB.mkv
They both are 1080p.

For a dirrenet movie, chaning the video player within the TV Jellyfin app to that VLC (experimental) one, solved my issue, but not for my Lost TV Series.
Another interesting fact is that, I have downloaded on my TV, the VLC player app and connected it to my NAS so I can temporary watch the Lost series. The fact is that it runs without any problem trough the VLC native tv app.

I run the Jellyfin on Proxmox LXC. The container itself has the following parameters (2 gigs of RAM, 16 gigs of OS storage and 2 CPU - https://prnt.sc/hOKn4srYNZMW).
Also, I have NFS that is comming from my Xpenology (hosted on Proxmox VM). There my videos are placed.
My processor is Intel N100. I suppose I have activated/allowed the quicksinc hardware acceleration trough the container via the console, where I've written several commands and changed some files' info to allow ffmpeg transcode and allow the container to use my processor video driver (it was i915 or soemthing like that).
Also here is the setting within the Jellyfin - https://prnt.sc/XXc67GKwko4q.

Here is the logs I get when I play the problematic Lost serie:
- This one is for the 'Direct stream' (I suppose that tries to stream the video without transcoding): https://pastebin.com/e5i9AtUK
- This one is for the 'Transcode': https://pastebin.com/X664KMYD
PS: They are like 6-7 of error logs for one action (playing the particular lost episode) and at the end the TV's Jellyfin says 'too many errors' and aborts initiating video playing.

[TheDreadPirate]

It looks like the iGPU was not passed into the container.

Code:

No VA display found for any default device.

Make sure that all the drivers are installed on the host and that you pass the iGPU into the container. /dev/dri/renderD128.

[banchev]

Well, it looks like in terms of hardware it is all OK with my LXC based on this output: https://prnt.sc/G9TkH5xzJxqE

This error related to the XDG_RUNTIME_DIR and X server when running vainfo in my LXC container shouldn't be the case since Jellyfin primarily uses FFMPEG for transcoding.

But in fact, I suppose that is the source of my issue since I get this log now: https://pastebin.com/Ch41Z4P7

Code:

[AVHWDeviceContext @ 0x55afb461ef00] No VA display found for any default device.
Device creation failed: -22.
Failed to set value 'vaapi=va:,kernel_driver=i915,driver=iHD' for option 'init_hw_device': Invalid argument
Error parsing global options: Invalid argument

And this error suggests that the VA-API device is not being recognized or created. I shall try installing it and add to the LXC. 

But before that, do you have any other suggestions?

[TheDreadPirate]

https://jellyfin.org/docs/general/admini...-container

[banchev]

I've red that. And I suppose I did everything. But nothing seems to be working. I've followd this guy here too: https://www.youtube.com/watch?v=tWumbDlbzLY but his solutions didn't work as well.

I'll give it up for now since I am loosing sleep over it and can't make it work. So frustrating. A step forward and 10 steps backward. Shouldn't be so damn confusing.

[TheDreadPirate]

Oh, wait. I keep forgetting about this. What kernel is ProxMox using?

Code:

uname -r

Alderlake needs kernel 6.2 and newer.

[banchev]

Hi,

it's 6.2.16-15-pve