markyp 38 Posted November 30, 2017 Posted November 30, 2017 I'm using the latest version of Next PVR to record TV, and am using the latest NextPVR plugin with emby Server 3.2.40.5 and ET 2.9.5 for playback. I don't know what has happened recently but for the last couple of weeks my recordings take a long time to start, like over 1 minute! I can reproduce this on two different machines running ET... I've attached the server and transcode logs... server-63647647229.txt ffmpeg-transcode-cd429830-f7bb-462a-af3b-50ba2d20df70.txt
Luke 42078 Posted November 30, 2017 Posted November 30, 2017 Instead of using nextpvr for recordings through emby, just instead add your recordings folder as an emby library. That will make things much simpler.
Spaceboy 2573 Posted November 30, 2017 Posted November 30, 2017 It may not. From my experience with dvblink their naming convention for recorded tv was not compatible with Emby direct so the plugin was needed to provide recording metadata
Luke 42078 Posted November 30, 2017 Posted November 30, 2017 It may not. From my experience with dvblink their naming convention for recorded tv was not compatible with Emby direct so the plugin was needed to provide recording metadata I'm sure we can look at improving that if you can offer discussion of examples. thanks.
markyp 38 Posted November 30, 2017 Author Posted November 30, 2017 I’ve already got that set up... what had changed though, because that used to work ok...
Luke 42078 Posted November 30, 2017 Posted November 30, 2017 The transcoding log looks fine to me but for comparison's sake you could try disabling nvenc.
Luke 42078 Posted November 30, 2017 Posted November 30, 2017 Or probably the issue is that it's transcoding at all. Compare your server url and dvb url. http://192.168.1.32:8096 http://family:8866 The app won't attempt to direct play to that url because it has no way of knowing that it can reach http://family:8866 Instead, try re-configuring your dvb plugin to use the ip address.
Luke 42078 Posted November 30, 2017 Posted November 30, 2017 Actually, if you want to just leave your setup as-is, i'm going to improve the in-network detection and then it should direct play to that url. thanks.
markyp 38 Posted November 30, 2017 Author Posted November 30, 2017 I never had problems with it transcoding before, would start after a few seconds regardless, but currently it takes an age.
Luke 42078 Posted November 30, 2017 Posted November 30, 2017 Try it again in a day or so. I don't think it will transcode at all anymore. thanks.
markyp 38 Posted December 3, 2017 Author Posted December 3, 2017 It’s certainly a lot better, but now I’m getting dropped frames half way through a watching live tv... Dropped frames starts at 0 and stays there for a while, then will suddenly start clocking up... Do you need logs?
markyp 38 Posted December 3, 2017 Author Posted December 3, 2017 I’ve just checked this and deinterlacing was on... switched to cuda and hardware deinterlacing and no dropped frames... It does sound like something has changed in the last couple of weeks...
Luke 42078 Posted December 3, 2017 Posted December 3, 2017 Nothing has changed. You can also try my advice in post #2.
markyp 38 Posted December 3, 2017 Author Posted December 3, 2017 Nothing has changed. You can also try my advice in post #2. I’d already done that... but recordings through nextpvr have never been a problem until recently.
Luke 42078 Posted December 3, 2017 Posted December 3, 2017 I would just continue using them as a regular library. Adding the next pvr layer in between just creates additional complication. Thanks.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now