SOLVED: New videos not able to be played on TV, ok via laptop

[acoustics]

Having fixed the issue of Jellyfin refusing connection, all was good for a few days. I managed to upload files to my NAS and watched them on my TV. However, new videos I uploaded could not be played back on my TV, though I can access them through my laptop. This shows that there is nothing wrong with the video files. No settings have been changed, yet newly uploaded files cannot be viewed. I have checked for updates for Jellyfin, ffmpeg via the Asustor app store. Everything is up-to-date. Any suggestions on how to fix this sudden issue?
Thanks!

[TheDreadPirate]

Are the permissions set correctly? Depending on who created the videos, you may need to give Jellyfin permission to read the files.

[acoustics]

Yes, the permissions are fine. What is puzzling is that some videos are ok, and others are not. No settings were changed, and I logged in as the admin, RW permission. When I click on Jellyfin on my TV, I can see the title, thumbnail. When I go into the file, I can see the chapters. But when I click on it, I get a message saying the player has encountered error and will re-try. Works ok on laptop.

[TheDreadPirate]

Is it trying to transcode when played on the TV and direct played on the laptop? Can you share the full Jellyfin logs with use via sourcebin or pastebin?

[acoustics]

Transcoding has been turned off. Logs available here: https://pastebin.com/NHR2vLJ8
Thanks for your help.

[TheDreadPirate]

It looks like all you did was set hardware acceleration to none, because this is a CPU transcode log. Transcoding very slowly.

Turning off transcoding doesn't mean that all clients will auto-magically direct play the video. Transcoding happens when it needs to happen and it happens for a reason.

What are your specs? Maybe we can get transcoding setup.

[acoustics]

Turns out that it was not a transcoding issue. Using Jellyfin-AndroidTV 0.16.7. Issue was resolved when I changed the media player fromExoPlayer to LibVLC.

[TheDreadPirate]

This likely didn't FIX the problem as libVLC will attempt to play more codecs, including via software decoding vs exoplayer which will only hardware decode.

But if it works, whatever.