Log error: there is no inputstream to return

[oldjohn]

Hi UMS team,

I just made the plunge from PMS to UMS - my intention was to ask for support regarding the problem below, but it turns out this may be a bug report instead (see my end note)

Description of problem:
- MKVs starts playing just fine (takes about 5 extra seconds to load though), however the timecode shows as: 18.18 (on any MKV)
- When I try to skip to a specific time, playback stops and the following two errors are shown (trace logs are attached):
"There is no inputstream to return for xxxxx.mkv"
"Stopped playing xxxxx.mkv"

Software:
- UMS 2.6.3
- Java 1.7.0_21_b11
- WDTV renderer

Tested with:
- different MKVs (have not tested any other containers)
- all have embeded SRT subtitles (I never use external anymore)

Solution found:
I started tinkering with the settings, and found that when turning ON the option "disable subtitles", all MKVs loads as fast as they should (from my experience with PMS), embeded subtitles works, timecode shown is correct, and I can skip to any time without playback stopping.

Hope this helps other people having this error

[SubJunk]

Thansk for the report, oldjohn.
Can you also attach the debug info for when you have disabled subtitles so I can compare them?

By the way, if you do a Clean Install (which resets your program settings) you will probably find you don't have to disable subtitles; by default, if the audio is English we won't use English subtitles

[oldjohn]

Hi,

Attached is the debug info with disabled subtitles on (when it works).
I use subtitles all the time, also when the dialogue is English - my hearing isn't what it used to be
Does that mean I could use a blank field for "audio/subtitle language priority"?

Should it be necessary to select a clean install the first time, when I had never installed UMS before?

[SubJunk]

Thanks, I'll compare them.
If you want to always load subtitles then you did set the correct priority

[SubJunk]

OK yeah in the version that worked for you, it just sent the files to your renderer without doing anything to them, and in the version that did not work for you, it attempted to transcode them.
I'm working on fixes for both of the issues that caused this to happen.

[oldjohn]

Great! Thanks for the help

[Taxman]

You might wanna check my recent detailed thread. My issue possibly seems to be somehow related...
Thanks in advance!