Universal Media Server | Forum

Please post the logs following the guidelines on the top of the screen.

When transcoding on the fly, UMS doesn't have the information about total length of the end file. Hence forward or seeking will not work. That's a known limitation.

That's a over-simplification @atamariya. The fact is that there are two "modes" in use, byte-based and time-based. When transcoding, byte-based seeking doesn't work and the length in bytes is unknown. However, the time-based counterparts work and are known.

What "seek mode" to use is set in the renderer configuration, so it could very well be that this renderer actually supports time-based seek. It wouldn't surprise me if the default renderer is limited to byte-based seek only.

@JericoBG It's not that simple. Your renderer needs a configuration file/profile, and somebody has to make it. Personally I don't even try to do that without actually having the renderer in question, since it can be an almost endless trial and error process, depending on how good the documentation for the device is.

You have these options as I see it:
1 - Try to "force" other standard renderer configurations and see if you're lucky and find one that works reasonably well.
2 - Search and read this forum and study the default configuration where most options are documented, and create one yourself: https://github.com/UniversalMediaServer ... derer.conf
3 - You can wait for somebody to "make it for you" either by guessing, having you test, feedback, correct -> test, feedback etc or because they have a Tesla TV themselves.

If I were you, I'd try 1) first, and then use 2) as necessary to refine the best one you found from 1), but it's completely up to you what strategy to pursue.