johnsonx42 Wrote:by the way, I've often wondered about skipping between i-frames... does it really do any good to do that? would it be hard to code your reader so it jumps the desired number of seconds and then to the nearest i-frame? I think most decoders would behave better that way. Skipping would also 'feel' smoother as there'd be no video freeze waiting for an i-frame to come up. It might even make auto-comskip points more accurate as presumably there will be an i-frame as a commercial break begins and another as the show resumes.
I dont disagree with you, but the reader doesnt currently parse this type of info from MPEG2 or H.264 streams, so its not straight forward to implement. Maybe in a future release though.
Since I've spent a lot of time posting about what's not working right in NPVR, I'll go ahead and post one more time about what is working very well. We've watched several more recordings this evening with the latest timing/skipping patches, and it's been excellent. Every bit as good as GB-PVR with DVR-MS files.
Sub, you've nailed it. Thanks!
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV
I've just installed NPVR with this patch but have not gotten around to record something yet (installed NPVR last night). Is there a way to get this extra info on previous recordings, I mean like running some commandline utility to create this extra info or MUST it be created at recording time?
I have quite a few recordings to watch (recorded as .ts files with GB-PVR) and wonder if they also will suffer from this skipping issue, perhaps it is only related to recordings created with NPVR?