Gaps in the Guide

[mvallevand]

How is the speed in Emby LiveTV assuming there are HD h264 channels in that satellite you can test

Martin

[sub]

The DVB-S system here is MPEG2 video, MPEG1 Layer II audio.

The DVB-T system is H.264 video, HE-AAC audio.

[mvallevand]

Ok then he is stuck with transcoding https://forums.nextpvr.com/showthread.ph...post536203 in Emby

Martin

[sub]

Ok then he is stuck with transcoding https://forums.nextpvr.com/showthread.ph...post536203 in Emby

Martin

Yeah, he'll need to do transcoding for playback in the web app. I know there is a couple places I could improve the startup time in the web app though, so I might be able to trim off a couple of seconds.

Other client types wont need to do that, like VLC, kodi, nextpvr.exe, Emby theatre etc.

[sub]

BTW, I have discovered some DVB-T H.264 broadcasts are also no great for web playback, so end up requiring transcoding anyway. ie depends on encoding profile and whether they've used advanced options (MBAFF/MPAFF etc). H.264 stuff that was originally encoded for the web, like IPTV source, is always safe.

[arrbee99]

Great - that's sounding like a pretty damn good improvement.

With the web app, it's likely to get down around the 6 second range.

For nextpvr.exe, I get about more like about 2 seconds to start live tv. If you want to post the logs after trying to start live tv in NextPVR, I'll check where your delays are.

(FYI, I am working on some new v5 specific playback components, which will give better times in future, but those changes are still a little way off)

Thanks for the info. Impressive you say it will be getting even faster...

Anyway, here, I hope, is a log.

Played tvnz1 in nextpvr.exe - 17 sec to start but first one played, so normal. Played tvnz1 again - 5 sec, tvnz2 - 5 sec, tv3 - 7 sec, bit slower but changing frequencies I presume.

I'll ask about times in Emby, hopefully they'll have a look.

[sub]

How is the speed in Emby LiveTV assuming there are HD h264 channels in that satellite you can test

Martin

FYI, after this message, I thought I'd experiment with our local H.264 channels, to see how quickly they'd start in the web app with only transcoding the audio (keeping the original H.264 stream). Some of the channels didn't work (probably because of the broadcasters encoding options), but those that did work were starting somewhere in the 3-5 second range...pretty nice.

[arrbee99]

Posted by me on Emby sub -

'So far in Chrome (hence transcoding for me) start up times have improved to about 9 seconds and in Theater they've dropped to an awesome 2 seconds Never been that fast since I started using Emby / NextPVR.



Will have to have a go on Shield / Fire TV soon.'

[mvallevand]

FYI, after this message, I thought I'd experiment with our local H.264 channels, to see how quickly they'd start in the web app with only transcoding the audio (keeping the original H.264 stream). Some of the channels didn't work (probably because of the broadcasters encoding options), but those that did work were starting somewhere in the 3-5 second range...pretty nice.

This is why I like the option of ffprobe details in cached_info for web browsing. The theory is it might not always work, but the video stream is typically pretty reliable.

Martin

[arrbee99]

Back on the OT, did this 10 minutes ago, reckon I should increase the guide scan time to 3 minutes ?

[ATTACHMENT NOT FOUND]