Jump when Transcoding

[jhb50]

Should I open a ticket? I suspect that it is related to #435 and the refusal of my TV to play the transcoded files unless I specify maxVBitrate, although when I specify maxVBitrate the duration is still not correct, but it does vary with the maxVBitrate value I use.

I'll be happy to test whatever you want.

[zip]

yep, go ahead

I'm experimenting with Samsung BD player D5300. I have created a separate transcoding profile extending from profile 1, so there is no any Samsung specific elements, besides bare minimum.
I have removed <ResourceTransportProtocolHandler> pair from the profile in order to avoid MediaInfo.sec insertion.
It seems to me that Samsung is sending TimeSeekRange.dlna.org npt=0- in decimal format, but expecting reply in hh:mm:ss format. This combination is nor recommended, but acceptable.
I also experimented with some other DLNA clients and it seems to me that Serviio is always returning npt in decimal format regardless of the format in the request.

[zip]

I also experimented with some other DLNA clients and it seems to me that Serviio is always returning npt in decimal format regardless of the format in the request.

That should not matter. Anyway I think it's the duration causing FFWD not being available. I played with it over the weekend and it looks like they are ignoring any duration (be it standard UPnP or Samsung's custom) element value and instead base it on the Content-Length of the response. For transcoded files Serviio uses some large constant number as it does not know what the target length is, so the duration is always the same (and wrong). No idea why they changed this from the B series where it works as expected.