Page 2 of 5
Re: Trying to find a proper workaround for seeking in a transcoded stream
Posted: Sun Jun 28, 2020 8:39 pm
by mik_s
I don't think most Samsungs use seek by time as most of the comments about unable to FF have been on Samsung TVs.
Did a quick test on my F series using exclusive but made no difference. Although it did show a total length, it was not correct. and FF RWD are greyed out
- DSC_0129-small.JPG (26.57 KiB) Viewed 8861 times
Re: Trying to find a proper workaround for seeking in a transcoded stream
Posted: Sun Jun 28, 2020 8:52 pm
by SubJunk
I meant most of our Samsung TV renderer configs use that. Some use exclusive though. Which config is your TV using?
Re: Trying to find a proper workaround for seeking in a transcoded stream
Posted: Sun Jun 28, 2020 10:57 pm
by mik_s
It was one I made a while back, think it was based on the not-CD one. I don't use my TV for streaming so never bothered to get it 100% right, but it works better than the default.
Re: Trying to find a proper workaround for seeking in a transcoded stream
Posted: Mon Jun 29, 2020 7:03 am
by SubJunk
Cool, we should get it working then put it on GitHub so other users can benefit.
Can you try setting some different options for TranscodedVideoFileSize?
TranscodedVideoFileSize=-1
and
TranscodedVideoFileSize=1000000
PS3 and LG TVs like the first one, since it tells it that we don't have a size and then it works it out itself, and the second one is a hack to enable ff by telling the renderer the file is huge. The duration will appear very long but you get better functionality.
There may be interaction between that setting and the SeekByTime one too
Re: Trying to find a proper workaround for seeking in a transcoded stream
Posted: Mon Jun 29, 2020 7:22 am
by mik_s
No luck
tried both with SeekByTime = true and SeekByTime = exclusive but had same results.
Re: Trying to find a proper workaround for seeking in a transcoded stream
Posted: Mon Jun 29, 2020 8:52 am
by SubJunk
Hmm that's interesting, it should have had some effect on it. Can you attach logs when you used TranscodedVideoFileSize=1000000 so I can check if it sent that value to the TV properly?
Re: Trying to find a proper workaround for seeking in a transcoded stream
Posted: Mon Jun 29, 2020 11:49 am
by mik_s
No probs
Re: Trying to find a proper workaround for seeking in a transcoded stream
Posted: Mon Jun 29, 2020 1:04 pm
by SubJunk
Ok, I can see it is correctly setting that value in the logs, can you try it with SeekByTime = false as well? That way we are telling the renderer to use seek by byte and telling it a lie about how many bytes there are
Re: Trying to find a proper workaround for seeking in a transcoded stream
Posted: Mon Jun 29, 2020 2:53 pm
by mik_s
Done
Re: Trying to find a proper workaround for seeking in a transcoded stream
Posted: Mon Jun 29, 2020 8:04 pm
by SubJunk
Did it do the same thing as before?
Can you also split the line:
Supported = f:mpegps|mpegts v:h264|mjpeg|mp4|mpeg1|mpeg2|wmv a:aac-lc|he-aac|ac3|dts|lpcm|mp3|wma m:video/mpeg
Into two lines:
Supported = f:mpegps v:h264|mjpeg|mp4|mpeg1|mpeg2|wmv a:aac-lc|he-aac|ac3|dts|lpcm|mp3|wma m:video/mpeg
Supported = f:mpegts v:h264|mjpeg|mp4|mpeg1|mpeg2|wmv a:aac-lc|he-aac|ac3|dts|lpcm|mp3|wma m:video/vnd.dlna.mpeg-tts
That might not help with this problem but it's more correct