LG TV showing spinner on every video and wouldn't play...

[tunaz 0]

Before the LG app update, I started seeing a spinner on any video on my LG TV, and the video wouldn't play at all. There are no issues on other devices or in the web browser. I then updated the app on the LG TV to version 1.0.50 (thinking this might fix the problem), but the same issue persisted. I also tried updating my Emby server to version 4.10.0.3 Beta. I started experiencing the same problem again.

 

I reviewed threads opened regarding similar issues, and some mentioned that the problems were resolved and updates were released a long time ago. However, my issue persists. Could you guide me on this matter?

[Luke 42083]

 

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

 

[tunaz 0]

Infinite Loading Spinner on LG WebOS (43UF7787-ZA) - No Playback Started

Description

I have been using Emby Server for a long time without any issues across all my devices. However, recently, without any changes to my setup, I encountered a playback issue specifically on my LG Smart TV (Model: 43UF7787-ZA, WebOS). When I try to play any video media, a loading spinner appears on the screen and stays there indefinitely. The media never starts playing.

Steps to Reproduce

• Open the Emby app on LG Smart TV.

• Navigate to any video library.

• Select a movie or TV show.

• Click the "Play" button.

• An infinite loading spinner appears, and playback does not initiate.

What I have tried so far:

• Searched community forums and tested various configuration changes (none worked). (Logout, Delete LG App, Turn off and then install again, change file type etc.)

• Updated the Emby LG app to version 1.0.50.

• Updated the Emby Server to version 4.10.0.3 Beta.

• Verified that playback still works perfectly on other devices (Web, Mobile, etc.).

System Information

• LG TV Model: 43UF7787-ZA

• LG App Version: 1.0.50

• Emby Server Version: 4.10.0.3 Beta

• Custom CSS: None (or disabled for testing).

By the way here is the chown result of "/var/lib/emby/transcoding-temp"
drwxrwxrwx 2 emby emby 4096 Feb 22 18:27 /var/lib/emby/transcoding-temp

 

ffmpeg-transcode-d5efbebf-faa6-4c5f-8992-4afcfcb39ac0_1.txt embyserver.txt

[tunaz 0]

Update: Issue Resolved

I have managed to resolve the playback issue, although I performed two changes simultaneously and I am not entirely sure which one was the definitive fix. Here are the adjustments I made:

• Transcoding Path: I explicitly defined the Transcoding temporary path as /tmp. Previously, this field was left empty, which defaults to the server's internal data directory. I verified that /tmp has the correct permissions (drwxrwxrwt) for the Emby service to write.
• Bitrate/Quality Settings: I changed the playback quality on the LG client from a fixed 720p - 1 Mbps to Auto. My previous logs showed that the server was attempting to transcode because the media bitrate exceeded the 1 Mbps limit.

The "Invalid Argument" error in FFmpeg has disappeared, and playback now initiates instantly. It is possible that either the default transcoding directory had an underlying pathing issue on Ubuntu 24.04, or the specific 1 Mbps bitrate constraint was causing a conflict with the FFmpeg output parameters for this WebOS version.

Edited 1 hour ago by tunaz