2024-08-04, 08:36 AM
(This post was last modified: 2024-08-04, 11:52 AM by Efficient_Good_5784. Edited 2 times in total.)
The Jellyfin WebOS app is basically a wrapper for the Web UI (what you use when you access Jellyfin from a web browser).
It could be that LG's implementation just doesn't handle it well as compared to Samsung's own voice reader/navigator.
I haven't used the Tizen app, but from what I remember reading before, the Jellyfin Tizen app is not a Web UI re-wrap, but an actual app built for Tizen which might be why it works better in this use case for the voice reader.
Edit: The Tizen app is pretty much the same with it being a wrapper for the Web UI.
The performance of the screen voice reader depends on the tv manufacturer's native implementation of the feature and Jellyfin has little control over it.
It could be that LG's implementation just doesn't handle it well as compared to Samsung's own voice reader/navigator.
I haven't used the Tizen app, but from what I remember reading before, the Jellyfin Tizen app is not a Web UI re-wrap, but an actual app built for Tizen which might be why it works better in this use case for the voice reader.
Edit: The Tizen app is pretty much the same with it being a wrapper for the Web UI.
The performance of the screen voice reader depends on the tv manufacturer's native implementation of the feature and Jellyfin has little control over it.