External Player (Vimu) resume position issue on Android TV

[franco72 2]

Hi team,

I’m experiencing a sync issue when using Vimu Media Player as an external player in the Emby app for Android TV (Ugoos AM6b+ device).

The issue:

• When I start "Movie A" and stop it halfway, the position is saved correctly in Emby.

• When I then start "Movie B", Vimu prompts me to resume from the timestamp of "Movie A".

• If I disable "Resume from last position" in Vimu settings, every movie starts from 00:00, even if Emby has a saved resume point.

It seems Emby is not passing the resume_at or start_index parameters in a way that Vimu can interpret, or it's reusing the Intent data from the previous session.

I’ve contacted the Vimu developer, and he suggested that Emby might not be using the correct API constants for Vimu. He provided the API documentation here: https://vimu.tv/player-api/

Could you please check if the Emby Android app correctly passes the position or start_time extra when calling Vimu as an external player?

Thanks!

[ebr 16363]

Hi.  We do not have this integration with anything other than MPV.

Why do you feel you need to use an external player?

[franco72 2]

48 minutes ago, ebr said:

Why do you feel you need to use an external player?

Thank you for the reply. I understand you currently only have this integration with MPV, but for high-end home theater users, an external player like Vimu is a necessity for two critical reasons that the internal player currently cannot handle:

1. Dolby Vision Profile 7 (FEL) Support:

Vimu is one of the few players that correctly handles Profile 7 to Profile 8 conversion on the fly. Without this, my projector defaults to HDR10 when using the internal Emby player, losing the benefits of Dolby Vision.

2. Buffering and Cloud Streaming (Real-Debrid):

I frequently stream high-bitrate remuxes via Real-Debrid. Although I have a 200 Mbps connection, occasional ISP speed fluctuations are inevitable. In Vimu, I can set a 1 GB buffer, which completely eliminates stuttering by creating a massive "safety net."

The internal Emby player, with its much smaller buffer, constantly hits frame freezes during minor speed drops, and sometimes it freezes indefinitely. For files with a 100 Mbps bitrate, a massive buffer is the only way to ensure a seamless experience when streaming over the network.

[ebr 16363]

What device are you running on that has the RAM for a 1GB video buffer?

[franco72 2]

2 hours ago, ebr said:

What device are you running on that has the RAM for a 1GB video buffer?

I have two Android devices that handle a 1GB buffer perfectly.

The first is the Ugoos AM6b+ connected to my TV. The second is the Vidda C3 Ultra projector (MediaTek MT9681 processor, 8GB RAM + 128GB storage, 4K Dolby Vision), where both Emby (Lifetime licenses) and Vimu (Lifetime licenses) are installed directly on the projector's OS.

With 4GB of RAM on the Ugoos and 8GB on the Vidda, there is more than enough memory to allocate a large buffer for high-bitrate streaming. This is why I rely on Vimu — it allows me to actually utilize this hardware to ensure smooth playback of 100Mbps+ remuxes, something the internal player cannot do.

Edited 1 hour ago by franco72